![bling_bethere[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI183wEKJDfmbIqA65o3DgwR_QHH1pKtOhJC_2Ki1IzXKlHo-MhpJTXND8lqQIVq003gAc3T4FuBeCGYgbcyQ39F_XjgXuTzdNaOpgt8p-lolPSAH2jKlc8kPu5cQLI1kciMPW_78GN3W_/s1600-h/bling_bethere%25255B1%25255D%25255B4%25255D.png "bling_bethere[1]")
I will be doing demo’s of VDI / RDS in Windows Server 2012. If you have questions on VDI / RDS in Windows Server 2012 (or what’s coming in the R2 release) or want to see it live in action, drop by at the booth!
More info: http://europe.msteched.com/MicrosoftSolution
Opening hours of the Microsoft Solutions Experience area:
| Day/Date | Hours |
| Tuesday, 25 June | 10:30 – 13:30 |
| Wednesday, 26 June | 11:30 – 17:30 |
| Thursday, 27 June | 11:30 – 17:00 |
| Friday, 28 June | 11:30 – 15:00 |
A new blog post by Travis Howe, a developer on the Remote Desktop Virtualization team on default connections and file type associations in Remote Desktop Services on Windows Server 2012.
A summary:
When we added the RemoteApp and Desktop Connections feature in Windows Server 2008 R2 and Windows 7, many administrators wanted to be able to push connections to their users by using Group Policy. To help enable this, we supported a “silent install” API that allowed a user to be signed up for a connection without any prompts. Administrators had to push something like this script on Script Center to their users by using Group Policy.
In Windows Server 2012 and Windows 8, we improved this scenario. We have added a new Group Policy container under “Remote Desktop Services” called “RemoteApp and Desktop Connections,” and within that container have defined a new policy setting called “Specify default connection URL.” Enabling this policy setting causes users to be subscribed to RemoteApp and Desktop Connection at the specified URL. RemoteApp and Desktop Connections that have been installed by using this policy setting have a special name: default connections…”
So what do I mean when I say that default connections are able to install file type associations? When an administrator is publishing RemoteApp programs, they can also choose to publish file types that should be associated with that program. Then, when the RemoteApp program is installed as part of a default connection, we associate the RemoteApp program with those file types on the client machine.
The next time the user tries to open a file of that type, the standard Windows 8 file type association behavior will be used to determine which of the registered programs should be used to open the file. Often, the user will be given a choice. For example, if Microsoft Paint has been published as a RemoteApp program with the .bmp file type association, the user is presented with the following options…”
For the complete blog post and source:
My new article on VirtualizationAdmin.com has just been published.
