Windows Server

Microsoft · Guest

I'm getting ready to upgrade my nt4 domain to win2003 server. One of my
rollback questions in the "rare" event this doesn't work, is whether once
this has been done and clients begin to login to to the new active directory
domain, is there anything changed on the client or in the clients registry
(i've got nt4 workstation, win2k and xp pro clients) that prevents it from
logging back into an nt4 domain, in the event that we have to go back?

Thanks Art

mote · Guest

Art,

Can you please clarify: are you doing an in-place upgrade or a clean
migration to an Active Directory Forest?

Regards,

"Microsoft" <c_art@bellsouth.net> wrote in message
news:efw3Yql7EHA.3944@TK2MSFTNGP12.phx.gbl...

Carsyn Gu [MSFT] · Guest

Hi

Thanks for your posting.

Do you mean that you would like to roll back the client to logon Windows NT
domain instead of the Windows 2003 AD domain, in case the domain upgrade
fails? We have two choices:

1. If you are using the domain upgrade scenario, which upgrades the OS
version of the DCs:

We need to backup the whole image of the Windows NT domain controllers
before performing the upgrade. If the upgrade fails, we are able to roll
back the servers to Windows NT DCs by restoring the backup image.

2. If you are choosing the domain migration instead of upgrade, we can
have the Windows NT domain and Windows 2003 domain existing at the same
time. So, before you removing the Windows NT domain from the corp network,
the client can both logon to Windows NT domain and Windows 2003 domain
without any problem since they have established the trust between them.

If you want to move Windows NT to Windows 2003 smoothly, migration with
ADMT tool is a better option.

Happy New Year!!

Sincerely,
Carsyn Gu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Microsoft" <c_art@bellsouth.net>
| Subject: migratings effect on clients
| Date: Thu, 30 Dec 2004 05:31:59 -0500
| Lines: 11
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| Message-ID: <efw3Yql7EHA.3944@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: adsl-066-156-066-240.sip.asm.bellsouth.net
66.156.66.240
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:16249
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| I'm getting ready to upgrade my nt4 domain to win2003 server. One of my
| rollback questions in the "rare" event this doesn't work, is whether once
| this has been done and clients begin to login to to the new active
directory
| domain, is there anything changed on the client or in the clients registry
| (i've got nt4 workstation, win2k and xp pro clients) that prevents it from
| logging back into an nt4 domain, in the event that we have to go back?
|
|
| Thanks Art
|
|
|

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1