RDS Collection error: Unable to configure the RD Sessionhost server. Invalid operation

When trying to create a new Remote Desktop Session Collection you receive an error: Unable to configure the RD Sessionhost server servername.domain.local. Invalid operation.

rds collection error

The collection it self is created but not completly, some parts are missing, like there is no Desktop icon on the Webaccess page. And probably some other settings aren’t set correctly. So it would be wise to solve the problem, delete the old and create a new collection.

Described in this kb kb3014614 article it is a know issue, some policies are already applied to the RD Session Host server. To solve the issue make sure there are no policies set to the new RD Session Host server especially these two gpo strings:

  • Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Security
  • Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing

In most cases this would be the case when there is already an existing Remote Desktop server and policies are applied via a group policy to a specific OU and the new server is already moved to this OU.

Move the new Remote Desktop server to another OU where no policies are applied. Run gpupdate /force or reboot the new RDSH server. Then delete the existing collection and create a new collection.

If you already set local policies on the RD Sesions Host policy these also need to be removed.

Posted in Remote Desktop, Windows Server 2012 R2 at February 24th, 2016. 20 Comments.

Cannot import a server 2008 R2 Virtual Machine on a server 2012 R2 Hyper-V host

If you have created an export of a virtual machine on a windows 2008 R2 server and try to import the export on a windows server 2012 R2 Hyper-V host, you get the following error:

import vm error

“Hyper-V did not find virtual machines to import from location”

The Problem: After some searches I found this article “Windows Hyper-V 2012 & 8.1 Hyper-V Did Not Find Virtual Machine to Import” which describes the problem I ran into.

The problem is “WMI root\virtualization namespace v1 (used in Hyper-V)” has been removed in Windows Server 2012 R2, it was deprecated in Windows Server 2012 but still exist so you could import the export in Server 2012, but it is removed in Server 2012 R2. Since Server 2012 they introduced WMI namespace (version 2 or root\virtualization\v2.

Solution: There are a couple of workarounds possible,

  • First you can just copy the VHD files and just built a new Virtual machine with the existing VHD files.
  • Second if you have a windows Server 2012 server you can import the machine on this server and make an export and then copy that export to the 2012 R2 server.
  • Last option if the existing Virtual Machine is still on the windows 2008 R2 server, stop the Virtual Machine, copy the complete directory with VHD and configuration to the 2012 R2 server and on then choose import on the 2012 R2 and point to the copied folder.
Posted in Hyper-V, Windows 2008R2, Windows Server 2012 R2 at January 27th, 2014. No Comments.

Sharing Buttons by Linksku