Hi,
I am working with vRealize Configuration manager 5.8 in a two tier configuration, 1) Database / Reporting Service on Windows 2012 R2 and 2) vCM Web / Collector. All dependencies installed as per documentation, and I have been through the videos from VMware, but these vCM 5.7 but the installation process the same.
However I keep getting the error (see attached) and the sollution for this error is too install .NET framework 3.5 on Windows 2012 R2, however this does not seam to fix the problem.
Also, it is not quite clear what permissions are needed for 2-tier installation, the documentation recommends build accounts and domain accounts will local administrators right, I plan to use domain service accounts. Does anyone know what permission are required for these accounts.
If anyone has deployed, 2-Tier installation, can you please share your experience?
Thanks
PS: vRealize Configuration Manager should really be an Appliance.
VFK,
That error looks like a similar one I encountered in my test installation. Have you tried just closing the window and moving on with the install? I was able to do that.
Regarding the account/permissions, this is what I distilled from the docs and our own install.
I hope this helps.
VCM Administrator used for logging in during installation and possibly for administrator and maintenance of VCM. (vcm-admin)
Network Authority used for data collection from DCOM Windows machines, data collection from Active Directory, and for Active Directory and NT domain discovery. Requires local administrator permission on any Windows machine that they access, and SQL Server sysadmin rights if collecting SQL Server data. When policies permit, and for convenience, make the Network Authority account a separate, domain administrator account with permissions on Windows machines throughout a large enterprise. (vcm-network)
Service accounts can be the same account (vcm-services)
*This account needs to be able to logon as a service.
Sphere Client VCM requires admin permission on VCM db. (vcm-vcops-adpt)
IMPORTANT Never use the service accounts for logging in to the VCM Console or for any other purpose. Logging in to VCM using a service account can lead to unexpected or inconsistent behavior. Services that use the same account as a logged in user might modify the logged in user's current role or the machine group, or log the user out of the system.
Admin/User accounts added
vcm-admin | Local/system admin |
vcm-services | Local admin |
vcm-network | Domain admin |
vcm-vcops-adpt | Local admin, non-interactive user, requires admin access in VCM. |
Add service account users to local admin on hostserver
VFK,
That error looks like a similar one I encountered in my test installation. Have you tried just closing the window and moving on with the install? I was able to do that.
Regarding the account/permissions, this is what I distilled from the docs and our own install.
I hope this helps.
VCM Administrator used for logging in during installation and possibly for administrator and maintenance of VCM. (vcm-admin)
Network Authority used for data collection from DCOM Windows machines, data collection from Active Directory, and for Active Directory and NT domain discovery. Requires local administrator permission on any Windows machine that they access, and SQL Server sysadmin rights if collecting SQL Server data. When policies permit, and for convenience, make the Network Authority account a separate, domain administrator account with permissions on Windows machines throughout a large enterprise. (vcm-network)
Service accounts can be the same account (vcm-services)
*This account needs to be able to logon as a service.
Sphere Client VCM requires admin permission on VCM db. (vcm-vcops-adpt)
IMPORTANT Never use the service accounts for logging in to the VCM Console or for any other purpose. Logging in to VCM using a service account can lead to unexpected or inconsistent behavior. Services that use the same account as a logged in user might modify the logged in user's current role or the machine group, or log the user out of the system.
Admin/User accounts added
vcm-admin | Local/system admin |
vcm-services | Local admin |
vcm-network | Domain admin |
vcm-vcops-adpt | Local admin, non-interactive user, requires admin access in VCM. |
Add service account users to local admin on hostserver
Thank you, that is really helpful.
I would get the same every time, with the VMware professional service (glad it was not my money spent) we hired. He says it happens at almost all of his sites, you can ignore it.