The next server at the office will be…

On December 21, 2012, in news, by

So this is going to be new MultiPoint server at the office…

HP ProLiant ML310e G8 4U Micro Tower Server – 1 x Intel Xeon E3-1240V2 3.4GHz – 1 Processor Support – 8 GB Standard/32 GB
Maximum RAM – DVD-Writer – 6Gb/s SAS RAID Supported Controller – Gigabit Ethernet

Four HP 300 Gig SAS 10,000 RPM drives

32 gigs of RAM

And yes I’ll be making it on a HyperV Base.

http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/15351-15351-241434-241646-241477-5249594.html?dnr=1

Hanging off of that will be several http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/12454-12454-321959-338927-3640406-5226823-5226824-5302897.html?dnr=1 Thin client stations.

 

 

 

7 Responses to The next server at the office will be…

  1. James feldman says:

    Hi Susan,

    I’m interested in how many users you expect to handle on this box, and how it handles under load.

    Hope you can keep us up to date on how it’s performing once deployed!

    Thanks again for a great blog 🙂

    James.

  2. tom says:

    Would love to see your step by step setup process.

  3. bradley says:

    The box has to arrive. That is the first step. I ordered it. 🙂

  4. bradley says:

    This is a box planned for growth. We overbought. We’re going to hang 4 people off of it with the potential that 20 people could hang off ultimately.

  5. Frank Hinojosa says:

    So are you planning for 20 or do you have 20? Maybe SBS 2011 Essentials would be better, but i do see you want to utilize HYER-V.

  6. bradley says:

    I still have my full blown SBS box under hyperV. This is intended to be a thin client deployment from the get go, ergo Multipoint

  7. The Webdoggie says:

    Since WMS server will be in a HyperV, will you be backing it up? Can Windows Backup do it successfully? Third party solution?

    I am kind of old school and am still a bit confused as to how to get virtual stuff stored on actual tapes and the like in a useful way.

    When Symantec tells me that they want north of $1k for a Virtual Machine agent, I start thinking that it is more complicated than it looks.

    Thanks.