(imported topic written by ktm_200091)
I’ve been chasing 5-10 PCs with large amounts of corrupt patches and am seeing a common thread, when the users are remote and connected with VPN they report a large amount of corrupt patches. When they return to the network the PC reports in fine.
I am able to patch PCs while on VPN connections so there shouldn’t be a networking issue.
Any suggestions on how to deal with this?
(imported comment written by BenKus)
That is very strange… Although it is possible that it is more correlated with the “pending restart” instead of the VPN use… can you check on that?
Ben
(imported comment written by ktm_200091)
Over the holidays I saw quite a bit more of this as PCs which are on VPN connections are reporting significant amounts of corrupt patches.
What steps can I do to identify what is going on here, Numbers of relevant fixlets went up over 30% due to all the corrupt patches on VPN PCs?
(imported comment written by BenKus)
Corrupt patches will occur when older previously-patched versions of files are updated… It sounds like perhaps something has overwritten older files on these computers… Any ideas if that is likely?
One potential investigatio path is to look at which patches have become corrupted. If they share a couple specific files, then that would be a good place to start looking.
Ben
(imported comment written by ktm_200091)
Hi Ben,
I understand the concept of corrupt patches. The funny part about this is while these PCs are remote and connected via VPN they report high #s of corrupt patches. They return to the network and the corrupt patches go away. What is the difference in the detection of the relevance of the patches while they are connnected via VPN?
(imported comment written by BenKus)
Hey KTM,
There shouldn’t be any difference at all… the agent doesn’t care/know how it connects…
Can you confirm the relevance of one of the corrupt patches when it is on or off the VPN to try to spot the issue?
Ben