NS Patch Management 6.2 HTTP Enabler - Version 1.0
Test this on a development box before using to updates your paths and make sure you get the desired results. Always have a good backup ready. I've never had any problems with it when the UNC and URL paths are correctly configured, but your mileage could vary.
This tool must be run on the NS server.
This tool loads all the packages for every patch inside of Patch Management and displays their current settings. This tool is designed for those that use HTTP instead of UNC paths for patch delivery. For instance you might use Cisco content engines or have another reason. It changes the Package type from UNC to URL and updates the package location based on the UNC Path and URL Path you have entered.
It usually takes about 15-30 seconds to load when first opened.
Any that are highlighted in red are misconfigured according to the UNC/URL path combination you have set. No changes are made until you click repair all. Updating the paths and reloading can take several minutes depending on the speed of your NS Server. This is designed for NS6 and has not yet been tested on NS7 but may work, I'd be interested in your feedback. You can preconfigure the UNC and URL path from the app.config file if desired.
Look for more tools and articles by Screenbert on the Symantec connect site. Any comments regarding this tool can be posted there also.
Comments
So if I already have my NS
So if I already have my NS configured to work with CE what other benfit will this provide me?
Patches aren't automatically configured
When the patches are downloaded every month they are not automatically configured to use HTTP, the default is UNC. You have to manually run a script from the Knowledgebase to switch each download to use HTTP. Sometimes older patches revert back and need to be pointed back to your HTTP address. This also gives you a health check to make sure it's working right.
Screenbert
Would you like to reply?
Login or Register to post your comment.