Please wait for remote desktop configuration Server 2022

I'm building a new RDS farm on Windows Server 2016. 2 servers with connection broker, gateway, web server and licensing role (ha mode) installed and 4 session hosts - all on WS2016Standard.

Licensing is configured on both licensing servers - licenses per device are added on both and is integrated with AD. No errors or warning pop-up regarding licensing (though RD Licensing Diagnoser is no longer available in WS2016 apparently). Licensing servers are activated and integrated with AD. 

We changed the licensing mode from per user to, per device (an initial mistake). For this change we rebuild the RD licensing database and re-added the per-device licenses. Next we changed the deployment properties 'RD Licensing' mode: we removed both lic servers and re-added them with per device licensing mode. 

If we logon with our test users (5 of them) we all get this error. It states: "There's a problem with Remote Desktop Licensing - There is a problem with your license for Remote Desktop and the session will end in 60 minutes. Contact your system administrator to resolve this issue".

Just to be clear: no errors pop-up whatsoever in Group Policy, System, Application and Administrative Event Logs on the Terminal Servers and connection broker servers.

Any guidance on how i can troubleshoot this please?

0

0

Hello guys,

I'm building a new RDS farm on Windows Server 2016. 2 servers with connection broker, gateway, web server and licensing role (ha mode) installed and 4 session hosts - all on WS2016Standard.

I already have a RDS farm in production, based on Windows Server 2012 R2 (2 session hosts, 1 gw, cb, web server, licensing). This one has a few GPO's applied - all working as intended. The User Policies on this farm are scoped in security filtering to simply the user group. User Config GPO's are applying ok.

On my 2016 farm however, when i only have a user group in security filtering, the GPO is not applying. It is only applying User Configuration when i alsoadd the farm servers to the security filtering of the GPO.

Is this change intended due to changed security policies in Windows Server 2016? 

With kind regards,

Sven

0

0

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.

0

0

Hello,

I have a problem that will not just go away. I have two Windows 2012 R2 servers: one with RDS installed for 30 users with an appointment application and one "back-end" server were print queues and database are running.

So basically, users can connect to network printers by clicking on a link that points to the "back-end" server. In Windows 2008 R2, this is so simple but in Windows 2012 R2, I am experiencing tons of issues (with both V3 and V4 drivers). By the way, printer redirection in RDS (remote desktop) is disabled and forbidden by GPOs. I am listing the issues here to see if someone experienced them before:

1. After a disconnection between the printer and the RDP session (the servers are in a remote site as the printers are local and printing through a site-to-site VPN tunnel as they are all IP printers). Example: a power failure will set a particular printer at "offline", which is normal and eventually, it comes back online. But then, the problem starts: the printer "loses" it "default printer" status and none of the printers for a specific user are showing as default printer in his printer list. If I try to set again the desired printer to default, it is already "set as default" but the green "tick" is not showing on the printer icon and printing fails.

2.  When the above happens, I usually try to delete the printer from the user session and reconnect to it. But then, it is even worse: the specified printer is now showing "twice" in the list of "device and printers" for a specific user while working OK for another (when you right click the printer, you see two instances of it). This is interfering with our main application and a specific user session is non functional. A printer will also show in the "unspecified section"

3. Even a bigger problem: if I delete a particular printer from a specific RDS user session, the same printer disappears for all other users using that printer. So each time I try to fix a printer in one user session, I can expect a myriad of issues with the other users.

4. The only way I found to fix this issue (so far) is by rebooting both servers at the end of the day and after power recycling the printer exhibiting the issue. The only other thing I could try (never tried it yet) would be to delete the affected user profile and recreate it on the RDS server. But I do not know yet the consequences of that action (will everyone else lose the defective printer mapping as well???).

5. This issue doesn't seem to be driver or brand related as I had the issue with many printers of different brand. Both servers are virtual under Hyper-v (physical hosts are also Windows 2012 R2) and are running the latest integration version.

If anyone has experienced this issue, please let me know what you have to have done to resolve it. My next step is escalating this to Microsoft.

Thanks.

Benji.

Benjilafouine

0

0

Hi guys,

I am trying to access my work remote desktop through a company web access site - eg ts.companyname.org on a personal laptop 

I use internet explorer v11 and the RD Web access is running Windows server 2008 R2 

I am able to log in to the remote desktop system but when i try to connect to a specified terminal server and error displays stating

your computer can't connect because no certificate was configured to use at the Remote Gateway sever, please contact service administrator.

I have used this numerous times successfully before, and never had to configure a certificate before.

I wondered if this is something that needs to be fixed from my end, would some change likely caused this?

or would it need to be fixed by my company?

I'm afraid i'm not very good at these things so any help would be greatly appreciated!

0

0

I have some apps that are TZ sensitive on our 2012 RDS farm, as such TZ redirection is enabled in group policy.

The issue I have is one particular app requires the user TZ to match the local server which is in AU.  I have users in NY and other US regions using this app and they get TZ errors from the app because their local date differs from the server date.

Because the client redirection is a computer setting in GPO I can't turn off TZ redirection for specific users.  I've tried creating a targeted login script that runs TZUTIL and sets the zone to AUS +10 however I find this is hit and miss, sometimes it works sometimes not or it works the first time but if they reconnect it goes back to their local time. I've also seen it change the TZ to AU time when you first login but then 10 mins later it changes back to the remote clients TZ

Any suggestions how I can overcome this. 

I understand that the config may be mutually exclusive for the apps that require AU time and others that need actual local time but this is OK, the users of the apps are different roles and need one or the other.

0

0

System Architecture:

I have 5 Windows Server 2012 R2 Standard instances running a Remote Desktop Services Session Collection.

Server #1 is the Connection Broker, and hosts the share for central User Profile disks.

Servers #1 - #5 are load balanced under the Session Collection.

---

Problem:

1. New user (has not logged in before) RDPs to Server #1. Load balancing redirects to another Server (say Server #5).

2. Login is way too instant. An inspection reveals that the user profile has been logged in with a temporary profile.

3. User logs out fully (as opposed to disconnecting).

4. User logs in again, gets load balanced again to Server #5, this time the loading takes longer, it appears the .VHDX user profiledisks is being created. On inspection, user is using actual profile, no longer using a temporary profile.

---

This is readily reproducible by me. In one instance, it took logging off and then back on two times before the user profile disk was created.

---

An inspection of the logs gives the same error every time:

Remote Desktop Services could not apply a user desktop for a user account with a SID of S-1-5-21-3954512987-845256609-1816244978-2710. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct. The error code is 0x21.135

All online searches of this error all lead to the same hacky "fix" given by Microsoft of deleting a registry key of the profile. None even attempt at the source of the problem. Example article:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/734fae1e-9a47-415c-b53e-e1cdbdd8c38d/windows-2008-r2-you-have-been-logged-on-with-temp-profile

---

These Windows Server 2012 R2 instances are all  brand new and have not been subjected to odd changes over time - they are pretty much out of the box OS instances.

This is obviously pretty important to fix. Any ideas?

0

0

Hello, I am trying to remote into Windows Server 2012, which I did for months, but am now getting this error:

"The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license"

How can I fix this and why do I need a license server? I just want to log in to do administration, which doesn't require a CAL per below.

I am stuck right now. Any pointers please?

Thanks for any help.

0

0

Getting errors when trying to install the Remote Desktop Services (RDS) role on a new server running Server 2012 Std. 

Simple network with Domain Controller services running on a SBS-2011 Std server, and this new Server 2012 RDS function to run on this new server. All RDS roles are to be installed on the Server 2012 server.

2012 Server has been joined to domain as a member server without problem.

Problem is installing the RDS role on the 2012 Server.

Following the install flow of "Quick Start | Session Virtualization". It begins installing the RD Connection Broker - RD Web Access and RD Session host. Gets about 1/3rd way  into the "Remote Desktop Services Role Services" and reboots. Comes back up and attempts to continue but fails to fully install:

Remote Desktop Srvice role services: Succeeded

Session Collection: Failed (unable to create the session collection)

RemoteApp programs: Cancelled

I was attempting to follow this write-up as looked fairly straightforward and well documented, but getting this error condition on the very initial stages of getting this RDS role installed.

http://blog.concurrency.com/infrastructure/rds8-quick-and-easy-remoteapp-on-windows-server-2012/

I found another thread on technet on this same issue, but the issue was never documented as to  what the fix was.

http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b79cb8f8-9522-4735-bce1-4af973a4de23/

Looking for suggestions on how to approach resolving this issue as aside from the above technet article, I'm not finding much information out there on how to resolve.

Thank you.

0

0

I know this is a Win2008 forum, but I found a problem with Windows Server 2003 SP2 which might still be in Win2008, and I wanted others to avoid the same problem.

The problem: domain-member Windows Server 2003 SP2 machines prevent cilents from connecting via Remote Desktop unless the server can contact the domain-- even if the server has cached credentials available for the domain account the client is trying to use.  This domain-disconnected case is probably common in Home Office scenarios, where machines occasionally connect to the domain (via RAS) but generally log in via cached credentials.

Windows XP doesn't have the same problem, nor did (I'm nearly certain) Windows Server RTM.  Somewhere along the way of patches and service packs, I believe my server lost the ability to use cached domain credentials for authenticating a Remote Desktop session.  

The error I get in the Remote Desktop client is this:
    The system cannot log you on due to the following error:
    The specified domain either does not exist or cannot be contacted

On the server's event log, I get two errors: one in the Application Log and one in the System Log.  Below are the contents of those events (I removed domain & acocunt names for privacy)

- #1: NETLOGON event ID = 5719 in the System Log:
This computer was not able to set up a secure session with a domain controller in domain [DOMAIN] due to the following:
There are currently no logon servers available to service the logon request.  
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

- #2: NETLOGON event ID = 1219 in the Application Log:
Logon rejected for [DOMAIN\ACCOUNT]. Unable to obtain Terminal Server User Configuration. Error: The specified domain either does not exist or could not be contacted.

Anyway, I'm going to post the answer in a follow-up post so I can mark it as the answer. :-)

0

0

I have one client machine - thin T620 Windows 7 embedded.

It uses RemoteApps. Worked fine. Suddenly fail to launch RemoteApp with the error:

The remote computer disconnected the session because of an error in the licensing protocol.

There are dozens posts with a fix of this error... all of them about the same:

"Just delete the "HKLM\Software\Microsoft\MSLicensing" registry key...then launch remote desktop using "Run as Administrator". This worked for Windows 7. I had to launch as admin, otherwise it didn't work after deleting the key."

I remember I did this a year ago on one machine...

This time, I deleted MSLicensing in HKLM\Software\Microsoft\ but it is not recreated. So nothing works...

How do I fix Remote Desktop Connection please wait?

How do I fix RDP stuck at configuring remote session?

How to install Remote Desktop Services on Windows server 2022?