akhlaq khan

hi,
i am new to this migration thing, never done it before. we are running
windows 2000 AD with ms exchange 2000, supporting 40-50 client machines. we
have decided to upgrade to windows 2003 w/ ms exchange 2003. i have already
installed windows 2003 on a separate new machine but dont know where to
start looking for migrating the AD.

i was thinking that i should synchronize the 2000 AD with 2003 AD and then
bring down the 2000 AD machine. is that possible ? if yes, please let me
know what articles/tools will be required for this purpose. i am also
looking for exchange server migration information but maybe i should post
this in a separate newsgroup.

any help will be highly appreciated.

thanks

akhlaq.

mark dormer

Basically

1. Install Windows Server 2003 on new server
2. Run /Forestprep and /DomainPrep on the W2K domain
3. Join this server as additional domain controller to current window 2000
DC
4. Pass master domain controller operations to new win2k3 dc.
5. upgrade or remove other windows 2000 server.

More details
http://support.microsoft.com/?kbid=325379

Regards
Mark Dormer

marin marinov

In article <eFZv#vNYEHA.3568@TK2MSFTNGP10.phx.gbl>,
akhlaq.khan@softechww.com says...

Hi Akhlaq,
Since you already have AD then you would probably go for the "upgrade"
approach in contrast to "restructure". As Mark suggested, you would
introduce a new Win2K3 DC in the existing domain. Before you can install
a Win2K3 DC, however, you must do some preparation,specifically you must
run the Adprep.exe tool with the /forestprep option on the schema master
and /domainprep on the infrastructure master. However, be aware of an
issue with Exchange 2000:

Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes
in Windows 2000 Forests That Contain Exchange 2000 Servers
http://support.microsoft.com/default.aspx?kbid=314649&product=winsvr2003

After Adprep has run successfully, you may need to trasfer all
operations master roles to the new Win2K3 DC. "May" because you can
maintain your Win2K DCs for as long as you need, though you won't get
all the new features in Win2K3 AD untill you run all Win2K3 DCs:

HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801

HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690

You must also make sure you don't break DNS if you decomission Win2K DCs
and it's recommended to install DNS on the Win2K3 DC (and on every DC,
in most cases).

Since you haven't done a migration before, I would really suggest you
take the time to read through the below do***ents because no matter how
simple migration is never a routine task (URLs wrap):

Upgrading Windows 2000 Domains to Windows Server 2003 Domains
http://www.microsoft.com/resources/do***entation/WindowsServ/2003/all/de
ployguide/en-us/Default.asp?
url=/resources/do***entation/windowsserv/2003/all/deployguide/en-
us/dssbf_upwn_overview.asp

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx

Upgrading from Windows 2000 Server to Windows Server 2003 (white paper)
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w
2ktows03-2.mspx

Upgrading to Windows Server 2003
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technolog
ies/directory/activedirectory/upgadc14.mspx

How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?kbid=325379

HOW TO: Raise Domain and Forest Functional Levels in Windows Server 2003
http://support.microsoft.com/?id=322692


As far as Exchange goes, you can start here:

Exchange Migration and Upgrade Resources
http://www.microsoft.com/exchange/techinfo/interop/default.asp

...and if you still have concerns post in one of the Exchange newsgroups.

HTH
--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.

"True knowledge exists in knowing that you know nothing."
Socrates

charliel

Hi Akhlag,

Thank you for posting.

According to your post, I understand that you are going to move the AD and
Exchange Server to Windows Server 2003 Domain, If I am off-base on that,
please let me know.

Mark and Marie provided you with the most of the information on moving AD
to new Windows Server 2003 DC.

As you may know that the key point to adding a Windows Server 2003 DC to
Windows 2000 domain, you should run Adprep /foresetprep and /domainprep.

I suggest you refer to following article about upgrading:
325379 How to upgrade Windows 2000 domain controllers to Windows Server
2003 http://support.microsoft.com/default.aspx?scid=KB;EN-US;325379

After Windows Server 2003 DC is joined to Windows 2000 Domain, transfer
FSMO, Global Catalog to the Windows Server 2003.

For detailed steps, please refer to:
HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801
HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690
HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

Considering the Exchange issue, you should pay attention to following
potins:

1. Make sure that ALL Windows 2000 domain controllers are running SP3 or
later before you begin the upgrading process.
2. After you follow the steps above to run ADPREP /Forestprep and
/Domainprep, because forestprep will break some exchange schema, you should
fix Exchange server attributes.

For more information, please refer to:
314649 Windows Server 2003 adprep /forestprep Command Causes Mangled
Attributes http://support.microsoft.com/?id=314649

- On Exchange server 2000, re-run Exchange 2000 setup /Forestprep.
- Re-run Exchange 2000 setup /DomainPrep.
- Click Control Panel -> Add or Remove Programs.
- Select Microsoft Exchange, and click Change/Remove.
- Choose Reinstall under Action, and follow the wizard.

3. Before you migrate to Exchange server 2003, it's recommended that you
check the following articles first:

822178 Overview of Dependencies and Requirements for Exchange Server 2003
http://support.microsoft.com/?id=822178
822179 Overview of Operating System and Active Directory Requirements for
http://support.microsoft.com/?id=822179
822942 Considerations When You Upgrade to Exchange Server 2003
http://support.microsoft.com/?id=822942

4. Install Exchange 2003 on the new Windows 2003 domain controller, and
join the existing Exchange 2000 organization.

Note: It's highly recommended that you follow the steps in Exchange 2003
deployment tools. The wizard is very helpful and provides detailed steps on
how to install Exchange server 2003 in various scenarios. To use deployment
tools, run the setup program at the root folder of the Exchange 2003
installation CD.

For more information on upgrading Exchange Server, please post it in
<microsoft.public.exchange2000.admin> newsgroup.

Have a nice day!

Sincerely,

Charlie Li
MCSE/MCDBA/MCSA
Microsoft Partner Online Support


Get Secure! - http://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.

bob williamson

Will the Exchnage mangling occur if I am runnning E2K3 on a W2K domain that
I am upgrading/migrating or is it only E2K?

I will be downing my primary DC (all FSMO roles etc) and rejoing a W2K3 DC.

Thanks,
Bob

charliel

Hi Bob,

The article Q314649 (http://support.microsoft.com/?id=314649) not only
apply on Exchange 2000 but on Exchange 2003. You should reinstall Exchange
Server 2003 based on the steps I included in previous post. The steps I
included are easier then the steps in article Q314649.

If you have any other questions on Exchange migration, I suggest post it in
< microsoft.public.exchange2000.admin> newsgroup.

Have a nice day!

Sincerely,

Charlie Li
MCSE/MCDBA/MCSA
Microsoft Partner Online Support


Get Secure! - http://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.

akhlaq khan

thanks charlie/marin/mark for your valuable help.

i must say there is a lot for me to read and understand before i even start
thinking about starting the migration. since i am new to migration, i think
i will take some time to read/understand all the articles and try to do some
experiments on separate machines.

i hope i can get back to you guys if i need further help in this regards
.....

thanks for all the info

akhlaq.

bob williamson

After reviewing, Q325379, I can certainly see why you state the method you
posted is easier than the suggested method in the article. I can also see
why your method should work as the exchange domain and forestprep meets the
needs as stated in the article. (Exchange being installed post W2K3 DC).

On thing that concerns me, however, is the step that you stated of
reinstalling Exchange. Why is this necessary? I am concerned about this
step as I have AV on Exchange, antispam on Exchange etc. Obviously for a
reinstall it would be wise to remove these 3rd party products.

NOTE: Anytime the word 'mangle" is used in reference to Exchange server
and/or AD it scares me big time! You may want to suggest a different
verbiage be used.

One again, my environment is W2K AD, multiple DCs, E2K3 on a W2K member and
I want to replace my primary DC (primary meaning handles FSMO stuff)
hardware and up to W2K3 on that DC.

Thanks again for all of your help,
Bob