- SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH INSTALL
- SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH UPDATE
- SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH UPGRADE
- SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH WINDOWS
Migrate certificates to the destination servers running Windows Server 2016. Use IIS Web Deploy tool to migrate the RD Web website settings from the current RD Web Access servers to the destination servers running Windows Server 2016.
SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH INSTALL
Join the destination servers running Windows Server 2016 to the Remote Desktop Services deployment and install the RD Web role Migrate RD Web Access serversįollow these steps to migrate RD Web Access servers: Remove all RD Virtualization Host servers that required migration from the virtual desktop collection in the source server.Ī virtual desktop collection of RD Virtualization Host servers with a mix of servers running Windows Server 2012 R2 and Windows Server 2016 is not supported. Migrate all virtual machines in the current virtual desktop collection that are running on RD Virtualization Host servers to the new servers.
SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH UPGRADE
Upgrade the virtual desktop collection from the server running Windows Server 2012 R2 to Windows Server 2016.Īdd the new Windows Server 2016 RD Virtualization Host servers to the virtual desktop collection. Migrate virtual desktop collections only after successfully completing the previous step, Migrate RD Connection Broker servers. The User Profile Disks must be available at the same relative path in the new location as they were on the source server.Ī session collection of RD Session Host servers with a mix of servers running Windows Server 2012 R2 and Windows Server 2016 is not supported.įollow these steps to migrate a virtual desktop collection from a source server running Windows Server 2012 R2 to a destination server running Windows Server 2016.
SERVER 2016 REMOTE DESKTOP SERVICES PROFILE PATH UPDATE
If the UVHD template (UVHD-template.vhdx) is enabled in the session collection and the file server has been migrated to a new server, update the User Profile Disks: Location collection property with the new path. Sign out of all sessions in the RD Session Host servers, and remove the servers that require migration from the session collection. Upgrade the session collection from Windows Server 2012 R2 to Windows Server 2016.Īdd the new RD Session Host server running Windows Server 2016 to the session collection. Migrate session collections only after successfully completing the previous step, Migrate RD Connection Broker servers. Migrate session collectionsįollow these steps to migrate a session collection in Windows Server 2012 R2 to a session collection in Windows Server 2016. Upgrade the remaining RD Connection Broker server in the deployment to Windows Server 2016.Īdd Windows Server 2016 RD Connection Broker servers into the high availability deployment.Ī mixed high availability configuration with Windows Server 2016 and Windows Server 2012 R2 is not supported for RD Connection Broker servers.Īn RD Connection Broker running Windows Server 2016 can serve session collections with RD Session Host servers running Windows Server 2012 R2, and it can serve virtual desktop collections with RD Virtualization Host servers running Windows Server 2012 R2. If you have more than one RD Connection Broker server in the high availability setup, remove all the RD Connection Broker servers except the one that is currently active. For more information, see Deploy a Remote Desktop Connection Broker cluster. The Remote Desktop Connection Broker (RD Connection Broker) source servers must be configured for high availability to support migration.
This is the first and most important step for migrating: migrating your RD Connection Brokers to destination servers running Windows Server 2016. Use the following steps to migrate your Remote Desktop Services deployment: The only components with a direct migration are RD Web, RD Gateway, and the licensing server.įor more information on the upgrade process and requirements, see upgrading your Remote Desktop Services deployments to Windows Server 2016. Instead, for most of the RDS components, you first upgrade to Windows Server 2016 and then migrate data and licenses. In other words, there is no direct in-place migration from RDS in Windows Server 2012 R2 to Windows Server 2016. Migration for a Remote Desktop Services deployment is supported from source servers running Windows Server 2016 to destination servers running Windows Server 2016. If you are currently running Remote Desktop Services in Windows Server 2012 R2, you can move to Windows Server 2016 to take advantage of new features like support for Azure SQL and Storage Spaces Direct. Migrate your Remote Desktop Services deployment to Windows Server 2016
0 kommentar(er)
