Hi guys,
My RDS license Server is 2012R2, I can't logon it.
When I try to connect to the computer by using Remote Desktop or Remote App, I will receive an error message that indicates there is no Remote Desktop Services Client Access License.
How do I fix it?
Best regards,
Dusk
I am performing testing on a RDS/Citrix server for a Proxy system that we are implementing.
However I noticed that when the proxy settings are enabled in Internet Options, shortly after the server will be uncontactable on the network. Logging on to the console of the server shows that the internet connection is unavailable. But it isn't just internet, I am unable to access the server over the local network.
After I disable and re-enable the network card, network is restored. But if the proxy is left enabled, the network will drop again.
It isn't instantly, but usually happens minutes later.
Has anyone experienced this?
Windows Server 2008 R2 SP1
Symantec.Cloud Web Security with Client Side Proxy on another server
Daniel B IT Technician / Network Administrator
Hi,
I am trying to remove 2 RDSHs from the Collection/Deployment.
I restricted connections to 2 Hosts. When Under Task \ Remove RD Session Host Servers There are ) computer(s) found.
What happens?
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Hi there,
i recently set up a server in our DMZ with RD Web and RD Gateway role on it.
The RD Web should use the RD Gateway to authenticate which works fine. But after the user tries to connect to a "full desktop session". He gets the warning"
There are some sites out there recommending to not perform the check. But my CRL is on a HTTP server and i let the gateway Server access this address and also opened a port for the ldap query to the internal CA (these are the 2 CRL points).
I can see that the gateway server is not checking any of these or is this a task performed by the client? We want to allow external clients so "importing CAs" is not the solution.
Best regards
Stephan
Hello, my RDS farm is the following (all are 2012 R2 VMs):
1 connection broker
2 rds session hosts
1 machine sharing the folder used for user profile disks (aka "fileserver")
a few remoteapp published on a single collection
It started loading temporary profiles, so I checked in "open files" on the fileserver that vhdx (UPD) is never released after logging off the session (also if I force logoff from server manager console), they are locked from the computer account of the session host where the user connected to. Before I had only one session host so I didn't notice it but I suspect disks were already locked in that situation. Is there any fix for that?
Dear,
We are a small firm of 10 people and just migrated our servers to server 2012R2. We are an accountancy firm and want to publish our Accountant program to the clients. When we work with a full desktop session there is not a problem. When we use remote app for 1 specific account software the program freezes. It's from a Belgium company - Kluwer, Centraal Dossierbeheer. The program is using a Firebird Database.
We use Remoteapp to publish the applications to the desktops.
When I open the Task manager and press analyse process it show "splwow64.exe". So I guess this has something to do with the Print Spooler Service? I restarted the print spooler service when the freezing occurs but the program is still frozen.
Hi,
since the update of rdp (7.0 to 8.1) i have so much trouble to have a rdp connection between my PC to the server (2012 r2). The connection never initiate (despite the fact i'm able to see the flow on wireshark on every server i go trough).
the rdp windows can stay more than 4min to wait a connection, but never happens.
When i downgrade to 7.0, the issue still exists but sometimes it works.
I dont have the issue on w10.
So, i tried too much thing to troubleshoot and fix without success. What can i do now ?
thx for your help
Hello,
We have Windows 2008 R2 servers with SP1 fully patched and Windows 7 SP1 desktops also fully patched. We enabled NLA (Network Level Authentication) via group policy recently after we decommissioned our last 2003 R2 server. We can connect to all of our 2008 R2 servers via remote desktop except for one. We get the error:
“The remote computer requires Network Level Authentication, which your computer does not support.”
We are using other 2008 R2 servers and Windows 7 desktops to try to connect to the server. They all support NLA. But we still get the message. We rebooted the server from the console. That still did not resolve it. We could turn NLA off in the group policy at least for this server but we need it turned on for compliance reasons.
Any suggestions on what the issue is?
Thanks.
We run a Server 2012 R2 RDS environment using:
3 Servers running connection broker, Web access and session host roles
10 Servers running the session host role
3 Servers running the license server and session host server roles
We run the 3 connection brokers in HA mode using an external load balancer to manage the connections between them and a SQL 2014 database cluster
When a user logs on to any of these servers and receives the session id 114 they get an uncontrollable blank screen. When a domain admin also RDP's to the one of these servers using the /admin switch and gets the session id 114 they also get the same issue.
Has anyone seen this issue or anything similar before
We are running a two server RDS solution for a client. Both machines are 2012 r2.
Occasionally, one of our clients' employees logs in and gets a black screen, and they are unable to do anything until we reboot the server. This is not feasible in a live environment, and a user can be shut out for the whole day before we can schedule the reboot
that night.
Here are some characteristics of the black screen issue:
- The screen is entirely black within the remote session.
- Pressing things like Ctrl + Alt + Del and Ctrl + Alt + End do not bring anything up. The mouse may briefly get an hourglass, so it seems like something might be happening, but the black screen doesn't go away.
- Forcing the user to sign out using administrative access does not resolve the issue.
- Deleting the account and recreating it does not resolve the issue.
- All our graphics drivers are up to date.
- Unchecking 'Persistent bitmap caching' does not resolve the issue.
- I've played around with group policy, and enabling and disabling UDP to various degrees. This does not resolve anything.
- We made minor progress by changing the display configuration in the Remote Desktop Connection app to a smaller size desktop (such as 640 x 480). The screen will sometimes (not always) appear, but only partially. Clicking the start button can cause part of
the screen to go black. Signing out from this degraded session didn't do anything, and this ultimately didn't get us any closer to resolving the problem.
- The black screen only ever happens to one user at a time, and it is the user given Session ID 114.
I've read only a couple other posts about session ID 114. There is no way to predict when an ID will be doled out to a user, and there is no method that I've seen so far that can completely prevent a user from getting a certain ID. The best workaround we have
to date is to create a dummy account, force sign out the affected user, and sign in with the dummy so it takes over that ID.
This only works until a reboot, when Session IDs will get reassigned. This also requires a failure in order to make the change, which is not an ideal situation.
According to this thread (https://community.spiceworks.com/topic/693490-black-screen-at-remote-desktop-login-to-server-2012-r2), the poster was in contact with Microsoft and they said there is no solution. I want this to be recorded in writing by Microsoft
itself if that is the case. If a solution or better workaround has been found, please let us know.
We also have a couple of RDP 2012 servers which when a user gets allocated session ID 114, they get a black screen.Been having this for 6 months and still can't find a solution. Any ideas?
Hello,
We have a 2012R2 RDS farm with 3 session hosts.
DNS farm name = farm.domain.local
Session hosts = ts1.domain.local, ts2.domain.local, ts3.domain.local
I have created a SAN cert and it is issued to farm.domain.local from our internal CA. We are not exposing this farm to external users.
All 3 session hosts servers fqdns are listed under the subject alternative name section of the cert.
When I RDP to farm.domain.local I receive a name mismatch error
Name requested = farm.domain.local
Name in certificate from remote computer = ts1.domain.local
If I click view certificate I can see the name of the session host server listed in the SAN details.
Any assistance would be greatly appreciated
Hello,
I have been able to successfully publish my RDweb and RDGW on 2012 R2 servers using Azure AD Application Proxy.
I am looking on some guidance on whether it is possible to use the Azure AD proxy to pre-authenticate connections for the WebFeed.aspx URL for use with the RemoteApp and Remote Desktop Connections feature. I'm trying to see if I can have mobile RDP clients
(for iOS, Android, Mac etc.) to use my RemoteApps when I have published them behind an Application Proxy.
The mobile RDP client app seems to require the a webfeed URL. However, when that is published behind Azure AD Application Proxy, I do not get an authentication page and the connection breaks.
The mobile RDP clients do have an option to add Azure RemoteApp which seems to prompt for an Azure AD username and password. Of course, my apps are hosted on-premise and only published using Azure Authentication but this functionality is sort of what I am hoping I can find.
Any help would be greatly appreciated.
Thanks!
Environment:
Session Host: Windows 2012 R2
RDP Client: Any
Application: Clarion Win32 MDI based app.
Remote App mode.
Issue:
User is operating a Clarion Win32 MDI based application as a Published Remote App.
When an MDI window is opened and a user presses ALT to access main toolbar menu in the parent and then clicks outside the app and back in the whole app freezes. It stays locked with file highlighted as per below:
If I jump into process explorer and kill the MDI child thread the interface resumes per normal.
On further investigation it seems like child thread is blocking. If the user does not open MDI thread and presses ALT the issue does not occur.
------
The latest Windows 10 1607 anniversary patch seems to have caused this issue on local installs now too. On investigating wait chain we see the following result on the thread:
Thread is sending a USER message:
Window 0x180618 (SampleApp.exe (8296): 7632): ClaWin024A0000H_1 "Sample Application [Sample 1]"
At this point accessing other windows, launching start menu, etc... doesn't work properly until thread is killed.
I know on Windows Server 2012 R2 there is an option to assign different static IPs to each user or application by using either a DHCP server or setting a range of IPs via the registry. I need more control than that and need to assign a specific internal IP per user for some of the SIP-based applications to work. I need to NAT specific internal IPs to specific external IPs using the firewall and the only way I can achieve this is to make sure each user gets a unique static IP that remains the same every time a user logs in.
From what I read, this is not possible using Windows Server out of the box so I am asking if anyone knows a third party product or registry key setting that will allow me to set a specific internal IP per user when they login to Remote Desktop on the Windows Server. Does anyone know of a way to make this happen - even if it requires a third party program?
Thanks in advance,
Scott
Hello guys. Need ur help
Hoping somebody can help here. I have RDS farm (2 terminal Servers) , each with approx 40 users on each. I've noticed that some users have started to complain that their CAPS LOCK and NUM LOCK key is inverted. i.e CAPS lock light is off but typing in uppercase and visa versa.
Servers are all Win2012R2. They use RDS Servers
We have built a Windows server 2012 R2 RDS server, and setup the whole deployment on one server, Gateway, Broker, licensing, session host, and collection.
But when we go to shadow the user using Server manager or command line mstsc /shadow:n when get this very helpful error: Unspecified error in a Window called Shadow Error
I have tested Shadowing on another networks server with a similar setup and it works fine, only difference is the Active directory server are 2008 vs this one that doesn't work being 2003.
I have also tested using local accounts and still get the same error, and there is not a lot on the web regarding this error and RDS shadowing
I noticed some strange thing on one of my servers which is a hosted VM with Server 2012R2 on it and session-based RDS installed. First on the list of Administrators I found a non resolved SID then when I went to RDS Connections I noticed users from domainB connected to the server however in Session Connection properties the "domain\B Domain Users" group was missing. I tried adding the group and Check Name resolved it just fine yet after clicking OK an error popped up saying "The security identifier could not be resolved.... The network path was not found". I enabled debugging and found the following errors. Where to go next to fix this issue?
40963: Component RdmsUI: Error in script execution on: server
40963: Component RdmsUI: Failed to fetch local DB connection string from server: server: System.Management.Automation.RemoteException: Property DBConnString does not exist at path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters. at Microsoft.RemoteDesktopServices.Common.DeploymentModel.ExecutePowerShellScript(String serverName, String script, Object argumentList, Boolean isLocalhost) at Microsoft.RemoteDesktopServices.Common.DeploymentModel.IsHighAvailabilityConfigured(String managementServer)
40962: Component RdmsUI: Exception occurred in GetSecurityDescriptorFromPath with parameters path: WinNT://domainB/Domain Users. Exception details: System.Runtime.InteropServices.COMException (0x80070035): The network path was not found. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at Microsoft.RemoteDesktopServices.RDManagement.Utils.CommonUtils.GetSecurityDescriptorFromPath(String path)
40963: Component RDExceptionHandler: The security identifier could not be resolved. Ensure that a two-way trust exists for the domain of the selected users. Exception: The network path was not found.
yaro
I have a Remote Desktop server that has been working fine for almost two years. The RD server is ts03.xyz.local and the licensing is DC01.xyz.local.
Suddenly today, no one can connect. When I go into server manager > remote desktop services > Overview I get the following error:
The server pool does not match the RD Connection Brokers that are in it. Errors:
1. Cannot connect to any fo the specified RD Connection Broker Server. Ensure that at least one server is available and that the Remote Desktop Management (rdms), RD Connection Broker (tssdis), or RemoteApp and Desktop Connection (tscpubrpc) services
are running.
ts03.xyz.local
I checked and all of these servers are running, however, they did not all start automatically as they should have.
Next I clicked on Server to check the events. When DC01 is selected, I get Error 85 that the server could not be registered as a service connection point in Active Directory. It would not register and I even tried to do it manually with ADSI Edit, but no go. The DC01 server is all good except when I log in to it I keep getting temporary profiles (I cannot seem to fix that either).
Now going back up and clicking on ts03.xyz.locak, I get other errors.
Error 2: Config sync failed. Following error occurred: 0xFFFFFFFF
Error 1306: Remote Desktop Connection Broker Client failed to redirect the user abc\remote. Error: NULL
Error 1296: Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User abc\remote. Error: Remtoe Desktop Connection Broker is not ready for RPC communication
I am at a loss because it seems my whole infrastructure has crashed here. Any help will be appreciated.
Anyone use RDS 2012 with Citrix PVS or VMWARE Composer? Any documents or blogs that might have some insight into the subject? I am just looking to have the RDS Session Host servers on a Citrix PVS type disk so we can make sure all of them are exactly the same.
TIA for any info.
