PDQ Deploy

What is PDQ Deploy?

Are you worried about the lack of a critical software update? You may still need to upgrade your computers individually. It's time to rise up in the world and perform these deployments quickly, easily and most importantly with peace of mind. Without leaving your desk, PDQ Deploy can update virtually any application.

Choose from over 200 ready-to-deploy packages for Windows applications in the PDQ Package Library. These packages are created and maintained by PDQ and include all the configuration options and files needed to be deployed with peace of mind. In addition, you can even create your own silent custom packages. If it can be deployed silently, PDQ Deply can deploy it!

Licensing Requirements

1.     Free mode: Limited number of packages available in the package library. Custom packages limited to one installation step.

2.     Enterprise mode: Limited access.

3.     Enterprise Trial mode: Three (3) packages of your choice in the Package Library and unlimited custom packages during the trial period.

Supported Installation Files for Custom Packages

Microsoft Installer: Microsoft Installer files come in the MSI, MSP, and MSU varieties, each with slightly different options.

MSI : Very common installation files that are installed using msiexec.exe, which is part of all recent versions of Windows.

MSP: Patches or updates for existing applications (or the operating system). They are essentially MSI files that do not include the option of uninstalling or repairing. They can only be installed. MSP files are installed with msiexec.exe, exactly with MSI files. 

Executable: Many installations come as executable files. When using an executable file, it is critical to select the correct Silent Options, or the installation may appear to hang forever. Executable installations are often little more than a cover around an MSI file, so they accept many of the same command-line options that msiexec.exe does. 

PowerShell: PowerShell is Microsoft's new standard for script administrative tasks. PowerShell can also run dedicated in its own step type.

VBscript: VBscript is extensively used in system administration to perform routine tasks.

Batch: These are the same batch files that you probably used for a multitude of tasks. Generally, installations are not batched, but you can create your own. A good use for batch files in a package may be if you have an installation that requires environment settings before it runs. You can configure the environment in the batch and installation file. You need to select Include entire directory if you do this the batch and installation files are copied. You can also use batch files in packages to perform non-installation tasks, such as editing the registry from the target computer, creating or deleting files. Almost anything you can automate in a batch file can be "deployed" in this way. 

Regedit: Quickly add values to a target computer's registry using a .reg file exported from regedit.exe.

System Requirements

Machine Consoles

Windows 10, 8x, 7, Server 2008x - 2016x

Does not support

Windows 10 releases not supported by Microsoft

Editions of Windows Vista, XP, and Home

Microsoft .NET Framework 4.5.2 required, 4.6 recommended

4 GB RAM, 8 GB recommended

Installing on a domain controller or Microsoft Exchange Server is not recommended

Target Machines

Windows 10, 8x, 7, Server 2008x - 2016x

Does not support

Windows Vista, XP, and Home editions

NET Framework 4.5.2 required, 4.6 recommended (can be remotely installed via PDQ Inventory)

1 GB RAM, 2 GB recommended

PowerShell 3+ is recommended for PDQ Deploy

Configuration

Windows Firewall: Allow file sharing exception and incoming printer

This rule allows IPC$ and ADMIN$ shares to be available. Administrative access to these shares is mandatory.

Windows Firewall: Allow a target computer to respond to ping requests.