Brown Room Lavender Accents

Despiste 9: Cambiar de usuario en los servicios de vCenter

This is perhaps one of the most classic forgetfulness typical and give more courage to suffer, particularly when the third or fourth time that happens to you. Let's see, I put in a position, one begins to make the deployment of a new platform vSphere (migration or not) with all the enthusiasm in the world, set up your server database, preparing the database, which assembles will be the VirtualCenter server, configure your DSN, installed the software (VirtualCenter, Update Manager, Guied Consolidation, etc ...), vSphere installed your client, adds his hosts and made the first test configurations and. . Voila! perfect, wonderful, one pass ... (Here are all the superlatives you can think of).

At this point one thinks and says, "OK, I've installed it all with a user who is administrator of the domain and that the security (or I) is not going to like anything, so we secured a little" . Activate the firewall, we allow the appropriate ports (80, 443, 389.636, 902.903, 8084, 9084 and 9087), review the utility bills and we have the unpleasant "surprise" (it's not surprising because the installation program and we warned) that the service account associated with the VMware VirtualCenter Server service


and VMware VirtualCenter Management has an associated

Webservices administrator account I did the installation (bad royo). As administrators we are concerned about security and change the service account by an unprivileged account on the domain we have for this kind of stuff. We will start new services y. .. YaST yalaliaopardadiosmiodemivida!! service

VMware VirtualCenter Server will not start making a nice little message type error:

Failed to init TableDef: VER_ID Column does not exist in table VPX_VERSION. Database May Be incompatible version.

The problem is that the account that is allowed in the SQL Server installation is the original, which will have to tinker with the database. The original procedure is not mine, I've taken from the Communities of vmware, so you can see the original post here

(in English). For those who do not wish to translate, basically the steps are:

Open SQL Server Management Studio


seek the VMware database. If we followed the installation manual pat this will
VCDB

1. sailed across the tree of the database until VCDB-> Security-> Schemas-> db_owner
2. Open the properties of the scheme and we changed the parameter value Schema Owner original value \u0026lt;
vcuser
3. > (the initial installation) to
4. eliminated dbo user \u0026lt; vcuser > from the database. It can be found in VCDB-> Security-> Users . Be careful not to delete the login of the server that is mapped to that user. Open a new SQL query window
5. launched the following query, changing \u0026lt; vclogin > by name new user of the service account that you have partnered with VMware services:
6. EXEC sp_changedbowner @ loginame = '\u0026lt;
7. vclogin >', @ map = 'true'
1. started the departments concerned in the VirtualCenter server
8. FIN
9. I hope this post saves two days of headaches that I have taken my solve the "problem"