How to Migrate Windows Based vCenter Server to VCSA 6.7

How to Migrate Windows Based vCenter Server to VCSA 6.7

As you may already aware VMware has released the vSphere 6.7 and it ships with lots of new features and I’d like to show you the complete steps to Migrate Windows Based vCenter Server to VCSA 6.7. It is much similar to Windows based vCenter server to VCSA 6.5 Migration and I previously posted a blog post about the Migration.  vCenter 6.7 has released with a new appearance and I have tested it in my lab at the very first day of the release. Read my blog post about the vCenter Server 6.7 first impression here.

Before you start your migration make sure to check the VMware Product Interoperability Matrices and cross check your environment support. VMware vCenter Server 6.7 migration supports only for vCenter Server 6.0 and upper versions for the Migrations. If your vCenter is sitting in vSphere 5.5 or lesser version make sure to upgrade your vCenter Server to vCenter Server 6.0 first.

Migrate Windows Based vCenter Server to VCSA 6.7 : vCenter Compatibility

vCenter Server 6.7 can manage only ESXi version 6.0 and upper versions. If your environment consists with ESXi version 5.5 and lower versions you have to upgrade the ESXi version 6.0 first.

Note: Make sure to remove any older version of ESXi host profiles from your vCenter Server and that can cause the vCenter Server Migration failure at the middle of the Migration (Based on Personal Experience).

Migrate Windows Based vCenter Server to VCSA 6.7 : ESXi Compatibility

Migrate Windows Based vCenter Server to VCSA 6.7 From the Beginning (Stage -1 )

Migration of Windows based vCenter Server to VCSA 6.5 and 6.7 has no difference in steps, but I wanted show you the complete steps of the Migration so anyone can start and plan their migration without wasting time in their test labs. It is a two stage process and as the Stage – 1 it deploys the appliance and continue the configuration in stage – 2.

First things first, I assume you already fully patched your Windows based vCenter server from the Operating System Patches, because running the Migration assistant will require the C++ 2005 redistributable binaries installed on the system otherwise migration assistant will fail the prechecks.

Download the vCenter Server 6.7 Appliance and mount it to the Windows based vCenter server (6.0) and run the Migration Assistant located in “VMware VCSA/migration-assistant” folder as shown in the below screen capture.

Migrate Windows Based vCenter Server to VCSA 6.7 : Start Migration Assistant

Ensure that there is no errors in the Prechecks of the Migration Assistant and you can start the Migration once you get the “Waiting for Migration to start …” notification

Migrate Windows Based vCenter Server to VCSA 6.7 : Waiting for Migration to start

Now login to another server in your network and mount the vCenter Server 6.7 ISO and go to the

Migrate Windows Based vCenter Server to VCSA 6.7 : Run Installer

Select the Migrate Option, you can see a small self explanatory description under Migration tab

Migrate Windows Based vCenter Server to VCSA 6.7 : Migrate

Nothing to do with the Introduction Page, Just click Next

Migrate Windows Based vCenter Server to VCSA 6.7 : Introduction

Accept the “Terms of the License Agreement”

Migrate Windows Based vCenter Server to VCSA 6.7 : Terms

Provide the source vCenter Server details , Migration Assistant will use the default port. If you are intend to use a different port please specify otherwise use default port

Migrate Windows Based vCenter Server to VCSA 6.7 : vCenter Server details

Just verify the thumbprint in the next step

Migrate Windows Based vCenter Server to VCSA 6.7 : Thumbprint

Specify the target vCenter or the ESXi host details and credentials

Migrate Windows Based vCenter Server to VCSA 6.7 : Target Host

Accept the certificate

Migrate Windows Based vCenter Server to VCSA 6.7 : Certificate

Specify the Virtual Machine name and the the root password

Migrate Windows Based vCenter Server to VCSA 6.7 : VM name and root password

Specify the deployment size, if you are intend to use the VCHA feature at least you need to select the size as small. You can see the required resource size in the table

Migrate Windows Based vCenter Server to VCSA 6.7 : Deployment Size

Select the target datastore, I’m enabling thin provisioned virtual disks for my deployment. In a production environment I do not encourage to enable thin provision disks for your vCenter server

Migrate Windows Based vCenter Server to VCSA 6.7 : enable thin

Provide the networking details and we need to have a temporary IP address as similar to the 6.5 Migration

Migrate Windows Based vCenter Server to VCSA 6.7 : temp IP

Review your settings and Click on Finish to start the deployment and complete the stage -1 of the Migration

Migrate Windows Based vCenter Server to VCSA 6.7 : Finish

Just wait for the completion of the Stage -1 of the migration

Migrate Windows Based vCenter Server to VCSA 6.7 : In progress

Once it completed the Stage – 1 of the migration Continue to the Stage – 2

Migrate Windows Based vCenter Server to VCSA 6.7 : Start Stage - 2

Migrate Windows Based vCenter Server to VCSA 6.7 : Stage -2

As similar to the previous stage nothing to do with the Introduction and just click Next

Migrate Windows Based vCenter Server to VCSA 6.7 : Stage 2 Intro

Then it will perform a pre-checks

Migrate Windows Based vCenter Server to VCSA 6.7 : Stage 2 Precheck

You can see the pre-Migration check results and errors and warnings can be seen in the window. In my case I have two networks connected to the source vCenter Server and it gave as a warning as it cannot add the network adapter as a part of the migration

Migrate Windows Based vCenter Server to VCSA 6.7 : Pre-Check results

Provide the AD account credentials which has the privilege to add this appliance to the AD domain. You can perform this task later if you need

Migrate Windows Based vCenter Server to VCSA 6.7 : AD Credentials

After validating the credentials select the migration data which you want to migrate from the old vCenter server. Migration process time will vary depending on the data set you select here

Migrate Windows Based vCenter Server to VCSA 6.7 : Migration data

Tick or untick the CEIP selection according to your requirement and this is completely optional

Migrate Windows Based vCenter Server to VCSA 6.7 : CIEP

I hope, I don’t want to mention that you need to take a backup of the database before you start the migration and confirm that you have taken the backup in this stage. Also, you can see the summary of the configuration selections in this window

Migrate Windows Based vCenter Server to VCSA 6.7 : Confirm Backup

It will give you a Warning to the shutdown of the source Virtual Machine. Migration wizard will automatically power off the source virtual machine

Migrate Windows Based vCenter Server to VCSA 6.7 : warning

It will start the Migration wizard, there three main steps similar to the 6.5 migration

Migrate Windows Based vCenter Server to VCSA 6.7 : Three steps 1

I got this information at the end of the stage two

Migrate Windows Based vCenter Server to VCSA 6.7 : information

Finally, it completed the migration from Windows vCenter 6.0 to VCSA 6.7

Migrate Windows Based vCenter Server to VCSA 6.7 : Completed

Migrate Windows Based vCenter Server to VCSA 6.7 : Client

If you found this post as useful please rate the post and share it!

Click to rate this post!
[Total: 26 Average: 5]

14 responses

  1. Go0se Avatar
    Go0se

    I would like the VCSA server to eventually utilize the same IP address the original vCenter Windows server was using. You mention using a temporary IP address – does the system change the new server over to the old IP address? If not, is it easy to change that temporary IP address back to the original vCenter server IP address?

    1. Aruna Lakmal Avatar

      Thank you for your comment and following my article.

      In this case don’t worry about the IP it will get the same IP after the completion of the migration. This temporary IP will use to copy the data from your old vCenter to the new vCenter server appliance.

  2. Charles Avatar
    Charles

    Hey Aruna I am just curios if the old Windows server can be brought back online without causing issues and readded to the domain? I would remove vcentre from it of course after it is up. Our backup software runs on the server so I need it to be functional. I have read a lot of articles that doesn’t address this question. Thanks in advance

    1. Aruna Lakmal Avatar

      Charles, thank you for reaching out to me.

      Seems like you are in a trouble and you could have checked the dependencies before the upgrade.

      If you bring up the old server again it will power up with the same IP address and can lead you to an IP conflict in the network, obviously your new vCenter server will be in trouble due to this situation. You have to think about that before touching the old vCenter.

      In terms of vCenter services of the old server, those services will not run and cannot be used as a vCenter again. If you are planning to do so you have to revert the DB backup and snapshot before the upgrade. Sometimes domain relationship can be broken and you might need to reconnect to the AD.

      If you need further information or support please let me know.

      1. Mark Avatar
        Mark

        Aruna and Charles, You can change the IP Address after the migration is done of the VCSA and then bring back up the old server. So the new VCSA 6.7 will have a different IP than the old server.

        1. Aruna Lakmal Avatar

          Really, didn’t try that and it was not successful with my previous attempt with the VCSA (not 6.7). If there is a article please share so anyone can see the steps and thought it is good for everyone. Thanks for the comment.

          1. Cividan Avatar
            Cividan

            I think it would be easier to power up the OLD vcenter without network connectivity, take the windows machine out of the domain and change the network IP configuration (if your application is not dependent on that specific IP), reboot server, change windows server name and uninstall/disable vcenter stuff from that machine. When IP/Name/Vcenter is changed then connect the network and re-join AD with the new name. This would give you the ability to keep using the windows server without needing to mess with the VCSA.

          2. Aruna Lakmal Avatar

            Honestly, I have done many upgrades and there was no requirement for me to bring up the old server. But I doubt whether services will come up again!

  3. Cividan Avatar
    Cividan

    Forgot to say thanks for the walk thru it was helpful.

    1. Aruna Lakmal Avatar

      Thanks a lot Cividan 🙂 Appreciate your thoughts here!

  4. Dayo Avatar
    Dayo

    Hi Aruna

    Thanks for the very easy to follow Steps. Do you know what happens with Veeam Backup solution post migration to the new platform

    1. Aruna Lakmal Avatar

      Hi Dayo
      Sorry for the late response. Nope, I haven’t tried it yet.

  5. Craig Avatar
    Craig

    Hi Aruna, I am also interested in this as well, have you found any information regarding Veeam backups post migration?

    1. Aruna Lakmal Avatar

      Hi Craig
      No I haven’t tried it yet!

Leave a Reply

Your email address will not be published. Required fields are marked *