Remote Desktop services does not exist after server's RE-IP

Hi,
1.Kindly confirm if you are logging in with domain admin account to the server with RDCB role.

2.What if trying to add other servers into the RDCB server management pool again? If there is any issues, kindly share the details.

3.Steps instructed to check if WID was working well.

• Open PowerShell, and type “get-windowsfeature” with enter.
• Check the cmdlet result and confirm that if Windows Internal Database has been installed.

If WID(Windows Internal Database) has been installed:

• Open Run, type “services.msc” and end with enter.
• Find service Windows Internal Database, open its Properties – Log On, make sure it has been configured with “Local system account”.
• Save the change and re-start the service, try to install RD CB again.

If problem persists, please try:

• Uninstall the Windows Internal Database.
• Rename the old WID (C:\Windows) to WID_old.
• Try to install RDCB again to check the result.

4.Is there any other problem behavior when users started the remote session to the servers after RE-IP?

Reference link:
https://social.technet.microsoft.com/Forums/en-US/fd13f6a2-6f2b-482c-bd2b-14dc6c0894e0/windows-server-2016-rd-connection-broker-failed-to-install-because-one-or-more-parent-service?forum=winserverTS

Hope this helps and please help to accept as Answer if the response is useful.

Thanks,
Jenny

Thank you Jenny @Jenny Yan-MSFT .

1. I use the same domain admin account to login to the server both before and after re-ip.
2. other servers can be added into RDCB server management pool again without problem. Only one server has issue. It can be added to the "all servers" pool, but not "servers" pool in "remote desktop services". In the "all servers", this server shows no powershell installed although it has.
3. Windows Internal Database is installed and running. Changed it to "Local system account”. Rebooted. Still get the same error "a remote desktop service deployment does not exist". If trying to install it, then get "remote desktop services deployment is already exist. select an rd connection broker on which to create the remote desktop services deployment". But if I selected the current rd connection broker, it returns "could not retrieve the deployment information from the RD connection broker".
4. Can I try remove and reinstall connection broker? We have rds license installed already. Will remove connection broker affect that?
5. The GPO for RD connection broker has "use ip address redirection" enabled.

Thank you for your help. Any more suggestions?

I know this is a very old thread but I had this issue and couldn't find anything online to fix it.

Figured out today that if you remove the broker from the server manager and then add it back in, then it all comes back to life!

Not sure how I fixed it on the actual broker's Server Manager as you can't remove the server you are on... but after playing around and cleaning it out completely, that has started working again.

Hope this helps someone.

Our situation happened after migrating the broker VM from VMWare to Hyper-V which blats the NIC.