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 firstname.lastname@example.org and the vCenter server 2 uses account email@example.com.
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
Related Q&A from Stuart Burns
Both Ansible and Ansible Tower offer enterprises a wealth of resources for config management, but they aren't equals. Assess their differences in ... Continue Reading
Even though Ansible has its roots in open source software and Linux, is it possible to use the configuration management tool for Windows environments? Continue Reading
Roles are one of several functions in Ansible that simplify and streamline IT automation processes. Dig into this quick overview to learn the basics ... Continue Reading