windows 2000

[hamedit]

سلام
داخل 1 ارگانی از ویندوز سرور 2000 استفاده میکنن
حدود 700 تا کلاینت هم دارند.
میخوان ویندوز سرور 2000 رو به 2003 ارتقا بدن
به هیچ وجه هم نمیتونن 2000 رو پاک کنن یا از کار بندازنش
راه حل شما چیه

---

موضوعات مشابه:

• How to extend a data volume in Windows Server 2000, 2003, 2008 and Windows XP
• Migrating DHCP from Windows 2000 Server/Windows Server 2003 to Windows Server 2008
• Windows 2000 Server, Windows 2000 Client and Windows XP SP2 Support Ends July 2010
• راه های نفوذ به windows 2000
• مصرف بالای ram در windows 2000

---

[!!!!!!!!!!!!!!!]

چرا نمیشه از کار انداختش !؟ چرا نمیشه اطلاعات و وظایف 2000 رو منتقل کرد !؟ یکم توضیح نیاز هست ! یعنی در حد upgrade هم نمیشه خاموش کردش !؟

[hamedit]

ارگانی که گفتم خدمتتون بانک هست
و تمامی شعب به اون متصل میشن برا اتانتیکیشن کردن
یعنی اگه از کارش بندازیم مساوی میشه بااینکه که کل شعب از کار میفتن تو سراسر کشور

[patris1]

http://www.petri.co.il/active_directory_migration_tool_usage_w2k_windows_2003.htm

How to use Active Directory Migration Tool v2.0 to migrate from Windows 2000 to Windows Server 2003

This article describes how to set up the Active Directory Migration Tool (ADMT) to migrate from a Windows 2000-based domain to a Windows Server 2003-based domain

Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You can use ADMT to migrate users, groups, and computers from one domain to another, and analyze the migration affect before and after the actual migration process.
Note: This article assumes that the source domain is a Windows 2000-based domain, and that the target domain is a Windows Server 2003-based domain in Windows 2000 Native mode or later.
How to Set Up ADMT for a Windows 2000 to Windows Server 2003 Migration

You can install the Active Directory Migration Tool version 2 (ADMTv2) on any computer that is running Windows 2000 or later, including:

• Microsoft Windows 2000 Professional
• Microsoft Windows 2000 Server
• Microsoft Windows XP Professional
• Microsoft Windows Server 2003

The computer on which you install ADMTv2 must be a member of either the source or the target domain.
Intraforest Migration

Intraforest migration does not require any special domain configuration. The account you use to run ADMT must have enough permissions to perform the actions that are requested by ADMT. For example, the account must have the right to delete accounts in the source domain, and to create accounts in the target domain.
Intraforest migration is a move operation instead of a copy operation. These migrations are said to be destructive because after the move, the migrated objects no longer exist in the source domain. Because the object is moved instead of copied, some actions that are optional in interforest migrations occur automatically. Specifically, the sIDHistory and password are automatically migrated during all intraforest migrations.
Interforest Migration

ADMT requires the following permissions to run properly:

• Administrator rights in the source domain.
• Administrator rights on each computer that you migrate.
• Administrator rights on each computer on which you translate security.

Before you migrate a Windows 2000-based domain to a Windows Server 2003-based domain, you must make some domain and security configurations. Computer migration and security translation do not require any special domain configuration. However, each computer you want to migrate must have the administrative shares, C$ and ADMIN$.
The account you use to run ADMT must have enough permissions to complete the required tasks. The account must have permission to create computer accounts in the target domain and organizational unit, and must be a member of the local Administrators group on each computer to be migrated.
User and Group Migration

You must configure the source domain to trust the target domain. Optionally, the target may be configured to trust the source domain. While this may ease configuration, it is not required to finish the ADMT migration.
Requirements for Optional Migration Tasks

You can complete the following tasks automatically by running the User Migration Wizard in Test mode and selecting the migrate sIDHistory option. The user account you use to run ADMT must be an Administrator in both the source and the target domains for the automatic configuration to succeed.

1. Create a new local group in the source domain that is named %sourcedomain%$$$. There must be no members in this group.
2. Turn on auditing for the success and failure of Audit account management on both domains in the Default Domain Controllers policy.
3. Configure the source domain to allow RPC access to the SAM by configuring the following registry entry on the PDC Emulator in the source domain with a DWORD value of 1:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Control\LSA\TcpipClientSupport


You must restart the PDC Emulator after you make this change.
Note: For Windows 2000 domains, the account you use to run ADMTv2 must have domain administrator permissions in both the source and target domains. For Windows Server 2003 target domains, the 'Migrate sIDHistory' may be delegated. For more information, see Windows Server 2003 Help & Support.
You can turn on interforest password migration by installing a DLL that runs in the context of LSA. By running in this protected context, passwords are shielded from being viewed in cleartext, even by the operating system. The installation of the DLL is protected by a secret key that is created by ADMTv2, and must be installed by an administrator.
To install the password migration DLL:

1. Log on as an administrator or equivalent to the computer on which ADMTv2 is installed.
2. At a command prompt, run the ADMT KEY sourcedomainpath [* | password] command to create the password export key file (.pes). In this example, sourcedomain is the NetBIOS name of the source domain and path is the file path where the key will be created. The path must be local, but can point to removable media such as a floppy disk drive, ZIP drive, or writable CD media. If you type the optional password at the end of the command, ADMT protects the .pes file with the password. If you type the asterisk (*), ADMT prompts for a password, and the system will not echo it as it is typed.
3. Move the .pes file you created in step 2 to the designated Password Export Server in the source domain. This can be any domain controller, but make sure it has a fast, reliable link to the computer that is running ADMT.
4. Install the Password Migration DLL on the Password Export Server by running the Pwmig.exe tool. Pwmig.exe is located in the I386\ADMT folder on the Windows Server 2003 installation media, or the folder to which you downloaded ADMTv2 from the Internet.
5. When you are prompted to do so, specify the path to the .pes file that you created in step 2. This must be a local file path.
6. After the installation completes, you must restart the server.
7. If you are ready to migrate passwords, modify the following registry key to have a DWORD value of 1. For maximum security, do not complete this step until you are ready to migrate.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Control\LSA\AllowPasswordExport
The Active Directory Migration Tool v2 is included in the I386\Admt folder on the Windows Server 2003 CD.
Download Active Directory Migration Tool v2.0 (4.7mb)
For more information about how to use ADMT to perform a migration, see ADMT Help. Start the Active Directory Migration Tool, click Help Topics on the Help menu, click the Contents tab, and then click Active Directory Migration Tool.

[mahyar49]

من فکر نمی کردم سیستم شبکه بانکداری انقدر ضعیف باشه...
خارج از تایم اداری این کار رو انجام بدید
مثلا ساعت 2 نصفه شب

[patris1]

من فکر نمی کردم سیستم شبکه بانکداری انقدر ضعیف باشه...
خارج از تایم اداری این کار رو انجام بدید
مثلا ساعت 2 نصفه شب

میشه لطف کنید بفرماید، به فرض ایشان ساعت ۲ شب این کار را انجام دهند و تا ساعت ۶ بفرض طول بکشد ، بنا به دلایلی سیستم درست آپگرد نشود ، حالا چه کار باید انجام داد !!! نه از ویندوز ۲۰۰۰ اثری است و نه ویندوز ۲۰۰۳ کار میکند ؟؟الان میگید Backup استفاده کنه. باشه حالا اگر هجم اطلاعات زیاد بود چقدر طول میکشه تا Restore کند؟
باید بگه کل شعب تعطیل کنند بروند خانه؟؟
تلاش کنیم برای کمک دست افراد را بگیریم و بلندشان کنیم نه پایشان را .
با سپاس و تشکر

[mahyar49]

میشه لطف کنید بفرماید، به فرض ایشان ساعت ۲ شب این کار را انجام دهند و تا ساعت ۶ بفرض طول بکشد ، بنا به دلایلی سیستم درست آپگرد نشود ، حالا چه کار باید انجام داد !!! نه از ویندوز ۲۰۰۰ اثری است و نه ویندوز ۲۰۰۳ کار میکند ؟؟الان میگید Backup استفاده کنه. باشه حالا اگر هجم اطلاعات زیاد بود چقدر طول میکشه تا Restore کند؟
باید بگه کل شعب تعطیل کنند بروند خانه؟؟
تلاش کنیم برای کمک دست افراد را بگیریم و بلندشان کنیم نه پایشان را .
با سپاس و تشکر

قبول دارم حرفتون رو
من فرض بر این گرفتم که دوستانی که اینکار را انجام میدهند بسیار با تجربه و متخصص هستند و در اینگونه شرایط و شرایط سختتر قرار گرفته اند.
شبکه ی بانک کار من و امثال من که تجربه و دانش کافی را نداریم نیست.

شما با تجربه ی که دارید در این شرایط چه پیشنهادی می کنید؟
به نظر شما شب جمعه اینکار رو شروع کنند مناسب نیست؟

از دوستمون بابت راهنمایی غلط عذر خواهی می کنم.

[patris1]

http://support.microsoft.com/?scid=kb%3Ben-us%3B326480&x=18&y=13

How to use Active Directory Migration Tool version 2 to migrate from Windows 2000 to Windows Server 2003


This article describes how to set up the Active Directory Migration Tool (ADMT) to migrate from a Microsoft Windows 2000-based domain to a Microsoft Windows Server 2003-based domain. Back to the top

MORE INFORMATIONYou can use ADMT to migrate users, groups, and computers from one domain to ano...


You can use ADMT to migrate users, groups, and computers from one domain to another, and analyze the migration affect before and after the actual migration process.

Note This article assumes that the source domain is a Windows 2000-based domain, and that the target domain is a Windows Server 2003-based domain in Windows 2000 Native mode or later. Back to the top
How to set up ADMT for a Windows 2000 to Windows Server 2003 migration

You can install the Active Directory Migration Tool version 2 on any computer that is running Windows 2000 or later, including:

• Microsoft Windows 2000 Professional
• Microsoft Windows 2000 Server
• Microsoft Windows XP Professional
• Microsoft Windows Server 2003

The computer on which you install ADMT must be a member of either the source or the target domain. Intraforest migration

Intraforest migration does not require any special domain configuration. The account you use to run ADMT must have enough permissions to perform the actions that are requested by ADMT. For example, the account must have the right to delete accounts in the source domain, and to create accounts in the target domain.

Intraforest migration is a move operation instead of a copy operation. These migrations are said to be destructive because after the move, the migrated objects no longer exist in the source domain. Because the object is moved instead of copied, some actions that are optional in interforest migrations occur automatically. Specifically, the sIDHistory and password are automatically migrated during all intraforest migrations. Interforest migration

ADMT requires the following permissions to run properly:

• Administrator rights in the source domain.
• Administrator rights on each computer that you migrate.
• Administrator rights on each computer on which you translate security.

Before you migrate a Windows 2000-based domain to a Windows Server 2003-based domain, you must make some domain and security configurations. Computer migration and security translation do not require any special domain configuration. However, each computer you want to migrate must have the administrative shares, C$ and ADMIN$.

The account you use to run ADMT must have enough permissions to complete the required tasks. The account must have permission to create computer accounts in the target domain and organizational unit, and must be a member of the local Administrators group on each computer to be migrated. User and group migration

You must configure the source domain to trust the target domain. Optionally, the target may be configured to trust the source domain. While this may ease configuration, it is not required to finish the ADMT migration. Requirements for optional migration tasks

You can complete the following tasks automatically by running the User Migration Wizard in Test mode and selecting the migrate sIDHistory option. The user account you use to run ADMT must be an Administrator in both the source and the target domains for the automatic configuration to succeed.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (How to back up and restore the registry in Windows XP ) How to back up and restore the registry in Windows

1. Create a new local group in the source domain that is named %sourcedomain%$$$. There must be no members in this group.
2. Turn on auditing for the success and failure of Audit account management on both domains in the Default Domain Controllers policy.
3. Configure the source domain to allow RPC access to the SAM by configuring the following registry entry on the PDC Emulator in the source domain with a DWORD value of 1: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\LSA\TcpipClientSupport
   You must restart the PDC Emulator after you make this change.

Note For Windows 2000 domains, the account you use to run ADMT must have domain administrator permissions in both the source and target domains. For Windows Server 2003 target domains, the 'Migrate sIDHistory' may be delegated. For more information, see Windows Server 2003 Help & Support.

You can turn on interforest password migration by installing a DLL that runs in the context of LSA. By running in this protected context, passwords are shielded from being viewed in cleartext, even by the operating system. The installation of the DLL is protected by a secret key that is created by ADMT, and must be installed by an administrator.

To install the password migration DLL:

1. Log on as an administrator or equivalent to the computer on which ADMT is installed.
2. At a command prompt, run the ADMT KEY sourcedomainpath [* | password] command to create the password export key file (.pes). In this example, sourcedomain is the NetBIOS name of the source domain and path is the file path where the key will be created. The path must be local, but can point to removable media such as a floppy disk drive, ZIP drive, or writable CD media. If you type the optional password at the end of the command, ADMT protects the .pes file with the password. If you type the asterisk (*), ADMT prompts for a password, and the system will not echo it as it is typed.
3. Move the .pes file you created in step 2 to the designated Password Export Server in the source domain. This can be any domain controller, but make sure it has a fast, reliable link to the computer that is running ADMT.
4. Install the Password Migration DLL on the Password Export Server by running the Pwmig.exe tool. Pwmig.exe is located in the I386\ADMT folder on the Windows Server 2003 installation media, or the folder to which you downloaded ADMT from the Internet.
5. When you are prompted to do so, specify the path to the .pes file that you created in step 2. This must be a local file path.
6. After the installation completes, you must restart the server.
7. If you are ready to migrate passwords, modify the following registry key to have a DWORD value of 1. For maximum security, do not complete this step until you are ready to migrate.HKEY_LOCAL_MACHINE\System\CurrentControlSe t\Control\LSA\AllowPasswordExport

To download ADMT, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?familyid=788975B1-5849-4707-9817-8C9773C25C6C&displaylang=en (http://www.microsoft.com/downloads/d...displaylang=en)
For more information about how to use ADMT to perform a migration, see ADMT Help. Start the Active Directory Migration Tool, click Help Topics on the Help menu, click the Contents tab, and then click Active Directory Migration Tool.

For more information about ADMT, visit the following Microsoft Web site: http://www.microsoft.com/downloads/d...displaylang=en (http://www.microsoft.com/downloads/d...displaylang=en)
The Active Directory Migration Tool version 2 is included in the I386\Admt folder on the Windows Server 2003 CD. Back to the top

APPLIES TO

• Microsoft Windows Server 2003, Standard Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
• Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Advanced Server

---------------------------------------------------------------------------------------------------------------------------------------------------
Support WebCast: Domain Migration Using the Microsoft Active Directory Migration Tool

http://support.microsoft.com/?scid=kb%3Ben-us%3B325393&x=15&y=13

-----------------------------------------------------------------------------------------------------------------------------------------------
Active Directory Domain Services and DNS Server Migration Guide

http://technet.microsoft.com/en-us/library/dd379558%28WS.10%29.aspx

-----------------------------------------------------------------------------------------------------------------------------------------------
Migrating stuff with ADMTv3

http://blogs.dirteam.com/blogs/jorge/archive/2006/12/27/Migrating-stuff-with-ADMTv3.aspx

تا آنجایی هم که این حقیر دیده ، کسانی که بقول شما تجربه دارند و در اینگونه شرایط و شرایط سختتر قرار گرفته اند، فکر همه جوانب را میکنند ، برای همین از Migration استفاده میکنند که اگر اتفاق عجیب و غریبی افتاد ، سرور اصلی دست نخورده هست و فوری میتوان وارد شبکه کرد.

[!!!!!!!!!!!!!!!]

آقای سام ، مگه این دوستمون AD روی 2000 داره !؟ شعب از چه بانک ای دارن authenticate میشن !؟ اگه AD داره که مشکلی نیست !
یه win2k3 راه بندازید و BDC کنیدش و بعد هم کل 2000 رو move کنید روی 2k3 ! اما اگر نیست که شما صبر کنید جواب بده این بنده خدا بعد admt رو بیشنهاد کنید! یه وقت نسخه اشتباهی نپیچیم که به مشکل بر بخورن

[patris1]

بله این راه هم میشود

http://www.windowsreference.com/windows-2000/step-by-step-guide-for-migrating-windows-2000-server-to-windows-2003-server-part1/

Step By Step Guide for Migrating Windows 2000 server to Windows 2003 Server Part1

Scenario

A Windows 2000 server domain controller running on old hardware has to be replaced with a new hardware running Windows 2003 Server as the Domain Controller. This tutorial will explain how to migrate win server 2000 to win server 2003 includes Domain Controller, DNS, DHCP, File server, Rename new win server 2003 same as your old win server 2000.

In this tutorial we are assuming that you are using same domain name as on your new win server 2003

Make sure to have the latest backup of the existing server

1.Make Sure SP4 on the existing Windows 2000 domain controller

2. Run ADPREP to prepare the forest and domain for windows 2003

• Put the Windows 2003 Server installation CD, into the CD drive of the windows 2000 server.

• Go to Start -> Run and type cmd and click on OK button.

• At the command prompt type x:\i386\adprep /forestprep where x is the drive letter of the CD drive. Make sure the command exits with a success message. Reboot is not necessary.

• From the command prompt type x:\i386\adprep /domainprep where x is the drive letter of the CD drive on the server. Make sure the command exits with a success message. Reboot is not necessary.

Note: In case of any errors, you may look at the log files residing under %systemroot%\system32\debug\adprep\log\ folder.


Important Note :- If you want to upgrade win server 2000 to win server 2003 R2 insert the Windows Server 2003 R2 installation disk 2 to run the forestprep and domainprep otherwise you see the following error

The Active Directory Installation Wizard cannot continue because the forest is not prepared for installing Windows Server 2003. Use the Adprep command-line tool to prepare both the forest and the domain. For more information about using the Adprep, see Active Directory Help.


The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer.

3. On the new server hardware, install Windows 2003 Server and join it to the existing domain (i.e win 2000 domain). Also, install the DNS server (need not configure). Make sure you also install all the available service packs.


Install DNS Server on win 2003 Server


Open Windows Components Wizard from the following


Click Start, click Control Panel, and then click Add or Remove Programs.


Click Add/Remove Windows Components.


In Components, select the Networking Services check box, and then click Details.


InSubcomponents of Networking Services, select the Domain Name System (DNS) check box, click OK, and then click Next.


If Windows asks for a CD-ROM, do as it requests. When it is done, click Finish and you’ll have your very own DNS server.

4. On win 2003 server Run DC Promo and make this server as the additional domain controller to the existing domain:

• Go to Start -> Run and type dcpromo and click on OK button.

• On the Active Directory Installation Wizard screen, follow the wizard and make this server as an additional domain controller for the existing domain.

• Reboot the Server.

5. Wait for replication to happen. This may take around 30 minutes or longer, depending on the amount of data that has to be replicated from the SYSVOL folder of Win2000 server. You can use REPLMON.EXE, to monitor the replication status, which is available from the support tools package in your win 2003 server CD, or you can even check the event log on the Win server 2003 for the file replication service (FRS) status.

6. Check the DNS on the new Win server 2003.

• Check if all the details have been replicated

• Check if the forwarders are setup correctly

• Check if the event log is clear of errors

http://www.windowsreference.com/windows-2000/step-by-step-guide-for-migrating-windows-2000-server-to-windows-2003-server-part2/

Transfer FSMO (Flexible Single Master Operations) Roles from Windows server 2000 to Windows Server 2003 Part2

If you miss the part1 of this tutorial check here .In part2 we will see how to transfer FSMO (Flexible Single Master Operations) Roles from Windows server 2000 to Windows Server 2003

6. Transfer FSMO roles and GC from win server 2000 to win server 2003


a) Transfer the FSMO Roles to the new server.


(For more information, check this MS article )


There are 5 FSMO roles: Domain naming Master, Schema Master, RID Master, PDC Emulator and Infrastructure Master. There must be a domain controller that owns each one of those roles. These roles can be transferred to another Domain Controller either by using the MMC GUI tool or by using the ntdsutil.exe command line utility. Here are the steps to transfer FSMO roles by using the MMC tool:


Transferring RID, PDC, and Infrastructure Master roles:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
• Right-click the icon next to Active Directory Users and Computers, and then click Connect to Domain Controller.

Note: If you are not on the domain controller where you want to transfer the role, you need to take this step. It is not necessary if you are connected to the domain controller whose role you want to transfer.

• Click the domain controller, which will be the new role holder, and then click OK.

• Right-click Active Directory Users and Computers icon and then click Operation Masters.

• In the Change Operations Master dialog box, click the appropriate tab (RID, PDC, or Infrastructure) for the role you want to transfer. You need to transfer all the 3 roles.

• Click Change in the Change Operations Master dialog box.

• Click OK to confirm that you want to transfer the role.

• Click OK.

• Click Cancel to close the dialog box.

Transferring the Domain Naming Master role:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Domains and Trusts.

• Right-click the Active Directory Domains and Trusts icon, and then click Connect to Domain Controller.

Note: If you are not on the domain controller where you want to transfer the role, you need to take this step. It is not necessary if you are connected to the domain controller whose role you want to transfer.

• Click the domain controller that will be the new role holder, and then click OK.

• Right-click Active Directory Domains and Trusts, and then click Operation Masters.

• In the Change Operations Master dialog box: click Change.

• Click OK to confirm that you want to transfer the role.

• Click OK.

• Click Cancel to close the dialog box.

Transferring the Schema Master Role:


You can use the Schema Master tool to transfer the role. However, the Schmmgmt.dll dynamic-link library must be registered in order to make the Schema tool available as an MMC snap-in.


Registering the Schema Tool:

• Click Start, and then click Run.

• Type regsvr32 schmmgmt.dll, and then click OK. A message should be displayed stating that the registration was successful.

Transferring the Schema Master Role:

• Click Start, click run, type mmc, and then click OK.

• On the Console menu click Add/Remove Snap-in.

• Click Add.

• Click Active Directory Schema.

• Click Add.

• Click Close to close the Add Standalone Snap-in dialog box.

• Click OK to add the snap-in to the console.

• Right-click the Active Directory Schema icon, and then click Change Domain Controller.

Note: If you are not on the domain controller where you want to transfer the role, you need to take this step. It is not necessary if you are connected to the domain controller whose role you want to transfer.

• Click Specify Domain Controller, type the name of the domain controller that will be the new role holder, and then click OK.

• Right-click Active Directory Schema and then click Operation Masters.

• In the Change Schema Master dialog box: click Change.

• Click OK.

• Click OK.

• Click Cancel to close the dialog box.

Transfer the Global Catalogue role:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services.

• Under sites, expand your site name, then Servers and then your server name so that you can see NTDS Settings. Now right click on the NTDS Settings under the server that you want to demote (Win2K) and choose properties, in the window that appears, un-check Global Catalog and click OK.

• Now right click on the NTDS Settings under the server that you want to promote (Win2K3) and choose properties, in the window that appears, check Global Catalog and click OK.

• After making these changes wait about fifteen minutes till the Global Catalog replicates between domain controllers, after it you can continue with further configurations.

http://www.windowsreference.com/windows-2000/file-serverdhcp-server-migration-from-win-2000-to-win-2003-server-run-domain-controller-diagnosticspart3/

File Server,DHCP Server migration from win 2000 to win 2003 server, run domain controller diagnostics Part3

If you missed Part 1 and Part2 for Windows server 2000 to windows server 2003 follow these

For Part1


For Part2

In Part3 we will see how to Migrate file server,DHCP Server Migration,Domain controller diagnostics from windows server 2000 to windows server 2003

6. Transfer files/permissions over win server 2003


If you are using this server as file server you need to copy all your data in to the new win server 2003 with the following procedure


For this purpose you can use FSMT tool on Win2K3 server (FSMT cannot be run on Win2K), which can be downloaded from the Microsoft Website. Using FSMT all the shared files and folders can be transferred from the old Win2K server to the new Win2K3 server without losing the permissions on the shared folders.


If you want complete detailed Instructions how to use FSMT Check here

7. Take backup of win 2000 DHCP Server database.

• Run DHCPEXIM.EXE utility from MS Resource Kit (download from here)and export the required DHCP Scope(s) and configurations to a text file and copy this file on to the new win server 2003.

• Now, you can either disconnect the network cable or shutdown the win server 2000 completely. This server will again be used in the event of this migration failure.

8 . Authorize DHCP Server on win server 2003

• Click Start, point to All Programs, point to Administrative Tools, and then click DHCP

Note:- You must be logged on to the server by using an account that is a member of the Administrators group. In an Active Directory domain, you must be logged on to the server by using an account that is a member of the Enterprise Administrators group.

• In the console tree of the DHCP snap-in, expand the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized.

• Right-click the server object, and then click Authorize.

After several moments, right-click the server again, and then click Refresh. A green arrow indicates that the DHCP server is authorized.

9. Running domain controller (on win server 2003) diagnostics tools


From the command prompt, run DCDIAGS and make sure the command is completed successfully, without displaying any errors.If you want DCdiag GUI tool check here


Run adcheck (freeware tool from netiq) run through all the checks and make sure that the domain is healthy. Fix errors if any.You can download from here

http://www.windowsreference.com/windows-2000/disconnect-the-old-server-win-server-2000raise-the-domain-level-functionality-to-native-windows-2003rename-your-new-windows-server-2003part4/

Disconnect the old server (win server 2000),Raise the domain level functionality to native Windows 2003,Rename your new windows server 2003 Part4

If you miss Part1,Part2,Part3of migration tutorial check from the following places

Part1


Part2


Part3

In final part we will see how to remove your old server (win server 2000) from network,Raise the domain level functionality to native Windows 2003,Rename your new windows server 2003 same as your old server.


12 Disconnect the old server (win server 2000)

• Go to Start -> Run and type dcpromo and click on OK button.

• On the Active Directory Installation Wizard screen, follow the wizard and demote it from the domain controller to a standalone server.

• Reboot the Server.

• Change the server membership to a Workgroup.

• Reboot the Server.

• Shutdown and disconnect the server from the network.

13. Raise the domain level functionality to native Windows 2003 in win server 2003.


For this follow this procedure

• Log on the win server 2003 of the domain with domain administrator credentials.

• Click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.

• In the console tree, right-click the domain for which you want to raise functionality, and then click Raise Domain Functional Level.

• Under Select an available domain functional level, do the following

• Click Windows Server 2003, and then click Raise to raise the domain functional level to Windows Server 2003.

Note:- You can also raise the domain functional level by right-clicking a domain that appears in the Active Directory Users and Computers MMC snap-in, and then clicking Raise Domain Functional Level. To raise the domain functional level, you must be a member of the Domain Administrators group.

The current domain functional level appears under Current domain functional level in the Raise Domain Functional Level dialog box. The level increase is performed on the PDC FSMO and requires the domain administrator

14. Test with a client that you can logon, check the event log for any errors.

15. Changing the new DC’s (Win2K3) IP Address and Hostname to the same Hostname and IP Address as the old DC (Win2K)

• Make sure the Old Domain Controller (Win2K) is disconnected from the network.

• Make sure all the references of the old (Win2K) server name does not exist anymore In Active directory (Sites, Domain Controllers Container and DNS).

• Make sure the domain functional level is raised to Windows 2003 native mode.

• Change the IP Address of the new domain controller (Win2K3)

• Change the Domain Controller hostname using Netdom tool.

Netdom tool comes with the support tools package, which is available on the Server installation CD, under \support\tools folder.

• Install support tools and go to Command Prompt.

• Type the following command to add the new domain controller name, and then press ENTER:

netdom computername CurrentComputerName /add:NewComputerName


Note: The NewComputerName must be a fully qualified domain name (FQDN). Currentcomputername can be the existing FQDN or the IP Address of the computer.


c) Type the following command to designate the new name as the primary computer name, and then press ENTER:


netdom computername CurrentComputerName /makeprimary:NewComputerName


d) Restart the computer.


e) After the computer restarts, go to Command Prompt.


f) Type the following command to remove the old domain controller name, and then press ENTER:

netdom computername NewComputerName /remove:OldComputerName


Finally if you are using any logon scripts using kix program,Network Printers you need to make sure everything is working fine

[hamid khan]

با سلام
در این مورد اول باید ببینی روی سرور خودت چه سرویسهایی ارائه میشود تا ابتدا این نقشها را با یک سرور دیگر منتقل کنی (بوسیله ابزار های مربوطه خودشان)
دوم بصورت آزمابشی و کوتاه سرور را از مدار خارج کنی
اگر همه چیز بر وفق مراد بود دست بکار ارتقاء سرور شوی

در مورد Migration هم کاملاً اصولی و برنامه ریزی شده است بنده هم کاملاً موافق هستم ولی توصیه بنده اینه که از دیتابیس هر سرویسی بک آپ جدا تهیه کنی تا DownTime شما از حد معمول بیشتر نشود
در ضمن سرور یدکی فراموش نشود که آماده دم دستت باشد .

[hamedit]

از تمامی دوستان عزیز بسیار مچکرم
خیلی زحمت کشیدید

من به شخصه با 2000 کار نکردم و نمیدونم قابلیت هاش چیه(یکی از ضعف های خودم)
یه راه حل میدم نظرتون رو بهم بگید ببینید میشه یا نه؟

ما برای سرور 2000 یه aditional روی 2003 درست کنیم.بعدش یواش یواش تمام قابلیت های ADرو منتقل میکنیم به 2003.
نظرتون چیه؟

[patris1]

شما آن بالا را خواندید که به چند روش امکان دارد یا خیر؟؟
به هر حال شما مجبور هستید سرور را حداقل ۱۵ دقیقه Down کنید (اگر همه چیز با روال نرمال پیش برود)

[hamedit]

شما آن بالا را خواندید که به چند روش امکان دارد یا خیر؟؟

راستشو بخواید نه نخوندم،یعنی وقت نشد بخونم

جسارتا اگر به شما بزرگوار توهین نمیشه با زبون فارسی باهم صحبت کنیم بهتره
درسته سایت تخصصیه ولی همه که مثل شما بزرگواران متخصص نیستن
اگه کسی بعد از چندوقت اومد یه چیزی یادبگیره قشنگ با توضیحاتی که شما دوستان ارائه میکنید یاد بگیرن

[patris1]

دیگه فکر نکنم از Step-by-Step راحت تر و ساده تر وجود داشته باشد . فکر کنم کسی ادمین همچین شبکه ای است و میخواهد یک همچین کاری را انجام دهد ، نباید با زبان انگلیسی مشکل داشته باشد. شما اینطور فکر نمیکنی؟؟!!