Help with failed child DC!

[jamesb]

We have a 3-domain structure.
One "master" and two child domains. The two child domains have one DC each
(poor I know, but hey, I have to work to a budget....)

Anyway, one of the child DC's has died a death. In the meantime we had the
idea of letting users access a terminal server in the main domain so they
can do something vaguely useful. The trouble is, they can't log in as of
course the TS is trying to contact the child domain DC to authorise the
users logins. I thought it might work as the parent domain has a Global
Catalog but I guess not...

Anyway, is there any way I can seize FSMO roles from the child domain to the
parent one temporarily, or anything else that might work to enable the users
to access our TS?

My last resort is creating user accounts in the parent domain for the users
but it's a bit of a faff if there is a "proper" way to do this!

 

[Jmnts]

Hello
The fastest way to achive that is to create temporary users accounts on your
main server to allow users logon.

Now, if I understand right, you have 1 top level domain, and 2 different
child domains.

You can't seize rules to the main server because he is already a Master
Operations of the PDC Rule, RID and Infrastructure for his own domain.
PDC emulator, infrastructure master, and Relative Identifier (RID) master,
existes only once per domain.

You can only seize the Forestwide rules wich are schema master, domain
naming master.

You could seize rules to the child domain if you had a adicional cdomain
controller, but it seams that's not the case so...

So you need to recover the child domain to a different Server box to achive
please try this link:
http://support.microsoft.com/?id=263532