vShield Migration to new vCenter

Similar Questions

• Migration to new vCenter

  I have two vCenters up and running, ESXi 5.0 and 5.5 of ESXi. Our existing environment is 5.0 and 5.5 is a new environment, I built (we decided to not upgrade the environment existing for various reasons).  I'm trying to figure how best to migrate all our VM (over 100) of 5.0 to 5.5 quickly and with the least amount of downtime and I was wondering what others have done in the past.  We have different loads of work on those virtual machines (IIS, SQL, file servers, etc.) and I am open to any suggestions/ideas.

  Thank you in advance!

  Hello

  According to the Matrices of the interoperability of products VMware ESX/ESXi 5.0 is compatible with vCenter 5.5, you can add the 5.0 hosts to vCenter 5.5.

  Enter the vSphere 5.0 5.5 vCenter's existing licenses.

  The shared storage is accessible by two 5.0 host and new 5.5 hosts?

  If Yes, then you can vMotion 5.0 host to new 5.5 hosts so that they have the same series CPU, the procedures are described here: Library of vSphere 5.5 - movement of Virtual Machines using vMotion during an upgrade

  This allows to check the CPU/matrix series: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=cpu

  If they belong to different series of CPU, you can perform the Migration cold (requires downtime) Library of vSphere 5.5 - Migration of virtual machines

  Cold migration: moving a VM power off to a new host. Optionally, you can move the configuration and disk files to new storage locations. Cold migration can be used to migrate virtual machines from one data center to another.

  
  

  If you are using a shared storage, even, you can also perform migrations as below:

  1. turn off the VMs system in the old 5.0 hosts

  2. Remove VMS in vCenter inventory 5.0 (note the location of the files in the data store) library of vSphere 5.5 - remove virtual host computers

  3. Add VMS to vCenter inventory 5.5 5.5 Documentation Center - VSphere to return a virtual machine or the template to a host

  4. turn on the VMs and check.
  

  
  

  If the shared on 5.0 storage is not accessible from 5.5, you can perform LUN or migration cold.

  LUN migration requires less compare to cold migration downtime.

  LUN Migration:

  1. present the storage shared existing 5.5 guests.

  2. after the 5.5 can access the existing shared storage, stop the virtual machines

  3. remove virtual machines from existing inventory of the vCenter 5.0

  4. Add VMS in vCenter stock 5.5
  

  5. turn on the VMs and check

  6 storage vMotion the VMs to new shared storage (you can also perform Storage vMotion first, but you will need to present the new storage shared for guests 5.0)

  Cold migration:

  1. present the storage shared existing 5.5 guests.

  2. after the 5.5 can access the existing shared storage, stop the virtual machines (for consistency of data)

  3 clone virtual machines from 5.0 to 5.5 new hosts guests (you can rename the old VM so if you want cloned the new VM will have the name of the old virtual machine)

  4. make sure that the old VMs are turned off

  5. turn on new new 5.5 host virtual machines and check

  6. remove the old virtual machines in inventory, or remove disks

  7. If you need to rename the virtual machine name, rename the virtual machines and run Storage vMotion to different data store VMware KB: rename a virtual machine and VMware ESXi and ESX records

  You can try to migrate 1 VM first, or simply create a new dummy virtual machine and choose 1 5.0 ESXi host to test migration.

• New Vcenter server and host add

  Hello, we are planning to create a new server Vcenter.  Had a bunch of weird issues with Vcenter.  Vcenter 5.1 on Windows running.  have not decided if we will use the VCenter, or create a new virtual machine from Windows to Vcenter again but I don't think that will count for my question.

  My plan is to turn off HA and DRS on the old server Vcenter, then remove a host from the old server Vcenter, and then add this host on the new Vcenter server.  Then just repeat the process for each host.

  My question is, should I turn off any virtual machine running on the hosts before removing the old server vcenter?

  If I remember correctly you have not, the virtual machine must remain in place and running, no connectivity should be lost and users should not not the difference.  We plan to do this off-peak hours, but there are always a couple of vm that are used 24/7.  It would be therefore rather not have to stop first.

  Thank you

  Hi defrogger

  Yes, it's the right way to migrate a new vCenter ESX Server.

  Disable HA/DRS and then disconnect the ESXi, vCenter server and plug them into the new vCenter.

  By disabling the DRS, you will lose the Resource Pools. So its maybe you assign only manual DRS.

  Another thing that many people forget are the options of the virtual machine on the cluster options. they have been set up again on the new cluster.

  BTW. There is a guide of vmware:

  VMware KB: Move a managed ESX ESXi host to a vCenter Server to a different Server vCenter

• PowerCLI Script to migrate virtual machines with the same network Source for the new vCenter Server.

  Hi all

  I checked a few posts on the migration to the new vCenter Server virtual machine. But I'm not very good with Powercli and need some help here.

  We have a new vCenter server where we migrate virtual machines from one source vCenter server. Here are two things that I don't know how to connect together to make sure that bwfore we turn on the virtual machine to the virtual machine is connected to its source network.

  Part 1 - this script works well but do not get any network on the vCenter destination.

  cluster = Get-Cluster "clusterA.

  $inventory = get-Cluster $cluster | Get - VM | Add-Member - MemberType ScriptProperty-name "VMXPath" - value {$this.extensiondata.config.files.vmpathname}-Passthru-Force | Select-Object Name ResourcePool, folder, VMXPath |

  $inventory | Export-Csv c:\file.csv

  $inventory = import-csv c:\file.csv

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  Part 2 - I want to preserve the Portgroup macaddress and the Ip of the virtual computers and connect them to the new vCenter. How can I do this with the script below. Or how can I combine them together?

  $vm_list = get-Cluster-name "clustera | Get - VM test * | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  Step 2

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-RunAsync Verbose - confirm: $false

  Step 3

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool.Name

  New-VM - ResourcePool (ResourcePool-Get-name $resource_pool) VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  Step 4

  # Put the network cards

  foreach ($info in $inventory)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose-RunAsync-confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null}

  }

  Thanks in advance for any help.

  Hi all

  I made some changes to the script and it worked for me. We have added a host on the destination with all exchanges and storage mapped vCenter.

  $vm_list = get-Cluster-name 'Site B - b | Get - VM | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-Verbose - confirm: $false

  $cluster = get-Cluster "Site A - clustera.

  {foreach ($vm to $information)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm.path - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool

  New-VM - ResourcePool (ResourcePool-Get-name "test1") VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  # Put the network cards

  .

  foreach ($info in $information)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose - confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null

  }

  Hope this will help many of you.

• PowerCLI script to migrate virtual machines to the new vCenter environment

  Hello world

  in the next few weeks, we need about migrate 700 VMs (Windows/Linux) server to a new environment (new vCenter, new hosts, but VMs will remain on same data warehouses). VMs will be migrated not in one batch, but rather from time to time (which, however, can understand the need to migrate some 10s of virtual machines at the same time).

  Cluster names and folder structure will be identical to the old and the new vCenters. As host in the new vCenter names differ from those in the old vCenter, thought to provide a table of 'translation', which tells the script to save a given VM on host B (new vCenter) when having been registered in order to host a (old vCenter) and so on.

  I thought writing a PowerCLI script which, broadly speaking, can accomplish the following steps:

  • Connect to vCenterOld and vCenterNew
  • Correspondence table of host to read from a file (see step "register VM vCenterNew below)

  Then, in a loop:

  • Ask VM name
  • Get the settings of the virtual machine: Datastore/path, network/Portgroup, HA restart priority, host, folder, note
  • View the parameters and the VM name and request confirmation migrate the virtual machine
  • Turn off VM (closed OS gracefully, but force power off if power status is still not equal 'off' after a time given)
  • To unsubscribe from VM vCenterOld (removal of inventory)
  • Registry of the VM to the data store vCenterNew (assumptions: same folder as vCenterOld, host names are different, but for each source in vCenterOld host a host of destination in vCenterNew for you join the virtual machine to can be provided, that is, CSV)
  • The value of VM portgroup (same name as in vCenterOld)
  • Set VM HA restart priority
  • PowerON VM
  • Wait / check the VM (for example, ping) connectivity / continue immediately if the virtual machine is accessible or after a certain time if the virtual machine is still inaccessible
  • Confirm that the virtual machine has been migrated successfully, OR ask the user to check the connectivity of the virtual machine

  Now to my questions:

  • Is anyone know about an existing script that does something similar or contains parts that can be useful to compile a script like this?
  • How can vCenter two connections at the same time been managed within a PowerCLI script - or doesn't work at all and a connect/disconnect to/from the two vCenters must be completed for each virtual computer?

  Many thanks for any help.

  The following seems to work for me

  $vm = Get-VM -Name MyVM$nic = Get-NetworkAdapter -VM $vm $vdPG = $nic | select -ExpandProperty NetworkName
  
  Get-VDPortgroup -Name $vdPG
  

• Migrate VMS in vCenter former 3.5 to new vCenter 5.1

  I had (no license maintenance) situation where I have not maintained old environment VMWare vcenter and esx servers running in version 3.5. SAN is mixed two IBM N3300 iSCSI/NFS. All this will be removed from use. Then I got new brilliant vCenter 5.1 environment (new licences), is EMC e iSCSI SAN.

  I was wondering if I could really get the old N3300 on new vcenter, start the computer virtual and storage vmotion them away? But how VMWare reacts if the storage is mounted on two different groups? I should probably remove old vcenter storage before going up again?

  Hosts sharing the same LUN do not need to be in the same cluster, or even in the same environment - I'd go ahed and add logic unit number to the new environment to ensure that you are able to see the storage as well as the files that make up the VM - the steps that I follow are:

  1. Turn off the virtual machine
  2. Reove the VI3 environment (right click on the virtual computer name and select Remove from inventory)
  3. In the new environment, navigate to the location of the VM configuration file (.) VMX) on the LUN and add it to the inventory
  4. Turn on the virtual machine

  You can delete the original ESX host storage and adds it to the new environment - virtual machines should be discontinued for as long you need to add the storage to the new environment and the machine virtual to the new environment, but I think that the above method will be less intrusive and provide a more reliable migration

• VCenter simple Migration to new hardware

  have a Setup simple vCenter.  A vCenter server with 3 being the hosts managed and about 15-20 ESX servers.  He is currently a virtual machine host as we had no spare parts at the time.

  We do not use the advanced features yet (vMotion, etc.).  Basic host maintenance.  We have new equipment and Win2008/64-bit is installed.

  What moved the easiest way to get the old stuff?  Or I have to actually migrate?  Can I simply unattach the 3 former ESX servers and add it again?  Old server vCenter will be deactivated once all moved or added to the new server.

  Thank you

  Hello

  You need basically install new vcenter and remove all hosts to vcenter (unplug and remove). To add vcenter again.

  Also check http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=5850444

  and this discussion http://communities.vmware.com/thread/139206

  Hope helps

  Good luck

• Migration to new server vCenter ESX continuously.

  What would be the recommended steps to migrate seamlessly from one ESX host to a new vCenter Server?  I succumbed to find any documentation on this.  For some reason any I think remember me that with a previous version of Virtual Center (1.x and 2.x) that the host had to be in maintenance mode before it could be removed from the management server.

  I need to move the ESX 3.5 and 4.0 hosts to a new management 4.0.1 vCenter server.

  James Wood, VCP

  Senior Systems Administrator | Arizona Department of Transportation | Phoenix, Arizona

  You can simply disconnect and remove the host.  Then add the host in the new environment. This will affect any of your guests running. If your VI3 hosts, make sure that you have the available license server.

• Migrate to host new vCenter

  We are planning the upgrade of guests 4.1 to 5.0. Once the host is upgraded, we want to move hosts to a new vCenter within our environment. Completion of the upgrade of the host, we can vMotion VM on the improved host, disconnect it to vCenter and then plug it into the new vCenter with the virtual machine is still attached? The new VirtualCenter has all the same storage, port groups, etc.. We just want to with as little interruption to the virtual machine as possible.

  Yes - plan you described you will allow then to move the host with minimal downtime for virtual machines, the only other suggestions is to ensure that you disable HA and DRS if activated, because this allows you to put the host in maintenance mode whne you try to disconnect the host - force

• Migrate to new hardware of 5.1 to 6.0

  Hi all

  I foresee a great migration in our VMware environment. I want to spend all the virtual machines in an environment 5.1 to 6.0 with new hardware environment.

  Details: existing environment: two hosts with ESXi 5.1, an iSCSI SAN, and a 5.1 on 2003 VM Server vCenter. New environment: two with 6 ESXi hosts and a new iSCSI SAN.

  I found this interesting thread: migration to the blow by blow of 5.5 to 6.0 by using new materials and fresh install. and from there, I thought the following might work:

  1. Create a new vCenter on one of the new hosts using Windows Server R2 2012
     Now, I should have a new vCenter to manage a single host.
  2. Remove a former host of the former vCenter and add it to the new vCenter.
     1. Move all the VMs from the old host to the new host and remove the old host after moving virtual machines.
     2. Repeat for the second former host.
  3. Add the new second host to vCenter.
     Now, I should have a new vCenter 6 with two ESXi 6 hosts running all my virtual machines, right?

  Question: What is the best way to move files VM from the old to the new San SAN?

  I think I have two possibilitys (correct me if I'm wrong):

  1. Use vStorage Motion to move VMs old host and storage for two new
     Question: should the new host access iSCSI also the old SAN or simply for the new San?
  2. Browser data store allows to move the files to the new data store
     Question: should the new host access iSCSI also the old SAN or simply for the new San?

  Which would be best? My virtual machines have an average size of 50 GB except a few Windows VMs with about 100 GB and my file with 1.2 to server.

  If you have any other ideas, I'm open to any suggestion.

  Concerning

  Chris

  Same storage must be accessible on both hosts make VM vMotion and once that virtual computers running on new host, storage vMotion to migrate virtual machines from old to new DS DS.

  You can also try VM host and storage migration toghter using the web client to move virtual machines from the old host and DS, but especially first option is preferable.

• Migration of one vCenter to another cluster

  Hello

  We have a cluster under A vCenter which runs on the Cisco Nexus 1000v switch distributed. This cluster (all hosts of ESXi and VMs) must be migrated to VMs vCenter B keeping alive if possible.

  I know that this host can be removed form the VirtualCenter with VM direct and added a new vCenter but not sure a distributed switch

  Looking for options / advice

  Our vCenter is 5.1

  Thank you in advance,

  Arkady

  The switch really makes this difficult process.  You prefer to bet on it to make the following process:

  1 take a source host network adapter and connect to a standard virtual switch

  2. move all the VMS to the switch stanard

  3. remove the second 1000v virtual switch interface (DISPLACEMENT market out virtual switch management)

  4. move the hosts with vm to new vCenter

  5 Migtate of virtual machines to new switch

  I know that this process sucks but the virtual switches are a construction of vCenter and will not go through vCenter.    The other option is to wait for vSphere 6.0 and new vMotion allows to solve this problem.  With vMotion new this should be a right click and wait for the process, assuming that the source and target ESXi host have the same VLAN.

  Let me know if you have any questions.

  Thank you

  Joseph

• Great migrations: move from vCenter 5.1 on Windows 2008R2/SQL 2008 5.1 or 5.5 on 2012 2012 Windows/SQL

  In anticipation of the end of mainstream support for Windows Server 2008 R2, I want to migrate an installation vCenter to a whole new server and MS SQL Server.

  It is a virtual machine running in my host cluster. There Server vCenter Update Manager, Converter Standalone and some services not VMware that I can handle it myself. ADAM is installed as part of the vCenter Server requirements, and it is also attached to an AD domain where I use AD, single sign - on.

  The host cluster is four 5.1 ESXi hosts that are up to date, and helped HA and DRS. They use also switches distributed to all of their network connectivity, including vMotion, management, fault tolerance (although I do not use FT) and virtual machines.

  I did upgrades on-site to vCenter before and I replaced SQL Express with SQL Standard on the same server, but I did not move before vCenter. I'd make some drastic measures, as I understand:

  * Complete backups (of course) of SQL in the server itself, ADAM

  Installation of a new server operating system and SQL 2012

  Withdrawal of databases and reinstall them on the new server

  * Restoration of ADAM on the new server

  Installation vCenter, Update Manager, etc.

  * Hoping the host cluster is mounted on the new server, and nothing breaks

  I'm not all that worried about maintaining statistics, so maybe it is possible to install a new server vCenter Server and simply move the host cluster from the old server to the new. I moved one vCenter to another host, but that was before I put in place of distributed switching.
  --

  I found this on a related post:

  Migration in a new vCenter VMware environment. IT diversifies

  This manual seems to echo what I've read so far, I had to disassemble the distributed switches until I can migrate any host to a new server vCenter. Yuck. Well, I've migrated from the standard to the switches distributed without downtime before, so I can do the opposite.

  --

• Confirm the Migration process from vCenter

  I need the extra eyes to look at a process of migration, we are looking at the company.  Here's the situation:

  Former environment:

  5 ESX host running connected to vCenter 5.1 5.1

  ~ 170 virtual machines running

  EqualLogic SAN

  A host connected to the new Bay storage Compellent

  Gigabit network

  New environment:

  2 ESX host running connected to vCenter 5.5 5.5 (new forum)

  Compellent SAN

  10 gigabit network

  We want to forward the new virtual machines in the old environment without a reboot of the VMS if possible.  The process proposed by our implementation partner is to:

  1 vMotion the VMs on the old host which is connected to HDS

  2 storage vMotion to Compellent disk

  3. turn off the VMs system

  4. remove the virtual machines of the old vCenter inventory

  5. Add the virtual machines on the new vCenter inventory

  6. turn on the virtual machines on the use of one of the two new hosts

  We have been brainstorming (dangerous!) today and wondered about this process:

  1 vMotion virtual machines to a former host with connectivity Compellent

  2. Add the old host to the new vCenter (causing it to unplug the old vCenter)

  3 vMotion virtual machines from the old host to one of the hosts again in the new vCenter

  This seems to be a no to the approach of the time.  Given that the servers all run on the host computer while the host moves between vCenters, only real exposure that I see is the period between vCenters, there is no other host to pick up the virtual machines if something failed.  The servers are all processors from Intel and of a similar age, so I don't think CVS will be a problem.  That we can restart while we deem necessary to level of VMware Tools and virtual hardware.  Can someone dig holes into the present, or tell me that we are on the right track?

  Yes, absolutely, you can do these operations without interruption.

  If you do this by using the user interface (VI client or Web client)

  1. first vMotion virtual machines other 4 former host of a former host where the Bay storage compellent access available.

  -Make sure you of course old host with access compellent has enough CPU/memory so that all ON VMs can be placed.

  -Also make sure that all former host shared except compellent storage Bay (which is available on the single old host), I think there is already.

  2. now storage vMotion all virtual machines to the old host compeleent storage array.

  -This can be done using script or manually

  3. remove the old host (with compellent) from old server vCenter.

  4 create a cluster on new vCenter 5.5 and add that all welcome (old 1 + 2 new) to regroup.

  5. turn on the DRS in fully automatic mode with aggressive threshold. and make sure that vMotion network is correctly configured.

  6. turn the old host in maintenance mode. DRS automatically leave the old host and balance the load on other host new facilities.

  7. wait that all vMotion operation to complete, former host wud be now in maintenance mode.

  8. remove the old host in the cluster and out of MM and remove vCenter again.

  Note:

  -You can configure VMware HA/FT on the cluster to avoid any possible failure (make sure that you approve the requirement HA/FT)

  -If possible, explore XVMotion, which helps move VM even there is no shared data store.

  -If you want to use the script to vMotion/SVMOtion, get back to me.

  -Let me know if you have any doubt

  Please allow the points if it is useful.

• Moving hosts to new vCenter and retaining current licences for guests

  I need to upgrade an environment vSphere 4.1 to 5.1u1. I plan to install a clean vCenter 5.1 and need to migrate hosts without interruption to the virtual machines. The way to remove the old vCenter may not be because it requires the host mode maintenance and VMs to be evacuated. What plan do is disconnect from the host and have the new vCenter appropriated. I will then possibly incoming days guests through VUM to 5.1u1.

  My question is when the new vCenter appropriates the hosts what will happen to the licensing of 4.1 esx/esxi hosts? Will be the current 4.1 esx/esxi licenses follow the hosts or will I have to add the esx/esxi through the client license? The new vCenter will be installed in trial mode until licenses can be provided for me.

  A second question is when the esxi hosts are upgrading to 5.1 and I did not upgrade licenses will guests enter a grace period until a license can be applied? I don't know how long the hosts were in trial mode, before 4.1 licenses applied so I assume every 60 days were used.

  With adding hosts to the new vCenter Server, the license key from the host server will be added to the repository of the vCenter Server license; Even if this is not the case you could simply add the current license key to the new vCenter Server manually. Just make sure that you do not use more CPU that purchased licenses.

  Once you upgrade the host, make sure you have the new license keys already available. As much as I know there is no evaluation period additional to the hosts upgraded who were running older versions of 60 days. The grace period of 14 days you mentioned applied to versions in ESX 3.x used FlexLM licenses (i.e. license files).

  André

• New vCenter Server Hardware

  Hello

  I go to the construction of a new vCenter server to my upgrade to vSphere 5.  The server vCenter 4.1 existing will be decommisioned and a new vCenter 5 installed.  I will keep the existing SQL database however.

  All settings are since I was on the existing DB?  I don't need to execute one of this batch of data migration tool file I do?

  If you use an existing DB, you all that you need to do is create your ODBC connection, test it and install vCenter ' help and existing DB.  VCenter all the setting is preserved.

  The existing DB is external to the vCenter Server Correct?