This topic describes how to enable secure, Single Sign-On (SSO) access and enforce multi-factor authentication (MFA) via WS-Federation to Remote Desktop (RD) Web Access Server (2019 R2). On a server running Windows Server 2012 or above, launch Server Manager Add Roles and Features and ensure the following features are available. Remote Web Workplace (RWW) has been a key feature for the SBS line of products since SBS 2003. It provides a central web location for remote workers to access corporate resources no matter where they are. With the onset of Windows Small Business Server (SBS) 2011 Standard, the new name for RWW is RWA or Remote Web Access. How to connect RD Web Access on the Client system 1. Type the URL of the RD Web Access Web site into a Web browser. By default, you can access the RD Web Access Web site on the following location. Where servername is the fully qualified domain name of the Web server where you installed RD Web Access: For example: https://hostname.domain/rdweb.
How to connect RD Web Access on the Client system
This is great information. I know it’s been awhile but I’ve installed RDS on 2012R2, one server is running all the functions, RD Web, RD Gateway, RD Licensing, RD Connection broker. I installed the RSA web agent for IIS and configured RSA to protect all the pages. It works fine but it removed the sign out page on RDWeb. However, there is a vulnerability in the method used to encrypt sessions in earlier versions of RDP. This vulnerability can allow unauthorized access to your session using a man-in-the-middle attack. Remote Desktop can be secured using SSL/TLS in Windows Vista, Windows 7, Windows 8, Windows 10 and Windows Server 2003/2008/2012/2016.
1.Type the URL of the RD Web Access Web site into a Web browser.
By default, you can access the RD Web Access Web site on the following location. Where server_name is the fully qualified domain name of the Web server where you installed RD Web Access: https://server_name/rdweb
For example:
or
NOTE: To use RD Web Access, client computers must be running at least Internet Explorer 6.0 and a version of Remote Desktop Connection (RDC) that supports at least Remote Desktop Protocol (RDP) 6.1.
NOTE: RD Web Access requires Internet Explorer 6.0 or later.
2.Enter the user name and password to log in to the RD Web Access Web site.
Rd Web Access Windows 10 Free
3.Use the RemoteApp programs or Remote Desktop Option to connect the RD Web Access.
a.Connect to RD Web Access with RemoteApp Programs option:
b.Connect to RD Web Access with Remote Desktop option:
NOTE: The Internet Explorer 11 (Edge) does not support all RD Wed Access function. In order to use the RemoteApp programs option with Internet Explorer 11 (Edge), follow the instructions:
1. Press [F12] on the Internet Explorer.
You will see the developer tools.
2. Click on the Emulation (Crtl + 8) [Browser Mode IE11].
You are able to see all the previous version of Internet Explorer such as, IE 10, IE9, IE8 and IE7 in the User agent string.
How To Access Rd Web Access
3. Choose [Internet Explorer 10 or previous versions].
The screen reloads automatically.
Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016
Supported OS upgrades with RDS role installed
Upgrades to Windows Server 2016 are supported only from Windows Server 2012 R2 and Windows Server 2016.
Flow for deployment upgrades
In order to keep the down-time to a minimum, it is best to follow the steps below:
RD Connection Broker servers should be the first to be upgraded. If there is active/active setup in the deployment, remove all but one server from the deployment and perform an in-place upgrade. Perform upgrades on the remaining RD Connection Broker servers offline and then re-add them to the deployment. The deployment will not be available during RD Connection Broker servers upgrade.
Note
It is mandatory to upgrade RD Connection Broker servers. We do not support Windows Server 2012 R2 RD Connection Broker servers in a mixed deployment with Windows Server 2016 servers. Once the RD Connection Broker server(s) are running Windows Server 2016 the deployment will be functional, even if the rest of the servers in the deployment are still running Windows Server 2012 R2.
RD License servers should be upgraded before you upgrade your RD Session Host servers.
Note
Windows Server 2012 and 2012 R2 RD license servers will work with Windows Server 2016 deployments, but they can only process CALs from Windows Server 2012 R2 and older. They cannot use Windows Server 2016 CALs. See License your RDS deployment with client access licenses (CALs) for more information about RD license servers.
RD Session Host servers can be upgraded next. To avoid down time during upgrade the admin can split the servers to be upgraded in 2 steps as detailed below. All will be functional after the upgrade. To upgrade, use the steps described in Upgrading Remote Desktop Session Host servers to Windows Server 2016.
RD Virtualization Host servers can be upgraded next. To upgrade, use the steps described in Upgrading Remote Desktop Virtualization Host servers to Windows Server 2016.
RD Web Access servers can be upgraded anytime.
Note
Upgrading RD Web may reset IIS properties (such as any configuration files). To not lose your changes, make notes or copies of customizations done to the RD Web site in IIS.
Note
Windows Server 2012 and 2012 R2 RD Web Access servers will work with Windows Server 2016 deployments.
RD Gateway servers can be upgraded anytime.
Note
Windows Server 2016 does not include Network Access Protection (NAP) policies - they will have to be removed. The easiest way to remove the correct policies is by running the upgrade wizard. If there are any NAP policies you must delete, the upgrade will block and create a text file on the desktop that includes the specific policies. To manage NAP policies, open the Network Policy Server tool. After deleting them, click Refresh in the Setup tool to continue with the upgrade process.
Note
Windows Server 2012 and 2012 R2 RD Gateway servers will work with Windows Server 2016 deployments.
Rd Web Access Windows 10 Pro
VDI deployment – supported guest OS upgrade
Administrators will have the following options to upgrade of VM collections:
Upgrade Managed Shared VM collections
Administrators will need to create VM templates with the desired OS version and use it to patch all the VMs in the pool.
We support the following patching scenarios:
- Windows 7 SP1 can be patched to Windows 8 or Windows 8.1
- Windows 8 can be patched to Windows 8.1
- Windows 8.1 can be patched to Windows 10
Upgrade unmanaged shared VM collections
End users cannot upgrade their personal desktops. Administrators should perform the upgrade. The exact steps are still to be determined.