Do you have an MSDN, Technet, or Action Pack subscription available to you? If so, you can set the whole thing up in virtual land and step through the entire process using running VMs created to match your environment before you ever touch production. I can't stress enough how useful this is from both educational and practical standpoints. There might be other avenues for demo/test software availability. Those 3 just came to mind.
I did something very similar to what you've described 3 or 4 years ago when I "unclustered" Exchange 2003 and moved it to a single monolithic server. (< 100 users then and now.) On Thu, Jan 14, 2010 at 9:22 PM, Bill Lambert <[email protected]> wrote: > Thanks, Sean, for the informative reply. I’ll be sure to check out the > links you sent along. > > > > I tried to get E2010 approved for this year’s budget but was told that it > would have to wait until 2011. We are a division of a larger company so > change comes slowly here. So I’m stuck with 2003 for another year. > > > > I inherited this server which is also a domain controller. I want to get > Exchange on its own box so this will be a challenging project as it’s only > me doing Windows admin. > > > > > > *Bill Lambert* > > *Concuity* > > *Phone 847-941-9206* > > > > *The information contained in this e-mail message, including any attached > files, is intended only for the personal and confidential use of the > recipient(s) named above. If you are not the intended recipient (or > authorized to receive information for the recipient) you are hereby notified > that you have received this communication in error and that any review, > dissemination, distribution, or copying of this message is strictly > prohibited. If you have received this communication in error, please contact > the sender by reply email and delete all copies of this message. Thank you. > *** > > > > *From:* Sean Martin [mailto:[email protected]] > *Sent:* Thursday, January 14, 2010 5:44 PM > *To:* MS-Exchange Admin Issues > *Subject:* Re: February Project > > > > The first question that pops up is why not take the opportunity to upgrade > to Exch 2007 or 2010? > > > > While Windows 2003 Enterprise may support memory beyond 4GB, Exchange is > still limited to less than 4GB. If you plan on installing more than 4GB, > you'll want to add some options to your boot.ini (/3GB, /USERVA=3030, > /MAXMEM=4096). I believe the suggested values for USERVA and MAXMEM may vary > slightly, so I would start by researching their intended utilization. Using > the MAXMEM switch limits the OS to the value you specify. Since it is > recommended you limit Exchange 2003 to 4GB or less, you may not be gaining > much by having more than 4GB memory installed. > > > > Note: I've always used the /MAXMEM switch, but apparently it is recommended > you use the /BURNMEMORY switch as it can account for memory holes. > > > > Here's some articles to get you started: > > > > http://support.microsoft.com/kb/316739 > > http://support.microsoft.com/kb/810371 > > *http://support.microsoft.com/kb/108393* > > *http://support.microsoft.com/kb/833721* > > http://msdn.microsoft.com/en-us/library/ms791501.aspx - BURNMEMORY Info > > > > > > > > > On Thu, Jan 14, 2010 at 1:13 PM, Bill Lambert <[email protected]> > wrote: > > Hello all… > > > > In early February I’ll be getting a new box for our Exchange 2003 > Enterprise edition. I have been trying to prepare for this as much as > possible but have some questions. The current Exchange is running on > Windows 2003 Standard and I want the new box to have Windows 2003 Enterprise > to take advantage of the support of larger amounts of memory and CPU’s (and > because I have a license for it). Will this present any move/migration > problems that I should be aware of? > > > > Any advice/comments/suggestions/questions would be hugely appreciated! > > > > Thanks. > > > > *Bill Lambert* > > *Windows System Administrator* > > *Concuity* > > *A healthcare division of Trintech, Inc. * > > *Phone 847-941-9206* > > *Fax 847-465-9147* > > *[image: clip_image001]* > > > > > > *NASDAQ: TTPA* > > *The information contained in this e-mail message, including any attached > files, is intended only for the personal and confidential use of the > recipient(s) named above. If you are not the intended recipient (or > authorized to receive information for the recipient) you are hereby notified > that you have received this communication in error and that any review, > dissemination, distribution, or copying of this message is strictly > prohibited. If you have received this communication in error, please contact > the sender by reply email and delete all copies of this message. Thank you. > * > > > > >
<<image001.gif>>
