Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We installed RDS, all roles, on a machine in one domain, DomainA. We've decided to move the machine to a domain in a different forest, DomainB. Our admins simply joined the machine to the new domain, but now it appears that RDS has pointers to the old machine name, i.e. machine.DomainA.

We can remove the licenses and re-add them, but there seems to be information stored somewhere that is telling the machine that the old machine is associated with the "Deployment".

It doesn't appear that the information is stored in AD, because after we join the machine to the new domain and reboot, it still thinks that MachineA.DomainA is part of the RDS deployment.

The question is, how do you move a machine which is running RDS to a new domain, or is it impossible to do so?

share|improve this question
up vote 2 down vote accepted

Well, actually, you don't "move" the server (if you can avoid it), because of precisely the problems you're experiencing.

The Microsoft recommendation is to migrate the RDS role from the existing server to a new server you've prepared in the other domain/forest.

Following the link, you can see that it's not a trivial procedure, and varies greatly depending on your exact configuration. If I were in your shoes, I would probably try to put the RDS server back (join it to the old domain) and step through the migration procedure in the documentation I linked. If joining the server back to the old domain doesn't fix your issues (and it might not), then I think your best bet is to restore from backups, and try the migration procedure.

Oh, and try to sort your admins out. Just joining a server to a different domain does not strike me as the actions of someone who knows what they're doing. I could see trying it myself, but only after backing everything up, and preparing to quickly revert to a backup/snapshot in the expected case that it didn't work.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.