Server 2012 R2 - RDS - "A remote desktop services deployment does not exist"
I've got Remote Desktop Services running in a Server 2012 R2 environment.
There's these server/roles;
RDSPRD00.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
RDSPrd01.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
RDSPrd02.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
HQ-DC2012r2-1.cafenet.com-
Problem is if I remote into RDSPrd01 or RDSPrd02 using mstsc /admin and then local powershell try to run anything like "Get-RDLicenseConfiguratio
I can run the commands fine on RDSPRD00 so I'm not sure what the deal is.
Online advice elsewhere has advised to run Powershell as Admin, which I am, or verify no "PendfingFileRenameOperati
Applications are installed on these servers that are launchable. We have a remoteapps.cafenet.com website setup where we login to and then launch an application which could be round-robin'd from one of the RDSPRD servers.
There's these server/roles;
RDSPRD00.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
RDSPrd01.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
RDSPrd02.cafenet.com - {RDS-RD-SERVER, RDS-CONNECTION-BROKER, RDS-WEB-ACCESS}
HQ-DC2012r2-1.cafenet.com-
Problem is if I remote into RDSPrd01 or RDSPrd02 using mstsc /admin and then local powershell try to run anything like "Get-RDLicenseConfiguratio
Get-RDRemoteApp : A Remote Desktop Services deployment does not exist on RDSPrd01.cafenet.com. 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".
At line:1 char:1
+ Get-RDRemoteApp
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteE rrorExcept ion,Get-RD RemoteApp
I can run the commands fine on RDSPRD00 so I'm not sure what the deal is.
Online advice elsewhere has advised to run Powershell as Admin, which I am, or verify no "PendfingFileRenameOperati
Applications are installed on these servers that are launchable. We have a remoteapps.cafenet.com website setup where we login to and then launch an application which could be round-robin'd from one of the RDSPRD servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Would that configuration be causing the issue in post? I do appreciate that and will look into it. I'm just not sure what's going on with the error being returned in Powershell on those servers.
From the domain controller/licensing, I can show that those servers are part of RDS so I'm not sure why it returns an error when running get/set commands.
From the domain controller/licensing, I can show that those servers are part of RDS so I'm not sure why it returns an error when running get/set commands.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It looks like "Remote Desktop Connection Broker" can be unchecked in the Remove Roles and Features wizard, and I can leave "Remote Desktop Session Host" and "Remote Desktop Web Access".
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok thanks. By deployment wizard, you are referring to the built-in Server Manager in 2012 R2 right? Or is there a different deployment wizard that takes you through the steps?
ASKER
can you direct me to a topology chart that makes sense so I can go by it? very interested to see.
Would this one make sense to you? http://blogs.technet.com/b/yungchou/archive/2010/01/04/remote-desktop-services-rds-architecture-explained.aspx
Would this one make sense to you? http://blogs.technet.com/b/yungchou/archive/2010/01/04/remote-desktop-services-rds-architecture-explained.aspx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
by new wizards you mean the Server Manager Add Features/Roles in Windows 2012 server manager, right? I'm not missing some downloadable wizard, right?
I appreciate the link and will sift through all the stuff that isn't applicable.
As for other sites, what do you think of this guide? http://searchvirtualdesktop.techtarget.com/tip/How-to-install-Remote-Desktop-Services-in-Windows-Server-2012
I appreciate the link and will sift through all the stuff that isn't applicable.
As for other sites, what do you think of this guide? http://searchvirtualdesktop.techtarget.com/tip/How-to-install-Remote-Desktop-Services-in-Windows-Server-2012
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok thank you.
ASKER
How does this high level look for a new simple deployment?
1. Create 4 new Server 2012 R2 servers. 1 for RD management in Server Manager, 1 for Connection Broker, 1 for Web Access, 1 for RD Session Host
1. New servers will be a fresh start and allow us to start over and also fix local Windows OS/profile issues we’ve been noticing. Can be identical VM specs to existing servers.
2. We can add scale to additional later as needed and revisit more high availability options once we have a known working system in order that we can backup/restore if further changes cause issues.
2. Organize servers into a new AD OU container accordingly, for easier server and GPO management.
3. From management server’s “Server Manager”, add the servers to a new server group to be managed.
4. Select that group in the navigation pane and run the Add Roles and Features Wizard.
5. Choose the installation type "Remote Desktop Services installation" > “Standard Deployment” > “Session-based desktop deployment” in the Wizard.
6. Assign each role to each server accordingly, allowing it to perform the installations and reboots as needed.
7. Edit the new RDS deployment properties to point to HQ-DC2012r2-1 for licensing, since it’s already setup there.
8. Create Collection and add the 1 RD Session Host to it, install & configure applications, etc.
1. Create 4 new Server 2012 R2 servers. 1 for RD management in Server Manager, 1 for Connection Broker, 1 for Web Access, 1 for RD Session Host
1. New servers will be a fresh start and allow us to start over and also fix local Windows OS/profile issues we’ve been noticing. Can be identical VM specs to existing servers.
2. We can add scale to additional later as needed and revisit more high availability options once we have a known working system in order that we can backup/restore if further changes cause issues.
2. Organize servers into a new AD OU container accordingly, for easier server and GPO management.
3. From management server’s “Server Manager”, add the servers to a new server group to be managed.
4. Select that group in the navigation pane and run the Add Roles and Features Wizard.
5. Choose the installation type "Remote Desktop Services installation" > “Standard Deployment” > “Session-based desktop deployment” in the Wizard.
6. Assign each role to each server accordingly, allowing it to perform the installations and reboots as needed.
7. Edit the new RDS deployment properties to point to HQ-DC2012r2-1 for licensing, since it’s already setup there.
8. Create Collection and add the 1 RD Session Host to it, install & configure applications, etc.
That should work
ASKER
thanks again. still going through blog, checking for other best practices. really simply here though, we're talking 1 application for under a hundred users. would probably have to outsource if we were to expand into an extreme HA / farm /cluster environment with more advanced applications.
ASKER
Is it bad due to translation issues or something?
I believe you but do you have source for this recommendation