Here's another little bit of fun:
Windows accounts with just "user" permissions cannot issue shutdown -a.
I am working on a batch file using cpau to run with admin rights so they can stop the shutdown, since they have to wait for the popup window before they can issue the command. I'd rather not touch ~700 machines. I'm assuming that once McAfee releases the fixed DAT, ePO can then push it out to the affected computers to correct this isue.Message was edited by: CrazyFingers on 4/21/10 11:28:19 AM CDT
Getting all the machines back in a working state that have been affected by the .dat without actually touching them is the issue for us now. Epic Fail on McAfee's part on this one. What about all those hospitals that are using McAfee's products..."oops" doesn't cut it.
Anyone have any suggestions on how to do that on a domain of 2000+ computers? 😕
It is deleting the file.
I have now tested 5 Windows XP SP3 machines and the SVCHost.exe is not present in C:\Windows\System32.
Due to this Services.msc does not work either and neither does half od the explorer.exe (Start Menu etc...).
I have tried to copy back in the SVCHost via different methods but McAfee Quarantine's / Deletes it straight away.
Currently working on Disabling McAfee OAS through Safe Mode.