A
alvin
In our test labs, I've noticed that when we rolled back
from our W2k migration to NT4 (by turning off our single
W2k DC server which is also PDC emulator (after upgrading
NT BDC) and promoting 2nd NT BDC to NT PDC), our 95/98/NT
wks logs in fine but w2k server and pro dekstops can not
log in to the network. Saying can find computer account
or username/pwd is incorrect.
Upon further investigation, I noticed that the domain for
the w2k srv/pro computers were changed from our original
NT domain called ABCD to the FQDN AD domain ABCD.com. So
now that the single W2k DC is off and NT BDC is back as
NT PDC, they can't log in to the network.
If I re-join the wks to ABCD domain, it will work. But
then this would mean that if we actually need to rollback
(in case we actually come across w2k migration problem)
we have to go to each W2k server and pro wks and rejoin
the NT domain for them to work & be able to log back in
the domain/network.
Hope somebody has a solution to this.
Thanks.
from our W2k migration to NT4 (by turning off our single
W2k DC server which is also PDC emulator (after upgrading
NT BDC) and promoting 2nd NT BDC to NT PDC), our 95/98/NT
wks logs in fine but w2k server and pro dekstops can not
log in to the network. Saying can find computer account
or username/pwd is incorrect.
Upon further investigation, I noticed that the domain for
the w2k srv/pro computers were changed from our original
NT domain called ABCD to the FQDN AD domain ABCD.com. So
now that the single W2k DC is off and NT BDC is back as
NT PDC, they can't log in to the network.
If I re-join the wks to ABCD domain, it will work. But
then this would mean that if we actually need to rollback
(in case we actually come across w2k migration problem)
we have to go to each W2k server and pro wks and rejoin
the NT domain for them to work & be able to log back in
the domain/network.
Hope somebody has a solution to this.
Thanks.