http://rorymccaw.spaces.live.com/blo...6E21!143.entry

I also copied the post below to speed you along. I've looked for a fix
for a long time. the formus link below doesn't work any longer but the
fix does. I copied my file from another 2k3 server we had here.

"December 15
ePO v 3.5.0 on Servers upgraded from Windows 2000 to Windows Server
2003
Do you work with ePO v 3.5.0 in an environment where you have or are
upgrading your operating system from Windows 2000 to Windows Server
2003? If you do and you use MOM 2005, you might want to create a rule
to alert you to a know issue. See
http://forums.mcafeehelp.com/viewtop...426 86a90fdd2.

The issue is that on upgraded servers the EntDrv52 service fails to
start and error events from Event ID 7000 from source Service Control
Manager are logged in the System Event log. The cause of this service
failure which logs events every 5 minutes is that the version of the
file on the upgraded server is incorrect. The service based on the
registry value ImagePath in
HKLM\System\CurrentControlSet\Services\EntDrv52 is looking for
EntDrv52.sys and the file on the upgraded server is EntDrv50.sys.

The resolution to this problem is to copy the EntDrv52.sys file from
another copy, likely one that hasn't been upgraded to the computer
logging the errors and voila, issue should be solved.

MOM 2005 can help you to identify the servers logging this error
through the creation of an Event rule that looks for Source = Service
Control Manager, Event ID = 7000, and Type = Error. You could also
configure a response that sends you a notification and create an event
or alert view based on this criteria to quickly and easily identify
affected computers."


--
PaulM
------------------------------------------------------------------------
PaulM's Profile: http://forums.techarena.in/member.php?userid=39580
View this thread: http://forums.techarena.in/showthread.php?t=91106

http://forums.techarena.in