Agent Install

[mabarnes536]

When I go to install the agent on a server through the Administrator Console I get this error:

The MOM Server could not find directory \\serverIP\C$\. Agent will not be installed on computer "servername".  Please verify the required share exists. 

Error Code: -2147024843 
Error Description: The network path was not found.

Before I was getting this error:

The MOM Server detected that the following services on computer "servername" are not running. These services are required for  push agent installation. To complete this operation, either start the required services on the computer or  install the MOM agent manually by using MOMAgent.msi located on the product CD. 
 
Required services : RemoteRegistry

I would get the RemoteRegistry error first. When I looked at the server for the Remote Registry service I found that it was disabled. I enabled it and started the service and that is when I get the first error. This one server I am using as an example is a Windows 2000 Server with SP3. We can not up it to the latest service pack nor can we install Windows Sever 2003 because of the software that runs on it does not support it. All of our servers that are 2003 the agent installed fine. I am just have problems with Windows 2000 with SP3 and above. I do relize that you can not install the agent on servers with Windows 2000 SP2 and below. Please Help!

 

[nedmega]

Hi there,

This may be a stupid question but since you didn't mention it I thought I would ask.

Have you double-checked to make sure that the default Admin share for the C drive is still enabled? It's been awhile since I've dealt with a W2K server but I think you can just right-click the drive and look through the Sharing properties.

 

[mbarnes536]

I thought I put that in there but oppps. Yes I did check that it and it shares as C$.

 

[monsterjta]

I understand you'd like a solution to this. However, for the time being cannot you just install the agent directly from the problematic server rather than pushing from MOM?

I have seen a similar issue a couple years ago, and the issue derived from a security policy that the company was applying to all their Windows servers. There was a registry key that needed to be modified on ALL these servers in order to push out the agent. Sorry I cannot remember what the exact key was!

I hope you find this post helpful,

Jonathan Almquist
Minneapolis, MN