Horizon View Connection Server Migration


Any advise on “retiring” our Horizon View Connection Server that is on 2008 R2? We have a 2016 replica server up and running. Is it possible to just switch the connection broker settings over to the replica and update firewall rules and DNS? These are running 7.9 and the older server is pared with a security server.


We also have AirWatch running in the cloud, but I can enable IDM on the replica quickly.

View Reddit by CaptainBrownBeard42View Source

Related Articles


  1. Once you cut over to the new security server, make sure you cleanly remove it from your view cluster using the vdmadmin command. Make sure that no one else can connect to it. Proper decommissioning of a CS/SS:

    – Uninstall View Connection Server/Security server app from the Windows box.

    – Uninstall the ADLDS instance (I think it’s listed as VMware VD<something>)

    – On your new connection server run vdmadmin -S -r -s <old-CS-NetBIOS>

    – Wait for that to complete and see the change reflected in view admin.

    – Shut down old system.

  2. we just did this, 2008R2->2019. including going from Security server to UAG.

    get comfortable deploying UAG from powershell with the ini config and then once that is in place, proceed with connection servers.

    setup your new servers, install Horizon Connection Server and add them to the replication group. then remove all but the master CB using the vdmadmin command (including security servers)

    transfer the master role to one of the new servers:

    * login to the connection server you want to set as the new master server
    * open cmd as admin
    * dsmgmt
    * dsmgmt: roles
    * fsmo maintenance: connections
    * server connections: connect to server server:389
    * server connections: quit
    * fsmo maintenance: transfer naming master
    * fsmo maintenance: transfer schema master
    * verify status with repadmin /showreps server:389
    * if it failed to update, run the following to force the new server to seize the roles
    * fsmo maintenance: seize schema master
    * fsmo maintenance: seize naming master

    now remove the old master and you’re done

Leave a Reply

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