Here is the history of this situation. Sorry for the length but I want to give as many details as possible up front.
Our "live" network is Windows 2003 AD mixed-mode with Exchange 5.5 running on NT4. I have a server running the forest. Let's call the forest, forest.local. I have another server running a child to that called, child.local. I want to create a test environment emulating the live network so I can test Exchange 2003 with our custom application that currently requires Exchange 5.5 for custom reports. So, what I do is make a ghost copy of the forest and restore it on an identical server and put it on a stand alone test network. I created an additional AD server with the Global Catalog and with DNS. I ghost this server as well and put it on the test network. I make a ghost image of the exhange 5.5 server and restore it on a server on the test network as well.
I am now on the test network. I know that none of the FSMO roles are on this server so I need to sezie them. I go to the Operations Master tab with a right click on child.local. I seized the PDC and Infrastructure Operations Master roles with no problem. The RID Operations Master will not let me seize it. I then try the following steps.
To seize the relative ID master role
Click Start, click Run, and then type cmd.
At the command prompt, type ntdsutil.
At the ntdsutil prompt, type roles.
At the fsmo maintenance prompt, type connections.
At the server connections prompt, type connect to server, followed by the fully qualified domain name.
At the server connections prompt, type quit.
At the fsmo maintenance prompt, type seize RID master.
At the fsmo maintenance prompt, type quit.
At the ntdsutil prompt, type quit.
That works fine until I get to seize RID master where the server says Insufficient rights. I understand that I should be an Enterprise admin to do this. But, when I try to go to the Forest to add my account as Enterprise Admin, the Forest cannot see the accounts on the child.local domain. I checked the live network and it doesn't see the accounts on the child domain either from the add members to Enterprise admin tab. This will probably be a multi-step fix. Please let me know where to start.
Thanks for the help in advance