I set my original Exchange 2007 Server here up as a single server (not SBS or EBS) when I migrated from Exchange 2003 and it was very simple. Later, when hardware was available, I broke apart my configuration to allow for my CAS and my MBX to be on separate servers. This was also very simple to do, just had to be very careful with the connector configurations to ensure that the mail kept flowing. Tim
-----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, October 28, 2009 1:46 PM To: NT System Admin Issues Subject: RE: Exch2003 to 2007 experiences? Thanks to Jim Kennedy, Joseph Castle, and everyone else who responded so far. It seems like the general consensus here is, since my current Exchange organization running Exchange 2003 runs under a single Exchange box without any issues, that I should likely be able to migrate to Exchange 2007 using a single Exchange 2007 server (typical installation) which includes all the various roles; Hub, Client Access, Mailbox, etc. without a real need for a Edge Transport. Then I come across an MS tech article (Deploying a Simple Exchange Server 2007 Organization) that says --> "During the planning phase of your deployment, and before you deploy any Exchange 2007 servers in a simple Exchange organization, consider the following points: * We recommend that you deploy the single-server simple Exchange organization only when using Windows SBS. * We recommend that you deploy the multiple-server simple Exchange organization only when using Centro." (Centro is EBS I believe) So, MS doesn't recommend a Simple Exchange Organization server solution unless you're running SBS or EBS? Serious? I have seen this reference to NOT using a single Exchange server except only with SBS (or EBS) documented now several times. Which leads me to having to setup a Standard Exchange Organization instead and going to have to setup multiple exchange servers? Or am I just over-analyzing this stuff? Maybe I should just push ahead with a single Exchange server box with all the roles rolled into one anyways. We're only talking 300 mailboxes here with average mailbox sizes of only 20-30MB approximately. Thanks for tips. >1. When building my new Exchange 2007 server, I am probably going to >install Windows 2008 right away to save me from having to upgrade in >the future. Is this what most people are doing, or are they sticking >with Windows 2003 for Exchange 2007 >2. If I install Windows 2008, can I use my Exchange 2007 CD (no service >pack), or do I need an Exchange 2007 CD (slipstreamed w/SP1)? http://technet.microsoft.com/en-us/library/bb123694.aspx >3. My Exchange 2003 environment consists of a single Exchange 2003 server. >It is currently virtualized under ESX with a single vCPU and 1GB memory >with 300 mailboxes. Performance monitoring shows the system is NOT >taxed at all (not even close). With Exchange 2007, is a single vCPU >and 4GB memory going to suffice for approx. the same level of performance? 300 MB's 2k7? Uhm, you prolly could but it would be like watching Tugo's race? You can do it, but know want to see it happen:) I virtualize 2007 with 1 proc and 4 gig and it works for 6 users at home, but the console is dog slow. >4. Do I "require" a seperate Edge Server? Or can that be on the same >box as our hub transport, client mailboxes, etc.? (it seems doing a "typical" >installation of Exchange 2007 puts it all on all box even though the >"typical" installation doesnt say anything at all about Edge >Transport?) It can all be on one box, sure. Different needs require splitting it up, but it is designed to coexist. >5. In a small sized Exchange organization (a single Exchange 2003 server), >would you "recommend" a seperate Edge Server? Or just lump it in with the >main Exchange 2007 box. Put it on one, keep it simple. If you have specific needs like HA or sec for edge servers, you would know:) If you have a single 2003 box now, a single 2007 box will do. BTW, 2010 is peeking its head through the door, and it plain rocks. >I've read a number of Exchange 2007 technotes, articles, etc, but I am >looking for real world answers from people that have done this. Thanks! HTH, jlc -------------------------------------------------------------------- mail2web - Check your email from the web at http://link.mail2web.com/mail2web ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
