Dear All,
We are planning to deploy Windows 2016 RDS infrastructure. does Windows 2016 RDS support windows 2008 RD sessions?
Dear All,
We are planning to deploy Windows 2016 RDS infrastructure. does Windows 2016 RDS support windows 2008 RD sessions?
Hi Everyone. We have a published app problem that occurs only under Windows 10. The app has been published from a Server 2012 R2 terminal services environment. The issue presents itself as a failure for the published app to redraw its screen after the user shifts focus to another application and then swaps back again.
Initially the fault presented itself as a Z order display issue, i.e. any dialogue boxes would display behind the published apps foreground / main interface. Clicking on the applications icon in the system tray would cause the dialogue box to come to the foreground. After hours of fault finding, I managed to fix that issue by disabling "Use advanced RemoteFx graphics for RemoteApp" on the Server 2012 R2 Terminal Server using gpedit.msc (in Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment). I was happy and all seemed fine, but...
Now the fault presents itself as a complete failure to redraw the foreground. This happens after the user has swapped focus from the published app to another app and back again a few times. It does not happen immediately. The app focus is there, as you can still click menu items etc (fun when their location is not drawn) and they will behave normally (i.e. redraw occurs over the display area of the drop-down menu for example). The only way to fix this is to exit the published app and relaunch. It will then work for a while and then the fault repeats.
This issue does not happen in a full terminal services session, only if the app is run as a published app.
If anyone has any ideas to resolve this it would be much appreciated.
Hi,
Our production environment is RDSH windows server 2016. I just want to know how RDSH server worked with RDS broken server. does they communicate with any service? How I can troubleshooting it if one of them broken.
By the way, if one of the server broken. does the RDS console still can be used? from my testing if one of them broken is impossible to lauch the RDS console.
Best Regards,
Apollo Ye
Hi
I am currently setting up a 2016 RDS server deployment using version 1607. The problem we are having is the trying to hide individual settings pages in the immersive control panel when using gpedit.msc Computer Configuration > Administrative Templates> Control Panel > Settings Page Visibility. However it doesn't work with version 1607. Is there anyway to get this to work as we need to open up display and screen saver settings as would like our users to access this. Currently we are having to lock down both the control panel and the immersive control panel using User Configuration > Administrative Templates > Control Panel > Prohibit access to control panel and PC settings as we dont want them to access other stuff in PC settings such as windows update
Can anyone provide any suggestions\workarounds
So we have a few 2012 R2 Terminal Servers at my company that were working fine until we started the process of replacing our Domain Controllers with new Windows 2016 Servers.
Since then our users are getting intermittent "Access Denied" errors when they try to RDP to these terminal servers.
Generally the "Access Denied" error occurs when a terminal servers starts to use one of the newly added 2016 domain controllers. We can workaround the problem by sending an command telling the terminal server to use one of the older 2012 R2 domain controllers instead. Then things work again.
So the question:
Is there a misconfiguration with the new 2016 domain controllers or can an adjustment be made with the 2012 Terminal Servers?
Is the problem that Windows 2016 Domain Controllers are not compatible with 2012 R2 Remote Desktop Services servers?
We are having problems finding documentation on this.
What we do know is that if we decide to start upgrading to new 2016 Terminal Servers we will have to purchase new 2016 RDS Cals (not sure if we are budgeted for that...)
For those interested, you can find out the domain controller you are using by running the following elevated PowerShell command (this assumes the command is run remotely as you might be locked out due to the RDP access denied error):
nltest /Server:<your-terminal-server> /DSGETDC:<ad domain>
to specify the domain controller you want to be on (in our case we want to switch to back to a 2012 R2 domain controller), the command is:
nltest /Server:<your-terminal-server> /SC_RESET:<ad domain>\<specific domain controller>
Hi,
Trying to set up a new manamgemnt server. Activated RDS on it, and it gets the connections to the servers as it should. Changed the gpedit (Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections) for limit number of connections.
But still just two can connect at the same time. Is there anything else that should be checked off somewhere?
Hello,
i have a problem with my RDS.
I have installed my environmnet and i it works ok.
When i want to provide a second collection and want that only users from group A see the Apps from Collection1 and Users from group B the Apps from Collection2 it doesn't work.
Everybody can see every APP over both collections.
What i am doing wrong?
I have 2 Brokers in HA
one RDWEB Server
20 RD Session Hosts (18 for collection1 and 2 for collection2)
2 Collections
Regards
Sven
Can you tell us when we can join the Public Preview for RDMi please?
All we can find is availability Q1 2018 - do you have any more detail than this ?
Thanks
I have a fail-over cluster with two host servers and one connection broker. Each server is running Server 2016. Within the RDS deployment, there are multiple pools for individual workstation pools. The virtual machines in the pools are running Windows 10. We have a similar deployment for many sites across our company. They work pretty flawlessly most of the time. However, occasionally an issue arises where all users will receive the "requested session access is denied". Upon investigating, the services seem to be running, as expected. The virtual machines in the pools are running, and I can connect to them via Hyper-V Manager. There is just some disconnect that arises between the Connection Broker, the RDS Deployment, and the vms. The quick fix I've found is to restart the Connection Broker, which resolves the issues. I've tried restarting only the Remote Desktop Connection Broker service, but that didn't correct the problem.
In the event logs, at the time of the problem, I'm seeing:
RD Connection Broker could not find an assigned Personal Virtual Desktop for user XXXXX. HRESULT = 0x80070005
and
RD Connection Broker failed to process the connection request for user XXXXX. Load Balancing failed or Specified endpoint could not be found. Error: Access is denied.
Again, this is for ALL users across the deployment, and the issue is corrected when restarted the connection broker. I'm stumped. Has anyone seen this before or have any insight?
Hello
I am running a Server 2016 based RDS deployment. I have created a virtual desktop collection with Gen2 VM as the master image.
The collection will deploy initially with no issues at all and work as it is expected to do.
However, when I attempt to recreate all desktops due to updates etc, the job will fail with the following error reported in Server Manager:
Failed: Task: Calling into Hyper-V: failed. Result of task [0x80004005]
Looking in the event logs on the CB I am able to find this message under Microsoft-Windows-TerminalServices-SessionBroker/Admin:
VM host [host.name] failed to execute VM Provisioning operation [Task: Calling into Hyper-V: ] for virtual machine [Gen-0] in pool [Gen_2_Test], Error: [Unspecified error ]
If I look in the VMMS event log on the actual Hyper-V host itself I can find this message:
However, the machine is still there and booted? However it will stop the rest of the recreations so a collection with more than one vm will not finish.
Any pointers would be really appreciated I've Googled everything, tried with/without checkpoints, with/without the machines started at the time of recreation, with/without secure boot and nothing works. All that works, is regeneration with a Gen1 VM
Please help :)
Steve
Hi,
Since a recent update, it is no longer possible to connect to a machine running Server 2016 on the iPad and Android MS RD apps. The following message appears when trying to connect:
We couldn't connect to the remote PC. This might be due to an expired password. If this keeps happening, ask your admin or tech support for help. Error code: 0x207.
This has been tried on several servers, including fresh installs, with separate users.
There is not a problem with server 2012 R2.
Please can you help? Our staff are unable to use their iPads and Chromebooks to access important software on a remote server.
I would appreciate it if someone could get back to me as soon as possible as this is getting quite urgent now.
Kind regards,
Mark Cromwell
Hi,
We have a RDS server ( Windows Server 2012 ) connected to a DC controller ( Windows 2016 ) : frequently users can't login because domain can't be reached.
We already pushed the server in the domain again but problem remains, the events logged are
- 36887 schannel
- 1061 : remote desktop session host server was unable to retrieve users licensing information from AD. Error 0x8007054b
- 5719 NETLOGON
After sometime ... adn without changes users can login again.
What could the problem be and how could we solve that ?
Best regards
Dirk
Hi,
We have a Server 2016 with Remote Desktop Services enable but we can't connect to it anymore (it worked before).
We tried a lot of things already but not solved it yet. It seems the RDS isn't accepting connections on port 3389.
- telnet to it on port 3389 not working
- ping does work
- verified the port setting in registry
- rebooted the server
- added a separate rule to allow 3389 always
- netstat -an doesn't show an listening port on 3389
Someone an idea?
Kr Kevin
Hi, I've this issue after migration of RDS server from 2012 R2 to 2016 and client have Windows 10 1709 but with Windows 10 1703 no issue.
Any suggestions?
Hey Everyone,
I'm experimenting with 2016 RDS, as I want to upgrade our 2012R2 Session Host servers. I have 2012R2 domain controllers (if that matters).
I am noticing that roaming RDS profiles isn't working at all on my 2016 RDS session host servers. A user logs in and gets a local profile, and when they log out, the profile isn't uploaded at all. It's basically just a regular local profile. I have the field set to \\fileserver\rdsprofiles in AD. This has worked fine in RDS in 2003, 08R2, and 2012R2.
However, if I create a GPO and set the profile location that way (Computer - Policies - Administrative Templates - Windows Components - RDS - Session Host - Profiles - Set path for Remote Desktop Services Roaming User Profile), roaming profiles are created on the share and everything works fine, and I can see a new .v6 profile being created. Logging in and out roams the profile properly.
Any thoughts as to why? Has the AD 'Remote Desktop Services Profile' attribute been depreciated for 2016?
I have tried lots of troubleshooting, deleting profiles, new shares, etc, I can't seem to get it to work with the AD attribute (but works fine when set with GPO).
EDIT: Tried this in a homelab setup as well (all 2016 servers), and same thing - only the GPO setting takes effect.
Has anyone seen anything like this?
After many, many, hours of wading through and eliminating potential variables the issue has been narrowed down to being present with a Windows 8.1 VM and not on Windows 7 VM.
The problem is with glitchy display issues (Random Pixellation, Fuzzy Screen areas, Entire Screen filled with random shapes/colors etc.).
This is a Server 2012 R2 environment it is running Hyper-V Remote Desktop Virtualization Host.
Talmage D. Holt
I am looking for a way to use a single RD Web Access page to connect to different Collections. Here is what I have.
Session Collection 1 - Application published using farm webapp.domain.com (Five servers)
Session Collection 2 - Remote Desktop published using farm rds01.domain.com (Five servers)
Session Collection 3 - Remote Desktop published using farm rds02.domain.com (Five servers)
Each farm has a different use case and applications, hence the three farms. But I would like users to access any of them by logging into https://web.domain.com/RDWeb.
The farms are using round robin DNS, which could be part of the problem. I did this so if you use mstsc, the computer name points to rds01 which has an A record to all five servers.
The other potential problem could be that I used Set-RDPublishedName on the Connection Broker and changed the name to webapp.domain.com. I did this so the wildcard SSL certificate didn't issue any warnings.
It appears that the published name on the Connection Broker is what the Web Access server uses to launch everything. So instead of Remote Desktop going to RDS01 or RDS02, everything redirects to webapp. If what I am trying to do is possible, what do I need to change?
Hi,
Our production environment is RDSH windows server 2016. I just want to know how RDSH server worked with RDS broken server. does they communicate with any service? How I can troubleshooting it if one of them broken.
By the way, if one of the server broken. does the RDS console still can be used? from my testing if one of them broken is impossible to lauch the RDS console.
Best Regards,
Apollo Ye