1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Update Installation Logic

Avatar
Kurtis Reed
Updated

I'm working on creating an update system for full company deployment and patching. As it stands right now we have a few different versions of Windows 10 in action for various reasons. I have built some forced logic with nested packages to try and make the updating process more efficient but it doesn't looks like the logic is working correctly. Out of this came a few questions I would like some help with:

1. I have packages built with a cascading organization system of updates per windows version (Adobe Flash Package [flash for 1803, 1809, & 1903], Cumulative Updates [CU 1803, 1809, & 1903], etc) because I couldn't find a way to allow PDQ to intelligently target machines according to their versioning and/or skip installations based on their versioning. Is there a targeting or version matching function that I am missing or will the packages just apply as they are programmed in the package regardless of the target system version? Is this something that I just need to create a dynamic collection for in PDQ Inventory and build a version specific update package to target that collection with?

2. These collective update packages have each system version set to run with "Stop deployment on Success" but the packages continue to step down through the other versions and options even if there is a successful deployment. (IE, if 1803 update is applied, it still tries to run 1809 and 1903 updates afterwards) Each of these extra steps add about 30s-1m of extra time per step, per machine. This would add up to a considerable amount of wasted time when considering a full scale deployment that I would like to avoid. I looked around and it seems this was a similar bug in previous versions but was stated to be corrected. Has this bug come back or am I configuring this incorrectly? (Currently running 18.2.12.0 Enterprise Mode)

3. The packages I built were out of the auto-download/auto-approved packages. Do these packages hold the update packages as a reference for the most up to date package released and downloaded, or are these references only to that specific version that is currently available when the package was made?

0

Comments

0 comments