One extra point; Last time I checked, upgrading the OS on an Exchange 2007 server (i.e. an in-place upgrade of Windows) is NOT supported, thus you would not be able to upgrade the OS from W2003 to W2008 without uninstalling Exchange from it first. (or preferably by building a separate server & migrating to it).
Be sure to stick with W2008 NOT W2008R2, - as I *believe* it's still the case that Exchange 2007 isn't supported on R2, - for this you'd be compelled to go to Exchange 2010. (* I read the release notes for E2007SP2 a couple of weeks ago, and I don't recall seeing anything in SP2 that changed the support position for EX2007 on W2008R2, but things do change from time to time, so the landscape MAY have changed recently). HTH Paul G. -----Original Message----- From: Brian Desmond [mailto:[email protected]] Sent: 20 October 2009 01:48 To: NT System Admin Issues Subject: RE: Exch2003 to 2007 experiences? Hi- Find some feedback inline Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Monday, October 19, 2009 2:07 PM To: NT System Admin Issues Subject: Exch2003 to 2007 experiences? I have a few questions for anyone who has done an Exch2003 to 2007 transition. 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 [[Brian Desmond]] Works fine. Disable IPv6 completely (set DisabledComponents in the registry) and save yourself the hassle if you don't need it. 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)? [[Brian Desmond]] [[Brian Desmond]] You should download Exchange 2007 SP2 from download.microsoft.com. That is the full thing. If RU1 is out when you start, place the MSP for RU1 in the Updates folder for Exchange setup and it will automatically be applied 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? [[Brian Desmond]] I would suggest you use the Exchange storage calculator on the Exchange Team blog. It will calculate required memory. A single CPU is NOT enough. There is guidance on Technet for CPU sizing in a multirole scenario such as yours. 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?) [[Brian Desmond]] Edge Transport cannot be collocated. If you want to have an Edge server you'll need to install it on its own VM. Hub Transport can run most but not all of the antispam and transport agents that run on Edge. 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. [[Brian Desmond]] Not possible to lump it together. If you want to do antispam I would have a separate box. 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! -------------------------------------------------------------------- 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/> ~ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.422 / Virus Database: 270.14.20/2444 - Release Date: 10/18/09 09:04:00 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
