1 of 1 people found this helpful
- Download shavlik files referencing the links in patch global configuration / shavlik url configuration
- Put those 2 files somewhere on your network visible by appserver
- Modify the links in shavlik url configuration to point to the shavlik files locally (use NSH paths. example: //server/path/to/hf7b.cab)
warning, if you stick with this, then you'll need to modify your shavlik files on the local location every time you want to update the catalog
Thanks lazar, could you tell me where in the documentation that it mentions that a patch catalog update does a ping so I can possibly get it opened to do such.
I doubt such detail will be in the documentation.
If we do a ping, it's most likely at the code level. if ping does not return, then we assume the site down and throw some relevant error message.
That is the case. Thanks, the proposed solution would work if it was permanent but we will have to push and get it opened.
Just one more note...
If this helps creating the Catalog - good. But then after running Analysis Job, you would want to do Deployment. During Patch Remediation Job (a step prior to deployment) we generally download the missing patches, so during this 'download' action, we could also be pinging the host. I do not know if it's true, but something to keep in mind in case you have issues downloading patches.