I have set up a Remote Access Server/Gateway with an SSL certificate and it works perfectly from outside using the domain name provided. When I try to access this URL from the inside, I can log in, but when I try to launch any application, I am prompted to login again and I get the following error:

"Your computer can't connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address." 

I have configured split DNS so that the external domain name points to the IP of the inside server. I have tried toggling the settings in the RD Gateway configuration for "Use the same user credentials for RD Gateway and RD Session Host Server" and "Bypass RD Gateway server for local addresses" both ways, but neither makes a difference.  Any thoughts?

I'm running Server 12 with Remote Desktop Services (single server) functioning properly (as far my untrained eye can see).  I can login to the RDWeb site without any issues; the default applications, Calc/Paint/Wordpad, pull up as expected.  My next step is to add our custom in-house applications to this and test the functionality. 

I installed these applications on Vir-1 (1st virtual machine created during the sysprep & Remote Desktop Deployment) assuming that I'd just go into the RemoteApp Programs and Publish them.  After jumping in and attempting to Publish the RemoteApp Programs I realize that the only software I have listed is located on my 12 server.  Am I correct in thinking that I can utilize my applications from Vir-1?? 

For the grins of it I installed several on the 12 server and they opened and I was able to utilize most of the apps but ran into issues as expected.  That prompted me to go to the Publish RemoteApps Add route, where I can type in the network path, for this example it's, \\Vir-1.####.local\c$\program_location.  This route results in the following:

You must specify a file from the RD Session Host server, Remote.####.Local by using the UNC path; for example, \\Remote.####.local\c$\path\filename.exe.  If the problem persists, ensure that the following Firewall exceptions are enabled: 1. File and Print (SMB-Out) and File and Print (SMB-In).  I've disabled the firewally completely and also ensured Domain File and Print were sharing properly. 

Am I correct in thinking I can publish the apps from a virtual machine (vir-1)?  Am I missing something altogether? 

Any help would be greatly appreciated.  Feels like I'm right there but I'm missing something easily correctable.  Thanks!!!

We have a 2008 R2 Session Host that uses a Computer based Group Policy to assign a mandatory profile to all users.

Can we use the "mstsc /admin" command to access the server for admin purposes without getting the same "restrictive" profile assigned?

Cheers for now

Russell

Hello all,

one of my partners has downloaded the Windows Server 2012 RDS CALs -25 from Microsoft Partner Network without any issues but when he installs it, it complains that the CD-Key is invalid.

He has tried to use MSDN licenses already for this as a workaround but it won't take them.

Can someone please assist here?

Thank you,

Andy

If i start a remoteapp on my 11" laptop and then connect a external monitor of 22" to my laptop and use the 22" as my primairily screen, the RemoteApps correctly sizes with the new screen. But after i disconnect the external monitor, i can't drag the remoteapps over the right side of my 11" laptop screen. I have to logoff my session and start a new session to get the normal behaviour. Can someone tell me more about this behaviour?

Im using Win08R2Sp1 and Win7Sp1, rdp 7.1.

I am currently setting up server 2012 VDI using 2 servers. A connection broker, web access, licenseing server and a VM Host server. I have followed the wizards, created my master image, created the collection, and setup group policy to add the group I want to give RDS access to Allow log on through terminal services & Remote Desktop Users group. 

When I connect using my admin account everything works, it connects to the connection broker and then forwards to one of the running VMs.

When I connect using a non-admin account I am prompted with: The connection was denied because the user account is not authorized for remote login. I also get the following in the event log:

TerminalServices-SessionBroker

TerminalService-SessionBroker-Client

--

I searched the internet high and low and I can not figure this out. I have even put the the non-admin users in the remote desktop users on the server just to see what would happen, same results if trying to connect to the pool. But I am able to connect directly to the server. I am also able to directly connect to a VM in the pool using a non-admin account. 

Any help would be appreciated. 

Hi, i have a problem connecting old hp thin clients that uses rdp 5, 5.5 and 6 to a RDS (Server 2008 R2 w/SP1) that uses rdp 7.1. and RDS Broker

When enabling RDS broker uses have to authenticate twice because the thin client doesn't support rdp 7.1 (Network authentication)

While new thin clients that uses rdp 7.1 don't have that issue

now i took RDS Broker out to get it to work but users never get the chance to go back to their disconnected sessions 

Any solution will be appreciated

Noor

Noor

Hello

I’m not able to start any RemoteApp from my new RDS 2012 test farm when using DirectAccess from outside.
On the internal company network it just works without any problems.

Here is my setup:

RDS 2012 Farm:
RDweb
RD Connection Broker + Licensing server
RD Session Host

DirectAccess:
Forefront UAG SP1 + latest rollup.
Working and in production, where users access other internal company systems from outside without any problems.

I can access and login to the RDweb server, but when I try to start a RemoteApp it times out with the error message below.

Remote Desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network

If I start mstsc and connect directly to the RD Session Host server I can connect and get a full desktop.
So the problem must be DirectAccess and the RD Connection Broker

Any help with this would be much appreciated

Thanks,

Jesper

I am trying to print a document to a redirected printer using remote desktop over a vpn.  The server is running Win server 2008 R2.  The pirint failed and the following error message was in it's event log.

Anny ideas why this has happened and how do I fix it.

The document Microsoft Word - 201106202009 - D23 - xxxxxxxxxxx, owned by xxxx, failed to print on printer HP LaserJet 1200 Series PCL 6 on PERRY (redirected 4). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 4549. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\MYSERVER1. Win32 error code returned by the print processor: 5. Access is denied.

I'm using a laptop with windows7 to connect to a windows7 instance on a vmware server.

I saved the credentials for the rdp session, and clicking the shortcut opens the remote session without a problem without asking for username/password. Now when I put the laptop to sleep and resume it at a later time the remote desktop client tries to reconnect, but when the connection finally comes back the remote system will always ask for my password. If I cancel the reconnect and restart the rdp session by clicking the shortcut again I get in without any problem.

Why does rdp not automatically recoonnect without asking for a password?

Jur.

puedo conectarme 10 thin clients por medio del protocolo rdp a windows server 2008, el cual tiene instalado hyper-v con una maquina virtual w7 o w8, la idea es que los usuarios se conecten al servidor y obtengan el escritorio de windows 7 u 8.

actualmente solo puedo conectar los thing clients al servidor por medio de RDP, usando licencias CAL y terminal services, el cual me inicia sesion pero con el escritorio de windows server 2008, cosa que no le agrada a los usuarios.

espero y me puedan ayudar.

saludos

Hi!

We have specific situation where we need to use one specific smart card by multiple users that is connected directly to RDSH. Users are connecting to server over RDP. Server is 2008 R2 SP1.

Is it possible? If yes, then how?

Thanks,

whenever i connect to rdp via the web  and i click on a published app i get a personilization issue and error that "theme cannot be applied to desktop" i have checked GPO for not changing themes any ideas ?

it works fine if use rdp client only happens when going through web ?

Client: Mac OS X 10.8 (Mountain Lion) with RDC client 2.1.1 (http://www.microsoft.com/mac/downloads)
Server: Windows 2008 R2 Terminal server (all the latest patches and updates are installed)

Problem:
When Mac users login on the terminal server the time zone usually changes to "SA Pacific Standard Time". Both on the server as on the Mac the time zone is "W. Europe Standard Time"

We've found the following artikel on the internet:
http://mikepeth.blogspot.nl/2011/04/mac-rdp-and-time-zone-redirection.html

So we added the line TZUTIL /s "W. Europe Standard Time" to the login script. For some of the Mac's the problem is solved. others still have the same problem.

Anybody familiar with this problem?

Hi,

I am having some very annoying problems in my domain, it seems to be impossible for me to establish a remote desktop connection to any new servers or clients I add to it. I am able to RDP to my DC and also to one other application server which already exisited in another domain and was migrated but anything new just does not accept a connection. I have ensured I have the correct permissions and tried changing the ports they listen on but no joy.

 My domain is 2008 and the servers are all 2008 r2 also, my clients are all Win 7 ultimate desktops. I have looked at other threads and tried all they suggest but still can not get it to work. I am wondering if there is some thing in group poilicy at domain level which is blocking it from working??

Very odd and frustrating.

THanks

Andy

Thanks Andy

Hello,

I am noticing a large difference between the benchmark result for a VM hosted on Hyper-V (Windows Server 2012 Datacenter Edition, build 9200) and the benchmark result for the parent partition.

The VM referred to in the subject has the following specs:

1. 4 CPUs

2. 4GB RAM

3. RemoteFX Display Adapter

4. Windows 8 Enterprise Edition build 9200

The host has the following specs:

1. Intel Xeon 6-core CPU

2. 48GB RAM

3. Nvidia GeForce GTX560 Ti

4. Windows Server 2012 Datacenter Edition, build 9200

The results are:

VM

(a) Graphics score:3856

(b) Physics score:3414

(c) Combined score:2084

(d) 3DMarks score:3491

Parent partition

(a) Graphics score:4300

(b) Physics score:6612

(c) Combined score:4330

(d) 3DMarks score:4541

Would anyone care to suggest where the bottleneck in the performance of the VM lies?

Thank-you!

Hello,

I don't know if I should celebrate this, it had eaten my whole mind... ;)

Some time ago I ran into an error in a previously well-known dialog of creating virtual desktops pool (Pooled-Managed).

I spent few days trying to understand what caused this error.

I ended up in completely reinstalling RDCB server - nothing helped.

Enabling all RDMS-UI logs didn't help either -there was no relevant errors except of notorious "invalid parameter" error. 

I failed to find RDMSDeploymentUI.txt in \Windows\Logs though - thanks to those who explain what exactly I should have done to enable it.

Googling didn't help either.

Powershell command Net-RDVirtualizationDesktopPool was giving the same error.

So I had to try one-after-another all the parameters for me pool, and (DRUMS):

It happens when I add a server administrators domain user group to the pool.

I have only one idea why this can happen - this group exists in local administrators on each server.

But what is most strange, when I created a deployment previously on the same servers, it worked well with this group.

.

Maybe Microsoft guys give an advice on this problem, since my abilities are exhausted. :)

.

My configuration is:

vServer1 RDWA/RDLS (Windows Server 2012 Std ru-RU)

vServer2 RDCB (Windows Server 2012 Std en-US core-only)  

Both hosted on a separate vHost (doesn't participate in deployment)

vHost1, vHost2 - Hyper-V Server 2012.

All servers are joined a domain.

.

Thanks for reading and answering!

Eugene

Situation:

A Citrix farm with a number of servers that are all started from the same basic image through provisioning. This image contains Windows Server 2008 R2, fully patched, with XenApp 6.5 installed. Next to this is a separate Citrix farm that contains a test-environment for applications.

Issue:

User starts MSTSC (Remote Desktop) as an application on Citrix, and tries to connect to various other servers.

- RDP shows a licensing protocol error on connecting to a Citrix server
- RDP connects without any problems to a non-Citrix server

Details:

The remote user logs in through the internet and starts the remote desktop application which has been published for him. Upon starting the application however, and filling in the name of the server you want to connect to, the applications pops up a second 'logon screen' to provide apparently some passthrough credentials to the Remote Desktop application. When re-entering the data for the user, the connection seems to be made but ends in an error: 'The remote computer disconnected the session becase of an error in the licensing protocol.' This happens, regardless of the credentials I use here, even if I use Admin equivalent credentials.

This error seems to point at problems with the registry, specifically the HKLM\Software\Microsoft\MSLicensing and HKLM\SOFTWARE\Wow6432Node\Microsoft\MSLicensing keys. Since we're using an image, these keys are inherently empty, and should be filled with the appropriate license as logons occur. They have been provided with the correct set of permissions that are applicable to this key (i.e. the Users-group is also allowed 'full control' here).

I've looked at the permissions on these keys, and while the Users group (which contains all domain users, including the user I'm testing with) has full access to the 2nd entry, the first one shows the Users only to have 'read only' rights to the key. This is strange, because verification in the base-image shows this to be 'full control' aswell. Even worse, also checking the GPO's that are unleashed on these machines again show specifically that the Users should have 'full control'.

After altering this back manually, and then going back to the remote user, logging in and again failing this login, I found that the 'full control' option I granted has been removed from the MSLicensing key. I have since found this only happens if a user tries to start a remote desktop session. So if the user does not try to run a remote desktop session the permissions remain as-is. This explains why the users only have 'read only' rights, but doesn't explain why this occurs.

After browsing around trying to find any hint of this problem and coming up empty, I was still expecting that there might be something with the client and alterations it makes to the local registry. So just to test that scenario, I've tried just connecting it to one of our domain controllers... which went through without a hitch (after just popping a screen up asking me if I wanted to allow access to this computer). Also a mailserver would just allow me to gain access to the login screen through Remote Desktop. Same with an application and a database server. What's weird tho, is that a connection was made, but nothing was placed under the MSLicensing keys, and no permission alterations were made.

So I then tried connecting as the user to one of the other Citrix servers in the same farm as the Citrix server that has the application started. Which failed in exactly the same way as the connect to a server in a different farm. Even more strange is that there was no alteration in the permissions on the registry keys after trying this connect.

Eventho the user has indirect membership (through a group) of the 'Remote Desktop Users' group of a server I try to remotely control, even adding the user directly to make sure he has access to gain access to the server does not yield a difference in behavior.

In short:

As a user:

* Connecting to a Citrix server in the same farm with Remote Desktop requests some extra Windows credentials, and doesn't connect.
* Connecting to a Citrix server in a different farm with Remote Desktop requests some extra Windows credentials, and doesn't connect, and seems to change the registry permissions on HKLM\Software\Microsoft\MSLicensing to read-only for Users.
* Connecting to a non-Citrix server works without problems, and without asking for extra Windows credentials.

As a locally logged on Admin on the desktop of the same Citrix server the user is using:

* Connecting to a Citrix server in the same farm with Remote Desktop connects.
* Connecting to a Citrix server in a different farm with Remote Desktop connects.
* Connecting to a non-Citrix server works without problems.

I've been looking around for anything else to try here, but I'm running low on options. It sounds like something related to permissions for the user, but I'm not sure what. Anyone here have any possible insiht in what might be causing this problem?

Hi,

I am currently running Server 2012 Std on one physical server. I have configured the server as a DC and loaded Hyper V to handle RDS. I have purchased user cals and have loaded and activated the license server. I have set the license mode to per user. The RD Session Host, RD Licensing, RD Connection Broker, and RD Web access are all running on the HYPER V server.

Everything works fine but the licensing diagnostic tool gives me two warnings.

1.The licensing mode for the Remote Desktop Session Host server is not configured.

2.The Remote Desktop Session Host server is within its grace period, but the RD Session          Host server has not been configured with any license server.

I have followed the technet guide to configure RDS but get the same result.

Any pointers appreciated.