latpearl.blogg.se

1. #WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION HOW TO#
2. #WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION SERIES#
3. #WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION WINDOWS#

Let’s set up the group that we want to allow access to this WordPad RemoteApp so it will only be accessible for that particular set of users.

Now let’s try to do another common configuration with PowerShell. When we refresh the RD WebAccess page we are presented with the WordPad RemoteApp, and we have the possibility of launching it from this window. Set-RDRemoteApp -CollectionName MySessionCollection -Alias Wordpad -ShowInWebAccess $TRUE -ConnectionBroker So to configure our WordPad.exe RemoteApp to become available inside RD WebAccess we use the following command: You can use set-rdremoteapp to configure all the settings you would normally do inside the new Server Manager. This can easily be done by making use of the set-rdremoteapp cmdlet. As a next step, we are going to make the WordPad.exe RemoteApp also available on the RD WebAccess page. The output of the command is too large to show it here, but you can easily run the command yourself and check the results. A good way to get an overview of all cmdlets that are available inside the RemoteDesktop PowerShell Module, we run the following command: New-rdremoteapp -Alias Wordpad -DisplayName WordPad -FilePath “C:\Program Files\Windows NT\Accessories\wordpad.exe” -ShowInWebAccess 1 -collectionname MySessionCollection -ConnectionBroker įrom this step forward, we are assuming that the above-mentioned commands have been run. To complete, we finished it off by adding a new RemoteApp to launch WordPad.exe New-RDSessionCollection -CollectionName MySessionCollection -SessionHost -CollectionDescription “This Collection Serves purpose A, B and C” -ConnectionBroker New-SessionDeployment -ConnectionBroker -WebAccessServer -SessionHost Īfter the deployment, we ran the following command which created a new Session Collection inside the Quick Scenario Deployment. We then deployed a Quick Scenario using Session Virtualization by running the following command: The first step was to import the Remote Desktop PowerShell module by using the following command: So let’s do a quick recap of what we discussed related to the Session-based desktop deployment in the previous article.

We will be focusing on the Session-based desktop deployment. In this article, we will be diving deeper into further deploying a Remote Desktop Services scenario which serves Sessions.

#WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION WINDOWS#

In this article we’ll dive a little but deeper into PowerShell for RDS to take a look at how we can even further automate the installation, configuration and maintenance of Remote Desktop Services using the new PowerShell commands available with Windows Server 2012.

#WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION HOW TO#

In that article, amongst other things, we discussed how to do a quick RDS deployment, add a Session Collection and add a RemoteApp.

In a previous article, I discussed how to use PowerShell to set up a basic Remote Desktop Services environment.

#WINDOWS SERVER 2012 REMOTE DESKTOP CONFIGURATION SERIES#

If you would like to read the first article in this series please go to Using PowerShell to control RDS in Windows Server 2012.