Windows Virtual Desktop is a comprehensive desktop and app virtualization service running in the cloud. It’s the only virtual desktop infrastructure (VDI) that delivers simplified management, multi-session Windows 10, optimizations for Office 365 ProPlus, and support for Remote Desktop Services (RDS) environments. Enter the Remote Desktop Services directory, and launch Remote Desktop Licensing Manager.) Verify the connection method for the Remote Desktop license server: right-click the license server to which you want to migrate the RDS CALs, and then click Properties.
Windows 10 has a Store app (Universal Windows Platform) called 'Remote Desktop'. You can use it to connect to a remote PC or virtual apps and desktops made available by your admin. The app helps you be productive no matter where you are. It is possible to backup and restore its options. This is very useful, because you can restore them when required or transfer them to another PC or user account.
RECOMMENDED: Click here to fix Windows errors and optimize system performance
The Remote Desktop app can be installed from the Store.
For the Remote Desktop Store (UWP) app, you can manually backup the following options and preferences:
Jquery Migrate
- General settings
- Connections (remote PCs)
- Stored credentials
- Groups
Using your backup data, you'll be able to quickly restore connections and their options, user accounts for your connections, and custom groups to organize your connections.
If you use the Remote Desktop Store app frequently, you may be interested in creating a backup copy of your settings and preferences of the app, so you could manually restore them when required or apply them to another account on any Windows 10 PC. Here is how it can be done.
To backup the News app in Windows 10, do the following.
- Close theRemote Desktop app. You can terminate it in Settings.
- Open the File Explorer app.
- Go to the folder %LocalAppData%Packages. You can paste this line to the address bar of File Explorer and hit the Enter key.
- Right-click on the folder Microsoft.RemoteDesktop_8wekyb3d8bbwe and select 'Copy' in the context menu, or press the Ctrl + C key sequence to copy it.
- Paste the folder to some safe location.
That's it. You just created a backup copy of your Remote Desktop app settings. To restore them or move to another PC or user account, you need to place them under the same folder.
Restore Remote Desktop in Windows 10
- Close Remote Desktop. You can terminate it in Settings.
- Open the File Explorer app.
- Go to the folder %LocalAppData%Packages. You can paste this line to the address bar of File Explorer and hit the Enter key.
- Here, paste the folder Microsoft.RemoteDesktop_8wekyb3d8bbwe. Overwrite the files when prompted.
Now you can start the app. It should appear with all your previously saved settings.
Note: The same method can be used to backup and restore options for other Windows 10 apps. See the articles
RECOMMENDED: Click here to fix Windows errors and optimize system performance
-->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.
Migration for a Remote Desktop Services deployment is supported from source servers running Windows Server 2016 to destination servers running Windows Server 2016. In other words, there is no direct in-place migration from RDS in Windows Server 2012 R2 to Windows Server 2016. Instead, for most of the RDS components, you first upgrade to Windows Server 2016 and then migrate data and licenses. The only components with a direct migration are RD Web, RD Gateway, and the licensing server.
For more information on the upgrade process and requirements, see upgrading your Remote Desktop Services deployments to Windows Server 2016.
Use the following steps to migrate your Remote Desktop Services deployment:
Migrate RD Connection Broker servers
This is the first and most important step for migrating: migrating your RD Connection Brokers to destination servers running Windows Server 2016.
Important
The Remote Desktop Connection Broker (RD Connection Broker) source servers must be configured for high availability to support migration. For more information, see Deploy a Remote Desktop Connection Broker cluster.
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.
Upgrade the remaining RD Connection Broker server in the deployment to Windows Server 2016.
Add Windows Server 2016 RD Connection Broker servers into the high availability deployment.
Note
A mixed high availability configuration with Windows Server 2016 and Windows Server 2012 R2 is not supported for RD Connection Broker servers.An 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.
Migrate session collections
Follow these steps to migrate a session collection in Windows Server 2012 R2 to a session collection in Windows Server 2016.
Important
Migrate session collections only after successfully completing the previous step, Migrate RD Connection Broker servers.
Upgrade the session collection from Windows Server 2012 R2 to Windows Server 2016.
Add the new RD Session Host server running Windows Server 2016 to the session collection.
Sign out of all sessions in the RD Session Host servers, and remove the servers that require migration from the session collection.
Note
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. The User Profile Disks must be available at the same relative path in the new location as they were on the source server.
A session collection of RD Session Host servers with a mix of servers running Windows Server 2012 R2 and Windows Server 2016 is not supported.
Migrate virtual desktop collections
Migrate Microsoft Remote Desktop Mac Version 10 13
Follow 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.
Important
Migrate virtual desktop collections only after successfully completing the previous step, Migrate RD Connection Broker servers.
Upgrade the virtual desktop collection from the server running Windows Server 2012 R2 to Windows Server 2016.
Add the new Windows Server 2016 RD Virtualization Host servers to the virtual desktop collection.
Migrate all virtual machines in the current virtual desktop collection that are running on RD Virtualization Host servers to the new servers.
Remove all RD Virtualization Host servers that required migration from the virtual desktop collection in the source server.
Note
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. The User Profile Disks must be available at the same relative path in the new location as they were on the source server.
Migrate Microsoft Remote Desktop Mac Version 10 1
A 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 RD Web Access servers
Follow these steps to migrate RD Web Access servers:
Join the destination servers running Windows Server 2016 to the Remote Desktop Services deployment and install the RD Web role
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.
Migrate certificates to the destination servers running Windows Server 2016.
Remove the source servers from the Remote Desktop Services deployment.
Migrate RD Gateway servers
Follow these steps to migrate RD Gateway servers:
Join the destination servers running Windows Server 2016 to the Remote Desktop Services deployment and install the RD Gateway role
Use IIS Web Deploy tool to migrate the RD Gateway endpoint settings from the current RD Gateway servers to the destination servers running Windows Server 2016.
Migrate certificates to the destination servers running Windows Server 2016.
Remove the source servers from the Remote Desktop Services deployment.
Migrate RD Licensing servers
Follow these steps to migrate an RD Licensing server from a source server running Windows Server 2012 or Windows Server 2012 R2 to a destination server running Windows Server 2016.
Migrate the Remote Desktop Services client access licenses (RDS CALs) from the source server to the destination server.
Edit the Deployment Properties in Server Manager on the Remote Desktop management server (which is typically being run on the first RD Connection Broker server) to include only the new RD Licensing servers running Windows Server 2016.
Deactivate the source RD Licensing server: In Remote Desktop Licensing Manager, right-click the appropriate server, hover over Advanced to select Deactivate Server, and then follow the steps in the wizard.
Remove the source RD Licensing servers from the deployment in Server Manager on the Remote Desktop management server.
Migrate certificates
Migrate Microsoft Remote Desktop Mac Version 10 10 5
Successful certificate migration requires both the actual process of migrating certificates and updating certificate information in the Remote Desktop Services Deployment Properties.
Typical certificate migration includes the following steps:
Export the certificate to a PFX file with the private key.
Import the certificate from a PFX file.
Django Migrate
After migrating the appropriate certificates, update the following required certificates for the Remote Desktop Services deployment in server manager or PowerShell:
RD Connection Broker - single sign-on
RD Connection Broker - RDP file publishing
RD Gateway - HTTPS connection
RD Web Access - HTTPS connection and RemoteApp/desktop connection subscription