Comments on: Install vCenter in a Workgroup instead of joining a Domain cause warning and problem? http://www.modelcar.hk/?p=2895 My Die-Cast Collection & Interests Thu, 08 Jan 2026 15:35:11 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Tom http://www.modelcar.hk/?p=2895&cpage=1#comment-41450 Tom Wed, 27 Sep 2017 04:56:02 +0000 http://www.modelcar.hk/?p=2895#comment-41450 Anyone know how to stop/suppress this warning? "Encountered an error when checking domain trust health: error code: 1722" Anyone know how to stop/suppress this warning?

“Encountered an error when checking domain trust health: error code: 1722″

]]> By: Tom http://www.modelcar.hk/?p=2895&cpage=1#comment-41350 Tom Wed, 16 Aug 2017 07:40:59 +0000 http://www.modelcar.hk/?p=2895#comment-41350 In my case vRealize Operations Manager gives a critical alert: Ldap domain trust change monitor - Encountered an error when checking domin truste health: error code: 1722 Have no clue how to stop/suppress the error from occurring. In my case vRealize Operations Manager gives a critical alert: Ldap domain trust change monitor – Encountered an error when checking domin truste health: error code: 1722

Have no clue how to stop/suppress the error from occurring.

]]> By: admin http://www.modelcar.hk/?p=2895&cpage=1#comment-1634 admin Mon, 09 Apr 2012 15:11:46 +0000 http://www.modelcar.hk/?p=2895#comment-1634 Another scenario that requires an AD is VMware View, but again, you can setup an AD server easily with a VM, so I still prefer to run vCenter without AD for simplicity and easy management. Another scenario that requires an AD is VMware View, but again, you can setup an AD server easily with a VM, so I still prefer to run vCenter without AD for simplicity and easy management.

]]> By: Bud http://www.modelcar.hk/?p=2895&cpage=1#comment-1633 Bud Mon, 09 Apr 2012 15:05:28 +0000 http://www.modelcar.hk/?p=2895#comment-1633 I been running vCenter in a workgroup and no domain for years with no problem at all. One of the very reason why add VC to AD? is because, this give power to the administrator control to give permission / role of users to the vCenter (confinient as users can login using their domain credential). I do not need those feature since I am the sole Vmware administrator (and I do not need to delegate privileges to user). You do need to seperate AD and VC, to avoid complication, for example when you DCpromo Windows, it will disable the local admin, if you would install VC on the same VM or machine, then you would not be able to login as local admin anymore to VC(for troubleshooting for example). So this interdependent can be avoided if you separate above. I been running vCenter in a workgroup and no domain for years with no problem at all. One of the very reason why add VC to AD? is because, this give power to the administrator control to give permission / role of users to the vCenter (confinient as users can login using their domain credential). I do not need those feature since I am the sole Vmware administrator (and I do not need to delegate privileges to user).

You do need to seperate AD and VC, to avoid complication, for example when you DCpromo Windows, it will disable the local admin, if you would install VC on the same VM or machine, then you would not be able to login as local admin anymore to VC(for troubleshooting for example). So this interdependent can be avoided if you separate above.

]]> By: Harold http://www.modelcar.hk/?p=2895&cpage=1#comment-824 Harold Mon, 24 Jan 2011 05:14:37 +0000 http://www.modelcar.hk/?p=2895#comment-824 In response to you AD Question and the necessity of a physical DC, you could always create 2 virtual DCs on an ESX host before the installation of vCenter, instead of 2 physical DCs. In response to you AD Question and the necessity of a physical DC, you could always create 2 virtual DCs on an ESX host before the installation of vCenter, instead of 2 physical DCs.

]]>