

Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM). Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM).TotalSeconds) Seconds" -Verbose Write-Verbose "Setting Arguments" -Verbose Then import some Evergreen Auto Packages you wish to deploy to your MDT Image, for example:Ĭreate a PDQ nested package, so that the package the MDT PowerShell script references never changes: PDQ nested package PDQ nested package – propertiesĪdd the PowerShell Script that will call PDQ Deploy from the Master Image Task sequence to your MDT Scripts folder: \\MDT\C$\MDTProduction\Applications\PDQ Deploy Repository path Set the Repository path, I prefer it to be inside the Deployment share: I prefer to set Immediate Auto Downloads:Ģ.Unless you are manually running an install in a. It then connects and copies it to the workstation (s) using the deploy account, which in this case is the laps user. So make sure that the service account has access to the network share. Install the software and import your Enterprise license: PDQ licenseĬhoose your installation type, I prefer Local for this scenario, as I install PDQ onto the MDT server itself: Choose a installation typeĪdd a Domain Account to the PDQ Console Users, who has local Administrator privileges on the server where PDQ is installed, so the Task sequence has the privilege to execute the PowerShell remote command to launch the PDQ Deployment task: Console Users When using push, PDQ should be using the service account its running as to retrieve the data from the share. Download the latest release of PDQ Deploy:
