Hello!

   I have built a Windows 2012 R2 server with Remote Desktop Services running on it.  Remote users are having trouble with inconsistent printing through their RDP clients.  Their printers show up as redirected printers and do print sometimes, but other times nothing prints - the user click print, select their printer, and nothing shows up.  Later it will just start working for them again.  The problem seems to be universal - it is happening on clients with different versions of Windows, different printer models, and different printer manufacturers.  Has anyone seen this?  Are there any hotfixes for this that I can install?  I have all of the latest Windows Updates installed.

Thanks... Dave

Hello MSDN/Remote Desktop Services Team,

Good day. We used UPD for remote desktop services but it is slow in re-directing folders, user profile and even opening an excel file stored in local machine. May we ask for advise on how to enhance the UPD performance?

Current Set-up: RDS/RemoteApp on Windows 2012 R2

Please advise.

Thanks,

Glenn Jose

We are running a terminal server farm using round robin DNS. Users login to three different terminal servers. Out of about 60 users we have about 5 of them currently that use IMAP accounts in Outlook 2013 that are experiencing extreme delay in receiving emails. They will randomly receive about 17 emails at once; some of which have a received date from the day before... they do not have an Exchange server on premises as they use a hosted mail service. At the same time these users can receive email correctly fine on their local workstations. But when using the terminal servers this problem re-occurs.

We have reset passwords, re-created the Outlook profiles, all kinds of things. Has anyone noticed delayed receipt of emails when using IMAP in a terminal server environment? Anyone know of any fixes?

Also I notice that the RDS profiles have lots of glitches (I create a few shortcuts on one server log off and log onto another server in the farm and the same icons I created on server1 do not show up on server2 or server3..... ) Does anyone have anything to troubleshoot this synchronization behavior? I have this same behavior happening with another completely separate environment and would like a better understanding as the only setting in AD is in the users profile settings under the "Remote Desktop Services Profile" tab > Profile Path and the RDS Desktop Services Home Folder (Connect (drive letter)) > paths....

Since there isn't much to it... I don't understand why if the settings are correct in their RDS profiles settings and the permissions are correct for their profile paths the synchronization of shortcuts / settings aren't working for some users and ok for others?

Thanks in advance!

This is probably not a RDS specific question, but the problem presented itself on a RDS server and I don't know where else to post it.

I'm troubleshooting a RDS server where there are some problems with Dropbox. While doing this I tested Jumpshare, and got the following message(html site) in the browser when clicking the Jumpshare link:

"Web access is restricted. Please contact the administrator. (Download Sites.)

"(If you feel this site has been improperly categorized, please visit here to submit a review.)

The page is butt ugly and feels amateurish. The link goes to a butt ugly site form. No company is listed as creator of the site, but the URL of the seemingly old web form is iframe.commtouch.com/urlf-miscat. (There is actually a Commtough company.)

I've googled this but doesn't get a singel hit regarding this message.

So there seems to be some shite installed on this RDS server, no? You get to the message independently of browser, and it doesn't matter if the browser is recently installed or not.

I've checked rsop.msc but can't find any Group Policy settings that would make this happen (there are very few Group Policy settings at all). I can't find any application on the server that would interfere with browsing as far as I can see. I do not get this message when accessing Jumpshare on other servers on the same site, in the same AD. I've seen this message before, but didn't think much of it then, because I had other things on my mind, but anyways it is not only Jumpshare that is restricted.

One thing, however, that catches my attention, is that in the list of installed programs on the server, there's one called simply "WebClient", and it has no Publisher. May that be the culprit? Since I don't know what it is I don't want to just uninstall it on a live RDS server.

Anybody seen the message before, or the WebClient? Any input appreciated!

PS. This is a new customer of ours, there's no documentation etcetera.

My RDS GW is in DMZ (192.168.255.x) and my RDS Hosts are in internal network (172.23.1.x)

Sometimes, the Gw try to connect with the RDS Hosts by name and other times by their internal IP address.

When the GW try to connect with internal IP address, obsviously, it gets an error to connect.
The user "ad\username1", on client computer "x.x.x.4", 
met connection authorization policy and resource authorization policy requirements, 
but could not connect to resource "172.23.1.x". The following error occurred: "23005".

When teh GW try to connect by the name, it WORKS!!
The user "ad\username2", on client computer "x.x.x.4", 
met resource authorization policy requirements and was therefore authorized to 
connect to resource "rds.xpto.com".

I dont know how it gets the internal RDS host IP!!!

My RDP file is setup with rdsgw.xpto.com for the gateway and rds.xpto.com to the RDS Host.

There is no IP configured in the RDP file!

nslookup rds.xpto.com   -> ip: 192.168.255.x  (there is a NAT to internal RDS Host)

Why does the GW sometimes try to connect by name and other times by IP????

Any help is welcome!!

Hi

When Windows updates are available for our work servers, I use my Windows 10 Pro home computer (from home) to establish a VPN connection and then use Remote Desktop to log on to the servers, install the updates and restart the servers. After they have restarted I log on again to make sure everything is OK. I use Remote Desktop Connection Manager V2.2 (RDCM) to do this - this allows me to establish a connection to all 4 servers at the same time. I have been doing this for several years using various methods with XP, Vista, Win7 and Win8.1

I tried this last Thursday and although I could establish a VPN connection to my employers network, I was unable to establish a remote desktop connection. For example, I tried to connect to a server and the RDCM tries to connect but after between 5 and 10 seconds a message is displayed:

Disconnected from server-name (Unable to establish a connection)

I tried using Windows' built-in Remote Desktop Connection (Desktop App), but it displays an error message saying

Remote Desktop can't connect to the remote computer for one of these reasons:...

I have tried connecting using the server name (which is how I normally connect) and via IP address.

Our work network has Remote Access installed on a member server. Staff can connect remotely only if they are members of a global security group named VPN and NPS has a policy defined that explicitly allows for this (the default NPS policies are disabled). The work network comprises 4 servers and 35 clients and uses a 192.168.0.xxx addressing range. It comprises a single Active Directory domain on a single 255.255.255.0 subnet. There are two domain controllers: 2012 R2 and 2008. Remote access connections to the network are routed via the gateway (a Draytek 2830) router using NAT.

I have an LMHOSTS file on my home PC that identifies the domain and which maps the name/address of our data server. When connected via VPN I am no longer able to connect to the data server using either its name or IP address via Windows Explorer (nothing happens when I try this, I don't even see an error message).

I use Emsisoft Internet Security and have disabled the firewall (and all the components as well), but my PC is still unable to establish a Remote Desktop connection.

I have tried resetting TCP using my admin account but saw the following:

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Blood>netsh int ip reset c:\resetlog.txt
Resetting Interface, OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Restart the computer to complete this action.

But it did not help.

After restarting I enabled the Administrator account, logged on using the Administrator account and tried resetting TCP again but saw the same message and after restarting am still unable to establish a Remote Desktop connection. I have also tried restarting the gateway router.

VPN connections are handled fine and IMAP connections to our data server that hosts our mail server software (Mercury/32) also work fine.

The only thing that has changed on my work network is that I have moved a wireless router from one part of the building to another.

I cannot see any error messages in the event logs on my home computer nor on the remote access server at work or the other servers I was trying to connect to.

Does anyone have suggestions I might try to fix this, please?

Thanks.

Hi all,

after adding the role for virtual desktop to my RDS, the Server Manager crashed and after that the "Deployment overview" is empty - all items stay as the "plus" sign.

If I go through PowerShell, the deployment is still there and works, but I can't manager it from the Server Manager. I've tried managing from another server in the pool but the result is the same.

Deployment servers is also empty and in both cases, the "refresh bar" over them never stops.

Any ideas?

I have

domain 100.0.0.1  gateway 

dns 100.0.0.10

Router gateway 100.0.0.254  ( here internet is comming from and internal 

IPs and external IPs are defined )

I have RRAS server which give me Internet  100.0.0.20   which route Internet from 100.0.0.254 to the gateway 100.0.0.1

I have also RDS 100.0.0.120  server which added to domain gateway 100.0.0.1 

How external users can see the routing table in 100.0.0.254 and login to my RDS  . Do I need any routing issue in the RDS ..means to connect to

100.0.0.1 and 100.0.0.254 at the same time to see the external ip

Hello,

I have an RDS deployment where I have the following machines:

Domain Controller 1

Domain Controller 2 

RD Connection Broker / RD Licensing Server

RD Gateway Server 1 / RD Web Access 1

RD Gateway Server 2 / RD Web Access 2

RD Session Host 1

RD Session Host 2

File Server (SMB share for User Profile Disks)

The problem is every time the a user remotes in and it gets into Session Host 1 the user cannot delete any files on that user's profile, but if the user logoff and login again an it's assigned into Session Host 2 then the user can delete files. I have check the permission on the SMB share and they look the same that it was before this issue appear.

Have anyone has this issue before?

Thanks in advance for any help.

redirectclipboard:i:1
 redirectposdevices:i:0
 redirectprinters:i:1
 redirectcomports:i:1
 redirectsmartcards:i:1
 devicestoredirect:s:*
 drivestoredirect:s:*
 redirectdrives:i:1
 disableremoteappcapscheck:i:1
 session bpp:i:32
 prompt for credentials on client:i:1
 span monitors:i:1
 use multimon:i:1
 remoteapplicationmode:i:1
 server port:i:3389
 allow font smoothing:i:1
 promptcredentialonce:i:0
 authentication level:i:2
 full address:s:192.168.56.103
 remoteapplicationname:s:||notepad
 remoteapplicationcmdline:s:
 remoteapplicationprogram:s:notepad
 alternate full address:s:192.168.56.103
 alternate shell:s:rdpinit.exe
 screen mode id:i:2
 winposstr:s:0,3,0,0,800,600
 compression:i:1
 keyboardhook:i:2
 audiocapturemode:i:0
 videoplaybackmode:i:1
 connection type:i:2
 disable wallpaper:i:1
 allow desktop com:1
 disable full window drag:i:1
 disable menu anims:i:1
 disable themes:i:0
 disable cursor setting:i:0
 bitmapcachepersistenable:i:1
 audiomode:i:0
 redirectdirectx:i:1
 autoreconnection enabled:i:1
 prompt for credentials:i:0
 negotiate security layer:i:1
 remoteapplicationicon:s:
 shell working directory:s:
 gatewayhostname:s:
 gatewayusagemethod:i:4
 gatewaycredentialssource:i:4
 gatewayprofileusagemethod:i:0
 use redirection server name:i:0
 displayconnectionbar:i:1
 redirectclipboard:i:1

Hi guys,

A client of ours has a medical practice and all their consultation rooms have thin client computers and network printers. It's currently set up so that the doctors can move between rooms and not lose any open applications (specifically Genie) and to be able to print to any printer in the building.

What the client would like is for a particular networked printer to be the default printer when a doctor uses a specific computer.

For example, there are 3 consultation rooms, all of which have their own network printers. At the moment when a user logs into a TS session, their default printer is whatever was set last, and it stays the same no matter what thin client they are using. When they log into a session on the thin client in room three, they want room three network printer to become the default printer, and when they log into a session in room one, the room one network printer becomes the default machine.

Is this possible ? 

Hi,

First of all, please note this: 

• Network level authentication IS supported on all machines as per theAbout Remote Desktop Connection. So please don't ask me to check this on the about remote desktop connection window.
• All clients are set per GPO to use the Remote Setting of the "more secure" option:
• The problem is on random machines, all windows 7. We only have a few windows 10 machines but no issues found on those so far. 
• It doesn't matter if the RDP connection is initiated from a windows 7, windows 10 or Windows Server 2012 R2. The problem remains and is exactly the same.
• The problem exists when attempting to connect RDP from personal home PCs (not managed by company GPOs and MS update schedules) over VPN

So the problem is this, first comes the first message and then the second.

It seems to have started after we deployed some Microsoft server updates, but its very inconsistent, some sites seems worse off then others, but its not all machines at any site. We haven't even done client updates yet.

Again, please don't give me a link to an old post or blog saying that I need to enable network level authentication, as shown by the top screenshot, it is already enabled/supported.

I already spent hours googling this. Please, I want responses from people who have actually had the exact same symptoms and issues or someone who has an idea that I haven't already clearly stated that I've checked above already.

Thank you.

Hello,

Our Environment is as follows:

2 RDS hosts, 2012R2
1 host running Gateway, Web Access, Connection broker, 2012R2

Client: Windows 7

The client has two .rdp files on the desktop. I saved one from RD Web so that I got all the config rows in there (workspace ID et cetera) and then made a copy, changing only the user name in the second copy.

Here's the issue:
1. The user connects one session and logs in to the full desktop
2. The user minimizes the session and connects using the second .rdp-file, which has another user name specified
3. A new MSTSC windows connects to an RDS host, but instead of the saved username, the user is reconnected to the first session which was minimized in step 2.
4. Looking at the first MSTSC window, there's an information box letting the user know that he was disconnected from the server

So, in short: Connecting a second RDP session to the same collection/workspace ignores the saved username in the rdp file and instead reconnects to the first, live session.

Question; is this the expected behavior in 2012R2 RDS?
What we are trying to do is connect two concurrent sessions with different user accounts. Is there a setting we can modify to meet that goal?

If we connect the first session, then right click and modify the rdp-file, change the username, and then connect, we get two concurrent sessions with different accounts (the goal scenario). Can't figure out why this exact procedure changes the result.

Config<o:p></o:p>

Win2012 WAP proxy in DMZ using AD FS and 2FA integration (working fine) <o:p></o:p>

RDS 2012
publishing applications only, separate servers for gateway, broker, web and app hosts. Applications launch successfully for users on internal network.<o:p></o:p>

Problem<o:p></o:p>

When connecting from external https:\\rds.mydomain.com I get a credential check asking for my AD credentials as expected, I then get directed to the RDS credential challenge and then I am presented with my applications. I then try to launch an application andI am asked to enter my credentials again, this time it is asking for 'Type your user name and password to connect to <internal FQDN of the broker server>. Once entered I am told that the gateway is temporarily unavailable.

Findings:

Checking the event logs it appears that the process  goes as far as launching the application (app server says that the applicationwas launched successfully). There is an error on the brokeras follows:

EventID: 1306
Remote Desktop Connection Broker Client Failed to redirect the user <domain>\<user>. Error NULL<o:p></o:p>

TechNet says this error means that the Broker is unavailable. This is not the case. I can rdp to it, the services are all running, it has no errors and locally things are working fine.

The process which appears to be failing is when connecting to the broker and applying the user specific settings, profile, policy etc

more details:

I took an .rdp file from a client which was failing and launched it on the internal network, it asked for my credentials then launched the application successfully.

There is a 'locally stored group' on the gateway containing the RAP for the RD users and the IP addresses of the application host servers.

The RAP contains the user group of the RDS users

the CAP also contains the user group of the RDS users, there are no computer group members, password is the authentication method

in RD Gateway Manager: Properties of local gateway

there is one RD Gateway server farm member, the RD CAP store is local so no local NPS is used.

The server farm tab shows one gateway with a status of OK

Local groups such as RDS Endpoint Servers are populated as described in their descriptions.

Anyone got any ideas?  it feels like I've tried everything!

Dan

Hi,

I have servers running Windows 2008 and Windows 2008 R2.  When I enable Network Level authentication on those servers I'm unable to RDP to them with a domain account.  Local accounts and domain admin accounts work though.  I get the error message "The Local Security Authority cannot be contacted.  This could be due to an expiring password."  The password is not expired or being forced to change.  If I disable NLA I can login without any issues.

Any ideas?

I am sure this topic has been discussed many times from the Internet.  Some people suggested CRTL-ALT-END from the client, some suggested to turn off Presistent Bitmap Caching from the Experience tab under RDP, uninstall Powershell 2.0 etc...  None of this work for me.  Does anyone have a better recommendation?

Thanks,

Brian

Window 2012 R2, How do I configure Remote Desktop Services for Access RemoteApp and Desktops?

Thanks

Pat

Hi there,

I'm currently running a RDS environment with 1 fileserver, and 1 terminal server.

On the terminal, which is the Session Host, i'm running "Publish RemoteApp Programs" but it's been running for 24 hours now.
Any idea if this takes as long as 24hours or more?

Or am i missing someting?