Manage Learn to apply best practices and optimize your operations.

How do you fix a linked server issue with vCenter Operations Manager?

What are the alternatives when an existing linked server configuration disrupts vCenter Operations Manager?

I’m setting up vCenter Operations Manager and having issues configuring the linked servers. A service account runs the vCenter service on both vCenter servers. The vCenter server 1 uses account vcenterserver1.svc@domain.com and the vCenter server 2 uses account vcenterserver2.svc@domain.com.

Related content:

VMware takes the software-defined data center a step further with vCenter Operations Management Suite 5.8

Pacifying end users with vCenter Operations Manager for View

An inside look at the vCenter Operations Management Suite

This configuration has worked in the past, but now it breaks vCOPs. It appears the linked server setup wants to use the same account on both servers, which won't work in this environment. Is there a fix for this?

The vCenter Operations Manager (vCOPs) can connect to vCenter Server instances that are linked. These servers are required to have common logins. If you configurevCOPs to connect to multiple vCenter Server instances, you must have login privileges to all the vCenter Server instances and use the same password to log in.

I am not aware of any fix. In an ideal world, you should use one service account for this process, as it is a best practice and simplifies management and troubleshooting when required. The other great thing about assigning the service account a role is that you modify it to exclude hosts and clusters you are not too concerned about monitoring.

Dig Deeper on Using monitoring and performance tools with VMware

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.