We have about 15 Windows 2012 R2 servers, virtual and physical
Systems are patched until 14-04-2016.
Eventlogs seems clean.
other systems like Windows 2008 R2 do not have this problem.
We have about 15 Windows 2012 R2 servers, virtual and physical
Systems are patched until 14-04-2016.
Eventlogs seems clean.
other systems like Windows 2008 R2 do not have this problem.
Hello,
Please read the whole post before giving answers, because I spent 8 hours of search with no result.
Architecture:
- Print server: Windows 2008r2 : has 3 shared printers
- TS server: Windows 2008r2 ==> Distant
- TS clients: Windows 7 64 bit (notebooks + Desktops)
Everything was working fine the printers were mapped either on the laptops or the desktops until we had power problem on the building, the UPS did not hold for the whole period, So before I turned off the Print Server.
After the power returned, I switched the print server ON:
- The printers are mapped on all the desktops and laptops but:
When the users tried to connect to the TS server the problem begin :
- From the desktops ===> the printers are mapped on the user TS session
- From the Laptops ====> the printers are not mapped on the user TS session.
(I REPEAT: EVERYTHING WAS WORKING FINE BEFORE THE POWER WENT OFF)
I checked everything:
- Drivers on the TS servers match the one on the computers
- The client settings on the TS server
- Permissions on the Spool
- logs on the TS server does not shows errors related to the printers mapping
- On the print server: I see one error 1111 TerminalServices (But the drivers are matching)
- Restarted the TS server : nothing
I need help to resolve this issue and understand why
Thank you
Hi,
After extensive testing with some users, it was decided to implement the VDI for everyone.
First users were OK, but at once, we got that kind of error
And that one.
Today, occurred with someone who has no problem yesterday.
Any idea how to solve this?
Thx
Olivier
I'm seeing the following 311 Event ID in my Remote Desktop Services logs on a Windows 2012 R2 server when trying to connect to the RDGateway server using itself as an Remote Desktop Gateway server:
The user DOMAIN\User, on client computer "IPv4 IP Address", did not connect to the following network resource: "hostname" because the remote computer does not support secure device redirection. Try selecting another network resource or possibly lower RD Gateway security by modifying RD CAP to allow client connections to resources that do not enforce device redirection.
I can RDP directly onto the server, so I don't believe it's a problem with the Remote Desktop client application on my PC. I can also use the RDGateway server to connect to other machines on the same network and domain as the RDGateway server - it only fails when I attempt to connect to the RD Gateway server using the RD Gateway server. All machines on the domain are Windows 2012 R2, but I can only surmise there's a difference somewhere between the working servers and the RDGateway server which is causing this error.
Looking through some articles the only suggestion is to remove the Only allow client connections to Remote Desktop Session Host servers that enforce RD Gateway device redirectionoption from the CAP, however that appears to make the connections less-secure, and also shouldn't be necessary being as it works for all the other PCs I'm connecting to. To confuse matters further, I have another completely separate environment built from the same scripts where this works as expected! Finally, to add insult to injury, this does appear to work following a reboot of the RDGateway server (not a practical solution for a production environment, obviously!).
Any ideas, assistance or thoughts would be greatly received.
I know about Remote Desktop Session time limits for disconnected and idle sessions etc.
Is there a way to set a minimum time for users to log back in?
We just had an issue where a user logged out, then logged right back in. Their User Profile Disk did not have enough time to un-mount and the user got logged into a different Session Host with a temporary profile.
This is on a Server 2012 Standard RDS Farm.
We would like to force users to wait at least 60 seconds before they can log back into the RDS Collection.
Hi all,
I have a client who currently has 6 RDS device CAL's for Server 2008 R2 Foundation. They would like to switch to user CALs, but they have no information with regards to their current licenses. They don't know if they include software assurance. They have no records of purchasing the current licenses. I've called Microsoft hoping that they would be able to provide the information but unfortunately they were no help.
How can I tell whether the currently installed device CALs include software assurance?
I couldn't find the Remote Desktop Services Manager snap-in in W2016 TP4
Browsing the web I understood that it is already missing from W2012. Yet I failed to find a replacing tool.
I mean, how to get an overview of who is connected to which RDS servers ?
I have numerous RDS servers, 2003R2 and 2008 R2. They are not members of a farm or alike. No broker, No roaming profiles. We kept things simple. They all are independent servers. The virtualization layer taking care of the "high availbility".
At the moment I have a MMC running in a W2008 server, where I have added all my servers (note that monitoring a W2016 TP4 RDS is OK...).
But will I monitor all my RDS servers from a W2016 or W2012 server ?
I have setup the following lab in Azure and i need your help.
A server (Domain controller) and Remote desktop services.
And another server with Multi factor authentication server.
I have setup everything following this one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/
and when im connecting i got the following error.
The user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "RPC-HTTP". The following error occurred:"23003".
Also on the security log i've got the following
Reason: The remote RADIUS (Remote Authentication Dial-In User Service) server group does not exist.
I have setup CAP to allow Domain users... Register the NPS to active directory....
I don't know what else to do.
Can someone help on that?
Thanks
I'm trying to set up an RD Connection Broker for RemoteApp, but I'm getting an error when I try to create a self signed cert for the RD Gateway:
The self-signed certificate has been successfully created, but RD Gateway cannot store the certificate in the directory C:\Users\myuserid\Documents. Please specify a different directory, and try again."
I tried other directories, all of which I have full rights to, but still no dice. I can't find anything with this error. Any idea how I can get past it?
FWIW, I have no problem logging into this server through RDP.
Thanks.
I have a Dell VRTX server with 2 blades. Each blade has 2 hyperV VMs running on them consisting of - 1xDC, 1xFile/Print, 2xTerminal Servers.
The terminal servers are running Windows Server 2008 R2.
I have setup network load balancing and rd connection broker.
The problem I have is when I connect via my NLB IP it goes in fine, if I disconnect the session and try and connect again via NLB IP it might reconnect me to the same TS again or if it tries to connect to the other TS it times out. I thought this should redirect to the disconnected TS session? This is a problem as I don't want users repeatedly trying to login until it tries to connect them to the TS they had the disconnected session on.
Any help will be greatly appreciated.
Hello everybody,
at a customer's site, we monitor how many users are online on several 2008 R2 terminal servers by querying the Win32_LogonSession WMI class filtered by LogonType = 10. However, we get way too many entries, much more than the RDP manager shows. It turned out that WMI gives us entries for sessions which had logged off weeks (!) ago.
How can we get the correct number of RDP server users active via PowerShell on 2008 R2? How do we have to filter Win32_LogonSession correctly? Thanks for any enlightment.
Best Regards, Stefan Falk
We have one windows 2012 R2 server with 200 licenses available with only 20 terminal services licenses being used currently.
This server is not a license server that we want to licenses from. We do not have a license server in our enterprise. And we do NOT want to migrate all the licenses from the source server. We only need to migrate some of the licenses. note the server with all the 200 licenses is currently using 20 of these licenses so we want to continue to be able to add terminal services licenses on this server with the 200 licenses. Note- we do not want to rebuild the licensing server database with the terminal licenses because we have user who use terminal services.
And we have a windows 2012 R2 server which needs some of these licenses.
How do we migrate some of the remote desktop services (terminal services) licenses from one Windows 2012 R2 server to another Windows 2012 R2 server?
dsk
Hi -
I have a Hyper V 2012 R2 Host that has 8 different VMs. 2 out of 8 VMs are running 2008 R2 as Terminal servers.
In the terminal server environment, we run one application, which hangs in the background even after closing the window. It happens on only that program.
I ran process explorer, process monitor - it doesn't point anything out to why the application is hanging under windows task manager under processes even after closing the application window.
Not sure what/where to take this issue, is it hyper-v? is it Terminal services?
Thanks.
I am switching our currently 2008 RDS server over to a new 2012 server. I have it all setup but am looking to replicate the setting on 2008 called "Show a remote desktop connection to this RD Session host server in RD Web Access" under "RD Session Host Server".
Right now I just wanted a way for our users to login to the RD Web Access page and see a link to RD into the current host like we did with 2008. It should not be that difficult but for some reason I cannot figure it out or even search for what I am asking for...lol
Thanks,
Scott
Hi All,
Currently have a server 2008 r2 machine running rdsh & rdweb services (no broker or gateway installed).
I recently started customizing our RDWeb page - a few changes i made were to remove the remote desktop access option from the rdweb menu (showdesktop from true to false), comment out the help link once logged into rdweb and added in compatibility options for IE when viewing RDWeb on IE11 - X-UA-Compatible IE=9.
Once i did these i then tried publishing some apps using the App Manager, however now when i publish any apps, as shown in the pictures, they seem to appear as RDP icons even when i dont have any custom RDP options set. I also seem to get 'The Remote computer could not be found' even when executing both the 'paint' file or the custom rdp files i created.
Any help would be much appreciated.
Regards, sas_786
Hello,
We have a 2012 r2 server running RDS publishing a number of RemoteApps.
When we go to the Server Manager and drill down to the Remote Desktop Services area we are seeing a number of the sections that will not display their information and we can no longer manage RDS via Server Manager.
Starting at Server Manager\Remote Desktop Services\Overview the "Deployment Servers" window shows a red banner with "Could not refresh the list of servers"
Going to the Server Manager\Remote Desktop Services\Collections, all three of the windows, Collections, Host Servers, and Connections will eventually display the similar type of error message, stating to check the status of the services for Remove Desktop Connection, Windows Remote Management and Windows Internal Database.
The server is fully patched, event logs don't show anything of note.
We've rebooted the server and confirmed all those services and all "Remote Desktop *" services are running.
We're still able to access the RDWeb instance to use the published applications.
This had been working previously, not sure when it last was though as we don't always go into Server manager. We can manage the remoteapps via powershell, but are curious why Server Manager no longer functions.
Any assistance would be greatly appreciated.
thanks...
Hi,
Got two collections for RDS. One for remoteapp, one for desktop. When I change/add an app to the remoteapp Collection, the Remoteapp gets displayed the next day on my Clients after the scheduled task (update Connections) is run. This task takes sometimes up to 30 minutes to finish running. (Windows 10 Clients) The task default is run at 00:00. But when the Client starts the task scheduler recognizes it hasn't run, so it runs it for the logged on user.
I am looking for a way to trigger this update/refresh by GPO or something.
Anyone got an idea?
yours sincerly, Robin E. Turpijn Microsoft System Center Specialist @ Atea, Norge.
We have about 15 Windows 2012 R2 servers, virtual and physical
Systems are patched until 14-04-2016.
Eventlogs seems clean.
other systems like Windows 2008 R2 do not have this problem.
I am trying to do a quick start session installation and I am getting this error for the connection broker
I manually added the roles and its working except it says there is no deployment server.
I then switched over to using the admin account that was migrated over from the Windows Server 2003.
I removed the manual installation of the RDS roles. I rebooted, then I tried using a standard session deployment. I am now running into this error:
The active directory services are now non existent as I can't see the database anymore. It says the domain is not available even though it has been migrated over from an old server.
I am not onsite to reload the database and I am starting to question if the transfer came over successfully because I should be able to cut off the old server and this server will be the primary. It also has the FSMO roles as well.
Update:
I restarted the AD DS services and now DNS is encountering an issue with Active Directory services. I tried to open up the Active Directory forest and here is the error message:
I find this very confusing because the server was working yesterday when I took it back to my facility. I just couldn't get RDS to install correctly.