pasalott
Enthusiast
Enthusiast

Need to migrate composer and connection servers to new Windows 2019 VMs

Jump to solution

We are currently running Horzon View 7.12. We need to migrate our composer and connection servers to new Windows 2019 VMs.  I've found instructions for migrating the composer server.

Would migrating the connection server be as simple as adding a second connection server (replicated) running Windows 2019 and then decommission the old Windows 2012 connection server?  If so, are there any special steps to decommission the old server?  I'm not having much luck finding documentation for the process.

0 Kudos
1 Solution

Accepted Solutions
Shreyskar
VMware Employee
VMware Employee

High level steps to migrate connection server to 2019 OS will be as follow:

> Take a snapshot of all CS, composer server including composer DB backup and connection server ADAM database VMware Knowledge Base

> Install windows 2019 CS as a replica to existing 2012 server.

> Once installation is finished, make sure replication is working fine between both servers by running repadmin command. This is critical before moving forward. VMware Knowledge Base

> Do the same for remaining 2019 servers.

> Decommission existing 2012 servers following VMware Knowledge Base . This should done as early as possible otherwise ADAM database may get corrupt since 2012 and 2019 server will be using different AD LDS schema and keeping both in replication for longer run may cause conflicts.

> After this you can migrate composer to 2019 server as below:

  • On new composer server, prepare the ODBC connection and create a system DSN to point to view composer DB.
  • On the old server, stop view composer service.
  • Install view composer on new server and point it to the ODBC.
  • Once installation is finished , login to view admin page.
    Navigate to View configuration > Servers > Edit > View composer >Edit and put the new server FQDN name and reauthenticate with user name and password > Click on 'Verify server information'    > Ok.
  • Test the provisioning now.

In case of any confusion or doubt, please contact vmware support.

View solution in original post

5 Replies
Shreyskar
VMware Employee
VMware Employee

High level steps to migrate connection server to 2019 OS will be as follow:

> Take a snapshot of all CS, composer server including composer DB backup and connection server ADAM database VMware Knowledge Base

> Install windows 2019 CS as a replica to existing 2012 server.

> Once installation is finished, make sure replication is working fine between both servers by running repadmin command. This is critical before moving forward. VMware Knowledge Base

> Do the same for remaining 2019 servers.

> Decommission existing 2012 servers following VMware Knowledge Base . This should done as early as possible otherwise ADAM database may get corrupt since 2012 and 2019 server will be using different AD LDS schema and keeping both in replication for longer run may cause conflicts.

> After this you can migrate composer to 2019 server as below:

  • On new composer server, prepare the ODBC connection and create a system DSN to point to view composer DB.
  • On the old server, stop view composer service.
  • Install view composer on new server and point it to the ODBC.
  • Once installation is finished , login to view admin page.
    Navigate to View configuration > Servers > Edit > View composer >Edit and put the new server FQDN name and reauthenticate with user name and password > Click on 'Verify server information'    > Ok.
  • Test the provisioning now.

In case of any confusion or doubt, please contact vmware support.

pasalott
Enthusiast
Enthusiast

So just to verify, the View Connection server should be migrated first, then the Composer server?

0 Kudos
a_p_
Leadership
Leadership

Unless there's something that I'm not aware of, the order in which you migrate the servers shouldn't matter, since you are not going to do a version upgrade.

André

Shreyskar
VMware Employee
VMware Employee

Yes.

0 Kudos