RE: System Copy Windows Server 2003
From: Carsyn Gu [MSFT] (kshengu_at_online.microsoft.com)
Date: 12/06/04
- Next message: Rebecca Chen [MSFT]: "RE: NT4 Server suddenly cannot authenticate on our W2K3 domain"
- Previous message: Rebecca Chen [MSFT]: "RE: ADMT - SID History Issues, Cannot access resources in old domain"
- In reply to: Mark Term: "System Copy Windows Server 2003"
- Next in thread: Mark Term: "RE: System Copy Windows Server 2003"
- Reply: Mark Term: "RE: System Copy Windows Server 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 06 Dec 2004 09:53:07 GMT
Hi Mark,
Thanks for your posting.
You may use the ADMT tool to perform the migration. The Active Directory
Migration Tool (ADMT) provides an easy, secure, and fast way to migrate
users, groups, and computers from one domain to another. ADMT is commonly
used to migrate accounts from Microsoft? Windows NT? to the Microsoft
Windows? 2000 Server Active Directory directory service. ADMT 2.0 now
supports migrating accounts from earlier versions of Microsoft Windows to
Microsoft Windows Server 2003.
In addition, you can use ADMT to restructure existing Active Directory
domains or to help diagnose possible problems before starting migration
operations. The task-based wizards enable you to migrate users, groups, and
computers; update correct file permissions; and update user-related
security settings on Microsoft Exchange 5.5 Server mailboxes. The tool's
reporting feature also enables you to assess the impact of the migration,
both before and after move operations.
In many cases, if there is a problem, you can use the rollback feature to
automatically restore previous structures. The tool provides support for
parallel domains, so you can maintain your existing Microsoft Windows NT
4.0 operating system domains while you deploy the Microsoft Windows 2000
operating system.
Many new features have been added to ADMT 2.0, including the following:
， Scripting ADMT operations from Microsoft Visual Basic? Scripting Edition
(VBScript) and other COM-enabled languages.
， Access to ADMT functionality from the command prompt.
， Enhanced performance, especially in group membership operations.
， Log file history is maintained to better track migration results and
issues.
， Full Domain Admin rights in the target domain are no longer required for
the majority of migration tasks.
， Passwords can now be migrated between domains in different forests.
， Account objects with name conflicts can be left in their original
containers rather than having to be moved to the target organizational unit
(OU).
， More flexible options to handle the state of the source and target
accounts after migration-either or both can be set to enabled or disabled,
or set to expire.
， A list of attributes can now be defined that will be excluded in a
migration.
， The option to automatically fix group memberships for migrated users can
now be turned off if group accounts have not already been migrated.
， The ability to track account objects that are moved between OUs after
migration so that group memberships are more accurately maintained during a
migration.
， Greatly improved computer migration operation to ensure that computers
more reliably succeed in joining the new domain after a reboot.
， The ability to refer to a security identifier (SID) mapping file to
allow security translation for accounts that were not migrated with ADMT
and are therefore not in the ADMT database.
， Security Translation will now survive the decommissioning of the source
domain, since the required information is placed in the ADMT database as
the objects are migrated.
， Additional information is now provided in the reports generated by the
Reporting Wizard.
A scenario is using ADMT:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
/cookchp9.mspx
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.
--------------------
| Thread-Topic: System Copy Windows Server 2003
| thread-index: AcTZZ11Myn6m7Vt1QpKIXXD9VVx9uw==
| X-WBNR-Posting-Host: 81.214.0.91
| From: =?Utf-8?B?TWFyayBUZXJt?= <Mark Term@discussions.microsoft.com>
| Subject: System Copy Windows Server 2003
| Date: Fri, 3 Dec 2004 10:39:04 -0800
| Lines: 6
| Message-ID: <AFACAF33-93EC-4D73-8D72-60D639DC5CB1@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:15751
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hello
| I've been searching an appropriate article about win server 2003
migration.
| But I couldn't. So I want to make a exact copy of a Windows Server 2003
| (active directory) to another hardware platform.
| Thanks in advance for your help.
|
|
- Next message: Rebecca Chen [MSFT]: "RE: NT4 Server suddenly cannot authenticate on our W2K3 domain"
- Previous message: Rebecca Chen [MSFT]: "RE: ADMT - SID History Issues, Cannot access resources in old domain"
- In reply to: Mark Term: "System Copy Windows Server 2003"
- Next in thread: Mark Term: "RE: System Copy Windows Server 2003"
- Reply: Mark Term: "RE: System Copy Windows Server 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
