hi all,

       Win server 2016 connection brokers, 2012 R2 session hosts (due to application requirements), currently 154 session hosts in farm.

if i logon to specific session host, using mstsc.exe /admin, first logon time is approx 8 seconds. Subsequent logons are approx 3 seconds.

if i logon via the farm ()via rdweb, or an rdp file downloaded via RDWweb), the logon times are 18 seconds and 13 seconds respectively.

It seems to me as if the farm negotiation and deciding where to place the client is taking a full 10 seconds - which just ruins the user experience.

i havent been able to find anything by googling this - has anyone got some suggestions as to what to check or what tools i can use to troubleshoot this ?

Hi, 

We want to use RDP for connecting to remote machine, execute Desktop Application Automation there. The challenge that we face is that on the customer end there are restrictions on idle timeout in RDP session. Once we start executing the automated desktop application and if execution takes longer that than the idle timeout to execute, the remote desktop session ends, and the Desktop Automation fails. Is there a way to handle this?

1. I have tried TSCON, but TSCON unlocks the console session, so it may not be acceptable to customers.

2. I have also tried Java's Robot classes to do some mouse action(https://stackoverflow.com/questions/52874/how-do-you-keep-the-machine-awake) This also works with limited scope. In case the RDP session loses focus, it does not work.

Is it possible to keep the RDP session from disconnecting on Idle Timeout?

Thanks in Advance.

Best,

Sumit

When I log onto our rds gateway, I see the Remote Dektop Icon from the collection object I created.

But when I click on the icon, the local RDP client starts. It should just give me a login dialog.

Anyone seen/solved this before?

++ 2008R2  Environment.

++ Installed Session host role, RDGW role and RD WEB access role on one server 

++ Customer is accessing third part application via RD Gateway.

++ Customer has public certificate XYZ.COM but the internal domain is different i.e. XYZ.local

++ RD Gateway is configured on the SSL certificate name.(XYZ.COM)

++ Customer created the Forward lookup zone within DNS with the name XYZ.COM and created the host records.

++ Customer has published third party applications to access them via RD Gateway instead from RDweb.

++ I checked from DC customer is able to ping the Gateway server and able to access the third party application.

++ But from client machine which are in same Network unable to ping RD Gateway and unable to access third party application along with mstsc.

Error Message:

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Contact your network administrator for assistance.

Could any one please suggest on the above issue...

Hello and thanks for the help.

I'm trying to find a solution for allowing external users on a different domain to securely access TFS from their copy of Visual Studio to check-in/check-out code. 

I'm using a Privileged Access appliance that has a technology that allows folks to start applications remotely like this, but the rep told me they do not think I could use Visual Studio in this kind of manner because it is not on the "approved list" of RemoteApps.

I've been looking for a little while and can't find any sort of list of approved Microsoft RemoteApps.

It's difficult to search for this because it always brings back error-related threads.

Does an approved list of software for RemoteApps exist and if so, where can I find it?

I have an rds farm with three rds_host servers. I have defined three domain user groups for sage_sales, sage_admin and sage_outside.

I have three collections pointing to the three rds host servers; sage_sales, sage_admin and sage_outside.

In my tests:

When I setup a user Joe in the Domain user manager, and make him a member of the sage_admin group, he can log into the RDWEB portal by entering his domain.user/password and clicking sign in. He is presented with the collection icon as shown below.

Clicking on the Sage_Admin icon takes the user to a successful remote session on the correct rds host configured for sage_admin users.

When my test user Joe is a member of two groups (sales_group and admin_group), he is presented with two collection icons after signing into the rdweb portal as shown below:

However Joe can only connect using the Sage_Admin icon. When clicking the Sage_Sales icon, the following error dialog is displayed.

What is happening here? I can't find any difference in the group rights.

Does the Set Primary Group in the Domain User settings effect which icons are available in an rdweb session?

Comments on these configuration options would help. What a battle!!

Hi All,

I've been trying for the past couple of days to deploy Remote Desktop Services to newly built 2016 Server (member server not DC). It just fails repeatedly when trying to install the connection broker role.

I've completed the windows updates (although that was dramatic in itself!) and then turned my attention to installing RDS services, tried Role based and remote desktop services type deployments, but on both it just fails and gives a useless and generic error message:

----------------------------------------------------------------

----------------------------------------------------------------

I've tried the following:

Change the Windows Internal Database service to administrator, or network service, or local system. (didn't work)

Moved server to separate container and disabled GPO inheritance incase it's a group policy setting issue.

Tried installing connection broker role via powershell.

Changed local security policy to make sure log on as service right is set for NT Service\All services, domain admins and network service.

SFC scan and DSIM repair image.

I can't figure out which service is possibly required to install this role which I haven't already enabled.

CBS logs don't provide much insight into why this has failed unfortunately.

Any advice or help would be greatly appreciated.

Cheers,
Billy

Hi Guys

I am running a 2012R2 RDS environment with 'HA' Connection Brokers with SQL in the background hosting the RDS DB. All working nicely. What I have noticed however is that if I use the 'Active' Broker Server Manager (GUI) to update Collection or RemoteApp settings, I seem to get inconsistent results. Before I give a couple of example, What is the best practice for updating Collection or RemoteApp settings in an HA Broker/SQL enviroment? GUI or Powershell? Or should the both give exactly the same result?

Thanks!

Hi,

our workstations with Windows 10 pro are in this weekend updated to version 1803. For main system we use RemoteAPP aplications on Windows server 2012R2 (Windows server 2012R2 is full updated). After update on client station are RemoteAPP slower, and  right mouse button is unresponsive, or react verly long time... 

It is a big problem for us.

PS: after replace mstsc.exe and mstscax.dll from older version Windows 10 is all OK. but this is not a solution.

Thanks.

We have a customer wit a newly setup cloud server environment with RDS (single server). The first day of production the datacenter that holds the servers lost the NIC (virtual network card) in the VMware-environment.

We added a new NIC and the server was accessible again. But here is where the problems begin:

- The sessions is never registered and therefore the users cannot disconnect and later connect again
- The users need to remember to Sign Out every time they leave the RDP-session

If we look in the Server Manager on the RDS we get this error:



When running checks in Powershell we get these results:

PS C:\Windows\system32> Get-RDSessionCollection

CollectionName                 Size  ResourceType       CollectionType    CollectionDescription
--------------                 ----  ------------       --------------    ---------------------
QuickSessionCollection         1     RemoteApp programs PooledUnmanaged

PS C:\Windows\system32> Get-RDSessionCollectionConfiguration -CollectionName QuickSessionCollection | fl

CollectionName        : QuickSessionCollection
CollectionDescription :
CustomRdpProperty     : use redirection server name:i:1


PS C:\Windows\system32> Get-RDSessionHost -CollectionName QuickSessionCollection
Get-RDSessionHost : No session collection QuickSessionCollection was found.
At line:1 char:1
+ Get-RDSessionHost -CollectionName QuickSessionCollection
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDSessionHost

PS C:\Windows\system32> Get-RDServer

Server                                             Roles
------                                             -----
RDS01.PRENOVA.SE                                   {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS, RDS-GATEWAY...}


PS C:\Windows\system32> Get-RDUserSession

CollectionName    DomainName        UserName          HostServer                                        UnifiedSessionId
--------------    ----------        --------          ----------                                        ----------------
QuickSessionCo... PRENOVA           admmisko          RDS01                                             86
QuickSessionCo... PRENOVA           magges            RDS01                                             113
QuickSessionCo... PRENOVA           kathyt            RDS01                                             106
QuickSessionCo... PRENOVA           johfor            RDS01                                             97
QuickSessionCo... PRENOVA           emeohm            RDS01                                             94
QuickSessionCo... PRENOVA           ulrnor            RDS01                                             119
QuickSessionCo... PRENOVA           lareri            RDS01                                             121
QuickSessionCo... PRENOVA           ulfagr            RDS01                                             124
QuickSessionCo... PRENOVA           andkle            RDS01                                             114
QuickSessionCo... PRENOVA           kimami            RDS01                                             118
QuickSessionCo... PRENOVA           lenwes            RDS01                                             93
QuickSessionCo... PRENOVA           Urbohm            RDS01                                             125
QuickSessionCo... PRENOVA           parbom            RDS01                                             96


PS C:\Windows\system32> Get-RDConnectionBrokerHighAvailability
Get-RDConnectionBrokerHighAvailability : A valid fully qualified domain name (FQDN) for the server was not specified.
At line:1 char:1
+ Get-RDConnectionBrokerHighAvailability
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDConnectionBrokerHighAvailability

PS C:\Windows\system32> Get-RDSessionCollection

CollectionName                 Size  ResourceType       CollectionType    CollectionDescription
--------------                 ----  ------------       --------------    ---------------------
QuickSessionCollection         1     RemoteApp programs PooledUnmanaged

HELP WANTED:

We need help in solving this situation once and for all. We would like this fixed without installing a new RDS as they have som difficult applications that we do not want to install again.

HOW do we get rid of the probable cause of this issue? Is it the first (lost) NIC's MAC-address that is causing this?
Is that MAC-address hidden somwhere in the Registry or in Windows Server 2016s own local DB?

Any tips on HOW this should be fixed is HIGHLY APPRECIATED!

Regard
Mikael Sköld, Atea

Hey

Unable to connect to RDSH (collection) from Windows 7 - All Windows 10 works.

If I disable NLA on the Windows 7 clients its able to connect to the RDSH (collection)

If I connect "directly" to a RDSH it works. (but not over our connection broker)

Any ideas?

Mike

is there any way to Restrict the users from access the network resources only allow them to join domain controller.

A couple months ago I deployed a Windows Server 2012 R2, with the intent of using RDS Gateway on it for a client.  I got it working, but there is a 60 second delay during the login process to the RDS Gateway.  Specifically, the RDP client hangs on "Configuring Remote Session."  This happens 100% of the time from outside the network (but never when connecting to the same server on port 3389 from *inside* the same network that the server is on).  It is also important to know that even though there is always a 60 second delay, it still connects successfully 100% of the time.  The client is not happy with the 60 second delay though (understandably), and has asked me to to solve the problem.  I have done a ton of research, but the few possible solutions I came up with ended up not solving the problem.  Here is everything I have done so far:

-My problem is *most* similar to this other post:  http://social.msdn.microsoft.com/Forums/en-US/20a68eec-d639-47f7-abd1-3ae10aaf4db8/remote-desktop-to-web-role-gets-stuck-on-configuring-remote-connection    However, the problem in that case eventually resolved on its own, & I have already tried the only suggestion mentioned in that thread (disabling port re-direction).....either I did that improperly, or it did not help).

-100% of the time immediately after a 60 delay login, I get this warning in the server's event log:  

"Remote Desktop Services has taken too long to load the user configuration from server \\servername.domainname.local for user XXXXXX"   (where XXXXXX is an actual username).

The only recommendation I can find after researching *that* warning message is a small registry edit, which I have tried, and it did not help.

-In my research, I came across someone's theory that the problem is related to the SSL certificate, & the fact that the internal domain has a .local extension (which mine does).  According to this theory, Microsoft's RDS Gateway (unfortunately) exposes the RDS Session host's computer name (including its .local extension) to the remote/external RDP client, and therefore the 60 second delay is caused by the remote/external RDP client taking time to look for the SSL certificate for the session host, which doesn't exist.  The only way to determine whether this theory is the actual cause of the 60 second delay, or not, is to actually purchase a UC Certificate, which supports multiple domain names.  There is an additional problem with testing this theory however, in that ICANN has mandated that certificates will no longer support .local (and similar) domain extensions come November, 2015.  Therefore, even if I go through all the work to purchase & install the UC Certificate, *and* it happens to solve this 60 second login delay problem (which is a big "if"), that solution would only work for 1.5 more years from now.

I hope you can see I have tried hard to solve this problem on my own, but I am unable to.  I really need some outside perspective to cut through the troubleshooting fog in my head regarding this particular problem.  It is for that reason that any assistance with this problem would be greatly appreciated!  Thank you in advance!

Hey everyone!

Need help. I have a terminal server in AD. The terminal server is public with few remote apps for 5 accountants. Installed Remote Apps connect to another server with MySQL databases in my local network and he is not public. I want to block network access from the public terminal to the local network with the exception of the SQL server. That 5 accountants should not have access to my network at all. Via GPO I blocked cmd, powershell, and iexplorer. In RemoteApp settings, I left only the clipboard and printer mapping. Any advice for resolving my idea?

Thanks for help

Hello. First time posting here, so please bear with me and my broken English.

I'm working as IT guy in small company that uses program called Symfonia for invoices, wares etc. It is installed on virtual machine with Windows Server 2012 R2, to which people connect via RemoteApp shortcuts with redirecting of their local printers.

My problem started 3 weeks ago, when one of rdp sessions hanged while probably printing bill from Posnet Thermal connected via USB and redirected using COM port. I couldn't (using local administrator account on server) log that user out or kill their instance of Symfonia.exe (access denied)(wait chain empty in task manager). I installed ProcessExplorer to change permissions to kill hanged process, but something weird happened. I couldn't use ProcessExplorer using "run as administrator", it just doesn't show up, but process creates itself in Task Manager. It worked normally (not as admin), but i couldn't change permissions of other processes.

After one process hanged, anyone who tried to print something would experience same thing, even while using not redirected printer.

And the best part is, sometimes when this occurs, I can't log out myself from local admin user (sits at logging off).

Only thing that helps in this situation is restarting server itself, which sometimes doesn't "end", just hangs in "turning off" state. Have to forcefully shut it down in that case.

While everything runs normally (more or less for about a day after restart) I can normally run ProcessExplorer as administrator.

When I log in RDS servers to try and publish applications to RD Web Access.  The Collection tab is missing under my profile.  Other users log into the server and the Collection tab is visible.  Does anyone know the fix for this?

Whenever I connect to more than one RDP session that is through a gateway, some of them will not allow me to log on.  I get the error "The logon attempt failed" and that is all.  If I disconnect from some of the other sessions and reboot my computer, I can then connect to the server that was given me said error.

I can also connect to the server giving me said error without closing down other sessions or rebooting by connecting through a Hyper-V virtual machine on my computer. 

None of this makes any sense.  Has anyone else seen this behavior?

James