We are working on sending out a message through Support Notification Service (SNS) now.
To sign up for SNS, go to: http://my.mcafee.com/content/SNS_Subscription_Center
I will also respond to this thread.
Oh dear, McAfee KB is slashdotted.
This hasn't affected my XP SP3 box, even though it had been running 5958 for two hours before I rolled back the DAT file.
That implies that I have a config which somehow "saved" my PC.
So what are the necessary conditions to cause this problem?
Anyone have a good way of fixing this without touching every PC that got the update? Currently, we are goint to each PC, running shutdown -a, and then rolling back the driver. Even when an updated version comes out, I don't think there will be enough time for the PC to get the file and apply it before it reboots.
psexec.exe from Sysinternals.com http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx ?
Set the local directory to be the Windows one, copy the file etc etc. Or create a batch file to pull it from a share on another machine.
That is assuming that a) The correct services are running on the machine to use PSEXEC, and b) that Windows File Protection doesn't stop the copy.
Also you would probably need to consider versions of the file affected. In a corprate environment this shouldn't be a biggie.
You can get a list of affected machines from EPO, and make them into a list to use with PSEXEC.Message was edited by: Mal09 on 21/04/10 16:21:10 GMT