Re: upgrade from Win2k to win 2003 + exchange
From: Oren (Oren_at_scoopnyc.com)
Date: 08/20/04
- Next message: Joe R.: "Migrating from Groupwise to Exchange 2003"
- Previous message: OscarArg: "split and migration"
- In reply to: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Next in thread: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Reply: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Aug 2004 07:25:37 -0700
Steven,
I have changed to native mode, i have not removed the
connector yet i'll do it when i'll i upgrade the servers,
the plan is to do it next weekend.
i hope the upgrade/changes will go smoth
as for the deployment guide i already read it, they talk
more about exchange 5.5 to 2003 then on 2k to 2k3
is there other documents i can look into
for: preparing active directory 2k to 2k3 and upgrading
exchange2k to 2k3 on new hardware.
again, i appreciate your help, really helped me understand
the upgrade concept. and i hope i wont run into major
problems!
Oren.
>-----Original Message-----
>Do you have Exchange 2000 ADC installed now? I'd
suggest you go to Native
>Mode Exchange and remove any ADC that you currently have
installed. You
>should not need ADC for what you are doing. Make sure
you follow these two
>KBs on going to native:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;272314&Product=exch2k
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;327779&Product=exch2k
>
>For more information Look at the Deployment Tools:
>http://www.microsoft.com/downloads/details.aspx?
FamilyId=271E51FD-FE7D-42AD-B621-
45F974ED34C0&displaylang=en
>
>and the Deployment Guide:
>http://www.microsoft.com/technet/prodtechnol/exchange/2003
/library/depguide.mspx
>
>
>
>--
>Steven Halsey
>Stevhal@online.microsoft.com
>Microsoft Exchange
>
>Please do not send email directly to this alias. This
alias is for
>newsgroup purposes only.
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>"Oren" <oren@scoopnyc.com> wrote in message
>news:940201c48619$85f9c6e0$a401280a@phx.gbl...
>>
>> now it make sence,
>> one qustion,
>> do i need to indtall AD connector like i did in the
exc2k
>> or 2003 does not need it, if so where can i fine it?
>> i did see it on the install CD
>> also, where can i read more about this type of migration
>> that you described below?
>>
>> Thank you again!
>> Oren.
>>
>>
>>
>>
>>
>>>-----Original Message-----
>>>
>>>So the first thing you are going to want to do is get
the
>> new Windows 2003
>>>server installed as a Domain Controller into the
existing
>> Windows 2000
>>>domain. By doing this it allows you to keep all the
>> same information you
>>>had before in the domain as it will all replicate to the
>> new domain
>>>controller in the domain. Installing the server
>> requires some preparations
>>>steps before you actually do this. The following covers
>> the steps:
>>>
>>>1. Run Exchange 2003 "Setup /forestprep" - This will
>> avoid a schema issue
>>>between Windows 2003 and Exchange 2000. You will have
to
>> do it at some time
>>>so you might as well do it earlier. This is avialable
as
>> part of Exchange
>>>setup on the CD.
>>>
>>>2. Run Windows 2003 "adprep /forestprep". This is
>> avialable from the
>>>Windows 2003 CD. Basically all this does is expand the
>> windows schema and
>>>prepare the forest for Windows 2003 DCs.
>>>
>>>3. Run Windows 2003 "adprep /domainprep". This
>> prepares the permissions
>>>and objects within the Windows domain for Windows 2003
>> DCs.
>>>
>>>4. Build and join the Windows 2003 server as a member
of
>> the existing W2k
>>>domain. Then on the Windows 2003 run from the command
>> window "DCPromo.exe"
>>>This will take you to a wizard to install the server as
a
>> DC. Select
>>>options that join an Existing domain, and the Windows
>> 2003 server will
>>>become a replica domain controller for the Windows
>> Domain. Once windows
>>>active directory replication completes you will have all
>> your information
>>>for the domain on the Windows 2003 server. You will
have
>> completed the
>>>"migration" of the Windows Accounts, computer accounts
>> etc to the Windows
>>>2003 server. Later on after you are finished with the
>> Windows 2000 server
>>>you will run DCPromo again to remove the Windows 2000
DC,
>> leaving you with
>>>just the new server.
>>>
>>>
>>>Next you'll need to install the Exchange 2003 server to
>> join the same
>>>Exchange 2000 Organization you already have. Use the
>> deployment tools
>>>available to do this. It will take you through step by
>> step on what to do,
>>>for the most part it involves running Exchange 2003
setup
>> and installing the
>>>server. The server will join your existing Exchange
>> 2000 server and you
>>>can just move all the mailboxes and public folders over.
>> No permissions or
>>>information should be lost in this way.
>>>
>>>Basically to migrate the mailboxes you'll run "Move
>> Mailbox" from "Active
>>>Directory Users and Computers" or from "Exchange System
>> Manager". This
>>>will migrate your mailboxes, it is explained more in the
>> Deployment tools
>>>Post Installation section. This way all the permissions
>> and mail in the
>>>mailboxes can gradually be moved across to the new
Server.
>>>
>>>To move the public folders you'll run a tool like
>> pfmigrate to create
>>>replicas of your public folders. After the replicas
have
>> time to replicate
>>>you run pfmigrate again to remove the replicas from the
>> Windows 2000 server.
>>>
>>>You'll also need to migrate your connectors to the new
>> server, but this may
>>>be as easy as just adding the new Exchange 2003 server
as
>> a bridgehead on
>>>the properties of your existing connectors.
>>>
>>>When everything is removed from the Exchange 2000 server
>> you'll remove it
>>>from your organization by running Exchange 2000 setup
>> after checking the
>>>following KB:
>>>http://support.microsoft.com/default.aspx?scid=kb;en-
>> us;307917&Product=exch2k.
>>>
>>>
>>>--
>>>Steven Halsey
>>>Stevhal@online.microsoft.com
>>>Microsoft Exchange
>>>
>>>Please do not send email directly to this alias. This
>> alias is for
>>>newsgroup purposes only.
>>>
>>>This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>>
>>>
>>>
>>>"Oren" <oren@scoopnyc.com> wrote in message
>>>news:88d901c48558$13866e90$a401280a@phx.gbl...
>>>>
>>>> can you go over step 1 and 2 with more detail please,
>>>> your reply now make more sence i just want to make
sure
>>>> that I'm on the same page as you.
>>>>
>>>> Oren.
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>You can still proceed with this method.
>>>>>
>>>>>Run in the order I specified. It will have the new
>>>> Server join your
>>>>>existing domain. After you migrate the Mailboxes and
>> PFs
>>>> from the old
>>>>>W2k/E2k server you just remove Exchange from the old
>>>> server and run Windows
>>>>>DCPromo again. This will remove the old DC, and viola
>>>> you will have
>>>>>everything on the new server without needing to
migrate
>>>> computers, user
>>>>>accounts, mailboxes etc.
>>>>>
>>>>>Is there a part of the information that I gave you
that
>>>> was unclear or you
>>>>>are unsure of? I can explain better or go over any
>> parts
>>>> you need more
>>>>>information on.
>>>>>
>>>>>--
>>>>>Steven Halsey
>>>>>Stevhal@online.microsoft.com
>>>>>Microsoft Exchange
>>>>>
>>>>>Please do not send email directly to this alias. This
>>>> alias is for
>>>>>newsgroup purposes only.
>>>>>
>>>>>This posting is provided "AS IS" with no warranties,
and
>>>> confers no rights.
>>>>>
>>>>>
>>>>>
>>>>>"Oren" <oren@scoopnyc.com> wrote in message
>>>>>news:854601c48503$b6690af0$a601280a@phx.gbl...
>>>>>>
>>>>>> Steven
>>>>>> my plan is not move a new domain just replacing
>> hardware
>>>>>> and installing win2k3/exh2k3
>>>>>> i think that a clean install is a better way to go
>> with
>>>> a
>>>>>> new oprating system
>>>>>> also,the server that i currently have is old, i want
>> to
>>>>>> move everthing to the new machine, the plan is to
>> format
>>>>>> the old one and turn him into an admin server.
>>>>>> back to my qoustions, any ideas?
>>>>>>
>>>>>> Oren.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>I would recommend just using your existing
>>>> infrastructure
>>>>>> and move forward.
>>>>>>>Unless there is a definite requirement that you move
>> to
>>>> a
>>>>>> new domain, why
>>>>>>>not use your existing structure.
>>>>>>>Look into the Deployment tools for steps on moving
the
>>>>>> Exchange Forward in
>>>>>>>terms of moving users and public folders.
>>>>>>>http://www.microsoft.com/downloads/details.aspx?
>>>>>> FamilyID=271E51FD-FE7D-42AD-B621-
>>>>>> 45F974ED34C0&displaylang=en
>>>>>>>
>>>>>>>> 1. what is the best way to move the active
directory
>>>> or
>>>>>>>> just the users to the new Win 2003 server?
>>>>>>>
>>>>>>>Join the new W2k3 server to the same domain as the
W2k
>>>> DC.
>>>>>>>Run Exchange 2003 "setup /forestprep" on the W2k DC.
>>>>>>>Run Windows 2003 "adprep /forestprep" on the W2k DC
>>>>>>>Run Windows 2003 "adprep /domainprep" on the W2k DC
>>>>>>>Run DCpromo on the W2k3 DC and make it a domain
>>>>>> controller for the same
>>>>>>>domain.
>>>>>>>Then look at the Deployment Tools for Exchange:
>> Deploy
>>>>>> the First Exchange
>>>>>>>2003 Server, Upgrade From Exchange 2000.
>>>>>>>
>>>>>>>> 2. what are steps that i need to do in order to
>>>> migrate
>>>>>>>> all the mail box's and the public folders?
>>>>>>>
>>>>>>>Look into the deployment tools: Post Installation
>> Steps
>>>>>>>
>>>>>>>
>>>>>>>> 3. since this is a new install/new machine do i
need
>>>> to
>>>>>>>> rejoin all the workstation to the doamin?
>>>>>>>
>>>>>>>I would re-use your exisiting domain as it will save
>> you
>>>>>> effort of moving
>>>>>>>your workstation and users.
>>>>>>>
>>>>>>>> 4. what about all the rights that users had? (mail
>>>>>> access,
>>>>>>>> public folder security...)
>>>>>>>
>>>>>>>If you re-use the structure this should all be moved
>>>>>> forward with very few
>>>>>>>issues.
>>>>>>>
>>>>>>>
>>>>>>>--
>>>>>>>Steven Halsey
>>>>>>>Stevhal@online.microsoft.com
>>>>>>>Microsoft Exchange
>>>>>>>
>>>>>>>Please do not send email directly to this alias.
This
>>>>>> alias is for
>>>>>>>newsgroup purposes only.
>>>>>>>
>>>>>>>This posting is provided "AS IS" with no warranties,
>> and
>>>>>> confers no rights.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>"Oren" <oren@scoopnyc.com> wrote in message
>>>>>>>news:09e101c48491$4d176640$a301280a@phx.gbl...
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> i have been reading most of the qustions that user
>> are
>>>>>>>> posting but i have not found what I'm looking for
>>>> thats
>>>>>>>> why I'm posting my qustion.
>>>>>>>>
>>>>>>>> we have Win2k sp4 server (dual PIII-550Mhz/1Gig
ram)
>>>> with
>>>>>>>> exchange 2k sp3.
>>>>>>>> i have a new server win 2003 and im ready to
install
>>>>>>>> exchabge 2003.
>>>>>>>> few qustions
>>>>>>>
>>>>>>>
>>>>>>>.
>>>>>>>
>>>>>
>>>>>
>>>>>.
>>>>>
>>>
>>>
>>>.
>>>
>
>
>.
>
- Next message: Joe R.: "Migrating from Groupwise to Exchange 2003"
- Previous message: OscarArg: "split and migration"
- In reply to: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Next in thread: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Reply: Steven Halsey [MSFT]: "Re: upgrade from Win2k to win 2003 + exchange"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
