Jules
Fri Jun 02 20:22:01 CDT 2006
Thank you. I will have a look.
"Jeff Stockamp" wrote:
> You're correct, you'll want to upgrade exchange first since exchange 2000
> will not run on server 2003. You can find more information about which
> versions of exchange run on which versions of windows here:
>
>
http://www.microsoft.com/uk/windowsserversystem/exchange/product-information/why-upgrade/windows-Server-2003.mspx
>
> Also, if you haven't already read the upgrade article on msexchange.org, you
> should, it's pretty good and has some special notes for upgrading domain
> controllers:
>
>
http://www.msexchange.org/tutorials/Upgrade_Exchange_2000_to_2003.html
>
> Hope that helps. Good luck.
>
> - Jeff
>
> "Jules" <Jules@discussions.microsoft.com> wrote in message
> news:5134D4A4-8A66-491E-A2FF-4DC8FB9DD458@microsoft.com...
> > Thanks for the info. My concern is that this is a domain controller. I am
> > planning on performing the in place upgrade. My understanding is that I
> > start
> > with the Exchange upgrade first. Are there any other considerations I
> > should
> > be aware of?
> >
> > "Baruch Ortiz" wrote:
> >
> >> Hello Jules:
> >>
> >> When Migrating from Windows 2000 and Exchange 2000, is pretty easy,
> >> you
> >> have 2 scenarios, do it in-place or doing it at phased, the first have
> >> down
> >> times of service (aprox 20 to 30 mins, depending from your server
> >> hardware),
> >> and is too simple to migrating to 2003, and the second Scenario THERE IS
> >> NO
> >> DOWN TIME OF SERVICE
> >>
> >>
> >> The First scenario, just insert the disc of windows 2003 and next to
> >> everything, and finally you're on 2003, then the same steps with
> >> exchange....
> >>
> >> The second Scenario is using a NEW Hardware (ok, is not needed that the
> >> hardware have to be NEW, but compatible and fast recommended), just you
> >> have
> >> to made 2 previews steps to migrating your Windows...
> >>
> >>
> >> 1.- In the windows 2003 compact disc go to the path X:\i386 in a command
> >> prompt, do this steps (your user have to be Schema Admins and Enterprise
> >> Admin member group)
> >> 2.- adprep /forestprep (it will delay a few seconds before to prompt
> >> something)(this proces could take several minutes, don't worry your
> >> production still running and nobody will notice this, just yoy)
> >> 3.-adprep /domainprep (this is a very fast process)
> >> 4.- Install Windows 2003 on the "New" hardware and join your domain
> >> 5.- promote that server to aditional domain controler
> >> 6.- in the "NEW" hardware move roles (exist two ways using the mmc or the
> >> ntdsutil.exe)(there are several documentation about this moving)
> >> 7.- in Active Directory Sites and Services Snap-in you must to select the
> >> NTDS of your New Domain controler and right-click, then properties and
> >> select the check box "Global Catalog", then Ok to all the windows and
> >> Wait
> >> to be informed inside the Event Viewer Snap-in than that server is a
> >> Global
> >> Catalog"
> >> 8.- then in the same window select the NTDS of your original server and
> >> then
> >> de-select
> >> global catalog, and wait to be informed in the global catalog of your
> >> original server.
> >> 9.- depromote your original server, and finaly do all that you have to do
> >> with that server...
> >>
> >>
> >> "Jules" <Jules@discussions.microsoft.com> escribió en el mensaje
> >> news:39EDB362-8641-427D-B997-937027634292@microsoft.com...
> >> >I have just inherited a network that needs upgrading. I have one domain
> >> > controller running Windows 2000 and Exchange 2000. I am looking for any
> >> > recommendations and things to look out for when upgrading this domain
> >> > controller to Exchange 2003 and Windows 2003 server. Any help will be
> >> > greatly
> >> > appreciated.
> >> > Thanks
> >> >
> >>
> >>
> >>
>
>
>