When using PowerShell remoting from a client system that's not a member of the domain, I get the following error message:
Get-RDSessionCollection : A Remote Desktop Services deployment does not exist on rds1.lab.test. This operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help New-RDVirtualDesktopDeployment"
or "Get-Help New-RDSessionDeployment".
This is the command I'm using to connect to the RDS server remotely using PowerShell:
Enter-PSSession -ComputerName rds1.lab.test -Credential lab\administrator
I can run all default PowerShell commands without any problem and I can import the RemoteDesktop Module using Import-Module RemoteDesktop and see and run all the related cmdlets, but they all give the error message below.
For example, if I want to check the current sessions on the RDS server, I try to run this command:
Get-RDUserSession -CollectionName 'RDSfarm1' -ConnectionBroker 'rds1.lab.test'
It doesn't seem to make a difference which cmdlet I choose or if I specify the collectionname and connectionbroker or not...
I'm running PowerShell v5 on Windows 10 standalone client. The reason it's not connected to the domain is that I manage loads of different Windows Domain environments for multiple organizations.