My question is whether it is possible to deploy a PDQ package during audit mode while building an image?
I have an audit mode image that I attempt to deploy a baseline package to. I am using local account credentials and the file copy mode is push in order to not need credentials for the repository. The machine (while in audit mode) passes all remote repair steps and the package deploys successfully. The problem is that once I sysprep /generalize with my unattend.xml I get an error on Specialize pass, specifically the Shell Setup.
I have tested just deploying a single app (7-zip), not the whole baseline package from PDQ and I still get the "could not parse" error for the specialize-> Shell Setup error.
I can deploy a ninite install of just 7-zip and it succeeds in completing the sysprep process and the rest of my imaging completes.
What would be happening during the PDQ deployment that could cause this error?
I noticed that the AdminArsenal directory is left behind in the C:\Windows directory, but even if I delete it that doesn't fix the error.
Is this just not recommended practice? I get that a lot of people are moving to deploying via snapin w/ FOG after imaging. This isn't preferable for me since it would add 20-30 minutes to my imaging process and during the Summer I image close to 2500 machines. I want to explore and evaluate that option in the future, but for now it makes more sense for me to update apps in audit mode and have the imaging process go faster.
We have always done app installs via ninite before and updated them via PDQ Deploy and haven't had issues, but I would rather use the PDQ packages to perform the baseline install as I know how much work goes into making sure they are compatible between versions, and I also like the idea of auto updates being turned off, etc.
Please sign in to leave a comment.