Exchange 2010 Preparation

My Envrionement consists of a Server 2003 SP2 (DC, AD, GC) that has checked out successfully with DCdiag utility, the Server 2003 is also running our company exchange 2003 as well (mixed mode that I will change to native) server is about 6 years old.  it has limited harddrive space availalbe,  the C:\ is about 550mb the d:\ dirve that is home for the exchange store is 2.50gb.  Would like to transition our current exchange server to 2010 Exchange (have new hardware, installed server 2008 R2 (64bit). The 2008 server that is going to support the new exchange 2010 is already joined to the domain.  I would like to also move the DC and AD responsiblity to another new server that is Server 2008 R2 (32bit).  I was informed previously not to move the DC to another server until I transition the exchange to the new 2010 server or I could experience a lot of issues with the current exchange 2003.   My plan is to transition the 2003 exchange to the 2010 exchange first.  My concern is how much space will the schema upgrade take on the 2003 server  AD, do I have enough space to accomodate the changes in the 2003 schema for the 2010 exchange (there is about 20 users on the current 2003 AD).  Is this the proper global plan I should follow:  Exchange 2010 transition and then 2003 DC (AD)  to 2008 DC (AD)? The old server 2003 will be dpromo and removed after this full  process is complete.  I assumed this to be strait forward but do not want to take anything for granted knowing that any changes made to a Schema should not be taking lightly.  Any Thought is welcome.
ajc2cAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gregory_VCommented:
My thought would be to upgrade the active directory first to 2008.  Then do the exchange migration.  This way you already have the base domain set and can build exchange on it.  No harm to 2003 when you do this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ajc2cAuthor Commented:
Even though the same server 2003 has exchange 2003 running on it? I do not want any problems with email.... I was warned previously by a tech not to move the DC (AD) to another server until I moved the exchange server over.
0
Gregory_VCommented:
If you're adding a new DC server you can have ad mixed 2003/2008.  2008 will add some features to AD but wouldn't harm exchange.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

ajc2cAuthor Commented:
Not sure I follow I can have two DC's in one domain, one being a 2003 DC (AD) and one Being a 2008 DC (AD)? When I transition the 2003 exchange server to the 2010 exchange server the Schema updates will be pointed to the 2008 DC (AD)? Is this correct?
0
ajc2cAuthor Commented:
You stated that 2008 will add features to AD but not create issues with exchange.  Is there a way to find out how much space these features will need.  Again I only have 550mb C: and  2.50gb on d:\ on  the 2003 server to work with.  I have taking everything I could off to create more space. right now the FSMO roles are on the 2003 server DC (AD) if I need to run the 2008 adprep utility on the server 2003 and it attempts to add the schema updates I might run into space issues, i would like to know before I run that. The 2008 server is more then capable both in RAM and diskspace to handle the AD functions.

For background sake:   My basic goal is to get the old server off the network as it has limited space and is around 6 years old.  My Plan was to seperate and upgrade exchange and file repository functions on to different servers not only for scalibility but for maintanability as well.  Currently there are 3 servers on the network domain.  a 2003 sp2 file server DC AD along with exchange all on same box, currently in production.  A 2008 R@ (32bit) file server (only role for now) that is in production as a file repository.   (I want this server to also eventually  be the DC and AD of the domain).  Finally a 2008 R2 (64bit) server that be utilized as the new exchange server 2010. this server is not in production but is on the domain.
0
Gregory_VCommented:
You won't see much size increase.  Your domain is pretty small. perhaps a few megs.  You're really just running the prep from the cd on that 2003 server and then going about  promoting the file repository server to a 2008 dc, then moving the main fsmo roles to it.

Once you're there, you can start the install of the new exchange server.

0
ajc2cAuthor Commented:
after completing the above move of the FSMO roles I would have 2 DC's one 2003 and one 2008.  The 2008 would house the FSMO roles and be the PDC of the domain. 2003 server would just be a member DC.  is that correct?  What about DNS on the 2003 server? I would also need that to move over to the 2008 Server. After all this is done I would transition the exchange and move mailboxes to the 2008 R2
( 64bit) server, go to each workstation and point them to the new exchange 2010 correct?
0
Gregory_VCommented:
Correct,  you'd have active directory integrated DNS on both DC's.   You'll want to change your DHCP scopes to allow users to use the new DNS server.  I'll presume you'll also want to do DHCP on the new server eventually.  

I would leave the old server with exchange 2003 on it as intact as possible until you've migrated all the mailboxes off of it and are ready to shut it down.

You might not have to point any users to the new server.  If the mailbox move works correctly (and the 2003 server is up for a bit after the mailbox moves), outlook, when it opens, will realize the mailbox was moved and repoint automatically.
0
ajc2cAuthor Commented:
I will get back to you on how this turns out will not be doing this for a week at least, but I am ahead of the game, thanks for the help!
0
ajc2cAuthor Commented:
I am only rating the accuracy due to not having tried the solution as of this date.  We will be doing this in a week.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.