Suddenly unable to add new Session Host to Existing or New Collections.

DaveK 1,871 Reputation points
2020-07-27T09:36:59.043+00:00

I've got a relatively new RDS 2019 environment setup which has been active for around 2 months with a handful of users for testing. The image seems to work for the session hosts so I've started to add more users and server at a time I've been adding in a new Session Host to increase capacity. I've done this 3 times so far, once for the initial test 'host0' then another twice to add in extra capacity 'host1' and 'host2'. I've also built a 'test' collection with 'testhost0' session host as a play ground for tweaks before mirroring on live. All this worked just fine.

Last week I tried to build another server and add to a new collection for a new group of users which will have a much more customised desktop so using the same process as the all the other hosts (I'm using a SCCM task sequence to deploy defined image and additional software), then moving the computer object in AD into the RDS OU so it gets the right GPO's etc. The build process all works exactly like the ones in the past and everything looks to be working until it comes to adding into a collection. I've taken the following screen grabs to show whats happening and this is where I'm a bit lost..

In the following screengrabs, RDSHOST3 is the 'new' VM I'm trying to create a new collection for. so....

1) After building server, Add to All Servers in Server Management.

13784-1-all-servers.jpg

2) Add new Session Host. Server is then seen in Deployment Servers list

13827-2-deployment-servers.jpg

3) At this point if I look in RDS Management under Servers, I can see that its not listed.

13799-3-rds-servers.jpg

4) But its listed under Host Servers?

13777-4-host-servers.jpg

5) So I try to add into a collection and I get an error

15516-5-add-host-to-collection.jpg

I've had a look though the event logs on the Session Host and on the Brokers but can seem to locate anything which helps. I've also gone a bit of searching forums etc but I've yet to come up with anything which point to an actual 'cause' which I can look to fix so being fairly new to RDS and having not been running 'live' very long I don't want to poke around too much without finding some direction.

Is there anything I can get which would help with diagnostics?
Is this an error of sorts or I'm I doing something wrong in my process to add a Session Host?

Cheers

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
{count} votes

3 answers

Sort by: Most helpful
  1. DaveK 1,871 Reputation points
    2021-12-03T10:09:28.157+00:00

    Apologies, I'd in all honesty forgot about this as soon as I was asked to move onto another issue.

    In the end it turned out the issue was related to group policies being applied to the OU these new devices were being moved to. I found that if I moved them back into another OU with no policy applied I could then add into RDS collection and move back into the right OU, everything would then work as expected. I never found the root cause within the GPO but as a workaround this allowed me to build the required collections.

    1 person found this answer helpful.
    0 comments No comments

  2. Phoebe Lu (Shanghai Wicresoft Co,.Ltd.) 91 Reputation points
    2020-07-28T09:30:03.64+00:00

    Hi,

    You could try to remove this server from host servers first and then remove it from the deployment servers and all servers.After that, you could redeploy the server again. Remember to change the host name,like host 4 or any other,and add it to the domain.Then you could find the target collection to add this server in,finally you could configure the roles you need on this server.
    Hope this can help you!

    Please make sure that the pictures you post do not contain your company and your private information (including but not limited to domain name, public IP, email account, domain account, etc.). These private information must be altered.

    Phoebe

    0 comments No comments

  3. DaveK 1,871 Reputation points
    2020-08-04T12:57:43.62+00:00

    Thanks Phoebe, I edited out the company details on the first 4 so just missed that last one. I've taken care of that now too and updated the original post.

    Things have been hectic at my end the last couple weeks so I haven't had get had time to get back to this again. I'll see if I can make some time this week to carry out the steps you have suggested to see if that gets me any further.

    As these servers are being built from a SCCM task sequence, I have tried multiple times with fresh server builds with differing names to add them into existing or new collections without success. I would like the keep the session host naming conversion in sequence is possible to keep maintenance easier for supporting staff.

    From the error info MS display when it fails to add the server to the collection, is there a root cause behind this behaviour

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.