ExBPA correctly tells you how to set up your boot.ini; regardless of whether you are SBS, standalone, DC/GC, or whatever. It takes all of those into account.
It also tells you lots of other things. I recommend it. :-) Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Ken Cornetet [mailto:ken.corne...@kimball.com] Sent: Tuesday, January 27, 2009 11:04 AM To: NT System Admin Issues Subject: RE: SMB question.. I see where there are several responses to your note - this question always sparks a debate. The short answer is that what you are doing will work fine (with a couple of minor caveats - see below). Your hardware is not only sufficient, but probably way overkill - you could easily run that mix with a single CPU and 2GB of RAM. In fact, putting in any more than 4GB of ram is wasted in your scenario. CAVEATS: Disaster recovery - having exchange on a DC complicates DR a bit - Microsoft has papers on how to handle this. Exchange installed on a DC results in a server that can take forever to shutdown. The /3GB switch. Microsoft says any Exchange 2000 or 2003 server with more than 1GB of ram needs it (http://support.microsoft.com/kb/823440), but also recommends NOT using that on DCs, so that leaves you kind of stuck. Most likely, you will not see any issues without the /3GB switch. If you do (event log entries about memory fragmentation), set up an automated weekly reboot. Note: these caveats apply to SBS as well. -----Original Message----- From: Cesare' A. Ramos [mailto:cra...@idfllc.com] Sent: Monday, January 26, 2009 7:54 PM To: NT System Admin Issues Subject: SMB question.. Hello all. We are having an internal tech discussion and wanted to have some thoughts from others. The thoughts can be either opinion or reality. We have a handful of small clients, less than 50 users (50 is an average. The majority are under 20) that are currently running a single server that is acting as AD, file, print, IIS, DHCP, Internal DNS, and Exchange 2003 server on MS Windows 2003 standard server. >From the books, I can agree that this may be pushing the hardware, if not >sized correctly. The servers are all running qty 2 dual core processors, 4 to >8 GB of RAM, and over 500GB of available storage with all running. The internal conversation / discussion that we are having is that a single server cannot run all these items as it will lead to issues and error in the server. One of the guys, states that he feels that services such as server will become unstable. Is MS Windows SBS and option yet but not a reality.. Thoughts.. CAR Mobile: 786-412-1746 e-Mail: cra...@idfllc.com BB Pin: 305083B1 AIM: cramosMIA MSN: cramos...@hotmail.com Yahoo: cramosMIA This e-Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-Mail in error please notify the sender via returned e-Mail. Please note that any views or opinions presented in this e-Mail are solely those of the author and do not necessarily represent those of the company. Although IDF operates anti-virus programs, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. ** Think before you print this message. ** ~ 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/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
