Demoting/promoting

[Guest]

I have a scenario that might cause me some greif and need a little help. I
have a domain with a1 PDC and 1 BDC. My PDC happens to be running Echange
2000 and that box needs to be put to sleep. What is the best practice to get
that exchange/PDC box out of the system and get a new 2003 server in it's
place running exchange 2003? My BDC is just a clone PC that acts as a BDC
and i'm not sure if I am happy about making that my PDC. Can I promote
another server to BDC before I do anything and can it be a 2003 server?? Any
help or good KB articles would be great. Thanks

Perry

 

[Guest]

Is the existing domain NT 4.0 or Windows 2000?

 

[Guest]

Existing domain is Win 2000

Is the existing domain NT 4.0 or Windows 2000?

 

[Guest]

You could do the following:

1) Install the new Windows 2003 server
2) Run ADPREP /DomainPrep and /Forestprep as required to add a Windows 2003
domain controller to a Windows 2000 domain
3) Run DCPROMO on the Windows 2003 server and add it to the Windows 2000
domain.
4) Install Exchange 2003 on the server. Make note of requirements:
http://support.microsoft.com/kb/822179/
5) Migrate the FSMO (Flexible Single Master Operations) :
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504
6) Migrate the mailboxes to the new Exchange Server
7) Migrate the remaining services from the old Exchange server to the new
one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822931#XSLTH3140121122120121120120

Of course, you will make sure that you have appropriate system state backups
and Exchange backups before you begin and prior to critical steps involving
ADPREP.

 

[Guest]

Thank You Paul!! That is what I needed

You could do the following:

1) Install the new Windows 2003 server
2) Run ADPREP /DomainPrep and /Forestprep as required to add a Windows 2003
domain controller to a Windows 2000 domain
3) Run DCPROMO on the Windows 2003 server and add it to the Windows 2000
domain.
4) Install Exchange 2003 on the server. Make note of requirements:
http://support.microsoft.com/kb/822179/
5) Migrate the FSMO (Flexible Single Master Operations) :
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504
6) Migrate the mailboxes to the new Exchange Server
7) Migrate the remaining services from the old Exchange server to the new
one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822931#XSLTH3140121122120121120120

Of course, you will make sure that you have appropriate system state backups
and Exchange backups before you begin and prior to critical steps involving
ADPREP.

 

[Guest]

The ADPREP command is only required in a Windows 2000 Active Directory when
you are adding Domain Controllers. To add member servers that are Windows
2003, ADPREP is NOT required. So you are fine.

 

[Guest]

Great! Thanks again!!

The ADPREP command is only required in a Windows 2000 Active Directory when
you are adding Domain Controllers. To add member servers that are Windows
2003, ADPREP is NOT required. So you are fine.

 

[Guest]

One more concern that I have. You had mentioned the ADPREP that I needed to
run prior to putting a 2003 box in the domain. I never ran that command and
I have two 2003 servers in this domain already. Is this a problem and if so
how can i correct this without damage. These servers are just domain servers
and not any type of controllers. Thanks again for all the help.

Perry

 

[Jorge_de_Almeida_Pinto]

I have a scenario that might cause me some greif and need a
little help. I
have a domain with a1 PDC and 1 BDC. My PDC happens to be
running Echange
2000 and that box needs to be put to sleep. What is the best
practice to get
that exchange/PDC box out of the system and get a new 2003
server in it's
place running exchange 2003? My BDC is just a clone PC that
acts as a BDC
and i'm not sure if I am happy about making that my PDC. Can
I promote
another server to BDC before I do anything and can it be a
2003 server?? Any
help or good KB articles would be great. Thanks

Perry

To introduce w2k3 DCs you need to:
* Repair the schema (inetorgfix)
* prepare the schema for w2k3 (adprep /forestprep)
* prepare the domain for w2k3 (adprep /domainprep)

To introduce e2k3 servers you need to:
* prepare the schema for e2k3 (setup /forestprep)
* prepare the domain for e2k3 (setup /domainprep)

After updating the schema:
* install the w2k3 server and promote to DC
* move all roles (GC, TRANSFER FSMOs) and services (DNS, WINS, DHCP,
etc) to the w2k3 DC
(it is not recommended to install exchange 2003 on a DC)
(if you still want to install exchange on the new DC, install IIS and
exchange AFTER the promotion!!!)
* install exchange 2003
* Move exchange resources to the new exchange server
* deinstall exchange on the old DC
* demote the old DC and remove from the domain

for more info see:
For information on transfering or seizing FSMO roles see:
http://support.microsoft.com/?id=324801 (How to view and transfer FSMO
roles in Windows Server 2003)
http://support.microsoft.com/?id=255504 (Using Ntdsutil.exe to
transfer or seize FSMO roles to a domain controller)
http://support.microsoft.com/?id=255690 (How to view and transfer FSMO
roles in the graphical user interface)
http://support.microsoft.com/?id=197132 (Windows 2000 Active Directory
FSMO roles)
http://www.petri.co.il/transferring_fsmo_roles.htm
http://www.petri.co.il/seizing_fsmo_roles.htm

MS-KBQ314649_W2K3 ADPREP Command Causes Mangled Attributes in W2K
Forests That Contain E2K Servers
MS-KBQ325379_How to Upgrade Windows 2000 Domain Controllers to Windows
Server 2003
MS-KBQ555040_Common Mistakes When Upgrade Windows 2000 Domain To
Windows 2003
MS-KBQ324392_Enhancements to Adprep.exe in Windows Server 2003 Service
Pack 1 and in hotfix 324392
Also see:
http://www.microsoft.com/technet/pr...elp/bc5ebbdb-a8d7-4761-b38a-e207baa73419.mspx)
http://www.petri.co.il/windows_2003_adprep.htm
MS-KBQ555038_How to enable Windows 98-ME-NT clients to logon to
Windows 2003 based Domains
MS-KBQ887426_Incorrect Schema extension for OS X prevents ForestPrep
from completing in Windows 2000
MS-KBQ555262_Common Mistakes When Upgrading Exchange 5.5-2000 To a
Exchange 2003
MS-KBQ822942_Considerations When You Upgrade to Exchange Server 2003

When transfering the PDC FSMO you need to reconfigure the NEW FSMO
role owner DC with an external time source and reconfigure the OLD
FSMO role owner DC to use the domain hierarchy (ONLY IF YOU USE AN
EXTERNAL TIME SERVER - the list will be empty if you have no
configuration)
On the old FSMO role owner DC run:
--> NET TIME /QUERYSNTP
Configure the new FSMO role owner DC with
--> NET TIME /SETSNTP[:ntp server list]
or --> W32tm /config /manualpeerlist:â€<time server 1> <time server
2> <time server n>†/syncfromflags:manual

To update the “Windows Time Service†configuration:
--> W32tm /config /update
OR
--> Net stop w32time & net start w32time

To resync time:
--> W32tm /resync

To clear the NTP configuration on the old PDC
--> NET TIME /SETSNTP

Fore more info
MS-KBQ816042_How to configure an authoritative time server in Windows
Server 2003

good luck