Results 1 to 10 of 10

Thread: Migrating Windows 2003 server from old hardware to new hardware

  1. #1
    Zaur Bahramov Guest

    Migrating Windows 2003 server from old hardware to new hardware

    I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS) which has no
    FSMO roles from old hardware to a new hardware. This is not the only server
    on a domain and is located in a remote office. I have to preserve all
    settings and software install. How can I accomplish this with the least
    amount of effort? What would I have to do to make sure I have everything
    functioning after I do imaging (or ghosting) from this server to a newer
    hardware?




  2. #2
    kj [SBS MVP] Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Zaur Bahramov wrote:
    > I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS) which
    > has no FSMO roles from old hardware to a new hardware. This is not
    > the only server on a domain and is located in a remote office. I have
    > to preserve all settings and software install. How can I accomplish
    > this with the least amount of effort? What would I have to do to make
    > sure I have everything functioning after I do imaging (or ghosting)
    > from this server to a newer hardware?


    Image restoration of domain controllers, regardless of FMSO roles, is not
    supported and likely will lead to USN rollback problems.

    If you *must* image restore this server, demote it from being a DC first and
    repromot when running on the new hardware.


    --
    /kj



  3. #3
    Morgan che Guest

    RE: Migrating Windows 2003 server from old hardware to new hardware

    Hi,

    Thanks for posting here.

    Please understand we could only restore a system state backup from one
    physical computer to the same physical computer or another computer that
    has the same make, model, and configuration (identical hardware). However,
    please note: You may meet some unexpected issues if you restore a system
    state backup from one computer to another with different hardware.
    Microsoft does not support restoring a system state backup from one
    computer to a second computer of a different make, model, or hardware
    configuration. Microsoft will only provide commercially reasonable efforts
    to support this process. Even if the source and destination computers
    appear to be identical makes and models, there may be driver, hardware, or
    firmware differences between the source and destination computers.

    More information, please refer to:

    How to move a Windows installation to different hardware
    http://support.microsoft.com/default...b;EN-US;249694

    Therefore, I recommend you migrate the configuration and data manually. For
    the Domain migration, because there is other DC existing in your network,
    you can promote an additional DC to synchronize Domain data.

    About how to promote an additional DC, please refer to:

    How to promote and demote domain controllers
    http://support.microsoft.com/kb/238369

    Hope this helps. Have a good day!

    Sincerely
    Morgan Che
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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: "Zaur Bahramov" <zbakhramov@msn.com>
    --->Subject: Migrating Windows 2003 server from old hardware to new hardware
    --->Date: Thu, 22 May 2008 18:32:52 +0200
    --->Lines: 10
    --->X-Priority: 3
    --->X-MSMail-Priority: Normal
    --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->X-RFC2646: Format=Flowed; Original
    --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->Newsgroups: microsoft.public.windows.server.migration
    --->NNTP-Posting-Host: host67-143-static.57-217-b.business.telecomitalia.it
    217.57.143.67
    --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    --->Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.server.migration:3660
    --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->
    --->I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS) which
    has no
    --->FSMO roles from old hardware to a new hardware. This is not the only
    server
    --->on a domain and is located in a remote office. I have to preserve all
    --->settings and software install. How can I accomplish this with the least
    --->amount of effort? What would I have to do to make sure I have
    everything
    --->functioning after I do imaging (or ghosting) from this server to a
    newer
    --->hardware?
    --->
    --->
    --->
    --->


  4. #4
    Zaur Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Thank's for your reply!

    I decided to do a clean install to avoid any problems. So, I need just to
    confirm the following.
    I need to install DNS/DHCP/WINS and AD on this server which will replace the
    old server. In which order it's better to do it?
    As for DHCP, I believe I can do it in any moment. But as for DNS and WINS,
    when it's better to install these, before running dcpromo or after? WINS on
    existing old server is configured as a replication partner with WINS server
    in our headquarters.
    Another question is after I install AD/DNS/DHCP/WINS is it OK to rename this
    new server after I demote existing server to configure it with the same name
    and IP of the existing old server? I am thinking about demoting old server
    just after I promote the new one, and use the procedure as in the folowing
    link to rename the new domain controler.
    http://www.petri.co.il/windows_2003_...ler_rename.htm

    Will this procedure cause any problems with replication between sites? Would
    I have to re-configure site replication? Is there anything else what I need
    to bear in mind while doing this work?

    Thanking you in advance,

    Zaur





    "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    > Hi,
    >
    > Thanks for posting here.
    >
    > Please understand we could only restore a system state backup from one
    > physical computer to the same physical computer or another computer that
    > has the same make, model, and configuration (identical hardware). However,
    > please note: You may meet some unexpected issues if you restore a system
    > state backup from one computer to another with different hardware.
    > Microsoft does not support restoring a system state backup from one
    > computer to a second computer of a different make, model, or hardware
    > configuration. Microsoft will only provide commercially reasonable efforts
    > to support this process. Even if the source and destination computers
    > appear to be identical makes and models, there may be driver, hardware, or
    > firmware differences between the source and destination computers.
    >
    > More information, please refer to:
    >
    > How to move a Windows installation to different hardware
    > http://support.microsoft.com/default...b;EN-US;249694
    >
    > Therefore, I recommend you migrate the configuration and data manually.
    > For
    > the Domain migration, because there is other DC existing in your network,
    > you can promote an additional DC to synchronize Domain data.
    >
    > About how to promote an additional DC, please refer to:
    >
    > How to promote and demote domain controllers
    > http://support.microsoft.com/kb/238369
    >
    > Hope this helps. Have a good day!
    >
    > Sincerely
    > Morgan Che
    > Microsoft Online Support
    > Microsoft Global Technical Support Center
    >
    > 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: "Zaur Bahramov" <zbakhramov@msn.com>
    > --->Subject: Migrating Windows 2003 server from old hardware to new
    > hardware
    > --->Date: Thu, 22 May 2008 18:32:52 +0200
    > --->Lines: 10
    > --->X-Priority: 3
    > --->X-MSMail-Priority: Normal
    > --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->X-RFC2646: Format=Flowed; Original
    > --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > --->Newsgroups: microsoft.public.windows.server.migration
    > --->NNTP-Posting-Host:
    > host67-143-static.57-217-b.business.telecomitalia.it
    > 217.57.143.67
    > --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    > --->Xref: TK2MSFTNGHUB02.phx.gbl
    > microsoft.public.windows.server.migration:3660
    > --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->
    > --->I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS) which
    > has no
    > --->FSMO roles from old hardware to a new hardware. This is not the only
    > server
    > --->on a domain and is located in a remote office. I have to preserve all
    > --->settings and software install. How can I accomplish this with the
    > least
    > --->amount of effort? What would I have to do to make sure I have
    > everything
    > --->functioning after I do imaging (or ghosting) from this server to a
    > newer
    > --->hardware?
    > --->
    > --->
    > --->
    > --->
    >




  5. #5
    Morgan che Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    HI,

    <I need to install DNS/DHCP/WINS and AD on this server which will replace
    the old server. In which order it's better to do it?>

    It doesn't matter. You can follow this sequence: AD, DHCP, DNS, WINS.

    <But as for DNS and WINS, when it's better to install these, before running
    dcpromo or after?>

    You can install DNS when running Dcpromo. Or after running DCpromo, you can
    install DNS server. As for Wins, you can install it after or before running
    DCpromo.

    As for the other question, I will do further research and get back to you
    as soon as possible.

    Have a nice day!

    Sincerely
    Morgan Che
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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: "Zaur" <zbakhramov@gmail.com>
    --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    hardware
    --->Date: Sun, 25 May 2008 19:38:56 +0200
    --->Lines: 118
    --->X-Priority: 3
    --->X-MSMail-Priority: Normal
    --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->X-RFC2646: Format=Flowed; Original
    --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    --->Newsgroups: microsoft.public.windows.server.migration
    --->NNTP-Posting-Host: host13-35-dynamic.24-79-r.retail.telecomitalia.it
    79.24.35.13
    --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.server.migration:3671
    --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->
    --->Thank's for your reply!
    --->
    --->I decided to do a clean install to avoid any problems. So, I need just
    to
    --->confirm the following.
    --->I need to install DNS/DHCP/WINS and AD on this server which will
    replace the
    --->old server. In which order it's better to do it?
    --->As for DHCP, I believe I can do it in any moment. But as for DNS and
    WINS,
    --->when it's better to install these, before running dcpromo or after?
    WINS on
    --->existing old server is configured as a replication partner with WINS
    server
    --->in our headquarters.
    --->Another question is after I install AD/DNS/DHCP/WINS is it OK to rename
    this
    --->new server after I demote existing server to configure it with the same
    name
    --->and IP of the existing old server? I am thinking about demoting old
    server
    --->just after I promote the new one, and use the procedure as in the
    folowing
    --->link to rename the new domain controler.
    --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    --->
    --->Will this procedure cause any problems with replication between sites?
    Would
    --->I have to re-configure site replication? Is there anything else what I
    need
    --->to bear in mind while doing this work?
    --->
    --->Thanking you in advance,
    --->
    --->Zaur
    --->
    --->
    --->
    --->
    --->
    --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    --->> Hi,
    --->>
    --->> Thanks for posting here.
    --->>
    --->> Please understand we could only restore a system state backup from one
    --->> physical computer to the same physical computer or another computer
    that
    --->> has the same make, model, and configuration (identical hardware).
    However,
    --->> please note: You may meet some unexpected issues if you restore a
    system
    --->> state backup from one computer to another with different hardware.
    --->> Microsoft does not support restoring a system state backup from one
    --->> computer to a second computer of a different make, model, or hardware
    --->> configuration. Microsoft will only provide commercially reasonable
    efforts
    --->> to support this process. Even if the source and destination computers
    --->> appear to be identical makes and models, there may be driver,
    hardware, or
    --->> firmware differences between the source and destination computers.
    --->>
    --->> More information, please refer to:
    --->>
    --->> How to move a Windows installation to different hardware
    --->> http://support.microsoft.com/default...b;EN-US;249694
    --->>
    --->> Therefore, I recommend you migrate the configuration and data
    manually.
    --->> For
    --->> the Domain migration, because there is other DC existing in your
    network,
    --->> you can promote an additional DC to synchronize Domain data.
    --->>
    --->> About how to promote an additional DC, please refer to:
    --->>
    --->> How to promote and demote domain controllers
    --->> http://support.microsoft.com/kb/238369
    --->>
    --->> Hope this helps. Have a good day!
    --->>
    --->> Sincerely
    --->> Morgan Che
    --->> Microsoft Online Support
    --->> Microsoft Global Technical Support Center
    --->>
    --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    --->> --->Subject: Migrating Windows 2003 server from old hardware to new
    --->> hardware
    --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    --->> --->Lines: 10
    --->> --->X-Priority: 3
    --->> --->X-MSMail-Priority: Normal
    --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->NNTP-Posting-Host:
    --->> host67-143-static.57-217-b.business.telecomitalia.it
    --->> 217.57.143.67
    --->> --->Path:
    TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> microsoft.public.windows.server.migration:3660
    --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->
    --->> --->I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS)
    which
    --->> has no
    --->> --->FSMO roles from old hardware to a new hardware. This is not the
    only
    --->> server
    --->> --->on a domain and is located in a remote office. I have to preserve
    all
    --->> --->settings and software install. How can I accomplish this with the
    --->> least
    --->> --->amount of effort? What would I have to do to make sure I have
    --->> everything
    --->> --->functioning after I do imaging (or ghosting) from this server to a
    --->> newer
    --->> --->hardware?
    --->> --->
    --->> --->
    --->> --->
    --->> --->
    --->>
    --->
    --->
    --->


  6. #6
    Morgan che Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Hi,

    As DC renaming, we can use Netdom.exe tool or manually modify system
    properties.

    About these two methods, please see the following article:

    Renaming a Domain Controller:
    http://technet2.microsoft.com/window...4-883b-4e9a-89
    e6-f8c4509b1de11033.mspx?mfr=true

    Comparison of these two methods:
    ==========================

    1) Renaming a domain controller with the "NETDOM COMPUTERNAME" method

    Allows DC renames to be scripted or remoted from a client computer using
    the command-line utility NETDOM.EXE.

    Requires Windows Server 2003 domain functional level be enabled in the
    domain hosting the renamed DC.

    Service Principal Names and DNS "A" records for both the new and existing
    computer names are registered concurrently until the administrator
    configures the renamed DC to adopt the new computer name.

    Administrators can wait for full replication of SPN and DNS records to
    Global Catalog and DNS Servers in the forest before adopting the new
    computer name, minimizing service denials.

    2) Renaming a domain controller with the "Modify system propertities"
    method

    Uses the "Computer Name" tab visible in the properties page of "My
    Computer" to rename either the computer name or its primary DNS suffix
    through an easy-to-use GUI

    Is not dependent on Windows Server 2003 domain or forest functional levels

    Transitions the renamed DC to the new computer name immediately after
    reboot causing a possible loss of service until service principal names and
    DNS registration are fully replicated and considered by other clients and
    domain controllers in the forest

    According to your practical environment, please pick the most suitable
    method to rename DC.

    <Will this procedure cause any problems with replication between sites?
    Would I have to re-configure site replication?>

    {Morgan}:

    Normally, it will not affect the site replication. As we know, the DC
    renaming will update SPN attributes stored in Active Directory for this
    computer account and register DNS resource records for the new computer
    name. The SPN value of the computer account must be replicated to all
    domain controllers for the domain and the DNS resource records for the new
    computer name must be distributed to all the authoritative DNS servers for
    the domain name.

    The above two methods will automatically complete the replication of SPN
    and DNS record. If you do not want some service stoppage caused by DC
    rebooting, we can use Netdom.exe to complete renaming process.

    < Is there anything else what I need to bear in mind while doing this work?>

    {Morgan}:

    The DC Rename Preparation process is simple but critical. Before you
    perform any action, please consider and check the following:

    a. Check Application and Service compatibility

    Applications and services that are tied to a specific hostname may be
    "broken" by the renaming of a DC. If application and service compatibility
    is unknown, consult the application developer or rename a DC in an test
    scenario that mimics your production deployment. Core services in Windows
    Server 2003 are DC Rename compatible with the exception of Root Certificate
    Authorities. If installed applications are incompatible with DC Rename,
    determine if the application can be re-installed after the DC rename,
    otherwise halt the rename operation.

    b. Is the DC being renamed currently replicating inbound and outbound
    changes in Active Directory?

    Use the REPADMIN.EXE tool to verify that the DC being renamed is
    replicating all locally held directory partitions from direct replication
    partners. Similarly, confirm that direct replication partners are receiving
    inbound changes in Active Directory for the domain controller being
    renamed. Delay the rename operation until inbound and outbound replication
    for DCs, DNS Servers and Global Catalog are successful.

    c. Is the DC being renamed is a Root Certification Authority (CA)?

    Root CAs are not rename compatible. If a DC host a Root CA, move the root
    CA to a member computer in the domain using the steps outlined in Microsoft
    Knowledgebase article 298138

    d. Is the DC being renamed is Global Catalog server?

    Global Catalogs are essential for logon authentication to native mode
    domains, logon authentication with UPN logon names and Directory aware
    applications like Exchange 2000. If the DC being renamed is the only DC in
    a forest, domain or site, promote a new Global Catalog with sufficient
    horsepower in the appropriate Active Directory site.

    e. Is the DC being renamed is a FSMO role holder?

    FSMO roles residing on domain controllers being renamed could be
    transferred to an alternate DC to avoid a denial of service.

    f. Is the DC being renamed the target of a DFS root or link?

    The UNC path for DNS roots and links refer to specific computer name which
    is not updated by DC Rename. If the DC being renamed is the only target of
    a DFS Root, add an additional target. Temporarily remove the DC being
    renamed as a target of any DFS roots using the DFS snap-in. (start -> run->
    DFSGUI.MSC) provided the DFS root is NOT replicated by FRS.

    If the DC being renamed is the only target of a DFS Link, add an additional
    target. Use the DFS MMC Snap-in (start -> run-> DFSGUI.MSC) to take the
    renamed target "offline" during the DC Rename operation.

    g. Is the DC being renamed a DNS Server

    DNS "SOA" and "A" records for renamed domain controllers are updated
    automatically by the renamed DC. However, other DNS Servers with delegated
    DNS zones targeting renamed DCs will need to be updated.

    F. Make system state backup

    Hope this helps. If anything is unclear, pleas post back.

    Have a nice day!


    Sincerely
    Morgan Che
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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: "Zaur" <zbakhramov@gmail.com>
    --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    hardware
    --->Date: Sun, 25 May 2008 19:38:56 +0200
    --->Lines: 118
    --->X-Priority: 3
    --->X-MSMail-Priority: Normal
    --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->X-RFC2646: Format=Flowed; Original
    --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    --->Newsgroups: microsoft.public.windows.server.migration
    --->NNTP-Posting-Host: host13-35-dynamic.24-79-r.retail.telecomitalia.it
    79.24.35.13
    --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.server.migration:3671
    --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->
    --->Thank's for your reply!
    --->
    --->I decided to do a clean install to avoid any problems. So, I need just
    to
    --->confirm the following.
    --->I need to install DNS/DHCP/WINS and AD on this server which will
    replace the
    --->old server. In which order it's better to do it?
    --->As for DHCP, I believe I can do it in any moment. But as for DNS and
    WINS,
    --->when it's better to install these, before running dcpromo or after?
    WINS on
    --->existing old server is configured as a replication partner with WINS
    server
    --->in our headquarters.
    --->Another question is after I install AD/DNS/DHCP/WINS is it OK to rename
    this
    --->new server after I demote existing server to configure it with the same
    name
    --->and IP of the existing old server? I am thinking about demoting old
    server
    --->just after I promote the new one, and use the procedure as in the
    folowing
    --->link to rename the new domain controler.
    --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    --->
    --->Will this procedure cause any problems with replication between sites?
    Would
    --->I have to re-configure site replication? Is there anything else what I
    need
    --->to bear in mind while doing this work?
    --->
    --->Thanking you in advance,
    --->
    --->Zaur
    --->
    --->
    --->
    --->
    --->
    --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    --->> Hi,
    --->>
    --->> Thanks for posting here.
    --->>
    --->> Please understand we could only restore a system state backup from one
    --->> physical computer to the same physical computer or another computer
    that
    --->> has the same make, model, and configuration (identical hardware).
    However,
    --->> please note: You may meet some unexpected issues if you restore a
    system
    --->> state backup from one computer to another with different hardware.
    --->> Microsoft does not support restoring a system state backup from one
    --->> computer to a second computer of a different make, model, or hardware
    --->> configuration. Microsoft will only provide commercially reasonable
    efforts
    --->> to support this process. Even if the source and destination computers
    --->> appear to be identical makes and models, there may be driver,
    hardware, or
    --->> firmware differences between the source and destination computers.
    --->>
    --->> More information, please refer to:
    --->>
    --->> How to move a Windows installation to different hardware
    --->> http://support.microsoft.com/default...b;EN-US;249694
    --->>
    --->> Therefore, I recommend you migrate the configuration and data
    manually.
    --->> For
    --->> the Domain migration, because there is other DC existing in your
    network,
    --->> you can promote an additional DC to synchronize Domain data.
    --->>
    --->> About how to promote an additional DC, please refer to:
    --->>
    --->> How to promote and demote domain controllers
    --->> http://support.microsoft.com/kb/238369
    --->>
    --->> Hope this helps. Have a good day!
    --->>
    --->> Sincerely
    --->> Morgan Che
    --->> Microsoft Online Support
    --->> Microsoft Global Technical Support Center
    --->>
    --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    --->> --->Subject: Migrating Windows 2003 server from old hardware to new
    --->> hardware
    --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    --->> --->Lines: 10
    --->> --->X-Priority: 3
    --->> --->X-MSMail-Priority: Normal
    --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->NNTP-Posting-Host:
    --->> host67-143-static.57-217-b.business.telecomitalia.it
    --->> 217.57.143.67
    --->> --->Path:
    TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> microsoft.public.windows.server.migration:3660
    --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->
    --->> --->I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS)
    which
    --->> has no
    --->> --->FSMO roles from old hardware to a new hardware. This is not the
    only
    --->> server
    --->> --->on a domain and is located in a remote office. I have to preserve
    all
    --->> --->settings and software install. How can I accomplish this with the
    --->> least
    --->> --->amount of effort? What would I have to do to make sure I have
    --->> everything
    --->> --->functioning after I do imaging (or ghosting) from this server to a
    --->> newer
    --->> --->hardware?
    --->> --->
    --->> --->
    --->> --->
    --->> --->
    --->>
    --->
    --->
    --->


  7. #7
    Zaur Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Hi Morgan che!

    Thanks for your replies! They've helped me a lot! I had to rename DC using a
    GUI since we are running a mixed mode domain functional level (even though
    we have all windows 2003 dcs).

    Thank you!



    "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    news:4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl...
    > Hi,
    >
    > As DC renaming, we can use Netdom.exe tool or manually modify system
    > properties.
    >
    > About these two methods, please see the following article:
    >
    > Renaming a Domain Controller:
    > http://technet2.microsoft.com/window...4-883b-4e9a-89
    > e6-f8c4509b1de11033.mspx?mfr=true
    >
    > Comparison of these two methods:
    > ==========================
    >
    > 1) Renaming a domain controller with the "NETDOM COMPUTERNAME" method
    >
    > Allows DC renames to be scripted or remoted from a client computer using
    > the command-line utility NETDOM.EXE.
    >
    > Requires Windows Server 2003 domain functional level be enabled in the
    > domain hosting the renamed DC.
    >
    > Service Principal Names and DNS "A" records for both the new and existing
    > computer names are registered concurrently until the administrator
    > configures the renamed DC to adopt the new computer name.
    >
    > Administrators can wait for full replication of SPN and DNS records to
    > Global Catalog and DNS Servers in the forest before adopting the new
    > computer name, minimizing service denials.
    >
    > 2) Renaming a domain controller with the "Modify system propertities"
    > method
    >
    > Uses the "Computer Name" tab visible in the properties page of "My
    > Computer" to rename either the computer name or its primary DNS suffix
    > through an easy-to-use GUI
    >
    > Is not dependent on Windows Server 2003 domain or forest functional levels
    >
    > Transitions the renamed DC to the new computer name immediately after
    > reboot causing a possible loss of service until service principal names
    > and
    > DNS registration are fully replicated and considered by other clients and
    > domain controllers in the forest
    >
    > According to your practical environment, please pick the most suitable
    > method to rename DC.
    >
    > <Will this procedure cause any problems with replication between sites?
    > Would I have to re-configure site replication?>
    >
    > {Morgan}:
    >
    > Normally, it will not affect the site replication. As we know, the DC
    > renaming will update SPN attributes stored in Active Directory for this
    > computer account and register DNS resource records for the new computer
    > name. The SPN value of the computer account must be replicated to all
    > domain controllers for the domain and the DNS resource records for the new
    > computer name must be distributed to all the authoritative DNS servers for
    > the domain name.
    >
    > The above two methods will automatically complete the replication of SPN
    > and DNS record. If you do not want some service stoppage caused by DC
    > rebooting, we can use Netdom.exe to complete renaming process.
    >
    > < Is there anything else what I need to bear in mind while doing this
    > work?>
    >
    > {Morgan}:
    >
    > The DC Rename Preparation process is simple but critical. Before you
    > perform any action, please consider and check the following:
    >
    > a. Check Application and Service compatibility
    >
    > Applications and services that are tied to a specific hostname may be
    > "broken" by the renaming of a DC. If application and service compatibility
    > is unknown, consult the application developer or rename a DC in an test
    > scenario that mimics your production deployment. Core services in Windows
    > Server 2003 are DC Rename compatible with the exception of Root
    > Certificate
    > Authorities. If installed applications are incompatible with DC Rename,
    > determine if the application can be re-installed after the DC rename,
    > otherwise halt the rename operation.
    >
    > b. Is the DC being renamed currently replicating inbound and outbound
    > changes in Active Directory?
    >
    > Use the REPADMIN.EXE tool to verify that the DC being renamed is
    > replicating all locally held directory partitions from direct replication
    > partners. Similarly, confirm that direct replication partners are
    > receiving
    > inbound changes in Active Directory for the domain controller being
    > renamed. Delay the rename operation until inbound and outbound replication
    > for DCs, DNS Servers and Global Catalog are successful.
    >
    > c. Is the DC being renamed is a Root Certification Authority (CA)?
    >
    > Root CAs are not rename compatible. If a DC host a Root CA, move the root
    > CA to a member computer in the domain using the steps outlined in
    > Microsoft
    > Knowledgebase article 298138
    >
    > d. Is the DC being renamed is Global Catalog server?
    >
    > Global Catalogs are essential for logon authentication to native mode
    > domains, logon authentication with UPN logon names and Directory aware
    > applications like Exchange 2000. If the DC being renamed is the only DC in
    > a forest, domain or site, promote a new Global Catalog with sufficient
    > horsepower in the appropriate Active Directory site.
    >
    > e. Is the DC being renamed is a FSMO role holder?
    >
    > FSMO roles residing on domain controllers being renamed could be
    > transferred to an alternate DC to avoid a denial of service.
    >
    > f. Is the DC being renamed the target of a DFS root or link?
    >
    > The UNC path for DNS roots and links refer to specific computer name which
    > is not updated by DC Rename. If the DC being renamed is the only target of
    > a DFS Root, add an additional target. Temporarily remove the DC being
    > renamed as a target of any DFS roots using the DFS snap-in. (start ->
    > run->
    > DFSGUI.MSC) provided the DFS root is NOT replicated by FRS.
    >
    > If the DC being renamed is the only target of a DFS Link, add an
    > additional
    > target. Use the DFS MMC Snap-in (start -> run-> DFSGUI.MSC) to take the
    > renamed target "offline" during the DC Rename operation.
    >
    > g. Is the DC being renamed a DNS Server
    >
    > DNS "SOA" and "A" records for renamed domain controllers are updated
    > automatically by the renamed DC. However, other DNS Servers with delegated
    > DNS zones targeting renamed DCs will need to be updated.
    >
    > F. Make system state backup
    >
    > Hope this helps. If anything is unclear, pleas post back.
    >
    > Have a nice day!
    >
    >
    > Sincerely
    > Morgan Che
    > Microsoft Online Support
    > Microsoft Global Technical Support Center
    >
    > 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: "Zaur" <zbakhramov@gmail.com>
    > --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    > --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    > hardware
    > --->Date: Sun, 25 May 2008 19:38:56 +0200
    > --->Lines: 118
    > --->X-Priority: 3
    > --->X-MSMail-Priority: Normal
    > --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->X-RFC2646: Format=Flowed; Original
    > --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    > --->Newsgroups: microsoft.public.windows.server.migration
    > --->NNTP-Posting-Host: host13-35-dynamic.24-79-r.retail.telecomitalia.it
    > 79.24.35.13
    > --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    > --->Xref: TK2MSFTNGHUB02.phx.gbl
    > microsoft.public.windows.server.migration:3671
    > --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->
    > --->Thank's for your reply!
    > --->
    > --->I decided to do a clean install to avoid any problems. So, I need just
    > to
    > --->confirm the following.
    > --->I need to install DNS/DHCP/WINS and AD on this server which will
    > replace the
    > --->old server. In which order it's better to do it?
    > --->As for DHCP, I believe I can do it in any moment. But as for DNS and
    > WINS,
    > --->when it's better to install these, before running dcpromo or after?
    > WINS on
    > --->existing old server is configured as a replication partner with WINS
    > server
    > --->in our headquarters.
    > --->Another question is after I install AD/DNS/DHCP/WINS is it OK to
    > rename
    > this
    > --->new server after I demote existing server to configure it with the
    > same
    > name
    > --->and IP of the existing old server? I am thinking about demoting old
    > server
    > --->just after I promote the new one, and use the procedure as in the
    > folowing
    > --->link to rename the new domain controler.
    > --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    > --->
    > --->Will this procedure cause any problems with replication between sites?
    > Would
    > --->I have to re-configure site replication? Is there anything else what I
    > need
    > --->to bear in mind while doing this work?
    > --->
    > --->Thanking you in advance,
    > --->
    > --->Zaur
    > --->
    > --->
    > --->
    > --->
    > --->
    > --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    > --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    > --->> Hi,
    > --->>
    > --->> Thanks for posting here.
    > --->>
    > --->> Please understand we could only restore a system state backup from
    > one
    > --->> physical computer to the same physical computer or another computer
    > that
    > --->> has the same make, model, and configuration (identical hardware).
    > However,
    > --->> please note: You may meet some unexpected issues if you restore a
    > system
    > --->> state backup from one computer to another with different hardware.
    > --->> Microsoft does not support restoring a system state backup from one
    > --->> computer to a second computer of a different make, model, or
    > hardware
    > --->> configuration. Microsoft will only provide commercially reasonable
    > efforts
    > --->> to support this process. Even if the source and destination
    > computers
    > --->> appear to be identical makes and models, there may be driver,
    > hardware, or
    > --->> firmware differences between the source and destination computers.
    > --->>
    > --->> More information, please refer to:
    > --->>
    > --->> How to move a Windows installation to different hardware
    > --->> http://support.microsoft.com/default...b;EN-US;249694
    > --->>
    > --->> Therefore, I recommend you migrate the configuration and data
    > manually.
    > --->> For
    > --->> the Domain migration, because there is other DC existing in your
    > network,
    > --->> you can promote an additional DC to synchronize Domain data.
    > --->>
    > --->> About how to promote an additional DC, please refer to:
    > --->>
    > --->> How to promote and demote domain controllers
    > --->> http://support.microsoft.com/kb/238369
    > --->>
    > --->> Hope this helps. Have a good day!
    > --->>
    > --->> Sincerely
    > --->> Morgan Che
    > --->> Microsoft Online Support
    > --->> Microsoft Global Technical Support Center
    > --->>
    > --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    > --->> --->Subject: Migrating Windows 2003 server from old hardware to new
    > --->> hardware
    > --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    > --->> --->Lines: 10
    > --->> --->X-Priority: 3
    > --->> --->X-MSMail-Priority: Normal
    > --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->> --->X-RFC2646: Format=Flowed; Original
    > --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > --->> --->Newsgroups: microsoft.public.windows.server.migration
    > --->> --->NNTP-Posting-Host:
    > --->> host67-143-static.57-217-b.business.telecomitalia.it
    > --->> 217.57.143.67
    > --->> --->Path:
    > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    > --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    > --->> microsoft.public.windows.server.migration:3660
    > --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->> --->
    > --->> --->I have a task to migrate windows 2003 server (AD/WINS/DHCP/DNS)
    > which
    > --->> has no
    > --->> --->FSMO roles from old hardware to a new hardware. This is not the
    > only
    > --->> server
    > --->> --->on a domain and is located in a remote office. I have to
    > preserve
    > all
    > --->> --->settings and software install. How can I accomplish this with
    > the
    > --->> least
    > --->> --->amount of effort? What would I have to do to make sure I have
    > --->> everything
    > --->> --->functioning after I do imaging (or ghosting) from this server to
    > a
    > --->> newer
    > --->> --->hardware?
    > --->> --->
    > --->> --->
    > --->> --->
    > --->> --->
    > --->>
    > --->
    > --->
    > --->
    >




  8. #8
    Morgan che Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Hi,

    Thanks for the reply.

    If you have solve this issue or need further assistance, please let me know.

    Have a nice day!

    Sincerely
    Morgan Che
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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: "Zaur" <zbakhramov@gmail.com>
    --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    <4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl>
    --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    hardware
    --->Date: Fri, 30 May 2008 20:31:45 +0200
    --->Lines: 345
    --->X-Priority: 3
    --->X-MSMail-Priority: Normal
    --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->X-RFC2646: Format=Flowed; Original
    --->Message-ID: <etFdwNowIHA.420@TK2MSFTNGP02.phx.gbl>
    --->Newsgroups: microsoft.public.windows.server.migration
    --->NNTP-Posting-Host: host81-68-dynamic.17-79-r.retail.telecomitalia.it
    79.17.68.81
    --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.server.migration:3702
    --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->
    --->Hi Morgan che!
    --->
    --->Thanks for your replies! They've helped me a lot! I had to rename DC
    using a
    --->GUI since we are running a mixed mode domain functional level (even
    though
    --->we have all windows 2003 dcs).
    --->
    --->Thank you!
    --->
    --->
    --->
    --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    --->news:4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl...
    --->> Hi,
    --->>
    --->> As DC renaming, we can use Netdom.exe tool or manually modify system
    --->> properties.
    --->>
    --->> About these two methods, please see the following article:
    --->>
    --->> Renaming a Domain Controller:
    --->>
    http://technet2.microsoft.com/window...4-883b-4e9a-89
    --->> e6-f8c4509b1de11033.mspx?mfr=true
    --->>
    --->> Comparison of these two methods:
    --->> ==========================
    --->>
    --->> 1) Renaming a domain controller with the "NETDOM COMPUTERNAME" method
    --->>
    --->> Allows DC renames to be scripted or remoted from a client computer
    using
    --->> the command-line utility NETDOM.EXE.
    --->>
    --->> Requires Windows Server 2003 domain functional level be enabled in the
    --->> domain hosting the renamed DC.
    --->>
    --->> Service Principal Names and DNS "A" records for both the new and
    existing
    --->> computer names are registered concurrently until the administrator
    --->> configures the renamed DC to adopt the new computer name.
    --->>
    --->> Administrators can wait for full replication of SPN and DNS records to
    --->> Global Catalog and DNS Servers in the forest before adopting the new
    --->> computer name, minimizing service denials.
    --->>
    --->> 2) Renaming a domain controller with the "Modify system propertities"
    --->> method
    --->>
    --->> Uses the "Computer Name" tab visible in the properties page of "My
    --->> Computer" to rename either the computer name or its primary DNS suffix
    --->> through an easy-to-use GUI
    --->>
    --->> Is not dependent on Windows Server 2003 domain or forest functional
    levels
    --->>
    --->> Transitions the renamed DC to the new computer name immediately after
    --->> reboot causing a possible loss of service until service principal
    names
    --->> and
    --->> DNS registration are fully replicated and considered by other clients
    and
    --->> domain controllers in the forest
    --->>
    --->> According to your practical environment, please pick the most suitable
    --->> method to rename DC.
    --->>
    --->> <Will this procedure cause any problems with replication between
    sites?
    --->> Would I have to re-configure site replication?>
    --->>
    --->> {Morgan}:
    --->>
    --->> Normally, it will not affect the site replication. As we know, the DC
    --->> renaming will update SPN attributes stored in Active Directory for
    this
    --->> computer account and register DNS resource records for the new
    computer
    --->> name. The SPN value of the computer account must be replicated to all
    --->> domain controllers for the domain and the DNS resource records for
    the new
    --->> computer name must be distributed to all the authoritative DNS
    servers for
    --->> the domain name.
    --->>
    --->> The above two methods will automatically complete the replication of
    SPN
    --->> and DNS record. If you do not want some service stoppage caused by DC
    --->> rebooting, we can use Netdom.exe to complete renaming process.
    --->>
    --->> < Is there anything else what I need to bear in mind while doing this
    --->> work?>
    --->>
    --->> {Morgan}:
    --->>
    --->> The DC Rename Preparation process is simple but critical. Before you
    --->> perform any action, please consider and check the following:
    --->>
    --->> a. Check Application and Service compatibility
    --->>
    --->> Applications and services that are tied to a specific hostname may be
    --->> "broken" by the renaming of a DC. If application and service
    compatibility
    --->> is unknown, consult the application developer or rename a DC in an
    test
    --->> scenario that mimics your production deployment. Core services in
    Windows
    --->> Server 2003 are DC Rename compatible with the exception of Root
    --->> Certificate
    --->> Authorities. If installed applications are incompatible with DC
    Rename,
    --->> determine if the application can be re-installed after the DC rename,
    --->> otherwise halt the rename operation.
    --->>
    --->> b. Is the DC being renamed currently replicating inbound and outbound
    --->> changes in Active Directory?
    --->>
    --->> Use the REPADMIN.EXE tool to verify that the DC being renamed is
    --->> replicating all locally held directory partitions from direct
    replication
    --->> partners. Similarly, confirm that direct replication partners are
    --->> receiving
    --->> inbound changes in Active Directory for the domain controller being
    --->> renamed. Delay the rename operation until inbound and outbound
    replication
    --->> for DCs, DNS Servers and Global Catalog are successful.
    --->>
    --->> c. Is the DC being renamed is a Root Certification Authority (CA)?
    --->>
    --->> Root CAs are not rename compatible. If a DC host a Root CA, move the
    root
    --->> CA to a member computer in the domain using the steps outlined in
    --->> Microsoft
    --->> Knowledgebase article 298138
    --->>
    --->> d. Is the DC being renamed is Global Catalog server?
    --->>
    --->> Global Catalogs are essential for logon authentication to native mode
    --->> domains, logon authentication with UPN logon names and Directory aware
    --->> applications like Exchange 2000. If the DC being renamed is the only
    DC in
    --->> a forest, domain or site, promote a new Global Catalog with sufficient
    --->> horsepower in the appropriate Active Directory site.
    --->>
    --->> e. Is the DC being renamed is a FSMO role holder?
    --->>
    --->> FSMO roles residing on domain controllers being renamed could be
    --->> transferred to an alternate DC to avoid a denial of service.
    --->>
    --->> f. Is the DC being renamed the target of a DFS root or link?
    --->>
    --->> The UNC path for DNS roots and links refer to specific computer name
    which
    --->> is not updated by DC Rename. If the DC being renamed is the only
    target of
    --->> a DFS Root, add an additional target. Temporarily remove the DC being
    --->> renamed as a target of any DFS roots using the DFS snap-in. (start ->
    --->> run->
    --->> DFSGUI.MSC) provided the DFS root is NOT replicated by FRS.
    --->>
    --->> If the DC being renamed is the only target of a DFS Link, add an
    --->> additional
    --->> target. Use the DFS MMC Snap-in (start -> run-> DFSGUI.MSC) to take
    the
    --->> renamed target "offline" during the DC Rename operation.
    --->>
    --->> g. Is the DC being renamed a DNS Server
    --->>
    --->> DNS "SOA" and "A" records for renamed domain controllers are updated
    --->> automatically by the renamed DC. However, other DNS Servers with
    delegated
    --->> DNS zones targeting renamed DCs will need to be updated.
    --->>
    --->> F. Make system state backup
    --->>
    --->> Hope this helps. If anything is unclear, pleas post back.
    --->>
    --->> Have a nice day!
    --->>
    --->>
    --->> Sincerely
    --->> Morgan Che
    --->> Microsoft Online Support
    --->> Microsoft Global Technical Support Center
    --->>
    --->> 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: "Zaur" <zbakhramov@gmail.com>
    --->> --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    --->> --->Subject: Re: Migrating Windows 2003 server from old hardware to
    new
    --->> hardware
    --->> --->Date: Sun, 25 May 2008 19:38:56 +0200
    --->> --->Lines: 118
    --->> --->X-Priority: 3
    --->> --->X-MSMail-Priority: Normal
    --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->NNTP-Posting-Host:
    host13-35-dynamic.24-79-r.retail.telecomitalia.it
    --->> 79.24.35.13
    --->> --->Path:
    TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> microsoft.public.windows.server.migration:3671
    --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->
    --->> --->Thank's for your reply!
    --->> --->
    --->> --->I decided to do a clean install to avoid any problems. So, I need
    just
    --->> to
    --->> --->confirm the following.
    --->> --->I need to install DNS/DHCP/WINS and AD on this server which will
    --->> replace the
    --->> --->old server. In which order it's better to do it?
    --->> --->As for DHCP, I believe I can do it in any moment. But as for DNS
    and
    --->> WINS,
    --->> --->when it's better to install these, before running dcpromo or
    after?
    --->> WINS on
    --->> --->existing old server is configured as a replication partner with
    WINS
    --->> server
    --->> --->in our headquarters.
    --->> --->Another question is after I install AD/DNS/DHCP/WINS is it OK to
    --->> rename
    --->> this
    --->> --->new server after I demote existing server to configure it with
    the
    --->> same
    --->> name
    --->> --->and IP of the existing old server? I am thinking about demoting
    old
    --->> server
    --->> --->just after I promote the new one, and use the procedure as in the
    --->> folowing
    --->> --->link to rename the new domain controler.
    --->> --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    --->> --->
    --->> --->Will this procedure cause any problems with replication between
    sites?
    --->> Would
    --->> --->I have to re-configure site replication? Is there anything else
    what I
    --->> need
    --->> --->to bear in mind while doing this work?
    --->> --->
    --->> --->Thanking you in advance,
    --->> --->
    --->> --->Zaur
    --->> --->
    --->> --->
    --->> --->
    --->> --->
    --->> --->
    --->> --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in
    message
    --->> --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    --->> --->> Hi,
    --->> --->>
    --->> --->> Thanks for posting here.
    --->> --->>
    --->> --->> Please understand we could only restore a system state backup
    from
    --->> one
    --->> --->> physical computer to the same physical computer or another
    computer
    --->> that
    --->> --->> has the same make, model, and configuration (identical
    hardware).
    --->> However,
    --->> --->> please note: You may meet some unexpected issues if you restore
    a
    --->> system
    --->> --->> state backup from one computer to another with different
    hardware.
    --->> --->> Microsoft does not support restoring a system state backup from
    one
    --->> --->> computer to a second computer of a different make, model, or
    --->> hardware
    --->> --->> configuration. Microsoft will only provide commercially
    reasonable
    --->> efforts
    --->> --->> to support this process. Even if the source and destination
    --->> computers
    --->> --->> appear to be identical makes and models, there may be driver,
    --->> hardware, or
    --->> --->> firmware differences between the source and destination
    computers.
    --->> --->>
    --->> --->> More information, please refer to:
    --->> --->>
    --->> --->> How to move a Windows installation to different hardware
    --->> --->> http://support.microsoft.com/default...b;EN-US;249694
    --->> --->>
    --->> --->> Therefore, I recommend you migrate the configuration and data
    --->> manually.
    --->> --->> For
    --->> --->> the Domain migration, because there is other DC existing in your
    --->> network,
    --->> --->> you can promote an additional DC to synchronize Domain data.
    --->> --->>
    --->> --->> About how to promote an additional DC, please refer to:
    --->> --->>
    --->> --->> How to promote and demote domain controllers
    --->> --->> http://support.microsoft.com/kb/238369
    --->> --->>
    --->> --->> Hope this helps. Have a good day!
    --->> --->>
    --->> --->> Sincerely
    --->> --->> Morgan Che
    --->> --->> Microsoft Online Support
    --->> --->> Microsoft Global Technical Support Center
    --->> --->>
    --->> --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    --->> --->> --->Subject: Migrating Windows 2003 server from old hardware to
    new
    --->> --->> hardware
    --->> --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    --->> --->> --->Lines: 10
    --->> --->> --->X-Priority: 3
    --->> --->> --->X-MSMail-Priority: Normal
    --->> --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->> --->NNTP-Posting-Host:
    --->> --->> host67-143-static.57-217-b.business.telecomitalia.it
    --->> --->> 217.57.143.67
    --->> --->> --->Path:
    --->> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    --->> --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> --->> microsoft.public.windows.server.migration:3660
    --->> --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->> --->
    --->> --->> --->I have a task to migrate windows 2003 server
    (AD/WINS/DHCP/DNS)
    --->> which
    --->> --->> has no
    --->> --->> --->FSMO roles from old hardware to a new hardware. This is not
    the
    --->> only
    --->> --->> server
    --->> --->> --->on a domain and is located in a remote office. I have to
    --->> preserve
    --->> all
    --->> --->> --->settings and software install. How can I accomplish this
    with
    --->> the
    --->> --->> least
    --->> --->> --->amount of effort? What would I have to do to make sure I
    have
    --->> --->> everything
    --->> --->> --->functioning after I do imaging (or ghosting) from this
    server to
    --->> a
    --->> --->> newer
    --->> --->> --->hardware?
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->>
    --->> --->
    --->> --->
    --->> --->
    --->>
    --->
    --->
    --->


  9. #9
    Zaur Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    The issue is solved. However, there's another issue related to replication
    arisen after renaming a DC. I have posted it in
    microsoft.public.windows.server.active_directory



    "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    news:tzNh6pFxIHA.4216@TK2MSFTNGHUB02.phx.gbl...
    > Hi,
    >
    > Thanks for the reply.
    >
    > If you have solve this issue or need further assistance, please let me
    > know.
    >
    > Have a nice day!
    >
    > Sincerely
    > Morgan Che
    > Microsoft Online Support
    > Microsoft Global Technical Support Center
    >
    > 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: "Zaur" <zbakhramov@gmail.com>
    > --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    > <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    > <4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl>
    > --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    > hardware
    > --->Date: Fri, 30 May 2008 20:31:45 +0200
    > --->Lines: 345
    > --->X-Priority: 3
    > --->X-MSMail-Priority: Normal
    > --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->X-RFC2646: Format=Flowed; Original
    > --->Message-ID: <etFdwNowIHA.420@TK2MSFTNGP02.phx.gbl>
    > --->Newsgroups: microsoft.public.windows.server.migration
    > --->NNTP-Posting-Host: host81-68-dynamic.17-79-r.retail.telecomitalia.it
    > 79.17.68.81
    > --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    > --->Xref: TK2MSFTNGHUB02.phx.gbl
    > microsoft.public.windows.server.migration:3702
    > --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->
    > --->Hi Morgan che!
    > --->
    > --->Thanks for your replies! They've helped me a lot! I had to rename DC
    > using a
    > --->GUI since we are running a mixed mode domain functional level (even
    > though
    > --->we have all windows 2003 dcs).
    > --->
    > --->Thank you!
    > --->
    > --->
    > --->
    > --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    > --->news:4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl...
    > --->> Hi,
    > --->>
    > --->> As DC renaming, we can use Netdom.exe tool or manually modify system
    > --->> properties.
    > --->>
    > --->> About these two methods, please see the following article:
    > --->>
    > --->> Renaming a Domain Controller:
    > --->>
    > http://technet2.microsoft.com/window...4-883b-4e9a-89
    > --->> e6-f8c4509b1de11033.mspx?mfr=true
    > --->>
    > --->> Comparison of these two methods:
    > --->> ==========================
    > --->>
    > --->> 1) Renaming a domain controller with the "NETDOM COMPUTERNAME"
    > method
    > --->>
    > --->> Allows DC renames to be scripted or remoted from a client computer
    > using
    > --->> the command-line utility NETDOM.EXE.
    > --->>
    > --->> Requires Windows Server 2003 domain functional level be enabled in
    > the
    > --->> domain hosting the renamed DC.
    > --->>
    > --->> Service Principal Names and DNS "A" records for both the new and
    > existing
    > --->> computer names are registered concurrently until the administrator
    > --->> configures the renamed DC to adopt the new computer name.
    > --->>
    > --->> Administrators can wait for full replication of SPN and DNS records
    > to
    > --->> Global Catalog and DNS Servers in the forest before adopting the new
    > --->> computer name, minimizing service denials.
    > --->>
    > --->> 2) Renaming a domain controller with the "Modify system
    > propertities"
    > --->> method
    > --->>
    > --->> Uses the "Computer Name" tab visible in the properties page of "My
    > --->> Computer" to rename either the computer name or its primary DNS
    > suffix
    > --->> through an easy-to-use GUI
    > --->>
    > --->> Is not dependent on Windows Server 2003 domain or forest functional
    > levels
    > --->>
    > --->> Transitions the renamed DC to the new computer name immediately
    > after
    > --->> reboot causing a possible loss of service until service principal
    > names
    > --->> and
    > --->> DNS registration are fully replicated and considered by other
    > clients
    > and
    > --->> domain controllers in the forest
    > --->>
    > --->> According to your practical environment, please pick the most
    > suitable
    > --->> method to rename DC.
    > --->>
    > --->> <Will this procedure cause any problems with replication between
    > sites?
    > --->> Would I have to re-configure site replication?>
    > --->>
    > --->> {Morgan}:
    > --->>
    > --->> Normally, it will not affect the site replication. As we know, the
    > DC
    > --->> renaming will update SPN attributes stored in Active Directory for
    > this
    > --->> computer account and register DNS resource records for the new
    > computer
    > --->> name. The SPN value of the computer account must be replicated to
    > all
    > --->> domain controllers for the domain and the DNS resource records for
    > the new
    > --->> computer name must be distributed to all the authoritative DNS
    > servers for
    > --->> the domain name.
    > --->>
    > --->> The above two methods will automatically complete the replication of
    > SPN
    > --->> and DNS record. If you do not want some service stoppage caused by
    > DC
    > --->> rebooting, we can use Netdom.exe to complete renaming process.
    > --->>
    > --->> < Is there anything else what I need to bear in mind while doing
    > this
    > --->> work?>
    > --->>
    > --->> {Morgan}:
    > --->>
    > --->> The DC Rename Preparation process is simple but critical. Before you
    > --->> perform any action, please consider and check the following:
    > --->>
    > --->> a. Check Application and Service compatibility
    > --->>
    > --->> Applications and services that are tied to a specific hostname may
    > be
    > --->> "broken" by the renaming of a DC. If application and service
    > compatibility
    > --->> is unknown, consult the application developer or rename a DC in an
    > test
    > --->> scenario that mimics your production deployment. Core services in
    > Windows
    > --->> Server 2003 are DC Rename compatible with the exception of Root
    > --->> Certificate
    > --->> Authorities. If installed applications are incompatible with DC
    > Rename,
    > --->> determine if the application can be re-installed after the DC
    > rename,
    > --->> otherwise halt the rename operation.
    > --->>
    > --->> b. Is the DC being renamed currently replicating inbound and
    > outbound
    > --->> changes in Active Directory?
    > --->>
    > --->> Use the REPADMIN.EXE tool to verify that the DC being renamed is
    > --->> replicating all locally held directory partitions from direct
    > replication
    > --->> partners. Similarly, confirm that direct replication partners are
    > --->> receiving
    > --->> inbound changes in Active Directory for the domain controller being
    > --->> renamed. Delay the rename operation until inbound and outbound
    > replication
    > --->> for DCs, DNS Servers and Global Catalog are successful.
    > --->>
    > --->> c. Is the DC being renamed is a Root Certification Authority (CA)?
    > --->>
    > --->> Root CAs are not rename compatible. If a DC host a Root CA, move the
    > root
    > --->> CA to a member computer in the domain using the steps outlined in
    > --->> Microsoft
    > --->> Knowledgebase article 298138
    > --->>
    > --->> d. Is the DC being renamed is Global Catalog server?
    > --->>
    > --->> Global Catalogs are essential for logon authentication to native
    > mode
    > --->> domains, logon authentication with UPN logon names and Directory
    > aware
    > --->> applications like Exchange 2000. If the DC being renamed is the only
    > DC in
    > --->> a forest, domain or site, promote a new Global Catalog with
    > sufficient
    > --->> horsepower in the appropriate Active Directory site.
    > --->>
    > --->> e. Is the DC being renamed is a FSMO role holder?
    > --->>
    > --->> FSMO roles residing on domain controllers being renamed could be
    > --->> transferred to an alternate DC to avoid a denial of service.
    > --->>
    > --->> f. Is the DC being renamed the target of a DFS root or link?
    > --->>
    > --->> The UNC path for DNS roots and links refer to specific computer name
    > which
    > --->> is not updated by DC Rename. If the DC being renamed is the only
    > target of
    > --->> a DFS Root, add an additional target. Temporarily remove the DC
    > being
    > --->> renamed as a target of any DFS roots using the DFS snap-in.
    > (start ->
    > --->> run->
    > --->> DFSGUI.MSC) provided the DFS root is NOT replicated by FRS.
    > --->>
    > --->> If the DC being renamed is the only target of a DFS Link, add an
    > --->> additional
    > --->> target. Use the DFS MMC Snap-in (start -> run-> DFSGUI.MSC) to take
    > the
    > --->> renamed target "offline" during the DC Rename operation.
    > --->>
    > --->> g. Is the DC being renamed a DNS Server
    > --->>
    > --->> DNS "SOA" and "A" records for renamed domain controllers are updated
    > --->> automatically by the renamed DC. However, other DNS Servers with
    > delegated
    > --->> DNS zones targeting renamed DCs will need to be updated.
    > --->>
    > --->> F. Make system state backup
    > --->>
    > --->> Hope this helps. If anything is unclear, pleas post back.
    > --->>
    > --->> Have a nice day!
    > --->>
    > --->>
    > --->> Sincerely
    > --->> Morgan Che
    > --->> Microsoft Online Support
    > --->> Microsoft Global Technical Support Center
    > --->>
    > --->> 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: "Zaur" <zbakhramov@gmail.com>
    > --->> --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > --->> <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    > --->> --->Subject: Re: Migrating Windows 2003 server from old hardware to
    > new
    > --->> hardware
    > --->> --->Date: Sun, 25 May 2008 19:38:56 +0200
    > --->> --->Lines: 118
    > --->> --->X-Priority: 3
    > --->> --->X-MSMail-Priority: Normal
    > --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->> --->X-RFC2646: Format=Flowed; Original
    > --->> --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    > --->> --->Newsgroups: microsoft.public.windows.server.migration
    > --->> --->NNTP-Posting-Host:
    > host13-35-dynamic.24-79-r.retail.telecomitalia.it
    > --->> 79.24.35.13
    > --->> --->Path:
    > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    > --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    > --->> microsoft.public.windows.server.migration:3671
    > --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->> --->
    > --->> --->Thank's for your reply!
    > --->> --->
    > --->> --->I decided to do a clean install to avoid any problems. So, I
    > need
    > just
    > --->> to
    > --->> --->confirm the following.
    > --->> --->I need to install DNS/DHCP/WINS and AD on this server which will
    > --->> replace the
    > --->> --->old server. In which order it's better to do it?
    > --->> --->As for DHCP, I believe I can do it in any moment. But as for DNS
    > and
    > --->> WINS,
    > --->> --->when it's better to install these, before running dcpromo or
    > after?
    > --->> WINS on
    > --->> --->existing old server is configured as a replication partner with
    > WINS
    > --->> server
    > --->> --->in our headquarters.
    > --->> --->Another question is after I install AD/DNS/DHCP/WINS is it OK to
    > --->> rename
    > --->> this
    > --->> --->new server after I demote existing server to configure it with
    > the
    > --->> same
    > --->> name
    > --->> --->and IP of the existing old server? I am thinking about demoting
    > old
    > --->> server
    > --->> --->just after I promote the new one, and use the procedure as in
    > the
    > --->> folowing
    > --->> --->link to rename the new domain controler.
    > --->> --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    > --->> --->
    > --->> --->Will this procedure cause any problems with replication between
    > sites?
    > --->> Would
    > --->> --->I have to re-configure site replication? Is there anything else
    > what I
    > --->> need
    > --->> --->to bear in mind while doing this work?
    > --->> --->
    > --->> --->Thanking you in advance,
    > --->> --->
    > --->> --->Zaur
    > --->> --->
    > --->> --->
    > --->> --->
    > --->> --->
    > --->> --->
    > --->> --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in
    > message
    > --->> --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    > --->> --->> Hi,
    > --->> --->>
    > --->> --->> Thanks for posting here.
    > --->> --->>
    > --->> --->> Please understand we could only restore a system state backup
    > from
    > --->> one
    > --->> --->> physical computer to the same physical computer or another
    > computer
    > --->> that
    > --->> --->> has the same make, model, and configuration (identical
    > hardware).
    > --->> However,
    > --->> --->> please note: You may meet some unexpected issues if you
    > restore
    > a
    > --->> system
    > --->> --->> state backup from one computer to another with different
    > hardware.
    > --->> --->> Microsoft does not support restoring a system state backup
    > from
    > one
    > --->> --->> computer to a second computer of a different make, model, or
    > --->> hardware
    > --->> --->> configuration. Microsoft will only provide commercially
    > reasonable
    > --->> efforts
    > --->> --->> to support this process. Even if the source and destination
    > --->> computers
    > --->> --->> appear to be identical makes and models, there may be driver,
    > --->> hardware, or
    > --->> --->> firmware differences between the source and destination
    > computers.
    > --->> --->>
    > --->> --->> More information, please refer to:
    > --->> --->>
    > --->> --->> How to move a Windows installation to different hardware
    > --->> --->> http://support.microsoft.com/default...b;EN-US;249694
    > --->> --->>
    > --->> --->> Therefore, I recommend you migrate the configuration and data
    > --->> manually.
    > --->> --->> For
    > --->> --->> the Domain migration, because there is other DC existing in
    > your
    > --->> network,
    > --->> --->> you can promote an additional DC to synchronize Domain data.
    > --->> --->>
    > --->> --->> About how to promote an additional DC, please refer to:
    > --->> --->>
    > --->> --->> How to promote and demote domain controllers
    > --->> --->> http://support.microsoft.com/kb/238369
    > --->> --->>
    > --->> --->> Hope this helps. Have a good day!
    > --->> --->>
    > --->> --->> Sincerely
    > --->> --->> Morgan Che
    > --->> --->> Microsoft Online Support
    > --->> --->> Microsoft Global Technical Support Center
    > --->> --->>
    > --->> --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    > --->> --->> --->Subject: Migrating Windows 2003 server from old hardware
    > to
    > new
    > --->> --->> hardware
    > --->> --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    > --->> --->> --->Lines: 10
    > --->> --->> --->X-Priority: 3
    > --->> --->> --->X-MSMail-Priority: Normal
    > --->> --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    > --->> --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    > --->> --->> --->X-RFC2646: Format=Flowed; Original
    > --->> --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    > --->> --->> --->Newsgroups: microsoft.public.windows.server.migration
    > --->> --->> --->NNTP-Posting-Host:
    > --->> --->> host67-143-static.57-217-b.business.telecomitalia.it
    > --->> --->> 217.57.143.67
    > --->> --->> --->Path:
    > --->> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    > --->> --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    > --->> --->> microsoft.public.windows.server.migration:3660
    > --->> --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    > --->> --->> --->
    > --->> --->> --->I have a task to migrate windows 2003 server
    > (AD/WINS/DHCP/DNS)
    > --->> which
    > --->> --->> has no
    > --->> --->> --->FSMO roles from old hardware to a new hardware. This is
    > not
    > the
    > --->> only
    > --->> --->> server
    > --->> --->> --->on a domain and is located in a remote office. I have to
    > --->> preserve
    > --->> all
    > --->> --->> --->settings and software install. How can I accomplish this
    > with
    > --->> the
    > --->> --->> least
    > --->> --->> --->amount of effort? What would I have to do to make sure I
    > have
    > --->> --->> everything
    > --->> --->> --->functioning after I do imaging (or ghosting) from this
    > server to
    > --->> a
    > --->> --->> newer
    > --->> --->> --->hardware?
    > --->> --->> --->
    > --->> --->> --->
    > --->> --->> --->
    > --->> --->> --->
    > --->> --->>
    > --->> --->
    > --->> --->
    > --->> --->
    > --->>
    > --->
    > --->
    > --->
    >




  10. #10
    Morgan che Guest

    Re: Migrating Windows 2003 server from old hardware to new hardware

    Hi,

    Thanks for letting us know that you have solved this issue. I believe other
    members who encounter the similiar issue will benifit from our interaction.

    Thanks.

    Sincerely
    Morgan Che
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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: "Zaur" <zbakhramov@gmail.com>
    --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    <4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl>
    <etFdwNowIHA.420@TK2MSFTNGP02.phx.gbl>
    <tzNh6pFxIHA.4216@TK2MSFTNGHUB02.phx.gbl>
    --->Subject: Re: Migrating Windows 2003 server from old hardware to new
    hardware
    --->Date: Mon, 2 Jun 2008 12:36:17 +0200
    --->Lines: 486
    --->X-Priority: 3
    --->X-MSMail-Priority: Normal
    --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->X-RFC2646: Format=Flowed; Original
    --->Message-ID: <um#MAyJxIHA.5580@TK2MSFTNGP04.phx.gbl>
    --->Newsgroups: microsoft.public.windows.server.migration
    --->NNTP-Posting-Host: host173-14-dynamic.24-79-r.retail.telecomitalia.it
    79.24.14.173
    --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
    --->Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.server.migration:3714
    --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->
    --->The issue is solved. However, there's another issue related to
    replication
    --->arisen after renaming a DC. I have posted it in
    --->microsoft.public.windows.server.active_directory
    --->
    --->
    --->
    --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
    --->news:tzNh6pFxIHA.4216@TK2MSFTNGHUB02.phx.gbl...
    --->> Hi,
    --->>
    --->> Thanks for the reply.
    --->>
    --->> If you have solve this issue or need further assistance, please let
    me
    --->> know.
    --->>
    --->> Have a nice day!
    --->>
    --->> Sincerely
    --->> Morgan Che
    --->> Microsoft Online Support
    --->> Microsoft Global Technical Support Center
    --->>
    --->> 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: "Zaur" <zbakhramov@gmail.com>
    --->> --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    --->> <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    --->> <4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl>
    --->> --->Subject: Re: Migrating Windows 2003 server from old hardware to
    new
    --->> hardware
    --->> --->Date: Fri, 30 May 2008 20:31:45 +0200
    --->> --->Lines: 345
    --->> --->X-Priority: 3
    --->> --->X-MSMail-Priority: Normal
    --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->Message-ID: <etFdwNowIHA.420@TK2MSFTNGP02.phx.gbl>
    --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->NNTP-Posting-Host:
    host81-68-dynamic.17-79-r.retail.telecomitalia.it
    --->> 79.17.68.81
    --->> --->Path:
    TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> microsoft.public.windows.server.migration:3702
    --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->
    --->> --->Hi Morgan che!
    --->> --->
    --->> --->Thanks for your replies! They've helped me a lot! I had to rename
    DC
    --->> using a
    --->> --->GUI since we are running a mixed mode domain functional level
    (even
    --->> though
    --->> --->we have all windows 2003 dcs).
    --->> --->
    --->> --->Thank you!
    --->> --->
    --->> --->
    --->> --->
    --->> --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in
    message
    --->> --->news:4drb3XJwIHA.1788@TK2MSFTNGHUB02.phx.gbl...
    --->> --->> Hi,
    --->> --->>
    --->> --->> As DC renaming, we can use Netdom.exe tool or manually modify
    system
    --->> --->> properties.
    --->> --->>
    --->> --->> About these two methods, please see the following article:
    --->> --->>
    --->> --->> Renaming a Domain Controller:
    --->> --->>
    --->>
    http://technet2.microsoft.com/window...4-883b-4e9a-89
    --->> --->> e6-f8c4509b1de11033.mspx?mfr=true
    --->> --->>
    --->> --->> Comparison of these two methods:
    --->> --->> ==========================
    --->> --->>
    --->> --->> 1) Renaming a domain controller with the "NETDOM COMPUTERNAME"
    --->> method
    --->> --->>
    --->> --->> Allows DC renames to be scripted or remoted from a client
    computer
    --->> using
    --->> --->> the command-line utility NETDOM.EXE.
    --->> --->>
    --->> --->> Requires Windows Server 2003 domain functional level be enabled
    in
    --->> the
    --->> --->> domain hosting the renamed DC.
    --->> --->>
    --->> --->> Service Principal Names and DNS "A" records for both the new and
    --->> existing
    --->> --->> computer names are registered concurrently until the
    administrator
    --->> --->> configures the renamed DC to adopt the new computer name.
    --->> --->>
    --->> --->> Administrators can wait for full replication of SPN and DNS
    records
    --->> to
    --->> --->> Global Catalog and DNS Servers in the forest before adopting
    the new
    --->> --->> computer name, minimizing service denials.
    --->> --->>
    --->> --->> 2) Renaming a domain controller with the "Modify system
    --->> propertities"
    --->> --->> method
    --->> --->>
    --->> --->> Uses the "Computer Name" tab visible in the properties page of
    "My
    --->> --->> Computer" to rename either the computer name or its primary DNS
    --->> suffix
    --->> --->> through an easy-to-use GUI
    --->> --->>
    --->> --->> Is not dependent on Windows Server 2003 domain or forest
    functional
    --->> levels
    --->> --->>
    --->> --->> Transitions the renamed DC to the new computer name immediately
    --->> after
    --->> --->> reboot causing a possible loss of service until service
    principal
    --->> names
    --->> --->> and
    --->> --->> DNS registration are fully replicated and considered by other
    --->> clients
    --->> and
    --->> --->> domain controllers in the forest
    --->> --->>
    --->> --->> According to your practical environment, please pick the most
    --->> suitable
    --->> --->> method to rename DC.
    --->> --->>
    --->> --->> <Will this procedure cause any problems with replication between
    --->> sites?
    --->> --->> Would I have to re-configure site replication?>
    --->> --->>
    --->> --->> {Morgan}:
    --->> --->>
    --->> --->> Normally, it will not affect the site replication. As we know,
    the
    --->> DC
    --->> --->> renaming will update SPN attributes stored in Active Directory
    for
    --->> this
    --->> --->> computer account and register DNS resource records for the new
    --->> computer
    --->> --->> name. The SPN value of the computer account must be replicated
    to
    --->> all
    --->> --->> domain controllers for the domain and the DNS resource records
    for
    --->> the new
    --->> --->> computer name must be distributed to all the authoritative DNS
    --->> servers for
    --->> --->> the domain name.
    --->> --->>
    --->> --->> The above two methods will automatically complete the
    replication of
    --->> SPN
    --->> --->> and DNS record. If you do not want some service stoppage caused
    by
    --->> DC
    --->> --->> rebooting, we can use Netdom.exe to complete renaming process.
    --->> --->>
    --->> --->> < Is there anything else what I need to bear in mind while
    doing
    --->> this
    --->> --->> work?>
    --->> --->>
    --->> --->> {Morgan}:
    --->> --->>
    --->> --->> The DC Rename Preparation process is simple but critical.
    Before you
    --->> --->> perform any action, please consider and check the following:
    --->> --->>
    --->> --->> a. Check Application and Service compatibility
    --->> --->>
    --->> --->> Applications and services that are tied to a specific hostname
    may
    --->> be
    --->> --->> "broken" by the renaming of a DC. If application and service
    --->> compatibility
    --->> --->> is unknown, consult the application developer or rename a DC in
    an
    --->> test
    --->> --->> scenario that mimics your production deployment. Core services
    in
    --->> Windows
    --->> --->> Server 2003 are DC Rename compatible with the exception of Root
    --->> --->> Certificate
    --->> --->> Authorities. If installed applications are incompatible with DC
    --->> Rename,
    --->> --->> determine if the application can be re-installed after the DC
    --->> rename,
    --->> --->> otherwise halt the rename operation.
    --->> --->>
    --->> --->> b. Is the DC being renamed currently replicating inbound and
    --->> outbound
    --->> --->> changes in Active Directory?
    --->> --->>
    --->> --->> Use the REPADMIN.EXE tool to verify that the DC being renamed is
    --->> --->> replicating all locally held directory partitions from direct
    --->> replication
    --->> --->> partners. Similarly, confirm that direct replication partners
    are
    --->> --->> receiving
    --->> --->> inbound changes in Active Directory for the domain controller
    being
    --->> --->> renamed. Delay the rename operation until inbound and outbound
    --->> replication
    --->> --->> for DCs, DNS Servers and Global Catalog are successful.
    --->> --->>
    --->> --->> c. Is the DC being renamed is a Root Certification Authority
    (CA)?
    --->> --->>
    --->> --->> Root CAs are not rename compatible. If a DC host a Root CA,
    move the
    --->> root
    --->> --->> CA to a member computer in the domain using the steps outlined
    in
    --->> --->> Microsoft
    --->> --->> Knowledgebase article 298138
    --->> --->>
    --->> --->> d. Is the DC being renamed is Global Catalog server?
    --->> --->>
    --->> --->> Global Catalogs are essential for logon authentication to
    native
    --->> mode
    --->> --->> domains, logon authentication with UPN logon names and
    Directory
    --->> aware
    --->> --->> applications like Exchange 2000. If the DC being renamed is the
    only
    --->> DC in
    --->> --->> a forest, domain or site, promote a new Global Catalog with
    --->> sufficient
    --->> --->> horsepower in the appropriate Active Directory site.
    --->> --->>
    --->> --->> e. Is the DC being renamed is a FSMO role holder?
    --->> --->>
    --->> --->> FSMO roles residing on domain controllers being renamed could be
    --->> --->> transferred to an alternate DC to avoid a denial of service.
    --->> --->>
    --->> --->> f. Is the DC being renamed the target of a DFS root or link?
    --->> --->>
    --->> --->> The UNC path for DNS roots and links refer to specific computer
    name
    --->> which
    --->> --->> is not updated by DC Rename. If the DC being renamed is the only
    --->> target of
    --->> --->> a DFS Root, add an additional target. Temporarily remove the DC
    --->> being
    --->> --->> renamed as a target of any DFS roots using the DFS snap-in.
    --->> (start ->
    --->> --->> run->
    --->> --->> DFSGUI.MSC) provided the DFS root is NOT replicated by FRS.
    --->> --->>
    --->> --->> If the DC being renamed is the only target of a DFS Link, add an
    --->> --->> additional
    --->> --->> target. Use the DFS MMC Snap-in (start -> run-> DFSGUI.MSC) to
    take
    --->> the
    --->> --->> renamed target "offline" during the DC Rename operation.
    --->> --->>
    --->> --->> g. Is the DC being renamed a DNS Server
    --->> --->>
    --->> --->> DNS "SOA" and "A" records for renamed domain controllers are
    updated
    --->> --->> automatically by the renamed DC. However, other DNS Servers with
    --->> delegated
    --->> --->> DNS zones targeting renamed DCs will need to be updated.
    --->> --->>
    --->> --->> F. Make system state backup
    --->> --->>
    --->> --->> Hope this helps. If anything is unclear, pleas post back.
    --->> --->>
    --->> --->> Have a nice day!
    --->> --->>
    --->> --->>
    --->> --->> Sincerely
    --->> --->> Morgan Che
    --->> --->> Microsoft Online Support
    --->> --->> Microsoft Global Technical Support Center
    --->> --->>
    --->> --->> 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: "Zaur" <zbakhramov@gmail.com>
    --->> --->> --->References: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> --->> <krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl>
    --->> --->> --->Subject: Re: Migrating Windows 2003 server from old
    hardware to
    --->> new
    --->> --->> hardware
    --->> --->> --->Date: Sun, 25 May 2008 19:38:56 +0200
    --->> --->> --->Lines: 118
    --->> --->> --->X-Priority: 3
    --->> --->> --->X-MSMail-Priority: Normal
    --->> --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
    --->> --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->> --->Message-ID: <OoAF54ovIHA.5584@TK2MSFTNGP02.phx.gbl>
    --->> --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->> --->NNTP-Posting-Host:
    --->> host13-35-dynamic.24-79-r.retail.telecomitalia.it
    --->> --->> 79.24.35.13
    --->> --->> --->Path:
    --->> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    --->> --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> --->> microsoft.public.windows.server.migration:3671
    --->> --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->> --->
    --->> --->> --->Thank's for your reply!
    --->> --->> --->
    --->> --->> --->I decided to do a clean install to avoid any problems. So,
    I
    --->> need
    --->> just
    --->> --->> to
    --->> --->> --->confirm the following.
    --->> --->> --->I need to install DNS/DHCP/WINS and AD on this server which
    will
    --->> --->> replace the
    --->> --->> --->old server. In which order it's better to do it?
    --->> --->> --->As for DHCP, I believe I can do it in any moment. But as
    for DNS
    --->> and
    --->> --->> WINS,
    --->> --->> --->when it's better to install these, before running dcpromo or
    --->> after?
    --->> --->> WINS on
    --->> --->> --->existing old server is configured as a replication partner
    with
    --->> WINS
    --->> --->> server
    --->> --->> --->in our headquarters.
    --->> --->> --->Another question is after I install AD/DNS/DHCP/WINS is it
    OK to
    --->> --->> rename
    --->> --->> this
    --->> --->> --->new server after I demote existing server to configure it
    with
    --->> the
    --->> --->> same
    --->> --->> name
    --->> --->> --->and IP of the existing old server? I am thinking about
    demoting
    --->> old
    --->> --->> server
    --->> --->> --->just after I promote the new one, and use the procedure as
    in
    --->> the
    --->> --->> folowing
    --->> --->> --->link to rename the new domain controler.
    --->> --->>
    --->http://www.petri.co.il/windows_2003_...ler_rename.htm
    --->> --->> --->
    --->> --->> --->Will this procedure cause any problems with replication
    between
    --->> sites?
    --->> --->> Would
    --->> --->> --->I have to re-configure site replication? Is there anything
    else
    --->> what I
    --->> --->> need
    --->> --->> --->to bear in mind while doing this work?
    --->> --->> --->
    --->> --->> --->Thanking you in advance,
    --->> --->> --->
    --->> --->> --->Zaur
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in
    --->> message
    --->> --->> --->news:krlItdKvIHA.4088@TK2MSFTNGHUB02.phx.gbl...
    --->> --->> --->> Hi,
    --->> --->> --->>
    --->> --->> --->> Thanks for posting here.
    --->> --->> --->>
    --->> --->> --->> Please understand we could only restore a system state
    backup
    --->> from
    --->> --->> one
    --->> --->> --->> physical computer to the same physical computer or another
    --->> computer
    --->> --->> that
    --->> --->> --->> has the same make, model, and configuration (identical
    --->> hardware).
    --->> --->> However,
    --->> --->> --->> please note: You may meet some unexpected issues if you
    --->> restore
    --->> a
    --->> --->> system
    --->> --->> --->> state backup from one computer to another with different
    --->> hardware.
    --->> --->> --->> Microsoft does not support restoring a system state
    backup
    --->> from
    --->> one
    --->> --->> --->> computer to a second computer of a different make, model,
    or
    --->> --->> hardware
    --->> --->> --->> configuration. Microsoft will only provide commercially
    --->> reasonable
    --->> --->> efforts
    --->> --->> --->> to support this process. Even if the source and
    destination
    --->> --->> computers
    --->> --->> --->> appear to be identical makes and models, there may be
    driver,
    --->> --->> hardware, or
    --->> --->> --->> firmware differences between the source and destination
    --->> computers.
    --->> --->> --->>
    --->> --->> --->> More information, please refer to:
    --->> --->> --->>
    --->> --->> --->> How to move a Windows installation to different hardware
    --->> --->> --->>
    http://support.microsoft.com/default...b;EN-US;249694
    --->> --->> --->>
    --->> --->> --->> Therefore, I recommend you migrate the configuration and
    data
    --->> --->> manually.
    --->> --->> --->> For
    --->> --->> --->> the Domain migration, because there is other DC existing
    in
    --->> your
    --->> --->> network,
    --->> --->> --->> you can promote an additional DC to synchronize Domain
    data.
    --->> --->> --->>
    --->> --->> --->> About how to promote an additional DC, please refer to:
    --->> --->> --->>
    --->> --->> --->> How to promote and demote domain controllers
    --->> --->> --->> http://support.microsoft.com/kb/238369
    --->> --->> --->>
    --->> --->> --->> Hope this helps. Have a good day!
    --->> --->> --->>
    --->> --->> --->> Sincerely
    --->> --->> --->> Morgan Che
    --->> --->> --->> Microsoft Online Support
    --->> --->> --->> Microsoft Global Technical Support Center
    --->> --->> --->>
    --->> --->> --->> 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: "Zaur Bahramov" <zbakhramov@msn.com>
    --->> --->> --->> --->Subject: Migrating Windows 2003 server from old
    hardware
    --->> to
    --->> new
    --->> --->> --->> hardware
    --->> --->> --->> --->Date: Thu, 22 May 2008 18:32:52 +0200
    --->> --->> --->> --->Lines: 10
    --->> --->> --->> --->X-Priority: 3
    --->> --->> --->> --->X-MSMail-Priority: Normal
    --->> --->> --->> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
    --->> --->> --->> --->X-MimeOLE: Produced By Microsoft MimeOLE
    V6.00.2900.3198
    --->> --->> --->> --->X-RFC2646: Format=Flowed; Original
    --->> --->> --->> --->Message-ID: <O2S$8lCvIHA.524@TK2MSFTNGP05.phx.gbl>
    --->> --->> --->> --->Newsgroups: microsoft.public.windows.server.migration
    --->> --->> --->> --->NNTP-Posting-Host:
    --->> --->> --->> host67-143-static.57-217-b.business.telecomitalia.it
    --->> --->> --->> 217.57.143.67
    --->> --->> --->> --->Path:
    --->> --->> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
    --->> --->> --->> --->Xref: TK2MSFTNGHUB02.phx.gbl
    --->> --->> --->> microsoft.public.windows.server.migration:3660
    --->> --->> --->> --->X-Tomcat-NG: microsoft.public.windows.server.migration
    --->> --->> --->> --->
    --->> --->> --->> --->I have a task to migrate windows 2003 server
    --->> (AD/WINS/DHCP/DNS)
    --->> --->> which
    --->> --->> --->> has no
    --->> --->> --->> --->FSMO roles from old hardware to a new hardware. This
    is
    --->> not
    --->> the
    --->> --->> only
    --->> --->> --->> server
    --->> --->> --->> --->on a domain and is located in a remote office. I have
    to
    --->> --->> preserve
    --->> --->> all
    --->> --->> --->> --->settings and software install. How can I accomplish
    this
    --->> with
    --->> --->> the
    --->> --->> --->> least
    --->> --->> --->> --->amount of effort? What would I have to do to make
    sure I
    --->> have
    --->> --->> --->> everything
    --->> --->> --->> --->functioning after I do imaging (or ghosting) from this
    --->> server to
    --->> --->> a
    --->> --->> --->> newer
    --->> --->> --->> --->hardware?
    --->> --->> --->> --->
    --->> --->> --->> --->
    --->> --->> --->> --->
    --->> --->> --->> --->
    --->> --->> --->>
    --->> --->> --->
    --->> --->> --->
    --->> --->> --->
    --->> --->>
    --->> --->
    --->> --->
    --->> --->
    --->>
    --->
    --->
    --->


Similar Threads

  1. Migrating to Windows Server 2008 from 2003 Domain
    By Jake360 in forum Windows Server Help
    Replies: 1
    Last Post: 07-12-2011, 05:07 PM
  2. Replies: 4
    Last Post: 27-12-2010, 09:41 PM
  3. Replies: 5
    Last Post: 26-08-2010, 05:15 PM
  4. Replies: 2
    Last Post: 18-03-2009, 12:40 PM
  5. Replies: 4
    Last Post: 29-04-2008, 07:51 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •