Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating from 2003 to 2010 2

Status
Not open for further replies.

said07

IS-IT--Management
May 3, 2004
168
US
Greetings,

I am about migrating from 2003 to 2010 Exchange.
I have:
- 120 mailboxes with 3 datastores.
- Front end and back end infrastcture.
- Couple of public folders.
- One domain, one site, one forest.

I am planning on having one server with all the roles in the lan and one edge server in the dmz.
Any good article that clarifies the migration through co-existence then removal of 2003 will be greatly appreciated.

Thanks
 
Thanks you zbnet.
Couple of questions please for an advice.
I am thinking about 4 processors and 8 gig of Ram. Do you think that would be decent to run my system? And does the edge server has to have that much?

Thanks again.
 
Asking about sufficient resources without providing a plethora of data about your environment is a waste of time. Proper sizing of an Exchange installed takes considerable information.

Pat Richard MVP
 
Microsoft has some really good spreadsheets that will assist you in sizing. I don't see why you couldn't get away with a 2 node DAG if you require HA. That would require a hardware load balancer. If you need HA for the edge, you'll need two servers for that as well. But database sizing, server sizing, etc should only be done with the MS tools.

Pat Richard MVP
 
Keep in mind that's not a front end/back end scenario. Edge does only message hygiene in/out of your environment. Client access will still be handled by the internal server (which is what you want anyways - no need for domain joined servers in the DMZ).

Pat Richard MVP
 
Ok, I see. I still need to configure the forwarding of smtp traffic only to the edge server on my firewall, right?
 
Correct. Best practice would be that SMTP is allowed through the internal interface of the firewall ONLY to/from the hub transport and edge transport servers. On the external interface, only to/from the edge transport and the Internet.

Pat Richard MVP
 
4 Processors and 8GB of RAM? Do you mean 4 cores? 8GB is the absolute minimum for a multi-role server, and I always shy away from only just having the minimum when specing Microsoft systems. So this sounds a little undersized - I have a PC with that spec that I use for running a few VMs on in a mini testbed, and it isn't stellar fast.

Technet has some advice on how to spec a multirole server, see
I personally prefer the Microsoft sizing spreadsheet ( even though I work for HP(!)
 
I use HP servers and HP (as well as Dell, etc...) have sizing applications where you plug in the numbers and it shoots you a recommended hardware config. For example, a 1000 users with half being light and the other half being medium users, would spit me out a server with 2 Dual Core processors and 8GB of memory. This would be for a multirole install minus the unified message role.

I would still definetely run through the Microsoft spreadsheet as mentioned and use that as your primary base of information, but this other gives you a hardware focused view into your possible solution. Also, use that info given as minimum specs and provision for more as previouly suggested.
 
Thanks Guys. Just as anotherpiece of info, my actual exchange environment is all vmware based and I am planning to keep it that way.
 
The MS spreadsheet cameback with 8gb ram minimum.
So I think I am going to allocate 4 cores and 16 Gb. I can always add ram if needed.
 
Hey Pat, I think the new spreadsheet has a virtualization tab that does just that. Or at least there's a new one coming that will according to one the speakers at Tech-Ed.
 
The more i try to detail my plan the more questions i have!

1- Server hard disk: Since I have it as a vm, does it really make a difference to have separate disks for Logs, page files, and dbs like in the physical world? or should i just have one disk for the os, and the works?
2- Since I am going with a co-existence transition, two questions arose:
a: The owa now is directed to my front end. What should I do? Should I keep it there or move it to the new 2010 server.
b: The edge Server sync: Should it be done with the backend 2003 or the new 2010?

Thanks
 
1. Yes. The VHDs need to be on storage that can provide the performance that the storage calculator shows. And you should verify that with JetStress. Having separate volumes prevents problems with one affecting the others.
2a. There are some good articles on that. You'll create a legacy name. The 2010 server will be in front.
2b. Edge sync must go from an Exchange 2010 edge server to an Exchange 2010 hub transport server.

Stop by the new Tek-Tips group at LinkedIn. Come say hi, look for a job, have some fun.
Pat Richard MVP
 
Finally I got around installing Exchange 2010 in my environment.
For testing I moved my mailbox to the new 2010 server and since then I get only internal email. No external. I also tried to get onto Owa and I couldn't. Owa still works at the same address for the legacy mailboxes. For me it looks like it is trying to connect to the new server judging by the web page I get.
Did I miss a step?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top