Top Support Solutions for Windows Server 2012 and Windows Server 2012 R2 by TechNet Blogs post

I'd like to share one of useful TechNet blogs posts, Top Support Solutions for Windows Server 2012 and Windows Server 2012 R2. This post shared a lot of web sites for troubleshooting the following Windows Features, DirectAccess, Active Directory related, unexpected errors and restarts, Remote Desktop Services, Windows updates related, Failover Clustering, DNS and Access to file shares (SMB). 

We may find some hints from the web sites for troubleshooting the above Windows Features. Don't forget to bookmark this web site.

This posting is provided “AS IS” with no warranties, and confers no rights!

Microsoft Azure RemoteApp preview

Nowadays, administrators can use Remote Desktop from many devices like Windows, iOS, Android, Mac OS and so on to access the Remote Desktop. RemoteApp is a feature of Remote Desktop Services to install and publish applications on Remote Desktop.

In this year, Microsoft announced Azure RemoteApp Preview to allow administrators to publish applications through Microsoft Azure platform. Azure RemoteApp Preview supports 2 scenarios, cloud deployment and hybrid deployment. For cloud deployment, administrators can use Office 2013 pro plus to experience Azure Remote App from their devices. The template with Office 2013 pro plus is based on Windows Server 2012 R2 which is provided by Microsoft Azure platform.

Remark: For hybrid or cloud deployment, the operating system of templates must be installed Windows Server 2012 R2.

For hybrid deployment, administrators can upload their templates with their bueiness applications to Azure platform and then publish it for users to use it. To configure hybrid deployment, administrators need to set up VPN connection between Microsoft Azure. At this moment, RemoteApp doesn't support ExpressRoute. Then, administrators need to set up Active Directory synchronization between Azure Active Directory and on-premise Active Directory to allow users to use the same credentials when they use applications.

Remark: Azure RemoteApp doesn't support offline mode. Users need to have Internet connection to use applications which are published on Azure.

Azure RemoteApp is free during the preview period.

If you are interested in Azure RemoteApp, please sign up and try it.

Microsoft Azure RemoteApp

More information

Corporate Apps Anywhere, Anytime with Microsoft Azure RemoteApp

Azure RemoteApp Deep Dive

This posting is provided “AS IS” with no warranties, and confers no rights!

Choose an appropriate Remote Desktop Licensing server for your environment

The latest Windows version can be installed the current and previous Remote Desktop Licensing or Terminal Services Licensing licenses in the server. For an example, Windows Server 2008 R2 can be installed Windows Server 2008 R2 and previous Remote Desktop or Terminal Services licenses in the server. However, Windows Server 2008 R2 cannot be installed Remote Desktop or Terminal Services licenses of Windows Server 2012 later because it cannot support the future version of Windows. To deploy the latest Remote Desktop environment, administrators have to install the latest Windows for Remote Desktop Services Licensing.

For more detail, please read "RDS and TS CAL Interoperability Matrix".

This posting is provided “AS IS” with no warranties, and confers no rights!

Query and Reset the Remote Desktop session by Command on Windows Server 2012

To check and reset the current console and remote session on the Windows Server, we can use "Terminal Services Manager" (Remote Desktop Services Manager on Windows Server 2008 R2) to verify it. However, on Windows Server 2012, "Remote Desktop Services Manager" has been integrated into Server Manager. It cannot check the session. So I need to perform command, "qwinsta" and "rwinsta" to check and reset the remote session.

Prerequisites

• Make sure the user account is a member of Remote Desktop Users or local Administrators group on servers

Using qwinsta check the session

1. On the server, log in as Domain Administrator.

2. Launch "Command Prompt".

3. To query the current session of the local server, perform "qwinsta".

There is a console session which is logged on by Administrator on this computer.

4. To query the current session of the remote server, perform "qwinsta /server:<Server Name>".

The administrator and Mark logged on the Remote Server.

Using rwinsta reset the session

5. Still on the "Command Prompt", perform "rwinsta /server:<Server Name> <Session ID>" to reset the remote session.

To reset the remote session for a non-domain server or workstation, you can use "PsExec" to connect the server or workstation and then perform "qwinsta" and "rwinsta".

Download link

PsExec

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

References:

QWINSTA and RWINSTA

http://www.happysysadm.com/2010/07/qwinsta-and-rwinsta.html

This posting is provided “AS IS” with no warranties, and confers no rights!

Configuring Remote Desktop Gateway option in Remote Desktop Web Connection

In "RD Web Access", there is no option to enable Remote Desktop Gateway. Therefore, administrator can configure the default Remote Desktop Gateway for users in IIS.

Assuming Remote Desktop Gateway and Remote Desktop Web Access were installed in the same server named "rdg.contoso.com"

To configure Remote Desktop Gateway, please read "Deploying Remote Desktop Gateway in workgroup environment" for your reference.

1. At "rdg.contoso.com", log in as Administrator.

2. Launch "Internet Information Services (IIS) Manager".

3. Expand "RDG > Sites > Default Web Site > RDWeb > Pages".

4. In the detail pane, double-click "Application Settings".

By default, there is no Remote Desktop Gateway to be assigned.

5. Double-click "DefaultTSGateway".

6. Under "Value", type "rdg.contoso.com".

7. Click "OK".

Now, all Remote Desktop Connection in Remote Desktop Web Access is through the Remote Desktop Gateway, "rdg.contoso.com".

Remark: To configure the above settings of Terminal Services Gateway, the IIS path is "<Server Name> > Sites > Default Web Site > TS".



Reference:

Configure Remote Desktop Web Connection Behavior

http://technet.microsoft.com/en-us/library/cc731465.aspx

Forcing the Remote Desktop option in TS Web Access to use TS Gateway

http://blogs.technet.com/b/askperf/archive/2008/08/19/forcing-the-remote-desktop-option-in-ts-web-access-to-use-ts-gateway.aspx

This posting is provided “AS IS” with no warranties, and confers no rights!

Deploying Remote Desktop Gateway in workgroup environment

Installing and Configuring Remote Desktop Gateway or Terminal Services Gateway

Prerequisites

1. Operating Systems: Windows Server 2008 or Windows Server 2008 R2

2. The server could be accessed from Internet

3. A domain name registered domain service provider

To deploy Remote Desktop Gateway in Windows Server 2012 or Windows Server 2012 R2, please read the following post.
Deploying Remote Desktop Gateway in Windows Server 2012 or Windows Server 2012 R2 workgroup environment

Renaming the server for Remote Desktop Gateway

I will install remote desktop gateway on Windows Server 2008 R2. Assuming I registered a domain name, contoso.com, on Internet.

1. At a server, log in as Administrator.
2. Click "Start", enter "sysdm.cpl".
3. Select "Computer Name" tab, click "Change".
4. Under "Computer name", type "rdg".
5. Click "More".
6. Under "Primary DNS suffix of this computer", type "contoso.com".
7. Click "OK" three times.

You have to provide the FQDN for generating the certificate.

8. Click "Close".

9. Restart the computer.


Installing the Remote Desktop Gateway server role

1. At "rdg.contoso.com", log in as Administrator.

2. Click "Server Manager".

3. Right-click "Roles", select "Add Roles".

4. At "Before You Begin", click "Next".

5. Check "Remote Desktop Services".

6. Click "Next" twice.

7. Check "Remote Desktop Gateway", click "Add Required Role Services".

8. Click "Next".

9. Select "Choose a certificate for SSL encryption later".

10. Click "Next".

11. At "Authorization Policies", select "New".

12. Click "Next".

13. At "RD Gateway User Groups", you can add users or groups to use this Remote Desktop Gateway.

14. I would like to let Administrators group use this Remote Desktop Gateway, click "Next".

15. At "RD CAP", you can change the name select the authentication method for Remote Desktop Gateway.

16. Click "Next".

17. At "RD RAP", you can control which computers can be remote control through this Remote Desktop Gateway.

18. Select "Allow users to connect to any computer on the network".

Remark: You can change the settings of "RD CAP" and "RD RAP" after installing Remote Desktop Gateway.

19. Click "Next" twice.

20. Still check "Network Policy Server", click "Next" twice.

21. Leave the default IIS settings, click "Next".

22. Click "Install".

23. When installation finished, click "Close".


Create a self-signed certificate for Remote Desktop Gateway

1. At "rdg.contoso.com", log in as Administrator.

2. Launch "Remote Desktop Gateway Manager".

3. Right-click "RDG", select "Properties".

4. Select "SSL Certificate" tab.

5. Click "Create and Import Certificate".

6. Next to "Certificate name", make sure the name is same as your Internet domain name.

7. Check "Store the root certificate".

Remark: You can use the third-party certificate which is signed by Trust Root CA.

Remark: Remote Desktop Gateway supports wildcard certificate.

8. Click "OK" twice.

The certificate was installed in the server.

9. Click "OK".

Configuring the remote desktop connection

To connect Remote Desktop Gateway, the Remote Desktop Gateway version must be 6.0 or later.

Prerequisites

You have to install the certificate which was generated by "rdg.contoso.com".

1. Copy the RDG certificate to a workstation you want to use.

2. Right-click the certificate,"RDG", click "Install Certificate".

3. At welcome screen, click "Next".

4. Select "Place all certificate in the following store", click "Browse".

5. Select "Trusted Root Certification Authorities", click "OK".

6. Click "Next".

7. Click "Finish".

8. Click "Yes" to accept install the certificate.

Configure Remote Desktop Connection

1. At a workstation, launch "Remote Desktop Connection".

2. At "Remote Desktop Connection", click "Options".

3. Select "Advanced" tab.

4. Next to "Connect from anywhere", click "Settings".

5. Select "Use these RD Gateway server settings".

6. Next to "Server name", type "rdg.contoso.com".

7. Next to "Logon settongs", un-check "Use my RD Gateway credentials for the remote computer".

8. Click "OK".

9. Select "General" tab.

Now, you can remote the other computers through the Remote Desktop Gateway.

Remark: A computer installed Windows Vista or later need to be entered "Computer Name\User Name" for RD Gateway Server Credentials.

Remark: For Windows XP, you have to modify the registry to support Network Level Authentication.

1. Launch "Registry Editor".

2. Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\Lsa".

3. In the detail pane, double-click "Security Packages".

4. Add "tspkg" in the bottom.

5. Click "OK".

6. Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders".

7. In the detail pane, double-click "SecurityProviders".

8. Type "credssp.dll" at the end of value.

9. Click "OK".

10. Close "Registry Editor".

11. Restart the computer.

References:

Description of the Credential Security Support Provider (CredSSP) in Windows XP Service Pack 3

http://support.microsoft.com/kb/951608

Building a Remote Desktop Gateway (RDG) / RD Gateway Server

http://www.rayheffer.com/953/building-a-remote-desktop-gateway-rdg-rd-gateway-server/

Additional info:
Deploying RD Gateway R2 server with NAP
http://blogs.msdn.com/b/rds/archive/2009/08/17/deploying-rd-gateway-r2-server-with-nap.aspx

Improving TS Gateway availability using NLB
http://blogs.msdn.com/b/rds/archive/2009/03/24/improving-ts-gateway-availability-using-nlb.aspx

This posting is provided “AS IS” with no warranties, and confers no rights!