Windows vCenter 6.0 to Appliance vCenter 6.7: Horizon Composer Migration?

[noexistence]

Ok this is probably a obvious question but I'm upgrading my Windows vCenter 6.0 to the Appliance vCenter 6.7.  On the windows server I also have the Horizon Composer 7.8 service.  Now I've already upgraded my other vCenter server to the appliance and i know it shuts down the old Windows vCenter server.

So now for the probably obvious answer, but I'm assuming the vCenter Appliance will not migrate my Horizon Composer services and that I'll need to migrate the Composer to another server BEFORE migrating my vCenter to the 6.7 vCenter Appliance?    Thanks!

[scott28tt]

Moderator: Moved to Horizon Discussions

[rsaulitis · Accepted solution]

Hi @noexistence 

Yes You must migrate Composer to another windows server before migrating vCenter to vCSA. You can find Composer migration scenarios here:

https://docs.vmware.com/en/VMware-Horizon-7/7.9/horizon-administration/GUID-D9EE3EA8-8F71-44BE-B988-...

I would suggest to move from linked clones to instant clones, because linked clones are slowly dying, and then You will not need Composer anymore.

To be able to move from linked clones to instant clones you need to update Horizon to version 7.13 - on this version instant clones now are supported in standard and advanced version. You can read all new things about 7.13 here:

https://techzone.vmware.com/blog/whats-new-horizon-713-client-552009-app-volumes-4-2009-and-dynamic-...

In Horizon 8 linked clones are fully removed, so it would be nice start point to migrate from linked clones to instant clones before going to version 8.

[noexistence]

Thanks for the info rsaulitis!  Also thanks for the heads up on Linked-clones/Instant Clones.  I can't migrate to Horizon 7.13 as I am running a SQL server that isn't supported after 7.10 😞  Thanks again!

[rsaulitis]

@noexistence I would suggest for You to:

Before taking look in my suggested steps check if you current vCenter version is supported with Horizon 7.13.  https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&569=&2=

1. Install new windows server (trial version for server and sql) with supported version of SQL for Horizon 7.13. Migrate database to newly installed server. How to migrate composer DB you can look here https://www.pascalswereld.nl/2017/10/03/migrating-horizon-databases/
2. Install new windows server (trial version) for Composer and then migrate composer to newly installed server. https://docs.vmware.com/en/VMware-Horizon-7/7.9/horizon-administration/GUID-F84681E3-4CA7-402D-959C-...
3. Update Horizon to 7.13 version
4. Prepare windows 10 golden image for instant clones. Here will be very good guide https://techzone.vmware.com/creating-optimized-windows-image-vmware-horizon-virtual-desktop#1150974
5. Create new pool with instant clones
6. Assign to some of users and let them to test for a week
7. If all is good, replace all linked clones with instant clones
8. Remove composer service from Horizon and shutdown server
9. Shutdown composer DB
10. You have decommissioned two windows servers and that's great success :))))

I would say it's possible to do that all in one month so with trial of windows servers would be enough.

Also be aware of Event database, if it's also on same old DB server where is composer DB, then You cannot update Horizon. Of course You can update only events will not work 🙂 I would suggest to find some newer existing SQL server for event database.

P.S

Don't forget about backups and be carefully.

[noexistence]

Thanks for the info.  The issue isn't technical, it's budgetary.  SQL 2019 Standard licensing will be $16,000 CAD and we just purchased O365 and Exchange 2019.  So a SQL upgrade wasn't in the cards this fiscal.  Thanks again for the help!