Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).

5 Comments

  1. Hugo M
    February 10, 2022 @ 1:58 am

    Hi, thanks for the instructions, the only information I am really struggling to find is regarding the DB.
    Our current setup includes a Windows vCenter with an external MS SQL DB. As part of the migration and selecting the migration data, does it convert the external SQL DB into the embedded Postgres DB on the VCSA?
    Thanks

    Reply

  2. Dominic Shoemaker
    November 6, 2020 @ 4:31 pm

    Great article. Thanks for posting. 2 questions for you.
    Can I migrate vCenter 6.7uJ on Windows to VCSA 6.7 latest version?
    Also, can I use the same static IP for VCSA that I will use in Windows for the migration process, or will that cause issues?

    Thank you!

    Reply

    • lakonst
      November 7, 2020 @ 10:34 am

      Yes, you can migrate vCenter 6.7uJ on Windows to VCSA 6.7 latest version but you cannot use the same IP for VCSA.

      Reply

  3. Mike Y
    October 11, 2020 @ 7:02 pm

    hello, this looks nice and easy. But we have Horizon View with linked clones. Will this work migrating a Windows Vcenter 6.0 to the Appliance 6.7 in Horizon View Environment as well?
    Or are there other things to consider when migrating with Horizon View?
    We have our Connections servers pointing to the Windows Vcenter and the Composer tied to the Windows Vcenter server(composer is serperate VM). The migration makes it seem like our Connection and Composer server wont even know vcenter has changed to the vcsa. Is that the case?
    Thanks

    Reply

Leave a Reply

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