PDQ Deploy | Creating a New Package to Deploy
Guide Created With: PDQ Deploy
Guide Created On: 29.11.2024 Version 1.0
Potential Issues: N/A
Attention: N/A
Technical Specialists: Rob England. Adam Tuffin
1 Package Properties:
1.On the PDQ Deploy Main Console window, click New Package 
on the toolbar (or click File > New Package or press Ctrl+N).
A new blank Package window opens with the Detail tab of the Package Properties selected.
2.On the Details tab, type the name, version, and description for the package. Name as example would be GRY - Impero Console
NOTE: Generally you can include 64 and 32-bit applications in the same package. For the example used in this procedure, we are creating a simple custom package for the 64-bit version of Microsoft Silverlight only.
3.Click the Options tab.
•Push: Files are copied from the PDQ Deploy Console computer to target computers (default).
•Pull: Files are copied from a network share (via accessible UNC path). (Requires Pro or Enterprise mode)
2 Install Step Properties:
When you create a new package, no steps are added automatically, however there is a page for Steps 
to be added. For details see Install Step Properties.
To configure the Install Step properties:
1.Click New Step > Install or Steps 
and select Install.
The step property tabs display:
•Details: Properties unique to the step type.
•Conditions: Criteria that must be met for the step to be processed.
•Options: Additional options for the step.
This part of the procedure is about the Install Step properties on the Details tab. To configure deployment properties, see Part 3: Conditions and Options.
2.(Optional) Type a name for the step.
To clearly identify the step, use names that include the step type (for our example, Install Step), product name, version, and other important information such as architecture (for example, 32 or 64- bit). For additional naming guidance look at how steps are named in the Package Library.
3.Click the Browse for the main install file button 
, navigate to and select your primary install file (for this example, Silverlight_x64.exe), then click Open.
If you're unable to browse for the installation files due to them being on another File Server, you can simply add the UNC path of the software to be installed. I.e. \\staffdata-serv\software$\Impero\ImperoSetup.msi
NOTE: For consoles using the Central Server running in Client or Server Mode, all files used in a package must either be stored in the Server's repository or in a location that is accessible to the background user on the Server. To identify the repository location, click on Preferences > Repository. For details, see Repository Preferences.
4.Add any required command line / parameter switches in either parameters or command line fields.
Click SAVE