Microsoft Launches Windows Server 2012 R2 Remote Desktop Apps

Microsoft Launches Windows Server Remote Desktop Web Client. By. July 17, 2018 In since March, Windows Server's Remote Desktop Web client became on Monday.

The Remote Desktop Web client is production-ready in 18 languages, according to Microsoft's announcement. It can work with Windows Server 2016 and Windows Server 2019 (in preview), but it'll also work with the older Windows Server 2008 R2 (and later) servers. End users can use this browser-based Web client to remotely access applications housed in datacenters. The applications and resources they access get published by their IT departments. The Web client gives end users a more lightweight and cross-platform option for accessing applications compared with Microsoft's native Remote Desktop client option.

For instance, via a URL, end users can access applications from anywhere using Chrome, Edge, Firefox, Internet Explorer 11 and Safari browsers (HTML5-based browsers). The Web client will run on Chromebook, Linux, macOS and Windows operating systems, but there's no support yet for mobile OSes.

End users sign into the Web client using a URL provided by the IT department and the Web client will show a list of applications and resources in an 'All Resources' tab in the browser. Users get single sign-on access and full-screen access to applications. Printing gets done via a PDF print capability. There's also keyboard and mouse support for the Web client. IT pros have to set up a Remote Desktop Gateway and a Remote Desktop Connection Broker to enable the remote access.

They also have to set up the Remote Desktop Web Access role on the server. One caveat is that the Web client doesn't work when Azure Application Proxy is part of the network mix.

Another caveat is that IT organization should ensure that per-user Client Access Licenses (CALs) are used, rather than per-device CALs. Microsoft's also suggested that 'your users will see better performance connecting to Windows Server 2016 (or later) and Windows 10 (version 1611 or later)' with the Web client. In other news of possible interest to IT pros, Microsoft last week released updated Administrative Templates (.ADMX) for the Windows 10 April 2018 Update (version 1803), which can be used to configure Group Policy for that operating system.

The updated templates were, although they were first available. It's not clear what changed, but the first version apparently was.

Automatically launching a program or application upon login to a Remote Desktop Session. See below for methods to use the “start program at login” policy which can be configured per user.

Another method to limit specific programs to a user is via RemoteApp. We have several other posts regarding RemoteApp and how to set it up and its limitations (i.e. RemoteApp setup is easier in 2008R2 (works in Workgroup mode) than 2012R2 but RDweb requires ActiveX (so IE only) and it doesn’t work for MAC users, while use of RemoteApp in 2012R2 requires joining to a Domain). 1) USING ENVIRONMENT TAB OF EACH USER’S PROPERTIES ON SERVER: If you want a program to automatically start when a user logs on to the RDP server instead of showing a full desktop session, you can configure this in the Environment tab of the Properties window for each particular user.

After you have made the changes, you should test that it works properly for your users by logging into the server using the accounts you changed/created including testing it with simultaneous sessions and to verify the sessions close properly when the application is closed. We highly recommend enabling policy to log off disconnected sessions:. Enable policy to log off disconnected sessions immediately or within a few minutes so you don’t have a blank screen if users don’t properly exist a program. Existing the program (instead of clicking X in upper right corner of program) will properly log off the session but enabling this policy will ensure that an improper disconnected session is automatically logged off. See block post here for instructions on how to enable this policy on both 2012R2 and 2008R2 2 ) USING PROGRAMS TAB ON REMOTE DESKTOP CLIENT – Another method is to use the programs tab on your local remote desktop client prior to logging in to the server.

On the programs tab, you can enter the path for program to start upon login. You can also create a RDP shortcut with this information saved on to your desktop. We have a video on our website on creating RDP shortcuts –. A disadvantage to this method versus the first method above is that each user can edit the shortcut and change the settings.

Your IT person can create these shortcuts and provide them to each user. If you use this method on Windows 2008R2, you may have to change settings in RemoteApp under RDP Settings Change and allow access to unlisted programs. 3) USING GROUP POLICY – Another method to configure this is to configure programs to automatically start in the RD Session Host Configuration settings and in Group Policy, although then the logon settings could be applied universally to all users, including the Administrator (which means Administrator may not be able to access the desktop, start button, etc.) whereas the method above allows configuration by User. You could also create a separate group policy that would be applicable for a specific group, such as non-administrators, so the group policy change wouldn’t affect all users. 4) REMOTEAPP – Another method is to configure the RemoteApp feature in Remote Desktop Services (RDS).

Microsoft Windows Server 2012 R2 Standard

In 2008R2, this feature works great (either the RemoteApp distributable file or RD Web) for PC users but not for MAC users. In 2012R2, the RemoteApp features requires the Active Directory / Domain Controller service to be install on the server before RemoteApp can be used. This entry was posted in, and tagged, on. Post navigation.