Skip to main content

Edward Kelty

Go Search
Home
Ed's Picture Archive
Ed's Video Archive
  

Amazon
Archive
Archive (Calendar)
Blue's Angels
eBay
Ed's Docs
Ed's Flickr Site
eMail
Facebook
Kelty Photography
Online Picture Manipulation
Pandora
The Families Website
Dell PowerEdge 1900 Maximum Memory

Before I move on to all the decision points and steps I’m going through to setup my SBS2011, I’d like to address one point that I have not been able to find a definitive answer to on the web.

What is the maximum amount of memory a Dell PowerEdge 1900 can support? Over the last few years I’ve purchased two of these systems. One for production and one for testing and/or parts. One system cost under $1000 and the other under $1800 (and that was only because I purchased 16G of ram in the second system knowing that in the future I’d need that much memory when moving from SBS 2003 to SBS20xx).

So, the 1900 manual and Dell support site both indicate that the Dell PowerEdge 1900 can only support up to 16Gs of Ram.  But if you do a web search, there are plenty of vendors that say it can support up to 64G of ram!

How to know for sure?  In looking at the Dell PowerEdge 1950, 2900 and 2950, they all seem to have the same chipset, CPU support and number of memory slots as the 1900. These units all said they could support 32G of ram. So, after searching for the best possible price on 32G of ram, I purchased the memory and installed it in the 1900 that was out of warranty.

When I booted up the system, NO ISSUES!  It recognized the 32G of ram immediately and I’ve been running the test system for several days with the new memory configuration without issue.  I now have some additional breathing room to implement Hyper-V and SBS2011.

Also, incase you are wondering, below are the memory parameters for three different levels of RAM. Though I now believe that the 1900 could support even 64G of RAM I don’t think I could ever afford it nor would I likely need it.

I hope this helps some of you out there now that I’ve confirmed it’s possible.  Two items to consider before increasing your 1900 above 16G:

  • Update the 1900’s BIOS to the latest version!  I’m running 2.7.0.
  • Check the front of your 1900 to see if it has a roman numeral II (two) on it (lower left corner). I was told by one vendor that meant it was “Version 2” of the system and only version 2 could support above 16G of ram. Fortunately both of my systems have this mark.

1900-VII

Good luck! Ed

Memory Parameters

2G = DDR2 PC2-5300 • CL=5 • Fully Buffered • ECC • DDR2-667 • 1.8V • 256Meg x 72 (8x2=16G)
4G = DDR2 PC2-5300 • CL=5 • Fully Buffered • ECC • DDR2-667 • 1.8V • 512Meg x 72 (8x4=32G)
8G = DDR2 PC2-5300 • CL=5 • Fully Buffered • ECC • DDR2-667 • 1.8V • 1024Meg x 72 (8x8=64G)

Virtualized Windows SBS 2011

I’ve spent a lot of time experimenting with SBS in a virtualized environment. The issue I’ve been facing is whether or not to use Hyper-V Core or Windows Server 2008 R2 w/Hyper-V Role. The following were a few of the pros/cons, in my opinion, that were playing through my mind:

Hyper-V Core

Pros:

  • Smaller memory footprint (my tests show it takes up about 1.5G of RAM)
  • Bare metal installation
  • No overhead related to installing the overall Windows Server 2008 R2 system

Cons:

  • No GUI interface
  • I found it a bit confusing to try and get the management tools configured. There is a lot of information on the web related to getting these setup, but, I couldn’t find any single source that went through all the steps required to manage the Hyper-V system remotely from another computer. In the end I got it to work but I’m not 100% everything is configured exactly as it’s supposed to be.
  • 3rd party software for things like UPS and/or system management

Windows Server 2008 R2 running the Hyper-V Role

Pros:

  • Familiar GUI interface
  • Can install any 3rd party apps you may need
  • Easy GUI interface for backups (though remember, if you are using SBS 2011 Premium, you can only run the Hyper-V role and no others (though you can install certain “features” like backup)

Cons:

  • Mainly just the bloat of having to install the entire operating system

I should also state that though I work in the technology field, all the work I do with SBS 2003, 2008 & 2011 is pretty much related to supporting services for my family so I don’t have a lot of cash to buy a large server. So, with that said, I need to squeeze as much as I can out of the systems I have.

As an example, I have a PowerEdge 1900 with 16G of RAM.  I setup Hyper-V core and then I downloaded and installed the trial version of SBS 2011. I started with allocating 8G of ram and after installation, with nothing but the base installation, the system ran sluggish and was paging out memory like crazy. I shutdown the system and bumped it up to 10G of ram and restarted the system. It ran better but was still upwards of 80% memory utilization.  With some further testing it seemed like 12G of ram is where the system was hovering around 60% memory utilization without hosting any email or websites…

Considering that the system only had 16G of Ram, I would have maxed it out running the standard SBS 2011 as well as possibly running SQL (the premium version of 2011) in two virtualized environments.  Even if I squeeze the memory down to the minimums (i.e. 9G for Standard,  5G for SQL and 2G for the core), I’d hit the 16G limit immediately.

This testing alone validated that trying to run the full installation of Windows Server 2008 R2 with the Hyper-V Role wasn’t going to be an option for my world.

With that said, I still needed to be able to perform all the management of the system I’d become use to in SBS2003 and I finally figured out how to accomplish that… Read the next post to see how I finally decided on my configuration…

1 - 2 Next

 ‭(Hidden)‬ Admin Links