Hi

first bit of info is that this 32 char limitation will be lifted in the next SRM update due later this year. to the questions:

• Do I have to change the computername, or just add a 32 character DNS record pointing to the 'unchanged' vCenter?

Ans: if the current FQDN is > 32 char it needs to be less than this. how many characters are in the computername?

• If I have to rename vCenter, what should I look out for, as far as
  potential issues (e.g. impact on other services; licensing; vCenter
  database; ESX Host etc)

Ans: you will need to rename some of the windows services to reflect the correct computername. this can be done by editing the ODBC DSN

• If I have to rename vCenter, will i have to rename the ESX Hosts too?

Ans: no

• Would we run into the same problem during SRM install, if we kept the long FQDN, and used Windows CA certificates?

Ans: you mean following process outlined in this KB article http://kb.vmware.com/kb/1008390 then yes. If your VC servers use your own signed certs then SRM must also use your own certs. The process for the SRM side is covered in this document http://viops.vmware.com/home/docs/DOC-1261

• If we use Windows CA certificates, what do we have to generate them for (i.e. vCenter only, or for each ESX Host too)

Ans: vCenter and SRM servers. Refer to the viops site doc for example on creating the SRM certificates. also search on this forum for other useful posts on this

• Would we have to install certificates on any other hosts (ESX, VCB etc)

Ans: no

best regards,

Lee Dilworth

I wouldn't run SRM on the same server as vCenter. SRM puts a lot of stress on the Server... will it be a VM or a physical host?

Duncan
VMware Communities User Moderator

---

Blogging: http://www.yellow-bricks.com
Twitter: http://www.twitter.com/depping

If you find this information useful, please award points for "correct" or "helpful".