![]() While the size of the Remote Desktop session can still be set when you initiate the connection, you can also now freely adjust it while being connected.įirst, you’ll need to connect from Windows 8.1/Server 2012 R2 to Windows 8.1/Server 2012 R2 (or newer). In Windows 8.1 and Windows Server 2012 R2, Remote Desktop Connection client ( mstsc.exe) introduces resolution and scaling support, among other things. There’s also the fabulous Remote Desktop Manager, which does all this and “just works”, but it’s not free Admittedly, paying for good software is something we all should do more often, but still, $84,99 for a tool I already (kind of) have as part of the OS seems too steep. Several tools, like Remote Desktop Connection Manager from Microsoft ( download) have kind of resolved this issue, but it would always mean an additional software install on whatever host system you were working on. Just small enough as not to fill your desktop (and to fit in a window, so less than your max resolution on the host), but large enough to actually be useful. Before clicking Connect you have to scroll the slider from Large (Full screen) to something smaller. You first have to close the current connection, and start a new connection. Experienced RDP users know how to do this, but less regular users always seem to struggle with this view: Remote Desktop with default settings My number one gripe with RDP has in the past few years been the amazingly clumsy way to resize a remote session from full screen to something smaller. Today while being connected to my home server to do some development work I decided to test if the new features in Remote Desktop (RDP) work or provide any real benefits. I remember reading about this feature when Windows 8.1 was made generally available in late 2013, but I didn’t have time then to try this out. At this point you are ready to unauthorize and uninstall the old server.Thanks for reading my blog! If you have any questions or need a second opinion with anything Microsoft Azure, security or Power Platform related, don't hesitate to contact me. The wizard will transfer your licenses to the new server. ![]() When you have added all your licenses click Next. Click Next.Īt this point, you need to type your keys or agreement number and confirm the licenses with the Add button. In the next step, you have to identify the old, decommissioned server, by typing his name or IP address. As the first step, select Migrate licenses form another server to this license server and select the reason (in most cases is The source server is begin replaced by this license server). This will open the Manage licenses wizard. To do this, you have to right click on the newly installed server and select Manage Licenses. The next step is transferring the licenses from the old server to the new one. In the Server Manager menu Tools, Terminal Services, open the Remote Desktop Licensing Manager, right click on the installed server and select Activate server.Īdd your data and complete the activation wizard. Later, on Remote Desktop Services, on the step Role Services, you have to check Remote Desktop Licensing (of course you can check also other functionalities if you need them). Here you have to select Role-based or Feature-based installation and in the Server Role step you have to check Remote Desktop Services. ![]() The first step is the installation of the RDP Licensing role in Server Manager true Add Roles and Features Wizard. The process is easy, but before you start the migration, is necessary to have the documentation for all licenses (you need authorization numbers or keys during the migration process). I want to explain the process of migrating licenses from Windows Server 2008R2 to Server 2012. This job is done by the RDP Licensing server. One of the things we have to do when we upgrade our server environment, is to migrate licenses for the RDP clients.
0 Comments
Leave a Reply. |