Ok so XP EOL is upon us in 3 days...
We will be getting XP patches from Microsoft for 1 year (paid subscription) and have figured out our best approach at deploying these patches via SWD.
This is utilizing dynamic filters, patch files into catalog and policies. I plan on documenting this entire thing into an article to post up here for anyone else that wishes to utilize this method but need help with one part.
So currently we popup an annoying message every 2hrs stating reboot pending. We utilize this out of the patch policy but this will no longer work for XP. I am going to package an exe with Flexera Admin Studio 2013 soon and will target machines that need a reboot for this.
There is a report that someone was kind enough to help with that has the sql code but I think it targets where patch management was utilized. Anyone know of a way to report on machines requiring a reboot?
This works for our machines in prod but for our test environment I setup 2 patches (1 ie and 1 xp os) and deployed them. Havent rebooted yet and the code doesnt say the machine needs a reboot.
https://www-secure.symantec.com/connect/forums/que...
I can create a custom inventory if there is a place in the registry that will state this info. Any ideas greatly appreciated???