“The time has come,” the PDQ employee said, “to talk of many things…”
Welcome back to our continuing series on the many things in PDQ Deploy that you may not know, or may have forgotten. We’ve already brought you Copy Mode, Run As Options, and Offline Statuses; today we’ll discuss the very helpful Scan After feature. Please note, this nifty and helpful feature requires PDQ Deploy’s sibling: PDQ Inventory.
Automatically initiate a scan after a deployment completes
If you haven’t used the Scan After feature then you need to really consider changing your ways. With just one setting, you can ensure PDQ Inventory’s data is updated directly after a deployment. (This requires Pro or Enterprise mode in both products)
It is generally considered a “best practice” to set the global Scan After Deployment to use the Applications scan profile, since the majority of deployments will be installing applications. Then, depending on the package being deployed, you can change the Scanning option to use a different profile or, in some cases, not to scan at all.
These use cases below assume the global setting is set to Scan After using Applications.
- Use the global setting: You deploy a Java 8 package. Neither the package or deployment properties need altering since the Applications scan profile would capture the new Java 8 installation.
- Do Not Scan: You deploy a package to reboot a target computer with no other changes. In the package properties, you would set Scanning to Do Not Scan. Not only will this prevent a scan on a rebooting computer, it will prevent an unnecessary clog of your scanning queue.
- Different Scan Profile: You deploy a package which adds a new Service to the Windows Service Manager. In this case, the package properties would be set to scan using the Standard scan profile (or other profile containing the Services scanner). This ensures the Services scanner adds the new service to PDQ Inventory.
Enabling Scan After Deployment
Just like most settings in PDQ Deploy, they can be set globally and then overridden at various steps in the process:
- Global settings
Navigate to Options > Preferences > Deployments.
- Packages can override global settings
Open the Package > Properties > Options tab.
- Deployments will use the package setting first, then default to global if no package setting is set. This is most useful if you need to change a setting right before a deployment.
Navigate to the Options tab in the Deploy Once window or the Schedule window.
Not just for deployments…
You also have the option to automatically run scans after you initiate a Remote Command on a target via PDQ Inventory (Tools > Remote Command, Options tab). When you attempt to uninstall an application from the Applications page of the Computer window this option is automatically enabled.
In the image below, you can see that I am choosing to uninstall Adobe Acrobat Reader (via right-clicking the application and choosing Uninstall).
Once the Remote Command is launched from the Uninstall option, you will see that I’ve chosen the Applications scan profile under Scan After.
Stay tuned for one more installment to become an expert in PDQ Deploy.