D
Dr Watson
Hi,
I'm going to do an in-place upgrade from our Winnt domain to Win2000 Ad.
Because I do not want to lose our domain if the worst happens, I have few
questions about the best practices.
Is it totally impossible to use Windows NT 4.0 dhcp service to upgrade our
legacy clients (Windows 98 and Winnt 4.0 WS) dns data to Windows 2000 Server
ddns service dynamically?
Is it absolutely necessary to register these legacy clients ip addresses to
the Windows 2000 dns server in the means that these clients will logon
correctly and show up in the AD? We have two Windows NT 4.0 WINS servers.
Should I manually add records for our Winnt 4.0 servers and Winnt 4.0 and
Win 9x clients to Windows 2000 ddns server if I want to use static ip
addresses for them and I don't want to use dhcp to update these machines
data to Windows 2000 ddns server? The Windows 2000 clients will still
dynamically update their static ip addresses to the dns server.
Does the Winnt BDC's need any other record types than A record in the Win
2000 dns server when we're using the mixed mode?
We have about 20 branch offices that are connected to our resources with
ISDN connection. They do not log on to our domain but are using workgroup
settings. Is it possible to use our current NT 4.0 dns server to serve these
remote users dns requests although I will start to use the Win 2000 dns for
our domain needs?
Are there any new issues with replication between NT 4 BDCs and Win 2000 AD
server if I upgrade the AD server to Service Pack 4? Will the replication
work correctly after the SP upgrade without any special configuration? The
BDCs will be equipped with SP6a.
I will unplug one of our backup domain controllers from the network before I
begin the actual upgrade process to our brand new server that I will promote
to PDC. If I mess up the upgrade totally, should I promote this server to
PDC before or after I connect it back to our network? Is it possible to
promote one of the backup domain controllers that are connected to the
network during the failing in-place upgrade to be a new PDC. Should the
failed AD server be turned off before I do any kind of promotion to our
backup domain controllers?
Thanks in advance.
I'm going to do an in-place upgrade from our Winnt domain to Win2000 Ad.
Because I do not want to lose our domain if the worst happens, I have few
questions about the best practices.
Is it totally impossible to use Windows NT 4.0 dhcp service to upgrade our
legacy clients (Windows 98 and Winnt 4.0 WS) dns data to Windows 2000 Server
ddns service dynamically?
Is it absolutely necessary to register these legacy clients ip addresses to
the Windows 2000 dns server in the means that these clients will logon
correctly and show up in the AD? We have two Windows NT 4.0 WINS servers.
Should I manually add records for our Winnt 4.0 servers and Winnt 4.0 and
Win 9x clients to Windows 2000 ddns server if I want to use static ip
addresses for them and I don't want to use dhcp to update these machines
data to Windows 2000 ddns server? The Windows 2000 clients will still
dynamically update their static ip addresses to the dns server.
Does the Winnt BDC's need any other record types than A record in the Win
2000 dns server when we're using the mixed mode?
We have about 20 branch offices that are connected to our resources with
ISDN connection. They do not log on to our domain but are using workgroup
settings. Is it possible to use our current NT 4.0 dns server to serve these
remote users dns requests although I will start to use the Win 2000 dns for
our domain needs?
Are there any new issues with replication between NT 4 BDCs and Win 2000 AD
server if I upgrade the AD server to Service Pack 4? Will the replication
work correctly after the SP upgrade without any special configuration? The
BDCs will be equipped with SP6a.
I will unplug one of our backup domain controllers from the network before I
begin the actual upgrade process to our brand new server that I will promote
to PDC. If I mess up the upgrade totally, should I promote this server to
PDC before or after I connect it back to our network? Is it possible to
promote one of the backup domain controllers that are connected to the
network during the failing in-place upgrade to be a new PDC. Should the
failed AD server be turned off before I do any kind of promotion to our
backup domain controllers?
Thanks in advance.