bad upgrade

  • Thread starter Thread starter greg
  • Start date Start date
G

greg

Hi I have got a win2k dc with a problem that I not sure
how to fix with uot losing AD info.
Here is the porblem in a nutshell.I have an upgraded box
from nt4pdc to 2000dc in the upgrade the old domain was
St.Peter during the upgn drade win2k did not like this
with a dot in the domain. I think because it would be a
child domain to nte peter domain that did not exist. so
the AD and dns was named psteal.local durng the ad
install. Now the ad is not woking right and DNS is not
working properly. when you look in net id tab of my
comuter porperties it say that the computer name is
"server1.st.peter" and under domain it
says "psteal.local". Is there away to fix this or if i
need to dcpromo this can i get user acc's and group off
with out losing them. the nt4 bdc is still up and running.
Help I need some dirction or sugestions.
greg
 
You basically have a disjoint name space. The 2k dc needs to be taken off
line and you can then promote the nt4 bdc up to pdc (at this point for
additional backup etc if you have some desktop box you could install it as a
new bdc just so it will have a copy of hte sam etc). Note that all xp and
win2k servers/clients will not now want to validate against the pdc as once
they have discovered a Kerberos environment, they will only want to
authenticate against a 2k dc, so they would need to be dropped to workgroups
and then rejoined to the domain to set them back to using netbios again.
The existing can be demoted, either gracefully as last dc in the domain or
forcefully using the article below. When that finishes it will just be a
win2k server in a workgroup which you could now promote up as an additional
dc in an existing domain which would give you two win2k dc's. The old nt4
bdc to pdc to win2k could then be demoted if you only wanted one to run. It
would transfer its fsmo roles to the other dc, but you would need to make it
a global catalog server as well manually (on ntds settings under the server
in AD sites/services right click and check the box for gc).

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
The easiest thing to do would be to run the script sent in the other post
which will correct the disjoint name (as long as the name showing up in the
domain name line is correct), however, while the script is used quite a bit
and have not seen any problems with it, it is not supported.
With the disjoint dc name, I'm afraid ADMT2 would also run into naming
problems as well. I would either do the "long" way as laid out earlier, or
run the script.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
What script is that?
-----Original Message-----
The easiest thing to do would be to run the script sent in the other post
which will correct the disjoint name (as long as the name showing up in the
domain name line is correct), however, while the script is used quite a bit
and have not seen any problems with it, it is not supported.
With the disjoint dc name, I'm afraid ADMT2 would also run into naming
problems as well. I would either do the "long" way as laid out earlier, or
run the script.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.



.
Click to expand...
 
Could I run ADMT from the old nt bdc to the a fresh
serverthat is comming in on monday
greg
-----Original Message-----
Before you do that you can run this script that will make you DNS name the
same as you Domain name. This will allow Active Direcotry Users and
COmputers to work


--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
greg said:
Hi I have got a win2k dc with a problem that I not sure
how to fix with uot losing AD info.
Here is the porblem in a nutshell.I have an upgraded box
from nt4pdc to 2000dc in the upgrade the old domain was
St.Peter during the upgn drade win2k did not like this
with a dot in the domain. I think because it would be a
child domain to nte peter domain that did not exist. so
the AD and dns was named psteal.local durng the ad
install. Now the ad is not woking right and DNS is not
working properly. when you look in net id tab of my
comuter porperties it say that the computer name is
"server1.st.peter" and under domain it
says "psteal.local". Is there away to fix this or if i
need to dcpromo this can i get user acc's and group off
with out losing them. the nt4 bdc is still up and running.
Help I need some dirction or sugestions.
greg
Click to expand...
Click to expand...
 
Back
Top