Hi. We haven't used connection broker in our previous 2008 R2 RDS environment, but as it is now mandatory in 2012, I'm wondering how to do the following:

When I have a RDCB (non-HA) and a session collection consisting of multiple RDSH servers, where/how do I configure the "farm" DNS name to which the RDP client will connect to? For example, RDSH servers are "server1" and "server2", but I want users to connect to rds.domain.local (which would point to the session collection?) and then RDCB should create and distribute the sessions according to the balancing rules.

Thanks in advance

My first time posting here so go easy on me ;)

I have been experiencing a weird issue in regards to using Remote Desktop to remote into VM's hosted on our Windows Server 2012 server. Sometimes I can connect to the VM and run it but it will drop connection over time. I have also done ping tests and I can connect fine but immediately drops after the first ping.

However, for some strange reason I can only remote in only when I highlight the server on Hyper-V Manager and it works just fine. But it kinda defeats the purpose if I have to highlight each server I want to remote into every time I want to access a VM. Due note that this only occurs on VM's running Windows 7 machine. 

I have researched about how what could be affecting this, and came across a few things that could be related to this issue:

-Settings in NIC's (Both physical and virtual)

-Virtual Switch Manager - "Allow management operating system to share this network adapter" option is enabled

I'm hoping someone could provide some insight on this issue.

Thank You.

Ok, I've read probably hundreds of posts on this, and tried everything they said, but I'm going to post here anyway.

I have two servers running WS2012. I have set up an Active Directory domain on one (standard edition), and successfully joined the domain on the other (datacenter edition). Then I try to install Remote Desktop Services on the server that was joined to the domain (not the domain controller server), but it is unable to install role services.

1. I have tried the quick start and standard deployment. On the quick start, it gets about 1/3 of the way through the first installation, then fails everything. On the standard, it fails and says it was unable to install the broker role service.

2. I have tried installing the role services using powershell on the local server, and then from the other server, and role services could not be installed.

3. The user that is trying these tasks is a member of all user groups on the active directory, including domain admins. This user was also added as a local administrator on both servers.

4. Both servers are on the same network, but using different gateways.

5. When the installation fails, all server roles have management errors that say Online - unable to access role and feature data.

6. Both servers have static IP addresses.

7. I have tried this installation probably 20+ times tweaking the system slightly each time, and nothing has worked.

8. The server for RDS originally had Hyper-V installed, but then I disabled it, then removed it - nothing changed.

If anyone can point me in the right direction here, I'd appreciate it. Once again, my domain controller is on a separate server from the one I am trying to install RDS on.

Hi to all,

we have a NLB Remote Desktop Farm (2 node Windows 2008 r2 SP1) and another server (Windows 2008 r2 sp1 with RDGW, RDWA and RDCB).

The users access the applications via remote desktop web access that are configured with user assignment.

All remote app have a security group associated for to control access to the application on web site.

If we change the user assignment adding or removing some users directly on RemoteAPP manager the change is replicated on web server (RDWA) immediately.

If I try to add o remove a user on the security group associated to the RemoteAPP (from Active Directory Users and Computers)  the change doesn't work or is applied after some time. A reboot of the RDWA resolve immediately the issue.

Can you give me some advice how to resolve the issue or otherwise a possible workaround?
thank you.

Daniele Castelli 

Daniele Castelli

Работал сервер терминалов на Windows Server Std 2012 в течение нескольких месяцев. Случилось ему перезагрузиться, и после загрузки пользователи не смогли зайти на удаленные рабочие столы. Не работает так же и админская удаленная консоль. Пишет, не удалось проверить лицензию этого сервера терминалов и т.п. Однако сервер должным образом был активирован ранее.
Далее обнаружил, что при запуске непосредственно на сервере оснастки Лицензирование сервера терминалов выдает ошибку - отсутствует mstlsapi.dll
Данная библиотека была найдена где-то глубоко внутри в подпапках ОС (типа C:\Windows\xxxxx\7fdkrkufg4453\, точный путь не запомнил, скопировал ее в C:\Windows\system32, теперь при запуске оснастки пишет: licmgr.exe -"Ошибка при запуске приложения (0xc000007b). Нажмите ОК для продолжения"

Через удаление компонентов снёс лицензирование, перезагрузился, поставил вновь, перезагрузился, не помогло.

...

Hi

I have a questions:

With using a DNS round robin and a broker. Where is the fault detection? everywhere I look for best practices for setting up a broker it always talks of using DNS RR with Broker load balancing.

So if I have 4 records for RDSFarm (10.0.0.1 / 10.0.0.2 / 10.0.0.3 / 10.0.0.4)

If 10.0.0.1 is down and my client resolves 10.0.0.1, whether there are 3 other clients and an active broker........

How is this HA? or even a viable load balancing solution at all?

RGS

the mac clients are running RDC for mac version 2.1 and they cannot connect to Windows 2008 R2 TS server. They get the error "You were disconnected from the Windows-based computer because of problems during the licensing protocol".

really appreciated if someone have a fix for this.

thanks,

/dan

We currently run three Windows Server 2003 R2 64-bit terminal servers for all of our employees to work on.  We have done so for a number of years.  Since 2011 we have been running them in a virtual environment (VMware ESXi 4.1, migrating to 5.1 soon).  All in all, they have worked great for us and have been a great work environment for our employees.  Out of nowhere, however, we started having issues.

On May 20th of this year, we suddenly had one of our terminal servers seize up on us.  All employees working on this server suddenly saw their sessions stop responding entirely.  No new logins to the server could be made--even at the console.  Attempts to remotely connect via Event Viewer or Performance Monitor were no go.  Interestingly, remotely browsing the file system works fine, as well as connecting to see the services (though starting and stopping the services won't work).  The bottom line is that the server becomes completely unresponsive and all I am able to do is do a hard shutdown of the server and boot it back up.

Following is a list of bullet point notes of observations regarding this issues:

* This has happened since the given date to all 3 of our terminal servers and multiple times.  Sometimes it may go a couple days before it happens, sometimes it may go a couple weeks (we actually just went two weeks without any of this and then it happened again yesterday).

* Event Viewer looks clean when I get the server back up.  It indicates no issues logged, so whatever is causing this doesn't leave anything in the Event Viewer log.

* I have scoured the logs of our VMware ESXi server and things look mostly normal there.  No indications of abnormal events.

* I have moved the virtual machines to an entirely different VMware ESXi host and the issue still happens, so this helped rule out hardware issues on the ESXi host.

* No new updates have been made to the ESXi host servers--they have been running the same software and update revisions for quite some time now.

* I removed the most recent windows updates we had done before the first May 20th event (as best I could find for what had recently been installed), but that was to no avail--the issue still popped up

* The terminal server doesn't all seize up at once.  I'll find a few users will first report that they are seized up and usually by this time I am not able to log in at all to the console (or make any new remote desktop connection, either).  However, some users may still be able to work for a couple more minutes.  This all to say that it's not a sudden seize up for everyone on there at once.  It takes maybe 3-5 minutes from the first report before every last person is fully seized up.

* We have the latest service pack and windows updates (minus ones I removed which I had recently installed prior to the first event).

* We run the latest uphclean software (version 2.0.49 beta -- the most current that works on 64-bit terminal servers).  Unfortunately, the most recent non-beta version doesn't work on 64-bit Windows.

* The issue can happen no matter the load on the terminal server.  One of our terminal servers has half the number of people on it as the other two and roughly half the load.  The CPU usage and memory can be quite a bit lower than the maximum allocated for the machine and the issue will still happen.

* The issue doesn't seem to be tied to the length of terminal server uptime.  The first incident happened within 24 hours of a terminal server reboot.  This last stint has been two weeks of no seizing up (though right now we reboot our terminal servers weekly in off hours through a scheduled task).

* This KB article best describes the issue, except it's from 2003 and pre SP1 I think.  All current files I have are newer and I couldn't install this hotfix if I wanted to (I think it's rolled into current SPs / updates): http://support.microsoft.com/kb/832971?wa=wsignin1.0

* Another note on hardware activity.  Eventually once everyone has seized up and nobody is working anymore, the hardware monitor inside of the ESX host server shows most all hardware usage for the virtual machine going to little usage, except the CPU usage never flatlines.  There's still an accumulated usage of a couple Ghz of processor between 4 cores which indicates there's still something running on the terminal server and using CPU cycles.  It isn't anywhere near pegged, but there is still constant CPU activity after everything has stopped functioning.  I've noticed this every time one of our terminal servers has locked up.  There's a constant and steady indication of CPU usage that's roughly the same on any one of the terminal servers after it seizes up.

I'm sure there are more details and notes I don't have readily available of observations I have made of this issue.  I am fully and completely stumped and have no idea what more to do.  There are no leading indicators it's going to happen--it's just sudden and out of the blue.  I've been searching high and low for a pattern.  I've scoured through all software to see if a particular piece of software or an update to software might be causing it, but I'm finding nothing thus far.  I spent a couple hours last night after the lockup we had yesterday trying to get into the server to see what was going on (I moved all employees on this particular server off to a standby server to work while I tried to figure out the issue).  I can't get anywhere to see what might be the culprit.

For anyone who might be able to provide any insight or help into this problem, I would be truly grateful.  I am going to continue looking into other pieces of 3rd party software... and maybe printers as well (though nothing has been updated there in quite some time either).  I'm grabbing at straws to find what suddenly brought this on.

Thanks.

Environment

• Windows Server 2008 R2 / Remote Desktop Services
• Citrix XenApp 6.5

Users log into their Citrix published desktop and add printers through Control Panel > Printers (browsing through printers available on the Win2008R2 Print Server).

Once printers are added they are visible in their HKEY_CURRENT_USER\Printers\Connections key.

User logs out and back into another published desktop, user looks into Printers and there recently added printers aren't there. Looking at the server the user is on and browsing to HKEY_USERS\<SSID>\Printers\Connections the added printers are in there. After a short period of time (5-10mins average) the printers start appearing in the users Control Panel > Printers folder.

During that time when the printers are visible in Printers users can't add any new printers, errors with "Windows cannot connect to the printer. No printers were found". Once the printers appear in Printers then your able to add more AD printers.

The Printer Spooler service is running the whole time and no errors/warnings appear in Event Viewer.

Hi,

I have Windows Server 2012 RDS Server Farm. RDWA, RDG, RDCB and RDSH all of them on single machines. Everything works perfectly but I have a Problem with trusted Domain. All Collections are filtered / assigned to Groups but some trusted Domain users, can see all Icons in the RD web Access although they are not a  member of any Group with Access to this collections.

here is the trace from RD WEB Access Server:

2013/06/11 15:11:43 [Verbose] 8 Filtering apps for SID: S-1-5-21-604038444-1955260730-1790608899-25717
2013/06/11 15:11:43 [Error] 8 Error starting filtering: Could not initialize context from SID. SID: S-1-5-21-604038444-1955260730-1790608899-25717, Error: 0x80070005
2013/06/11 15:11:43 [Error] 8 Error calling NativeMethod to start filtering: Error: 0x80040302
2013/06/11 15:11:43 [Verbose] 8 Filtered apps stored in the cache for S-1-5-21-604038444-1955260730-1790608899-25717
2013/06/11 15:11:43 [Verbose] 8 ASP.NET location:/RDWeb/Page

Anyone able to help me?

Thanks,
Pawel

Hi,  I'm currently building a Windows 2008 R2 Remote Desktop Session Host Farm. One of the business requirements is to allow audio and video playback and I've followed all the steps outlined in the following article to the letter:

http://technet.microsoft.com/en-us/library/dd759165.aspx

When I - and my pilot users - log on to the RDSH Farm we get the speaker showing as avalable in the taskbar and to all intents and purposes everything looks fine.  I can play wav files in Windows Media Player but not much else, which unfortunately is not a lot of good for my users.

If anyone has any thoughts or recommendations, I'd appreciate them.

Hi all,

I've deployed an RDS farm with all rolesi implemented (3 session hosts, 2 connection brokers, 2 gateways, 2 rd web access). I've a strange behaviour from Windows XP Workstation:

scenario A

I can successfully connect to a remote desktop in my farm fromthe internet via the gateways

scenario B

If I try to launch a remote app trough my rd web access server, I get an error: "The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact system administrator or technical support."

I've disabled NLA in my deployment so, I can't figure out what's the trouble

Is tsctst.exe still valid on Windows 7? I try to run it to show CAL but get "Can't open key - 2" error. If not, what's the new tool to do the same thing?

Also, is KB support.microsoft.com/kb/187614 still applicable to Windows 7? I removed MSLicensing key but seemed had no effect.

In the last two days i've had two servers running Server 2008 R2 lose synchronization with the rest of the machines in the domain. When i try to RDP to the machines using their host names I get"The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name."error message.

However, when I use IP addresses I can connect without any issues. I came accross a fix yesterday suggesting i run w32tm /resync but it's not working on the second machine but it worked on the first.

The host configuration security layer on both machine is set to negotiate, I don't see how changing this option to RDS Security layer will fix it as the entire environment is configured to use negotiate security layer.

I've been using Remote Desktop to manage a remote Windows 2003 server for many years. It has been a very helpful tool.

I have used different client's windows versions during these years. I am using Windows 8 since it became available to MSDN subscribers.

Ever since I installed May 2013 Windows updates I began experiencing connection problems with my remote  Windows Server 2003.

It seems there is some kind of timeout. The connection windows shows the messages "Initiating..." and "Configuring..." twice and then presents the error message "This computer can't connect to the remote computer."

If I try again and again, eventually I am able to connect.

I have searched both client and server event viewer for the problem, but I have not found anything useful.

Any ideas?

We run TS on our SB server so that we do not have to install an often-updated custom program all the time.  In the past we used a  peer-to-peer network, but we recently went switched to a domain.

In the peer-to-peer setup, I would log into the TS server, install the program, and then all users could run the program without any special need to "run as admin".

Now that we are in a domain, we can only run the program "as admin".  So, I'm assuming there's some sort of permissions issue.  Either that or possibly my domain users cannot access SQL server for some reason.

This program inserts an .ini file into the Windows directory that all users are supposed to use.  Th thing that's different about the recent domain install from the others is that the Windows directory that the .ini file installed to was users/administrator.domain/windows

I'm pretty sure no one other than Admin can access anything in that folder to even read it.

I tried giving permissions to Domain Users for that directory, but Windows wouldn't let me.

Anyone think of something I can do?

I've searched high and low but have not yet found an answer to my problem.

I have 2 server 2012 physical machines hooked up in a cluster.

The 2 Machines are running the Remote Desktop Virtualization host & Hyper-v roles.

I have another server 2012 machine running in a cluster hosted VM. This server runs the remote desktop connection broker and Licencing server.

This all works fine.

The problem is I now would like to add the Remote Desktop Session host role to the 2 physical machines. Unfortunately this errors out during the 2nd reboot when installing the role.

I have turned on rds logging with the RDMSUI_TRACING  environment variable and enabling the debug logging under "Applications and Services Logs\Microsoft\Windows\RDMS-UI\Debug" in event log.  I'm getting no log files in c:\Windows\Logs\.

The only error I get from any of this is:

Component RdmsUI: Failed to fetch local DB connection string from server: <server running in VM (RDCB+RDLS)>.<domain>: 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)