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- {RDS-LICENSING}

Problem is if I remote into RDSPrd01 or RDSPrd02 using mstsc /admin and then local powershell try to run anything like "Get-RDLicenseConfiguration" or "RDRemoteApp" or anything with "Set-RDSessionCollectionConfiguration", I'll get the following error:

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.WriteErrorException,Get-RDRemoteApp

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 "PendfingFileRenameOperations" are in the registry, and they aren't. I've also tried rebooting the servers, but run into the same issue.

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.
garryshapeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
You should not have the RDCB role on all servers. Just one. There are ways to put it on two for high availability, but even that is a specialized cluster deployment. It really look like a bad deployment done by someone who isn't familiar with RDS in 2012.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
garryshapeAuthor Commented:
Can the RDCB role able to be removed?
Is it bad due to translation issues or something?
I believe you but do you have source for this recommendation
0
Cliff GaliherCommented:
Official RDS documentation has supported topologies. Not to mention what the RDCB does. As a broker, putting it on every server defeats the purpose. It wouldn't be "brokering" anything.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

garryshapeAuthor Commented:
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.
0
Cliff GaliherCommented:
Yes, it causes problems as you can't properly configure the topology. The topology configuration is stored on the RDCB data store. So multiple RDCBs introduces conflict and confusion.
0
garryshapeAuthor Commented:
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".
0
Cliff GaliherCommented:
Yes, you can easily remove the RDCB role from the other servers, but you'll likely need to do some cleanup and reconfigure the deployment properties from the remaining server. Otherwise the other servers may still look for their "missing" RDCBs.  As I said in my first post, that was quite a mess.  If this is a new deployment, I'd be inclined to suggest removing everything and starting over. And this time, use the deployment wizard.
1
garryshapeAuthor Commented:
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?
0
garryshapeAuthor Commented:
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
0
Cliff GaliherCommented:
Don't bother with blogs or posts before 2012 (that one is from 2010.) The architecture was fundamentally changed in 2012.  

Start with the RDS team blog. There are posts about architecture, design, topology, and the new wizards (which you *REALLY* should be using) and is a worthwhile read.   I won't focus on an individual post because there is actually a lot to learn and one shouldn't jump in too soon.

http://blogs.msdn.com/b/rds/
1
garryshapeAuthor Commented:
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
0
Cliff GaliherCommented:
The wizard is launched via add features/roles, but there is a special wizard in there just for RDS. It is one of the first selection boxes in the add roles wizard, that, if selected, triggers an entire set of screens to help you ensure you get a valid starting deployment.

I've found the official blog and TechNet documentation more than sufficient.  Furthermore, I've seen a *lot* of bad advice on the internet.  I'm not inclined to click through each link someone finds just to tell them if it is good or bad (Sorry, I don't have that kind of time) when I honestly believe the official stuff is plenty good.
0
garryshapeAuthor Commented:
Ok thank you.
0
garryshapeAuthor Commented:
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.
0
Cliff GaliherCommented:
That should work
1
garryshapeAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.