Tag: Terminal Services

When I tried to configure my Remote Desktop Web Access on Server 2012 I had a problem. I was unable to connect to the internal computers (they were not accessible on the network).
This is happens because RD Gateway configuration is missing (picture).

You can solve this issue in two ways. The first way is simply by typing RD Gateway in the IIS configuration. To see the configuration you have to open IIS and navigate to Sites > Default Web Site > RDWeb > Pages > en-US (or other language). There you have to click on Application Settings and write the public name of TS Gateway to the variable Default TS Gateway. You can also change some other setting like GatewayCredentialSource and others, but be careful.
The second way to correct this issue is editing web.config in the folder C:windowsWebRDWebPagesen-US. Here you can manually add TS Gateway. Web.config will look like this:
<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
    <appSettings>
        <remove key=”PasswordChangeEnabled” />
        <remove key=”DefaultTSGateway” />
        <add key=”DefaultTSGateway” value=”rdweb.public.com” />
        <add key=”PasswordChangeEnabled” value=”true” />
    </appSettings>
</configuration>
After this change, try to connect to the internal computers. They should work..

In many cases I still see, that administrators don’t install applications for publishing on terminal servers correctly.
I want to tell you once again, that the right installation of those applications is a crucial point for good working in Remote application mode. Here is the right way how to prepare the environment to install those applications from command prompt:

• Before the installation, you must enable the “installation mode” with the command change user /install. This has to be executed from elevated command prompt.
• Install the application (from command prompt …).
• After you installed the applications successfully, you have to return into “running mode” with the command change user /execute.

Of course, you can also install applications true Control Panel and Add programs. This is also a right way to install applications..

One of the things we have to do when we upgrade our server environment, is to migrate licenses for the RDP clients. This job is done by the RDP Licensing server. I want to explain the process of migrating licenses from Windows Server 2008R2 to Server 2012.

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).
The first step is the installation of the RDP Licensing role in Server Manager true Add Roles and Features Wizard.

Here you have to select Role-based or Feature-based installation and in the Server Role step you have to check Remote Desktop Services.

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).

Complete the wizard.
In the Server Manager menu Tools, Terminal Services, open the Remote Desktop Licensing Manager, right click on the installed server and select Activate server.

Add your data and complete the activation wizard.
The next step is transferring the licenses from the old server to the new one. To do this, you have to right click on the newly installed server and select Manage Licenses.

This will open the Manage licenses wizard. 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). Click Next.

In the next step, you have to identify the old, decommissioned server, by typing his name or IP address. Click Next.

At this point, you need to type your keys or agreement number and confirm the licenses with the Add button. When you have added all your licenses click Next.

The wizard will transfer your licenses to the new server. At this point you are ready to unauthorize and uninstall the old server..