sabya1232003's Accepted Solutions

The alarms that has been set at the resource pool level will be applied in this case. If there is no settings defined at this level then only the vCenter level Alarms will be applicable and trig... See more...
The alarms that has been set at the resource pool level will be applied in this case. If there is no settings defined at this level then only the vCenter level Alarms will be applicable and triggered.
The Best option for ESXi logs is to collect it via VI client.VMware does not recommend any diagnosis directly on the server console as it has a small hyperviser and no service console.
For the Console access of the VMs ..the vCenter really does not rely on the DNS config .It communicates only through ports 902/903 This problem might have appeared due to some misconfig while ch... See more...
For the Console access of the VMs ..the vCenter really does not rely on the DNS config .It communicates only through ports 902/903 This problem might have appeared due to some misconfig while changing DNS ...pls try below Remove and add again the ESX Server to the vCenter Restart the management services of the ESX ..#Service mgmt-vmware restart --All the Best
There would be no impact on the running VMs while moving from 4.0 to 4.1 vCenter.Its already tested by many experts.The only thing you may have to do is to use the new version of vSphere client.i... See more...
There would be no impact on the running VMs while moving from 4.0 to 4.1 vCenter.Its already tested by many experts.The only thing you may have to do is to use the new version of vSphere client.its recommended to use 4.1 client to connect to the 4.1 vCenter. We had few issues related to access performance tab and other pluginns on the new vCenter ...nothing else comes to mind right now. All the Best for a smooth migration ..
The Lic model for vSphere and ESX 3.x is different.There is no need of License server for vSphere .But still you can connect the ESX 3.x hosts to the vCenter 4.0 ...but you cant add ESX 4.0 hos... See more...
The Lic model for vSphere and ESX 3.x is different.There is no need of License server for vSphere .But still you can connect the ESX 3.x hosts to the vCenter 4.0 ...but you cant add ESX 4.0 hosts to the vCenter 2.5 (which uses lic server) Best option is to upgrade the lic to be compatible to vSphere 4.0 with no extra cost.Contact VMware support ...they will guide on the Lic part
As long as there are no activities on the vCenter the DB movement can be performed during production hours.But you have to make sure the automated vCenter Services are stopped (HA/DRS ) and you h... See more...
As long as there are no activities on the vCenter the DB movement can be performed during production hours.But you have to make sure the automated vCenter Services are stopped (HA/DRS ) and you have to stop all the services related to vCenter from windows services console. Coming to DB Migration : its very simple as long as you are using the same old data on a different DB Server.The only thing you have to take care is the proper backup of the current DB.Next Create/Configure new DB instance with old Data and then you need to point the existing ODBC DSN to the new DB instance on your DB Server.Test the ODBC connection and start the vCenter Services.