I was wondering if the issue described in KB68448 is still a concern when updating clients to Patch 3 or has the Patch 3 download been updated to accommodate this problem? If this is still an issue would checking Patch 3 into the repository along with the Hot Fix avoid this problem? Just wondering what would be the best approach to ensure no clients experience this issue.
Solved! Go to Solution.
Just a heads up, I recently checked in VSE 8.7p3 before I saw the hotfix (assuming that the repost of patch 3 eliminted the issue).
I had two XP laptops w/ Cisco VPN client installs fail to get to the desktop after patch 3 install. Granted, this was only 2 machines out of 500+ updated and 2 laptops w/ VPN client installs out of about 100 laptops. It was easy enough to go to a command prompt on the two machines, wack VSE and then reinstall clean.
The problem has been resolved? It's only resolved if you have an updated vscan.bof file. If you have a machine that hasn't communicated well with the epo server and somehow didn't get updated yet, then patch 3 will mess it up.
So, the issue is resolved if the client has the resolution.... How's that for a fancy answer...