- #2012 R2 REMOTE DESKTOP SERVICES PROFILE PATH INSTALL#
- #2012 R2 REMOTE DESKTOP SERVICES PROFILE PATH UPDATE#
- #2012 R2 REMOTE DESKTOP SERVICES PROFILE PATH UPGRADE#
#2012 R2 REMOTE DESKTOP SERVICES PROFILE PATH INSTALL#
Join the destination servers running Windows Server 2016 to the Remote Desktop Services deployment and install the RD Gateway role Remove the source servers from the Remote Desktop Services deployment.įollow these steps to migrate RD Gateway servers:
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. 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: The User Profile Disks must be available at the same relative path in the new location as they were on 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.
#2012 R2 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. 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:
#2012 R2 REMOTE DESKTOP SERVICES PROFILE PATH UPGRADE#
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.
0 kommentar(er)
