Hi,

we're facing the following issue while trying to add new Remote Desktop Session Hosts into
a session host collection  : "Unable to retrieve the session collection properties".

The server can be added into the deployment but can't be added into the session host collection and the message above
is returned. This error never happened before and is ennoying as we need to deploy more Servers/Collections.

A collegue noticed that adding a couple of servers at once (from the GUI) succeeded ...
I can't find anything related on EventViewer (Brokers / DataBase server)

Is this a known bug ? I can't find anything related on Microsoft support.microsoft.com
Any help would be much appreciated, Thanks.

MCTS Windows Server Virtualization, Configuration

Folks,

Just noticed this becoming an issue on a Windows 2012 R2 Terminal Server after the last round of Patch Tuesday updates stemming from August 9th, 2016.

Typically, I'm rebooting the server every 24 hours to over-correct the issue - rebooting not being the best option here.  

In previous discussions, it's advised to remove KB3002657 or KB3035132 from the server.  Is this still the best option to restore full functionality even with the last round of patches and updates? Just to confirm, we are not using webroot as an AV solution. 

We have this issue on many 2012 RDS session hosts. The issue has been seen at different clients with different set ups, some have a simple 1 session host RDS server, some have 4 or 5 session hosts in a load balanced farm with RD gateway, connection brokers, RDWeb, ect. The problem in simplest explanation:

A user will call the help desk saying they cannot access the server. They will get an error when RDP is trying to connect. 

We check the session hosts, and will find many errors:

"Event ID 4005 - The Windows logon process has unexpectedly terminated"

At that point in time, users who are currently logged in may be able to still work, or their session may lock up (it is not consistent). 

Regardless of the current users logged; after the logon process crashes, it continues to crash upon every user attempt to log on. It will happen indefinitely until the server is rebooted. We can not log in, not even via console until the server is rebooted.

Then, everything works fine for some amount of time (not consistent) it may be a couple of days, or it may be weeks, or a month even. 

We have had the case open with Microsoft for about two months and they cannot determine what is wrong. 

I believe I may have found a possible cause; Webroot Secure Anywhere antivirus. Since we have tried everything from moving from roaming profiles to local profiles, removing all printers, blocking inheritance of GP, fresh server builds with minimal software, ect - it has to be something that is consistent across the board on all servers. 

The only thing I can find consistent across the board is the Antivirus; Webroot. 

I am curious if anyone else is having this issue? I would like to pin point this to something but it is so intermittent and we cannot force replicate the problem. 

I have an issue with client PC's getting multiple login requests to get an RDP session via RD gateway.

This configuration only uses RDGW and RDweb roles.  there is no RDS deployment, we only use this gateway for remote desktop passthough.

I have a valid, trusted 3rd party certificate for the external DNS name.

Forms authentication is enabled on RDWEB site in IIS.

The RDgw server is a domain member and can authenticate logins to AD directly.

Client logs in to RDweb with domain credentials, tries to 'Connect to remote PC' then gets prompted for credentials for the RD GW server then again for the destination server to rdp (2008r2).

From here the behaviour is inconsistent depending what OS the client pc is.

On a windows 10 client, if I check 'remember password' from then on in it works seamlessly  (although I shouldn't be getting requested to authenticate again in the 1st place)

On Win7 client, after authenticating multiple times and checking remember password, the destination internal server kicks back a message saying the 'admin does not allow saved credentials'. If I supply the password again I can get in.

Note that connecting RDP to the SAME server from the same client when directly attached to the internal network either locally or via VPN I do not get this message about not allowing saved creds and it just connects RDP session so this only occurs when coming in via the RDgw.  (NB it also happens when just using mstsc.exe client)

How do I get SSO working with Rdweb, and why does this message about 'admin does not allow saved creds' only occur on Win7 clients, and then only when accessing via the RDGW

There are many posts about this same issue but I haven't seen any fixes applicable to my case

thanks

Hello.

I am having problems with having a Windows 10 PC access a workstation via RDP through Remote Web Workplace running on SBS 2008.  When the Windows 10 PC tries to access the workstation a dialog box appears:

1. Title:  VBScript Remote Desktop Connection
2. Message:  The wizard cannot configure Remote Desktop Connection settings.  Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer.

The Windows 10 PC can access the same workstation without problems when they are not "remote" from each other---just not through the Remote Web Workplace.

Any thoughts?

Hi,

We have 3 RDS servers and this is the 2nd time this issue has been happening. We have these servers setup since February 2015 and we never had this problem until this summer.

Last month, users were not longer able to connect to 1 of the 3 RDS servers and was caused by the fact that the RDP certificate had expired so my co-worker remove it, restarted the Remote Desktop Connection service and everything worked fine.

https://technet.microsoft.com/en-us/library/ee890902%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Today, this happened again with another RDS server.

What is the best way to fix this ? I definitely don't want to fix this again in 6 months and I refuse to believe that the best solution would be to do a script that will delete the certificate each 5-6 months and restart the Remote Desktop Connection service at night.

Hi -

Have a public facing 2012r2 server running RDGW and RDweb roles.  There is no RDS deployment, we only use this for RDP pass-through to internal servers.

After login in via RDweb and going to 'Connect to a remote PC'  this connection may take anywhere from 30 seconds to 3 minutes to secure and establish the connection to the remote server.

Once it gets through, if I disconnect and try again, it will connect almost instantaneously.  This occurs consistently.  If the client hasn't connected in a while, it will take a long time initially, every time.

Each time the connection process is slow there is an eventid 11 is generated in the RDGW server:

event 11 Source: RDWebaccess

RD Web Access was unable to contact "computer.domain", which is the server that is specified as running the RemoteApp and Desktop Connection Management service. Ensure that the name of the server that is specified as running the RemoteApp and Desktop Connection Management service is entered correctly, and that the server is running and available on the network. Error code: 2147944122.

This message does not appear on subsequent connections.

  As mentioned I do not have any remoteapp or SH servers setup in this deployment.

thanks

Env: 

- Win 2012 R2, with RDS Role added, and Web Access enabled.

- Checked "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber". Port number is already new (not 3389).

Problem: When accessing RmoteApp via Web Access, the downloaded *.rdp file (eg., cpub-javaws-Session-CmsRdsh.rdp) contains the default port # as 3389: "server port:i:3389"

How to change the downloaded *.rdp file's port number?

What specific advantages or differences, if any, accrue to setting up a new RDS farm with Windows Server 2016 instead of Windows Server 2012??

For example, is performance better?? Network latency decreased?? What??

I am not really interested so much in 'what's new' as in ascertaining 'what's better' if anything.

I am trying to evaluate if it's better to jump right into Win2k16 RDS sooner than later, or put in Win2k12 RDS for a couple years, then do Win2k16 RDS. 

Also if with Win2k16 it's better to serve a full desktop or applications.

Thank you, Tom

Hello,

I have come across several posts with a member "TP" was able to help resolve very similar issues.

Hoping he is still around and able to help me. I was not able to find a way to message directly on here.

So we have a 2012 RDS environment, the DC is also server 2012.

When users double click the RDP icon it takes almost almost a minute to connect.

It gets stuck at "configuring remote session"

I think its related to either the FQDN, DNS or certificate but we have had 3 people internally look at this and we just cannot figure it out. It was working fine when we intially set the servers up and worked for about 6 months, then last month, just out of the blue it started doing this.

Hoping someone will be able to assist

TP if you are here and able to assist we would be so very grateful to you!

Thanks!

Hiya,

For various reasons we are deploying RDS 2012R2 via our shiny new SSL VPN portal provided by our Firewall, the firewall proxys and obscures the address of any URLs that are opened through it.

As a result when you try and browse to the rdweb url you get an error message in IE:

The XML page cannot be displayed. Cannot view XML input using XSL style sheet.....

If i do the same with Chrome it partially loads but spits out errors in the Developer Tools:

"Unsafe attempt to load URL https://InternalServerHostname.domain.com/RDWeb/Pages/en-US/RDWAStrings.xml from frame with URL https://sslVPNURL.domain.com/proxy/https/obscuredURL/RDWeb/Pages/en-US/login.aspx?ReturnURL=/RDWeb/Pages/en-US/Default.aspx Domains, protocols and ports must match"

So from doing research it does seem that issue is down to trying to load the XSL sheet from a URL that is different from the URL open in the browser - looking at it, it appears that the XSL performs a look up of the local host URL and uses that to then provide the html headers etc. that includes href="https://InternalServerHostname.domain.com/RDWeb/Pages/en-US/"

Has anyone encountered this before and if so how did you get round it (yes I am aware of the RD Gateway, we are trying to avoid using that if possible as our Firewall provides excellent logging that we can't get from the gateway). In my mind it involves modifying the XSL or aspx files so that either the XSL is embedded in the same file, or that the URLs are all set to relative not something based on a lookup. I know relative works as our intranet loads fine and all of the href's are relative.

Thoughts on postcards, and try to avoid mocking the use of an SSL VPN portal over the Gateway please.... :)

How many surrealists does it take to change a lightbulb?

Two - one to hold the bulb and the other to put the clocks in the bathtub.

Hi,

My problem is:

After a while, I cannot map my local resources (drivers and printers) anymore.
Only with a reboot I can map again my local resources.

It is important to say that I can always map my local driver by the net use command.
So, its not network problem or permission.

It seems that run out of something... and I can only release with a reboot

Any help is welcome!

Marcelo 

Hello everybody!

i have a problema with print spooler in 2012 R2 environment.

RDS users (with disk profile) have connected printer with a 2012 print server. Sometimes printspooler seems to be blocked cause applications like Acrobat Reader DC gives an error no pages selected to print. Same user but different application (Foxit for examples) doesn't see any connected printers.

Tried many application settings but nothing resolved. After i have restarted print spooler, everything is back to work.

No events in application or system events. only in printservice/operational i got some error events:

event 221

source printservice

task enumerating printers

detail: Retrieving CSR cache information for printer \\xxxxxxxxxxxxxxxxxx\M5035 failed, error code 0x2. See the event user data for context information.

event 812

source printservice

task Executing a file operation

detail: The print spooler failed to delete the file C:\Windows\system32\spool\PRINTERS\00009.SHD, error code 0x5. See the event user data for context information.

event 603

source printservice

task Client-side rendering

detail: The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key SIDxxxxxxxxxxxxxxxxxxx\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.

Hi all,

I have an issue with a 2008 r2 terminal server.

A line of business application is running on the server, remote users connect in and use the line of business application on the terminal server.

The line of business application has 5 user licenses, which mean 5 remote users can RDP into the terminal server and use the line of business application.

The issue is this...

some users seem to have TWO active RDP session from the same computer, I see this by logging into the terminal server, opening task manager then clicking the users tab. This of course causes issues with the licensing of the line of business application.

Is there a way I can prevent multiple RDP session for the same user on the terminal server?

Many thanks.

Greetings,

  We have just deployed two Server 2012 r2 RDS Session collections (each with two RDSH servers, and both going through the same gateway/broker server), and during testing had no issues, but as soon as we rolled it into production, our users have been experiencing black screens when attempting to log in, and the Remote Desktop window just closes (no actual login is performed).

  This seems to happen intermittently, and on both collections at different times.  I thought I had solved it initially by disabling use of UDP in the RDP clients, but it wasn't a permanent fix.

  Looking at the event log of one of the affected servers, There seems to be an Event ID 36 generated at every logon attempt with the following message:An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070102)

  After scouring the web looking for answers, nothing came up.  Any help here would be appreciated.

On Service RDS on windows Server 2008 Can configure and define policy for remote desktop client .

But on windows Server 2012 i install RDS already and configure RDS on web already but cannot found menu setting Configure Remote desktop client . Please Advise me

Hello All,

My configuration is as follows:

All servers are 2012 R2 and all roles are on separate virtual servers unless otherwise noted.

Server Name - Function 

RDCB - Remote desktop connection broker in HA

RDCB2 - Remote desktop connection broker in HA

RDWA - Remote desktop web access server (Internal)

RDVH - remote desktop virtualization host

RDGW / RDWA - remote desktop gateway server and Web access (DMZ joined to RODC)

RDUPD - User profile disk server

All of the servers outside of the RDVH are part of a 17 node Microsoft cluster with over a TB of memory and 40GB/s network speed.

All of the storage is connected to a 3par SAN.

All connections (even internal ones) go through the gateway server. The connection issues I'm about to describe is intermittent but the error logs are always the same.

On the connection broker I get the following errors:

Event ID: 1306

Source: TerminalServices-SessionBroker-Client\Operational

Message: 

Remote Desktop Connection Broker Client failed to redirect the user USERNAME. 
Error: Unspecified error  Sometimes there is NULL but always the same message.

The other error on the connection broker is:

Event ID: 1296

Source:

Message:  TerminalServices-SessionBroker-Client\Operational

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : USERNAME 
Error: Element not found. 

The errors are usually in succession and I usually get error 1296 first then 1306.

The only other server I can find errors is on the RDVH. These errors have to deal with the UPD's (User profile disks) 

On the RDVH I get the following errors:

Event ID: 8479

Source: TerminalServices-TSV-VmHostAgent/Operational

Message: 

Remote Desktop Virtualization Host could not run the Hyper-V WMI job.

Error description: NULL
See also Hyper-V event logs
Hresult: 0x80078000

Event ID: 4890

Source: TerminalServices-TSV-VmHostAgent/Admin

Message: 

Remote Desktop Virtualization Host could not apply a user desktop for a user account with a SID of <SID>. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct.

Virtual desktop name: VMName
Error: 0x1.0

Event ID: 4893

Source: TerminalServices-TSV-VmHostAgent/Admin

Message: 

Remote Desktop Virtualization Host could not attach a user profile disk to the virtual desktop for a user account with a SID of <SID>.

Virtual desktop name: VMName
Hresult: 0x80078000

To go with the above errors I have noticed that the UPD's don't always get unmounted when a user logs off.  This has caused some of the connecting issues I noticed above. I know this because I will have a user not being able to connect, Ill find that their UPD is still mounted from the last time they successful connected. I'll unmount the UPD and they can connect again.

 All of my clients go strait to a VM, so I do not have a session broker, so the connection issues be referenced in the event log do not make any sense. If anyone can shed any light on this I would be grateful 

Thanks,

Scott

Good morning all,

I have just installed Windows Server 2012 Datacenter and started configuring Remote Desktop Services.

The idea is to have RDSWA + 2 session collections.

• 1 session collection for PROD environment
• 1 session collection for TEST environment

Both these session collections run the same applications, but with different configuration files (basically just a different version of the program and pointing to a different SQL Server)

I've created 2 Folders in the RDSWA (TEST and PROD), with the remote apps published here. The different applications have the same alias and name.

When I first start the application in the TEST folder, then the test Environment starts, if I open production with TEST opened, then he opens a second instance of TEST. Not of production. No session is opened on the server running production either.

The same goes for when I first start PROD.

Can anyone assist in this matter please?

Thank you.

Kind Regards,

Tom

I have several servers that the last few weeks all randomnly have started causing connections via RDP to go to black screen for about 10-15 seconds then close the session.  

I have checked roll up updates such as KB2887595 are installed, I can console into them from my VM Console, however RDP does not let me in unless a full Reboot occurs, sometimes multiple times.  The fix may be temporary for a few hours, but may quickly revert back from not allowing new connections to log in.  

These servers are part of a collection farm, I have disconnect sessions set to 1 minute, idle set to 15 min, active set to never for the connection properties for these farms. 

I am at my wits end, cause I have roughly 6-8 servers all behaiving the same way with roughly 600 users hitting this set of servers on a daily basis, this is overflowing my help desk guys and I need a fix or solution...like last week.

Please help!

Joshua Craddock PinComputing LP. Systems Administrator