KB: Error "Invalid parameter" when add Domain Local group for VDI collection (2877941)

A new KB article (2877941) was released today (FAST PUBLISH type) regarding adding Domain Local groups to the User Groups section of a Session Collection. Apparently, this is not supported yet, but will be added in Windows Server 2012 R2.

“…Consider the following scenario:
1. Click on a VDI collection (Personal or Pooled)
2. Click Task, then click “Edit properties”
3. In the opened window of the collection properties, click “User Groups”
4. Add a group, the type is "Security Group - Domain Local"
5. Click OK, we see error "Invalid parameter"

This is a known limitation with Windows Server 2012, There is no workarounds other than using other group types. This issue will be fix in Server 2012 R2…”

Source: http://support.microsoft.com/kb/2877941/en-us?sd=rss

Windows Server 2012 Remote Desktop Services, by Klaas Langhout, a Director of Program Management in the RDS team

Yesterday a blog post by Klaas Langhout, a Director of Program Management in the Microsoft RDS team was published on blogs.technet.com. A blog post on behalf of the entire Remote Desktop Virtualization Team. A good read!

“…For Windows Server 2012 we listened to our customers and partners and added the most desired features and resolved the top pain points in Remote Desktop Services (RDS). Following a description of RDS, I’ll summarize some of the many dramatic improvements we have made.
For those people that are not familiar with RDS, it is the workload within Windows Server that enables users to connect to virtual desktops, session-based desktops and RemoteApp programs. The key value that RDS provides is the ability to centralize and control the applications and data that employees need to perform their job from the variety of devices that the employee uses. This provides “work anywhere from any device” while ensuring that your control and compliance needs are met.
In the previous release, we received consistent feedback that:

1. RemoteFX was very popular however its underlying protocol (RDP) did not provide a great experience over Wide Area Networks (WANs)
2. Session and virtual machine infrastructures were complicated and costly and
3. The administration experience was not simple.

Windows Server 2012 addresses each of these issues….”

Read the complete blog post here: http://blogs.technet.com/b/windowsserver/archive/2012/05/09/windows-server-2012-remote-desktop-services-rds.aspx