Steve Pruitt at myITforum.com

In my earlier article, Settings for Distribute Software Updates Wizard, I said that we changed the grace period on the command line as required to change the patching deadline for various deployments rather than modifying the Date Authorized.

I have created a spreadsheet VBA script to assist with this. It works with all scanners - ITMU, Office, MBSA, and Extended MBSA. First it lists all updates in the deployment package with their individual Date/Time Authorized settings. This allows you to make certain they are consistent. After that list it creates two lines where the desired deadline can be entered and the required grace period is calculated. This goes on the SMS program command line in the g:<hours> switch.

To create a spreadsheet for your use, download file ParseXML macro.txt by right clicking on this link and choosing Save Target As. Open a blank spreadsheet and paste that into the macro code window. This text assumes that you have MSXML 4.0 installed on your computer. If not, edit the line "Set xmlDoc = CreateObject("MSXML2.DOMDocument.4.0")" accordingly. While in the code window, open menu item Tools, References and check the consistent library, such as "Microsoft XML, v4.0" and click OK. Save the spreadsheet with the desired name.

To use this:

• Run macro ParseXML in this spreadsheet
• A "File Open" window will open.
• Navigate to the folder on your SMS server where the DSUW packages are created.
• Select the folder containing the desired package, and open the PatchAuthorize.xml file. Note, only xml files will be displayed.

The spreadsheet will be populated with the package name, the list of updates with associated product name and Authorized Date/Time. The cell after the date will say Local or GMT, as appropriate. Underneath the list are cells labeled Deadline and Hours. The Deadline cell is filled with the current time. Change that to the desired deadline date and time. If you only enter a date, it is treated as midnight of that date.

Note that you can create multiple programs under the one SMS package created by DSUW, with different command lines for each. This allows you to have separate programs and advertisements for each deployment, further reducing the risk of error.

If you find any errors in this program, please let me know. At some time in the future I will update this to analyze the command lines of each program in that package and list the settings in the spreadsheet. This will complete the ability to verify all DSUW settings without rerunning the wizard and risking making accidental changes.