We have a Remote Desktop Services 2012 member server, this was on a Windows 2003 functional level domain and was working well. All RDS roles are on the same single server. Server is not a DC
We upgraded the last domain controller to Windows 2008, all went well
However, our RDS server is now not allowing Remote App Connections, I have tracked this down to a couple of issues which both appear to be linked to the DC functional level raise.
The last issue I can't solve is the following in the event log of the Session Broker
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. Pooled virtual desktop collection name: NULL Error: Logon to the database failed.
Searching has lead me to http://www.urtech.ca/2013/02/solved-server-2012-remote-desktop-connection-broker-server-could-not-enumerate-the-targets-for-the-provider-named-null-from-the-database/ which states that "you need to manually add your Remote Desktop server into the MEMBER OF tab of “Windows Authorization Access Group” via Active Directory Users and Computers."
I have tried this, I misread this at first and added the Computer account to the Members tab, this hasn't improved matters, reading the piece again I see that's this states the Broker (I'm assuming the computer, as the Broker Service uses the Network Service) needs to be added to the Member Of
I'm assuming this is a typo as attempting to add this Computer to the Member Of is not possible as the Add and Remove buttons are greyed and a message is showing stating "Builtin groups cannot be added to the other groups."
Any searches on this eventually lead me back to this article or http://support.microsoft.com/kb/331951 which I have read and as a result have added the Computer Account to the Windows Authorization Access group
Has anyone encountered this, or know how I can get the session broker access to the database?