Corrupt DNS moving

  • Thread starter Thread starter Ronrf1
  • Start date Start date
R

Ronrf1

Currently the Win2k domain is not in fqdn fashion but in
Netbios name only. The DNS database is corrupt and is not
supporting dynamic DNS, but it is located on a Win2k
server.
Is there anyway to rebuild the DNS database without
harming the AD structure or do we need to rebuild the
DNS, AD and move the users? We had issues moving user's
profiles (using XPsp1) from a Workgroup to the AD
environment. Is there an easier way to do this, or a util
that would do it better?
 
In
Ronrf1 said:
Currently the Win2k domain is not in fqdn fashion but in
Netbios name only. The DNS database is corrupt and is not
supporting dynamic DNS, but it is located on a Win2k
server.
Is there anyway to rebuild the DNS database without
harming the AD structure or do we need to rebuild the
DNS, AD and move the users? We had issues moving user's
profiles (using XPsp1) from a Workgroup to the AD
environment. Is there an easier way to do this, or a util
that would do it better?
Click to expand...

Is your AD Domain a single label name (domain vs. domain.com)?
In order to fix this you will need to build a new domain and migrate the
users to the new domain using ADMT.
 
If they are to rebuild then they will rebuild the entire
forrest. Would ADMT be used to move some accounts, groups
and OUs to the new forrest? Would relocating the users
profiles cause problems due to the fact XP will see
domain\user is not the same as domain.local\user and not
allow access to the profile?
 
In
Ronrf1 said:
If they are to rebuild then they will rebuild the entire
forrest. Would ADMT be used to move some accounts, groups
and OUs to the new forrest? Would relocating the users
profiles cause problems due to the fact XP will see
domain\user is not the same as domain.local\user and not
allow access to the profile?
Click to expand...

ADMT can migrate everything, including the user profiles. If you are using
roaming profiles make sure the roaming profile is in the same UNC sharename.
 
will ADMT work even if the profiles are local? Do I need
to copy the profiles and set it to roaming then copy the
profile from local to roaming. This would make me run into
the same problem as creating a new account in a new domain
then copying the profile using the copy wizard or a manual
copy.
 
In
Ronrf1 said:
will ADMT work even if the profiles are local? Yes

Do I need
to copy the profiles and set it to roaming then copy the
profile from local to roaming. This would make me run into
the same problem as creating a new account in a new domain
then copying the profile using the copy wizard or a manual
copy.
Click to expand...

The problem will happen only if the roaming profile is in a share on a
machine that will no longer be around, like the old domain controller.
As long as they are local or are in a share on a machine that is going to be
left intact they will be migrated.

Profiles are kept under the User's account unique identifier, the account
identifier is migrated. That is what make ADMT so cool, it saves a bunch of
work. Nobody notices the change.
 
Back
Top