Hi to all,
I've this problem, I've added a windows 2003 machine to an entire windows 2000 server domain that had only 1 DC.
Now, after the adding of 2003, in the net there are 2 DC.
My objective was to migrate the Active directory from 2000 to 2003, to the aim of remove the 2000 machine after the adding.
So I've applied all the step required by the migration, preparing the AD of 2000 with the adprep commands, joining the 2003 to domain as DC, transferring all 5 roles from 2000 to 2003, and flagging the 2003 to be a global catalog.
In this way I would have all the structure of the 2000 in an exacted copy in the 2003.
Normally after this, in the MMC if I add the snap-in Group Policy Object Editor (in new server 2003), I can select the default domain policy without problem.
In my case, if I add this snap-in, I have an error. This error tell me that "The DC controller for the operation Group policy editor is not available." I can select from a popup one of this 2 options:
"The DC with the token of master operation for the PDC emulator" or "any available DC".
You can see this error here: Then, if I select the first option (token PDC) I have another error, telling me that is impossible to find another DC and that there could be a policy that prevent to select another DC.
If I select the second, the server connected is the server2000 but not the 2003.
You can see this error here: This problem cause that if I shut off the server 2000 and leave the 2003 up I can't see the group policy in the mmc of this. Because I would to demote and remove the 2000 from the domain this is a big problem for me.
Moreover if I add some snap-in to the mmc from the 2003 server, I see that this snap-in are added referring by default to the old 2000 server.
In fact GPO, sites and services, users and computers links to the old server while schema of AD links to server2003.
Then, if I tell to this snap-in to connect to another DC, I can see these snap-in referring to the 2003 server.
You can see this situation in the screenshots below, in the first 4 snap-in I have added the snap-in by default, and in the last 3 I've connected the snap-in to the server2003 explicitly(the local where I execute mmc) telling to "connect to DC".
Some ideas to resolve this problem?
Thank you
I've this problem, I've added a windows 2003 machine to an entire windows 2000 server domain that had only 1 DC.
Now, after the adding of 2003, in the net there are 2 DC.
My objective was to migrate the Active directory from 2000 to 2003, to the aim of remove the 2000 machine after the adding.
So I've applied all the step required by the migration, preparing the AD of 2000 with the adprep commands, joining the 2003 to domain as DC, transferring all 5 roles from 2000 to 2003, and flagging the 2003 to be a global catalog.
In this way I would have all the structure of the 2000 in an exacted copy in the 2003.
Normally after this, in the MMC if I add the snap-in Group Policy Object Editor (in new server 2003), I can select the default domain policy without problem.
In my case, if I add this snap-in, I have an error. This error tell me that "The DC controller for the operation Group policy editor is not available." I can select from a popup one of this 2 options:
"The DC with the token of master operation for the PDC emulator" or "any available DC".
You can see this error here: Then, if I select the first option (token PDC) I have another error, telling me that is impossible to find another DC and that there could be a policy that prevent to select another DC.
If I select the second, the server connected is the server2000 but not the 2003.
You can see this error here: This problem cause that if I shut off the server 2000 and leave the 2003 up I can't see the group policy in the mmc of this. Because I would to demote and remove the 2000 from the domain this is a big problem for me.
Moreover if I add some snap-in to the mmc from the 2003 server, I see that this snap-in are added referring by default to the old 2000 server.
In fact GPO, sites and services, users and computers links to the old server while schema of AD links to server2003.
Then, if I tell to this snap-in to connect to another DC, I can see these snap-in referring to the 2003 server.
You can see this situation in the screenshots below, in the first 4 snap-in I have added the snap-in by default, and in the last 3 I've connected the snap-in to the server2003 explicitly(the local where I execute mmc) telling to "connect to DC".
Some ideas to resolve this problem?
Thank you
