A
ACE
Hi,
We did a NT4 to W2K AD migration. After the migration,
we realised that the XP machines domain name changed to
the new domain name with suffix appended to it, even
though we are on mixed mode. However, due to some
application problem, we are forced to rollback to the NT4
domain.
Now the problem comes!! Our XP machines cannot login
to the domain. We have to disjoin them from the domain
by joining a workgroup and from there join back the
domain again. Only then they can logon to their machine
and see their mapped network drive.
Did not seem to have seen this problem in any migration
literature. Can someone help or explain to me why this
is happening. We roll back according to what alot of
literature advise. Keep a BDC offline when doing the
upgrade and bring it back into the environment to be
promoted to PDC.
We did a NT4 to W2K AD migration. After the migration,
we realised that the XP machines domain name changed to
the new domain name with suffix appended to it, even
though we are on mixed mode. However, due to some
application problem, we are forced to rollback to the NT4
domain.
Now the problem comes!! Our XP machines cannot login
to the domain. We have to disjoin them from the domain
by joining a workgroup and from there join back the
domain again. Only then they can logon to their machine
and see their mapped network drive.
Did not seem to have seen this problem in any migration
literature. Can someone help or explain to me why this
is happening. We roll back according to what alot of
literature advise. Keep a BDC offline when doing the
upgrade and bring it back into the environment to be
promoted to PDC.