OA Installation error on Windows 2003 servers

[Bathina]

Dear Experts, We have around 500+ Windows Servers (WIN 2012, 2008, 2003) as managed nodes which have OM agent version 11.1 running on almost all nodes . Now there are few servers which are migrated recently have ip address change so we have to reissue the certificate from managed node to communicate with the servers.

Issue :  We are facing issue for windows 2003 servers while reinstalling the agent in the node. Eventhough it has met the prerequisite check but it was unsuccessful and also tried manual installation from the managed node but no luck.

Have attached the screenshot of the error. Kindly advice.

[Carol Park]

Changing the IP address (or even the hostname) doesn't require you to change the certificate.  And even if you decide to re-issue a certificate, there is no need to re-install the agent in order to re-issue a cert.

I can't tell much from the screenshot except that there might be a permission issue to map C$ but that should have shown up in the prereq check anyway.  Also, you mentioned that manual agent install failed - but no details on the error.

Given it concerns OMW, you might want to re-post with additional info to the System Management practitioner forum:
http://community.hpe.com/t5/Systems-Management-OpenView-OP/ct-p/sws-OMC

CP.

[Utkarshpatel]

Hello,

Not sure but win2003 works with -minprecheck option. Would not harm to try that out.

[Diego_Pereira]

If you don't use bind, you need to do  nothing.

else you just want to change the ip address use this command (Only if you are using BIND):
./ovconfchg -ns eaagt -set OPC_IP_ADDRESS X.X.X.X
./ovconfchg -ns bbc.cb -set SERVER_BIND_ADDR X.X.X.X

If you use HTTPS:

./ovconfchg -ns bbc.http -set SERVER_BIND_ADDR X.X.X.X
./ovconfchg -ns bbc.http -set CLIENT_BIND_ADDR X.X.X.X

About the error installing manually, please send the error.