Pages

Tuesday, July 26, 2011

Unable to add VMs to a pool in RD Connection Manager on RD Connection Broker - no VMs appear

Today when I tried to start up a Remote Desktop Services Pooled VM, I got the following message:


This correlated with the following Event ID on the RD Connection Broker:
  • Log Name:      Microsoft-Windows-TerminalServices-SessionBroker/Operational
  • Source:        Microsoft-Windows-TerminalServices-SessionBroker
  • Date:          7/26/2011 1:37:28 PM
  • Event ID:      802
  • Task Category: RD Connection Broker processes connection request
  • Level:         Error
  • Keywords:     
  • User:          NETWORK SERVICE
  • Computer:      PYRAMID.ash.local
  • Description:
  • RD Connection Broker failed to process the connection request for user ASH\kristin.
  • Farm name specified in user's RDP file (hints) could not be found.
  • HRESULT = 0x88130018.
On the RD Virtualization Host server, I got this event log error in the application log:
  • Log Name:      Application
  • Source:        Microsoft-Windows-WMI
  • Date:          7/26/2011 1:46:07 PM
  • Event ID:      5605
  • Task Category: None
  • Level:         Warning
  • Keywords:      Classic
  • User:          N/A
  • Computer:      ROCKY.ash.local
  • Description:
  • The root\cimv2\TerminalServices namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
On the RD Connection Broker, I removed and re-added the RD Virtualization Host server that houses the VMs for the VM pool was trying to access. I got a dialog box telling me that the "RDS hyper-v agent service was stopped" and the VMs for that virtualization host server would ont be available until it was started.

I naturally looked in the Services.msc to start the stopped service but it was not there. At least not listed as such.

THE FIX:

I stopped and restarted the following services on the RD Virtualization Host server:

  • Hyper-V Virtual Machine Management
  • Remote Desktop Virtualization Host Agent (a dependant service)
  • RemoteFX Session Licensing (a dependant service)
Issue solved.


 

Sunday, July 24, 2011

Screensaver (and screen power off option) does not activate on Windows 2008 R2

This also is not RDS specific but I am glad it’s now fixed so I am going to share it. An issue I had with my Windows 20008 R2 64bit laptop was that the screen saver would not start. I did find out (through trial and error) that if I run the screensaver (c:\windows\system32\bubbles.scr) from the RUN box, it comes on, and when I move my mouse, it goes away. So at least I had a workaround to needing to walk away from my laptop and not have my desktop stuff burned onto the screen over time. However, this is stupid and painful. I just want a silly screensaver to work!!!
Thankfully I found this: http://support.microsoft.com/kb/913405
I installed the latest Intellipoint software, as I do use a Microsoft optical mouse. This fixed my screensaver issue.

Incidentally, the screen now also turns off after the specified amount of time, whereas before I installed the latest Intellipoint, this power saving feature did not work.

Cannot Use Sleep Mode on Windows 2008 R2 With Hyper-V

This is not RDS specific but it is annoying. I have a laptop on which I run Windows Server 2008 R2. I use this laptop to run Hyper-V and VMs so I can do demos and testing. I also use this laptop for personal use. I would like to be able to take advantage of power settings like sleep mode, but because I run the Hyper-V hypervisor, I cannot (see: http://support.microsoft.com/kb/913405).

Here is a way around it: turn off the hypervisor when you boot by making a “no hypervisor” boot option.

IMPORTANT: THIS IS NOT SUPPORTED!!! (but it works for me):
1. At the command prompt, type the following: bcdedit /copy {default} /d "No Hypervisor"
         (this creates the extra boot option).

     The above command should say: The entry was successfully copied to {guid}.

3. Copy that guid to the clipboard including the brackets.

4. Now, type the following command: bcdedit /set {PLACE-GUID-HERE} hypervisorlaunchtype off 
         (this stops the hypervisor from running)
Now when you boot, you can use Sleep mode.

Monday, July 18, 2011

Using Wildcard Certificate and UCC certificates for RD Session Host server farms (2008 R2 SP1)

This is an update to a previous post I did regarding certificates for RDS. It used to be (in 2008, and 2008 R2) that you could not use wildcard or UCC for RD Session Host farm servers. This has changed.

Since installing 2008 R2 SP1, I have again tested securing RDSH farm servers using a wildcard certificate and a UCC certificate, and now I get no errors!

Example: I used a wildcard certificate (*.domain.com) for securing RD Gateway, securing the RDWA website, all RDSH farm servers, and for RemoteApp signing, and I now get no errors.

I have not been able to confirm exactly what change has been made by Microsoft but SOMEthing has definitely changed to make using wildcard and UCC certificates for RDSH farm servers work.

Monday, July 11, 2011

RDS certificate issue - The certificate is not valid for this usage

If you have purchased a certificate for use with RDS, and after you install it you get the error: 'The certificate is not valid for this usage', check to see if your certificate has a long certificate chain ( multiple intermediate CAs in the chain).

If it does, then get the public CA to re-issue a certificate to you that has a shorter chain (like, one root and one intermediary).