RE: System Copy Windows Server 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Carsyn Gu [MSFT] (kshengu_at_online.microsoft.com)
Date: 12/10/04


Date: Fri, 10 Dec 2004 09:36:00 GMT

Hi Mark,

Thanks for your update.

You may use the Microsoft File Server Migration Toolkit to perform the copy.

Here is a link of the white paper:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.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: AcTcgAZKZUiinbJIRbmq71QukiMljQ==
| X-WBNR-Posting-Host: 212.174.60.168
| From: =?Utf-8?B?TWFyayBUZXJt?= <MarkTerm@discussions.microsoft.com>
| References: <AFACAF33-93EC-4D73-8D72-60D639DC5CB1@microsoft.com>
<vzqqkl32EHA.2732@cpmsftngxa10.phx.gbl>
| Subject: RE: System Copy Windows Server 2003
| Date: Tue, 7 Dec 2004 09:13:09 -0800
| Lines: 125
| Message-ID: <33DE3BFB-FA15-4478-B3DD-ABAFA48F7446@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| 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!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:15809
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hello Carsyn, thank you for your help.
| So, that server is also a file server, I mean I'll have to copy also file
| structure with the ACL of them, so what is the best way and the procedure
of
| it?
|
| Thanks in advance...
|
|
| "Carsyn Gu [MSFT]" wrote:
|
| > 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.
| > |
| > |
| >
| >
|



Relevant Pages

  • RE: specific problem with migration
    ... Microsoft Online Partner Support ... | I'm writing you because I have a very specific problem with migration. ... | another Windows 2000 server which is secondary domain controler. ...
    (microsoft.public.windows.server.migration)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: SwingIt Pain and Suffering
    ... BTW - I did purchase the Advanced Windows Small Business Server 2003 Best Practices book and consumed large parts of it before starting this project. ... That being said, I do feel like his documentation could greatly benefit by having some more detailed check points for verifying the health of AD at various steps along the way, and what steps to take or resources to consult if the replication doesn't seem to be going according to plan. ... BTW, even after discovering this constraint and disabling the firewalls on my destination server as part of the base OS install, replication still initially failed and I was dumb founded to find the firewall reenabled. ... I did complete the AD replication from the migration computer to the destination computer as planned. ...
    (microsoft.public.windows.server.sbs)
  • Re: Gradual Win2k to SBS2003 Migration
    ... the migration has completed successfully. ... Microsoft Global Technical Support Center ... you can upgrade from Windows 2000 Server to Windows ...
    (microsoft.public.windows.server.migration)