Re: upgrade windows 2000 server to sbs2k3
From: Pedro Ferreira aka Dundee (prilhao_at_hotmail.com)
Date: 01/18/05
- Next message: daniel: "Re: Running OWA & RWW between two domains"
- Previous message: Bill Peng [MSFT]: "RE: Sharepoint www Site Admin Hangs"
- In reply to: Mark Jesiel: "RE: upgrade windows 2000 server to sbs2k3"
- Next in thread: Pedro Ferreira aka Dundee: "Re: upgrade windows 2000 server to sbs2k3"
- Reply: Pedro Ferreira aka Dundee: "Re: upgrade windows 2000 server to sbs2k3"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 Jan 2005 09:55:46 +0000
Mark Jesiel wrote:
> First off, how many DC's do you have anyway? The easiest way to upgrade a
> Windows 2000 domain to SBS2003 is upgrade an existing win2k DC.
>
> Read the articlle below, it works, done it.
>
> INTRODUCTION
>
> ============
>
>
>
> This article describes how to install a Microsoft Windows Small Business
> Server (SBS) 2003-based computer in an existing domain.
>
>
>
>
>
>
>
> Warning
>
> You should use the steps that are described in this article as an outline
> for how to install a new SBS 2003 computer in an existing domain to maintain
> the existing Active Directory directory service infrastructure. You should
> not use this article to add an SBS 2003 computer to a network where there is
> an existing SBS 2000 or SBS 2003 domain controller for migration purposes.
> For that, use the migration white papers. To view the migration white papers,
> visit the following Web site:
>
>
>
>
>
>
>
>
> http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx
>
>
>
> This article does not intend to provide a migration solution. However, if
> you use the steps in this article to join an existing domain that already
> contains an SBS 2003 computer or an SBS 2000 computer, you will have to
> demote the existing SBS server by manually running Dcpromo.exe to remove the
> computer from the domain. This retirement process must occur within 14 days
> of adding the new SBS 2003 computer to the domain or the new SBS 2003
> computer may display warnings and shut down periodically.
>
>
>
> The following conditions must be true after you install the new SBS 2003
> computer in an existing domain or the new SBS 2003 computer may display
> warnings and shut down periodically:
>
>
>
> - The new SBS 2003 computer must be a domain controller that is
>
> installed on the root of the domain.
>
>
>
> - The new SBS 2003 computer must hold all the Flexible Single Master
>
> Operation (FSMO) roles.
>
>
>
> - The new SBS 2003 computer must be a global catalog server and must be
>
> the licensing server.
>
>
>
> - There must not be any existing domain trusts or child domains.
>
>
>
> - Only one SBS server can exist on the domain. If SBS 2003 is
>
> installed, no other SBS 2003 or 2000 server can be installed on the
>
> same domain.
>
>
>
>
>
> Failure to meet these conditions may cause the SBS 2003 server to shut down.
>
>
>
>
>
>
>
> For additional information, click the following article number to view the
> article in the Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:842690.KB.[LN]: List of components that are included in
> Windows
>
> Small Business Server 2003
>
>
>
> MORE INFORMATION
>
> ================
>
>
>
> To install a SBS 2003 computer in an existing Active Directory domain,
> follow these steps:
>
>
>
> 1. On a Windows 2000 domain, you must prepare Active Directory before you
> install the SBS 2003 computer in the domain.
>
>
>
>
>
> For additional information about how to install a Windows Server 2003 domain
> controller into an existing Windows 2000 forest, click the following article
> number to view the article in the Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:278875.KB.[LN]: Cannot promote a Windows Server 2003
> domain
>
> controller into a Windows 2000 forest
>
>
>
> 2. Start the installation of SBS 2003 by inserting CD 1 into the CD or
>
> DVD drive.
>
>
>
> 3. When the operating system is installed and the computer restarts and
>
> continues with the integrated Setup program, click "Cancel" to stop the
>
> integrated Setup program. Note You must cancel the integrated Setup
>
> program at this point. If you continue with the integrated Setup, you
>
> cannot join the SBS 2003 computer to the existing domain.
>
>
>
> 4. On the SBS 2003 computer, configure a static IP address on the
>
> network card and make sure to configure DNS to include the existing
>
> server that hosts the Active Directory zone. Note You can ping other
>
> computers on the network by using their Fully Qualified Domain Names
>
> (FQDNs) after you complete this procedure.
>
>
>
> 5. Run the Dcpromo.exe program on the SBS 2003 computer to join the
> existing domain.
>
>
>
> Note Do not create a new forest and do not create a child domain.
>
>
>
> a. Click "Start", click "Run", type "dcpromo" (without
> the quotation marks), and then click "OK".
>
>
>
> b. Click "Next" two times.
>
>
>
> c. Click "Additional Domain Controller for an existing
> domain", and then click "Next".
>
>
>
> d. Enter the credentials for the domain administrator
> account, and then click "Next".
>
>
>
>
>
> e. In the "Domain name" area, type the FQDN for the
> Active Directory domain namespace that you want to join, and then click
> "Next". For example, type "contoso.local". If you are not sure of the FQDN,
> you can click "Browse" to select the correct domain.
>
>
>
> f. Click "Next" to accept the default locations for the
> Database and Log folders.
>
>
>
> g. Click "Next" to accept the default locations for the
> shared system volume.
>
>
>
> Note If you have to change the location of the
> shared system volume, you must select an NTFS file system volume.
>
>
>
> h. Type the Directory Services Restore Mode
> administrator password, and then click "Next".
>
>
>
> Note This is the password that you would use in
> Directory Services Restore Mode or when you use Recovery Console.
>
>
>
> i. On the Summary screen, click "Next" to start the
> Dcpromo.exe program. This process may take several minutes.
>
>
>
>
>
> j. Click "Finish" to complete the Dcpromo.exe program,
> and then click "Restart Now".
>
>
>
>
>
> k. Log on to the computer after it restarts and confirm
> that the computer has been successfully promoted to a domain controller. To
> do this, click "Start", click "Run", type "cmd" (without the quotation
> marks), and then click "OK".
>
>
>
> l. At the command prompt, type "gettype" (without the
> quotation marks), and then press ENTER. The output should read as follows:
>
>
>
> Host Name: <ServerName>
>
> Name: Windows Server 2003 for Small Business Server
>
>
>
> Version: 5.2 Build 3790
>
>
>
> Role: Domain Controller
>
>
>
> Components: Not Installed
>
>
>
> 6. Install the DNS server service.
>
> To do this, follow these steps:
>
>
>
> a. Click "Start", point to "Control Panel", and then
> click "Add/Remove Programs".
>
>
>
>
>
> b. Click "Add/Remove Windows Components".
>
>
>
>
>
> c. In the "Windows Components" list, double-click
> "Networking Services".
>
>
>
> d. Click to select the "Domain Name System (DNS)" check
> box, and then click "OK".
>
>
>
> e. Click "Next", and then click "Finish".
>
>
>
>
>
> For additional information about how to configure a
> DNS server, visit the following Microsoft Web site:
>
>
>
>
> http://www.microsoft.com/resources/documentation/windowsserv/2003/standard/proddocs/en-us/dns_server_role.asp
>
>
>
> 7. Promote the SBS 2003 computer to a global catalog server. To do this,
> follow these steps:
>
>
>
> a. Click "Start", point to "Administrative Tools", and
> then click "Active Directory Sites and Services".
>
>
>
> b. Expand "Sites", expand "Default-First-Site-Name",
> expand "Servers", expand your SBS 2003 computer, right-click "NTDS Settings",
> and then click "Properties".
>
>
>
> c. Click the "General" tab, click to select
> the "Global catalog" check box to assign the role of global catalog to this
> computer, and then click "OK".
>
>
>
> d. Restart the computer.
>
>
>
> Note Wait for the account and the schema information
> to replicate to the new global catalog server. Wait for event 1119 or event
> 1869 to be logged in the Directory Services event log with a description that
> states that the computer is now advertising itself as a global catalog server.
>
>
>
>
>
> 8. After the new computer is successfully promoted to a global catalog
> server, remove any other global catalog servers in the domain. To do this,
> follow these steps:
>
>
>
> a. Click "Start", point to "Administrative Tools", and
> then click "Active Directory Sites and Services".
>
>
>
> b. In the console pane, expand "Sites", and then
> expand "Default-First-Site-Name".
>
>
>
> c. Expand "Servers", expand any computers other than
> your SBS 2003 computer, right-click "NTDS Settings", and then click
> "Properties".
>
>
>
> Note You may have to repeat this step more than one
> time if more than one computer is listed, other than the SBS 2003 computer.
>
>
>
> d. On the "General" tab, click to clear the
> "Global catalog" check box to assign the role of global catalog to this
> computer, and then click "OK".
>
>
>
> Note If the "Global catalog" check box is not
> selected, go to step 8.
>
>
>
> e. Restart any computers where you removed the global
> catalog server role.
>
>
>
> Note Wait for the account and the schema information
> to replicate to the new global catalog server.
>
>
>
> 9. Transfer the FSMO roles to the SBS 2003 computer. To do this,
> follow these steps for each FSMO role:
>
>
>
> a. Transfer the Relative ID (RID) Master role. To do this:
>
>
>
> 1. Click "Start", point to "Administrative
> Tools", and then click "Active Directory Users and Computers".
>
>
>
> 2. Right-click your organization name, click
> "All Tasks", and then click "Operations Masters".
>
>
>
> 3. In the "Operations Masters"
> dialog box, click the "RID" tab.
>
>
>
> 4. In the "Operations Masters" dialog box,
> click "Change".
>
>
>
> 5. Click "Yes" to confirm that you want to
> transfer the role, and then click "OK".
>
>
>
> b. Transfer the PDC Emulator role. To do this:
>
>
>
> a. Click "Start", point to "Administrative
> Tools", and then click "Active Directory Users and Computers".
>
>
>
> b. Right-click your organization name, click
> "All Tasks", and then click "Operations Masters".
>
>
>
> c. In the "Operations Masters"
> dialog box, click the "PDC" tab.
>
>
>
> d. In the "Operations Masters" dialog box,
> click "Change".
>
>
>
> e. Click "Yes" to confirm that you want to
> transfer the role, and then click "OK".
>
>
>
> c. Transfer the Relative ID (RID) Master role. To do this:
>
>
>
> a. Click "Start", point to "Administrative
> Tools", and then click "Active Directory Users and Computers".
>
>
>
> b. Right-click your organization name, click
> "All Tasks", and then click "Operations Masters".
>
>
>
> c. In the "Operations Masters"
> dialog box, click the "Infrastructure" tab.
>
>
>
> d. In the "Operations Masters" dialog box,
> click "Change".
>
>
>
> e. Click "Yes" to confirm that you want to
> transfer the role, and then click "OK".
>
>
>
> d. Transfer the Domain Naming Master role. To do this:
>
>
>
> a. Click "Start", point to "Administrative
> Tools", and then click "Active Directory Domains and Trusts".
>
>
>
> b. Right-click "Active Directory Domains and
> Trusts", and then click "Operations Master".
>
>
>
> c. In the "Change Operations Master" dialog
> box, click "Change" .
>
>
>
> d. Click "Yes" to confirm that you want to
> transfer the role, and then click "OK".
>
>
>
> e. Click "Close" to close the dialog box.
>
>
>
> e. Transfer the Schema Master role. To do this:
>
>
>
> a. You can use the Schema Master tool to
> transfer the role. However, the Schmmgmt.dll file must be registered to use
> the Schema Master tool as an MMC snap-in. To register Schmmgmt.dll, click
> "Start", click "Run", type "regsvr32 schmmgmt.dll" (without the quotation
> marks), and then click "OK".
>
>
>
> Note You receive a message that confirms that the
> registration was successful.
>
>
>
> b. Click "Start", click "Run", type "mmc"
> (without the quotation marks), and then click "OK".
>
>
>
> c. Click "File", and then click "Add/Remove
> Snap-in".
>
>
>
> d. In the "Description" area, click "Add".
>
>
>
> e. Click "Active Directory Schema", click
> "Add", and then click "Close".
>
>
>
> f. Click "OK".
>
>
>
> g. Right-click "Active Directory Schema",
> and then click "Change Domain Controller".
>
>
>
> h. In the "Select DC" area, click "Specify
> Name", type the name of the SBS 2003 computer, and then click "OK".
>
>
>
> i. Right-click "Active Directory Schema",
> and then click "Operations Master".
>
>
>
> j. In the "Change Schema Master" dialog
> box, click "Change".
>
>
>
> k. Click "Yes", click "OK", and then click
> "Close".
>
>
>
>
>
> For additional information, click the following
> article number to view the article in the Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:324801.KB.[LN]:
>
>
>
> How to view and transfer FSMO roles in Windows
> Server 2003
>
>
>
>
>
>
>
> 10. Move the site licensing server to the SBS 2003 computer. To do this:
>
>
>
> a. On the SBS 2003 computer, click "Start", point to
> "Administrative Tools", and then click "Active Directory Sites and Services".
>
>
>
> b. Expand "Sites", and then click
> "Default-First-Site-Name".
>
>
>
> c. Right-click "Licensing Site Settings", and then click
> "Properties".
>
>
>
> d. Click "Change", type the name of the new SBS 2003
> computer in the "Enter the object name to select" area, and then click "OK".
>
>
>
> e. Click "OK" to close the "Licensing Site Settings
> Properties" dialog box.
>
>
>
>
>
>
>
> For additional information, click the following
> article number to view the article in the Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:273475.KB.[LN]:
>
>
>
> Licensing in Windows 2000 and differences with
> Windows NT 4.0
>
>
>
>
>
>
>
> 11. Wait for the new Active Directory objects to replicate to the SBS 2003
> computer. The time this takes depends on the Active Directory size and on
> network performance. You can view the Directory Service event log to verify
> that replication has completed successfully. The SBS 2003 integrated Setup
> program may not continue if replication has not completed or if replication
> has failed.
>
>
>
> To test replication, you can create a new test user on a domain controller
> and after several minutes confirm the object has been replicated to the SBS
> 2003 computer. You can also force replication from a domain controller. To
> do this:
>
>
>
> a. On the SBS 2003 computer, click "Start", point to
> "Administrative Tools", and then click "Active Directory Sites and Services".
>
>
>
> b. In the left pane, expand "Default-First-Site-Name",
> expand "Servers", and then expand the domain controller that you want to
> replicate from.
>
>
>
> c. Click "NTDS Settings". One or more objects are listed
> in the right pane. One of those objects is a link to the domain controller
> you want to replicate from. To see the "friendly" name of the object,
> right-click the object and view the name. Right-click the domain controller
> object, and then click "Replicate Now". The replication is performed
> immediately.
>
>
>
>
>
> 12. Change the DNS settings on all domain controllers to point to the new
> SBS 2003 computer as the primary DNS server. To do this, follow these steps.
>
>
>
> Note Follow these steps on all domain controllers in the Active Directory,
> including the SBS 2003 computer.
>
>
>
> a. Click "Start", point to "Control Panel",
> point to "Network Connections", right-click the internal network connection,
> and then click "Properties".
>
>
>
> b. Click to select "Internet Protocol (TCP/IP)", and
> then click "Properties".
>
>
>
> c. Change the preferred DNS server. Type the
> IP address of the SBS 2003 computer as the preferred DNS server. Also, make
> this change on the SBS 2003 computer.
>
>
>
> Note The alternative DNS server can point to the
> previous preferred DNS server as long as it is a server that hosts the Active
> Directory zone.
>
>
>
> 13. On the SBS 2003 computer, insert the SBS 2003 CD 1 into the CD or
>
> DVD drive and continue with the integrated Setup of SBS 2003 and its
>
> components.
>
>
>
> 14. If you already have Microsoft Exchange Server installed in the
> organization, the integrated Setup installs Exchange Server into the existing
> organization. If you already have an Exchange 2003 Server or an Exchange
> 2000 Server in your organization, and you plan to retire that Exchange
> Server, you can move the mailboxes and public folders to the new Exchange
> 2003 Server before you retire the old Exchange Server. To do this:
>
>
>
> a. On the existing Exchange Server in the organization,
> open Exchange System Manager. To do this, click "Start", point to "All
> Programs", point to "Microsoft Exchange", and then click "System Manager".
>
>
>
> b. At the top of the tree in the left pane, right-click
> the <Organization Name (Exchange)> icon, and then click "Properties".
>
>
>
>
>
>
>
> c. Click to select the "Display administrative groups"
> check box, click to select the "Display routing groups" check box, and then
> click "OK".
>
>
>
> d. Expand the "Recipients" container, and then click
> "Recipient Update Services".
>
>
>
> e. Double-click each entry, and then enter the name of
> the new Exchange Server that is running on the SBS 2003 computer in the
> "Exchange server" area.
>
>
>
>
>
> f. Expand "Administrative Groups", expand
> "<Administrative Group Name>", expand "Routing Groups", and then expand
> "First Routing Group".
>
>
>
> g. Click "Connectors", right-click your SMTP connector
> if it is present, change the server that is listed in the "Local bridgeheads"
> area to the new SBS 2003 computer, and then click "OK".
>
>
>
> h. In the left pane, under "First Routing Group", click
> "Members".
>
>
>
> i. In the right pane, right-click the new SBS 2003
> computer, and then click "Set as Master".
>
>
>
> j. In the left pane, expand "Administrative Groups",
> expand "<Administrative Group Name>", expand "Servers", and then expand the
> Exchange Server that existed before you added the new Exchange Server on the
> SBS 2003 computer.
>
>
>
> k. Expand "First Storage Group", expand "Mailbox Store",
> and then click "Mailboxes".
>
>
>
> l. Select all the mailboxes, right-click the mailboxes,
> and then click "Exchange Tasks".
>
>
>
> m. In the Exchange Task Wizard, click "Move Mailbox",
> and then click "Next".
>
>
>
> n. Click to select the new SBS 2003 computer in the
> "Server" list, and then click "Next".
>
>
>
> o. Specify how you want the Move Mailbox procedure to
> handle corrupted messages, and then click "Next" two times to re-home all the
> mailboxes to the new SBS 2003 computer.
>
>
>
> Note This procedure also re-homes the public folders
> to the new SBS 2003 computer.
>
>
>
> p. Click "Finish".
>
>
>
> q. As soon as replication is successful, remove Exchange
> Server from the computer that is to be retired. If the computer that is to be
> retired is also a domain controller, run the Dcpromo.exe program to remove
> this computer from the domain before you physically retire it.
>
>
>
>
>
> Note You must instruct all Exchange Server users to
> point to the new Exchange Server.
>
>
>
>
>
>
>
> For additional information, click the following
> article number to view the article in the Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:822931.KB.[LN]:
>
>
>
> How to remove the first Exchange 2003 Server
> computer from the administrative group
>
>
>
>
>
>
>
> If a domain controller is physically removed and the
> Active Directory Installation Wizard (Dcpromo.exe) is not run first to demote
> the domain controller to a member server, the computer object still exists as
> a domain controller in Active Directory. The previous computer object must
> be removed from Active Directory.
>
>
>
>
>
> For additional information about how to manually
> remove the configuration data for the domain controller from Active
> Directory, click the following article number to view the article in the
> Microsoft Knowledge Base:
>
>
>
>
>
>
>
> KBLink:216498.KB.[LN]:
>
>
>
> How to remove data in Active Directory after an
> unsuccessful domain controller demotion
>
>
>
>
>
>
>
> Note Before you physically retire any domain
> controller on the network, make sure you demote the domain controller by
> using the Dcpromo.exe program.
>
>
>
> "Pedro Ferreira aka Dundee" wrote:
>
>
>>it was told to me that the best way to put a sbs2k3 on a win 2000 domain
>> and make sbs the master server it was to install win 2000 server on
>>the box that will have sbs, put 2000 server as dc and then update to sbs
>>with the sbs cd's.
>>The problem is that i continue with the same issue that i had before
>>when i tried to install sbs and added to the domain.
>>The dcpromo ends with success but with a note that says the replication
>>found some errors and after reboot the problem will be solved. But when
>>he reboots the dns is not working right, and i have errors of dns and
>>ntfrs on the event viewer that it cannot contact the domain controller
>>or find the domain.
>>If i go to locals and services of active directory i can't make the
>>replication but on the active directory at Domain controllers i can find
>>the computer as domain controller.
>>I had already done the adprep and domainprep and it all end ok with no
>>errors.
>>Can someone help me to solve this issue?
>>I need to put sbs running as soon as i can..
>>
>>Thanks
>>
Ok,
thanks Mark, i will try it and then i will tell if everything worked ok
and the problem was solved.
Pedro Ferreira
- Next message: daniel: "Re: Running OWA & RWW between two domains"
- Previous message: Bill Peng [MSFT]: "RE: Sharepoint www Site Admin Hangs"
- In reply to: Mark Jesiel: "RE: upgrade windows 2000 server to sbs2k3"
- Next in thread: Pedro Ferreira aka Dundee: "Re: upgrade windows 2000 server to sbs2k3"
- Reply: Pedro Ferreira aka Dundee: "Re: upgrade windows 2000 server to sbs2k3"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|