Hi Guys,
Clients are set to update via HTTP and the location is accessible with all the necessary mime types, etc to ALL clients.
Some however, will simply lose the connection and I am seeking alternative ways for remediation instead of a reinstall.
Test scenario I made so far:
- Copy SAVSCFXP folder to c:\windows\temp
- use setup.exe from here to re-install the client with -updp c:\windows\temp\SAVSCFXP switch
This makes sure that even if the HTTP location is inaccessible, at least the initial install goes through - After this the client gets the certificate and logs on to the console
- It gets the policy and sets it to the HTTP location
- Update fails.
The policy is the same for thousands of machines, but I have like a 100 that fall into this update failed cycle ...
iconn.cfg is fully correct, as far as I found, registry does not contain anything about the update location.
Christian, another one for Wireshark? ;-)
Thanks
DanZi
This thread was automatically locked due to age.