We build turn-key solutions for customers, and for years, we have been doing this. What I am looking for is a script-based method of performing the following actions:
- Install Remote Desktop Services Session Host
- Configure some "standard" settings: IdleTimeOut, Disconnected session behavior, temporary folders, encryption levels and such
My understanding, with w2k12, is all of this must be done to a Session Collection. I have a PowerShell script that performs the install of Remote Desktop Services - Session Host, Connection Broker, and Web Access (Add-WindowsFeature RDS-RD-Server, RDS-Connection-Broker, RDS-Web-Access) while NOT on a domain, and now I am stuck trying to configure it.
When testing with this server on my production domain, I can get the following command to run: ($strFQDN is populated in the script)
New-RDSessionDeployment -ConnectionBroker $strFQDN -WebAccessServer $strFQDN -SessionHost $strFQDN
Once off of the domain (which is a requirement for customer server builds, not allowed to be on my domain, or any until it is at the customer site) I cannot get this command to function as expected. I am presented with the following output:
New-RDSessionDeployment : Validation failed for the "RD Connection Broker" parameter.
<ServerName> Unable to connect to the server by using Windows PowerShell remoting. Verify that you can
connect to the server.
At C:\scripts\ConfigureRDS.ps1:23 char:1
+ New-RDSessionDeployment -ConnectionBroker $strFQDN -WebAccessServer $strFQDN -Se ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDSessionDeployment
The answer provided here (http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/cbffb2d4-ff9d-49ee-a9ce-a60db2262422) is simply a cop-out, as to why this was so poorly designed. Yes, more people are moving to the AD world. Why in the world could that be used a justification to just completely bend over your smaller customers? Or, customers that provide a value-add on your products? But, I digress...
Thoughts? How can I accomplish this VERY simple task WITHOUT putting this system on a Domain? (Well, very simple in Windows Server 2003/8/8R2)