Tuesday, 14 June 2011

2 Node SR1695GPRX + VTrak E610sD Hyper-V Cluster Is Live

We are still ironing out a few things as far as how to set up the MPIO settings, but for the most part we are quite happy with the end results of our configuration testing.

A Hardware Problem

It seems that one of the Adaptec cards has taken exception to the current setup. We have not concluded as to whether the card has failed or needs a firmware reset as of yet. We need to determine _which_ card is causing the following on the VTrak:

image

47243 New Events

Last Event: 47272, Port 2 Ctrl 1, Info, Jun 14, 2011 08:44:20 – Host interface has logged out.

The corresponding error for a log in would follow the above. Note that none of the other three connections are throwing this error. As a result we are pretty sure it is one of the Adaptec cards since we connected like with like on the controllers.

  • Adaptec SAS:
    • Server 1: Port x on Controller 1
    • Server 2: Port x on Controller 1
  • Intel 1064e SAS:
    • Server 1: Port x on Controller 2
    • Server 2: Port x on Controller 2

We connected the cables in this manner just for this reason. We will be running through the VTrak’s Web GUI as well as the console session connected via Serial cable to see if we can figure out which port is which on Controller 1.

We have a pair of LSI 3442E-R SAS controllers on the way. We will replace both of the Adaptec cards with the LSi cards, flatten everything, and stand up a cluster for the third time.

Live Migration Success

This is a happy sign:

image

We initiated a Live Migration of the Windows Server 2008 R2 Standard Remote Desktop Services VM from Node-99 to Node-90.

image

The Live Migration ran successfully as shown above. The RDS VM was Live Migrated to Node-90. We left things alone for a while then Live Migrated the VM back to Node-99 without issue.

Cluster Events

There are a few Errors and one Critical error in the logs. All of them are from a problem with bringing additional LUNs online, formatting them, adding them as available storage in FCM, and then making them Clustered Shared Volumes.

The problems stemmed from a deadlock condition in the Cluster Resource Control Manager which we believe came about as a result of the problem path via the failed/flaky Adaptec card.

Conclusion

We are now confident enough to start proposing this Highly Available Failover Cluster to our clients.

Cost wise this HA Hyper-V cluster will be a very economical insurance policy against any single point of failure.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

P2V Using ShadowProtect V4.x – Quicker But with BSOD 0x0000007B for Windows Server 2003 R2 in Hyper-V

When we were running P2V processes using v3 of ShadowProtect we were waiting quite a while as the ShadowProtect Recovery Environment did not work too well on the Hyper-V side.

image

ShadowProtect version 4 uses the Win7/Win2K8 R2 codebase for its Recovery Environment so we get full keyboard and mouse functionality while working via RDP plus a pleasant 20MB/Second as shown above.

The P2V we were running was for a legacy Line of Business application running on Windows 2003 Standard R2 that cannot run on a current OS. Not only that, the LoB does an awesome job for what is does and there is no current application out there that comes even close.

On first boot after doing a straight restore we hit a BSOD: STOP: 0x0000007B

image

A problem has been detected and Windows has been shut down to prevent damage to your computer.

Nothing in our searches turned up anything really useful other than a similar error indicating an inaccessible boot device.

Since we did not do an HIR for this P2V we went back and ran the restore process again after extracting the Hyper-V Integration Services as explained here:

The commands are as follows:

  1. msiexec /a d:\support\amd64\Windows5.x-HyperVIntegrationServices-x64.msi TARGETDIR=C:\AIPx64
  2. msiexec /a d:\support\x86\Windows5.x-HyperVIntegrationServices-x86.msi TARGETDIR=C:\AIPx86

Once we had our x86 version drivers we were able to load all of the Integration Services drivers using the Hardware Independent Restore feature of ShadowProtect. About 20-30 minutes later we had our server back online.

We then ran through the Integration Services install via the Action drop down menu to load the ISO in the VM.

All was good to go from there.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Monday, 13 June 2011

2 Node Hyper-V Cluster Update: We have MPIO Based Storage

Well, it looks as though the problems in the first run through were indeed driver related as well as process (which step goes before which) related:

image

We enabled the MPIO feature on the Hyper-V nodes after installing the updated drivers for both the Adaptec (which comes up unsigned despite Adaptec’s indicating they are) and the Intel SAS module.

  • Driver install command line:
    • pnputil –i –a Adaptec.inf
    • pnputil –i –a IntelSAS.inf
  • MPIO feature enable (TechNet):
    • Dism /online /enable-feature:MultipathIo
      • Note that this command is case sensitive.
    • mpclaim –n –i –a
      • Grab all of those disks
    • mpclaim –l –m 4
      • Set load balancing mode to “Lease Queue Length”
    • mpclaim –s –d
      • Shows the current load balancing mode:

New to Windows Server 2008 R2 SP1 Core and thus Hyper-V Server 2008 R2 SP1 is the MPIO Control Panel:

  • MPIOCPL.exe

Once we go through and configure the MPIO based storage there are a few more steps to take to configure and test the networking and then we will stand the cluster up.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Hyper-V Server 2008 R2 SP1 Cluster On Two 1U SR1695GPRX And A Promise VTrak E610sD A Go . . . Sort Of

Well, after a lot of working through the various steps required we did manage to stand up a Hyper-V Server 2008 R2 SP1 based cluster on our two node setup connected to the Promise VTrak.

The set up process needs to be refined and possibly the hardware setup may need to be tweaked.

We did manage to do a successful Live Migration of all of the VMs running on the cluster but we had a number of funky behaviours that need to be ironed out first:

  1. Disk performance was very poor.
  2. The Promise VTrak had a lot of initiator log on and log off messages.
  3. Microsoft MPIO may not have set in properly.
  4. SBS 2011 VM kept losing network connectivity.

We suspect that the primary source of the problems above are the drivers and possibly the Adaptec card.

So, we are starting fresh with an up to date driver set (we used Intel ProSet v16.2 in the last run through and now v16.3 with the same error). So, we may toss version 16 of the Intel ProSet drivers altogether if we experience the same network connectivity problems.

We suspect that the Adaptec card may not have what it takes to make this configuration run. We have a couple of LSi 3442R-E SAS cards on the way to swap out the Adaptec cards if today’s run through still has MPIO and SAS connectivity issues.

The LSi cards are due to arrive tomorrow from LSi.

Our configuration post for this setup is here: Hyper-V Two Node Cluster Setup On Intel Server Systems and Promise VTrak RAID Subsystem – Part 1.

Every post related to this trial run through will be found under the following tag since this is the base Intel Server System platform that we will be using: Intel SR1695GPRX

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Friday, 10 June 2011

Intel ProSetCL.exe Error: TeamMode VMLB is not a valid team mode

We are doing the final preparation steps prior to running the Cluster Validation Wizard tests.

We ran the Intel ProSetCL.exe utility to create a pair of VM Load Balancing teams but ended up with the following:

C:\Program Files\Intel\DMIX\CL>prosetcl team_create 5,3 Team00 VMLB

    Attempting to create team 'Team00' ...

        TeamMode 'VMLB' is not a valid team mode.  See help for supported team modes

C:\Program Files\Intel\DMIX\CL>

A quick search result came up:

Following Mark’s instructions we ran through creating the team in ALB mode and then changing it to VMLB mode:

C:\Program Files\Intel\DMIX\CL>prosetcl team_create 3,5 Team00 ALB

    Attempting to create team 'Team00' ...

        Successfully created team 'Team00'

C:\Program Files\Intel\DMIX\CL>prosetcl team_enumerate

    Number of teams currently present: 1

        1) Team00


C:\Program Files\Intel\DMIX\CL>prosetcl team_ModifyTeamInfo 1 Mode VMLB

1) Team00

        Successfully set value: 'VMLB'

C:\Program Files\Intel\DMIX\CL>prosetcl team_GetTeamInfo 1

1) Team00

    Team Information:

        Team GUID       - '{571A22AB-1FE0-4FE7-B38E-1DBED9CC8BAB}'
        Team MAC        - '001E67024719'
        Team Mode       - 'Virtual Machines Load Balancing'
        Team Name       - 'Team00'

C:\Program Files\Intel\DMIX\CL>

We now have our NIC teams ready to go.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Integrating An Intel Desktop Board DQ67EP Into An Antec ISK 300-150 Caveat

We were putting together a desktop for a client that requires a couple of small form factor units.

  • Intel Desktop Board DQ67EP Mini-ITX
  • Intel Core i5-2400S CPU
  • 4GB Kingston RAM
  • 500GB 2.5” 7200 RPM Seagate SATA
  • Slim DVD-RW Optical
  • Antec ISK 300-150 Mini-ITX chassis

When we went to install the board we found the following:

image

There is a blank where a fan should go to the right of the stock fan. The clasps protrude past the housing quite a bit.

Well, with this particular board Intel has dropped the power supply connector on that side of the board right where one of the clasps was.

So, out came the handy side cutters and off went the clasp. :)

As we can see, with the clasp gone, the board can be installed with ease.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Connecting The Two 1U Servers Dual SAS Connectors To The Promise VTrak E610sD

We now have the two systems put together, all of the firmware updated, and the RAID 10 array configured on the four 300GB 15K Seagate SAS drives.

The next task is to connect the SAS cables between each SAS connection on the 1U servers to the Promise VTrak E610sD RAID Subsystem as follows:

image

To us, the circle and diamond symbols above each port provide for a little confusion as it would seem to us that one symbol would be associated with the SAS Data IN path and the other with the OUT.

A close up shot of the VTrak SAS controller diagram:

image

Note the difference.

So, now that we have our servers physically connected to the Promise VTrak we will be firing it up, resetting it to factory defaults, and then getting our disk setup configured in preparation for the Hyper-V cluster.

  1. 1.5 GB LUN for Quorum.
  2. 96.01 GB LUN for Hyper-V cluster guest memory and configuration files.
    • Each node has 32 GB of RAM plus extra.
  3. 50.02 GB LUN for Windows 7.
  4. 50.03 GB LUN for Windows 7.
  5. 130.04 GB LUN for SBS 2011 OS partition.
  6. 130.05 GB LUN for SBS 2011 Data partition.
  7. 75.06 GB LUN for RDS on Win2K8 R2 SP1.

Note that we will initially be LUN Mapping the first two LUNs to both nodes only. This will save on the length of time the Cluster Configuration Wizard takes to test the setup.

We will leave the balance of the storage available for later.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Thursday, 9 June 2011

Intel Server System SR1695GPRX2AC RAID and SAS Integration

Here are some shots of one of the two nodes going into our entry level Hyper- V Cluster:

image

  • Intel Integrated RAID Module SRAMBSASMR

We took the stock cables that come with the SR1695GPRX setup and plugged them into the RAID controller.

Note the battery backup cable that is plugged into the RAID controller near the “bottom” relative to the picture’s up/down. It is the black braided cable with a white end.

image

The cache battery sits in its own tray that gets locked into a mount in the server chassis shown above.

Below is a shot of the back of the chassis where the Adaptec and the SAS I/O Module are installed:

image

The Intel SAS I/O Module is sitting just under the Adaptec card installed in the PCI-E slot.

Next up in the configuration process will be setting up the Promise VTrak RAID Subsystem storage for the cluster, the SAS IDs, and LUN Mapping.

From there we will be installing the Hyper-V Server 2008 R2 SP1 OS and configuring each node.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 8 June 2011

Intel Remote Management Module 3 – Error Opening Video Socket

We have hit a problem with the KVM setup in Intel’s RMM3:

image

Socket Error

Error opening video socket

This particular server was set up here in the shop using the RMM3 connection plugged into our local network. We took the server to our client’s site, plugged everything in, and subsequently went to test connectivity via one of our shop systems.

The RMM3 site came up okay but when we went to start a KVM session the above error happened.

A call into Intel’s support line did not yield any positive results either.

The proper method to try and ground zero both the RMM3 module and the BMC can be found at the bottom of the following Intel Support page:

If you need to reset to factory defaults (e.g. invalid user name or password)

A reset can be done with the syscfg utility.  Download syscfg for for the 5500 series or for the S3420GP series

  • Unzip the file and copy the folder UEFI_SYSCFG_V501_B23\ preferably to an USB key

  • Boot the server and enter the BIOS

  • Go to the Boot Manager menu and select the option to boot to EFI shell and enter

  • In the EFI shell prompt, type fs0: (0 is the device containing the sysconfig utility e.g. USB pen)

  • Browse to the directory with the sysconfig utility

  • The path has to be defined by entering: set SYSCFG_PATH fs0:\<syscfg_efi> where syscfg_efi is the folder containing all the files from the sysconfig utility

  • The settings can be reset by entering: syscfg –rfs

Given the above, we will be leaving a small amount of space on any bootable USB flash drive permanently plugged into the server and formatting it FAT32 so that utilities like this can be accessed via the EFI shell.

A post on the Intel Communities Web site was the only result in our searching:

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Tuesday, 7 June 2011

Hyper-V Two Node Cluster Setup On Intel Server Systems and Promise VTrak RAID Subsystem – Part 1.1

Okay, so the first run through on getting things together we discovered that things are not always as they seem. It is to be expected considering what we are trying to do here.

Our Intel Server System configuration that will be connected to a Promise VTrak E610sD RAID Subsystem has been changed somewhat to the following:

  • 2x Intel Server System SR1695GPRX2AC server systems.
    • Intel Xeon Processor X3470
    • 32GB Kingston ECC RDIMMs (4x KVR1066D3Q8R7S/8Gi)
    • Intel Integrated RAID AXXROMBSASMR
      • Replaced RS2BL040 as the Integrated RAID part does not take up the PCI-E slot.
      • Plugs into custom PCI-E connector near the front of the board.
    • Intel Battery Backup AXXRSBBU3
      • Replaced the AXXRSBBU7 for the RS2BL040 RAID Controller
      • Attaches to the ROMBSASMR for on board cache protection.
    • 4x 300GB Seagate 15K.7 SAS drives.
      • Drives will be configured in RAID 10 or 5 depending on drive size and client needs.
    • Intel Integrated Server RAID Module AXXSASIOMOD
      • Originally planned for two of these in one chassis. One will be installed.
      • The custom PCI-E ports at the back of the server board are not set up to allow for two modules and a dual module configuration is not available.
    • Intel RMM3LITE for remote management
      • Full out-of-band management for each node.
    • On Board NIC Configuration
      • First through Fourth NICs will be paired together and connected to the production network (two pairs).
      • Fifth NIC will also pick up an internal IP for node management.
      • Fifth NIC will also provide network connectivity for the RMM3LITE.
    • External SAS Cables
      • 2x SASx4 SFF-8470 to mSASx4 SFF-8088 cable in 2M length
        • Connects to the Intel SAS Module via SFF-8470
      • 2x mSASx4 SFF-8088 to mSASx4 SFF-8088 cable in 2M length
        • Connects to the Adaptec via SFF-8088
    • Adaptec 1045 (ASC-1045) non-RAID SAS HBA
      • Replaces the second Intel SAS I/O Module.
      • Sister card ASC-1405 with four internal SAS connectors is on the Intel THOL for the SR1695GPRX.
      • No guarantees on compatibility for this card though.

Once we get going with our testing we will test the following configurations:

  1. 2x Intel Server System SR1695GPRX2AC with 1 SAS connection (using RS2BL040 + BBU).
  2. 2x Intel Server System SR1695GPRX2AC with 2 SAS connections as per above.

Even though the ASC-1405 is on the approved list there are no guarantees that the identical card with the external connection (ASC-1045) will work in this configuration.

We are confident that the single SAS connection setup should work with the Promise VTrak E610sD configured for the SAS IDs on each Intel SAS I/O Module. This will be the base configuration we will present to our smaller clients that are interested in a High Availability option for their business.

If we are unable to get the dual SAS connection configuration to work we will be looking at some alternatives to the Intel platform to provide both the server and storage.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

For A Good Read – Microsoft’s Windows 7 Threats and Countermeasures Guide

Microsoft recently released a complete guide to the security settings in Windows 7 and Windows Server 2008 R2 that provides a full explanation of each setting.

image

The guide is available here:

The document weighs in at 387 pages so it is quite comprehensive in its explanation of the various ways and means of securing and monitoring a Windows network.

On page 47 we find:

Audit object access
This security audit policy setting enables auditing of the event that is generated by a user who accesses an object—for example, a file, folder, registry key, or printer—that has a SACL that specifies a requirement for auditing.

How many of us have had to try and figure out which user or users are “accidentally” deleting data on a client’s network? Auditing object access is the way to find out.

Check out the guide as it is well worth it to read through and also to use as a reference.

Hat Tip: Yuri Diogenes

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Monday, 6 June 2011

SBS 2008 On Dell T300 With DRAC KVM – Reboot to Windows Recovery?

For those that are familiar with how the Dell DRAC Java based KVM works, there are times during a server’s reboots that the DRAC KVM session flashes if we are working in another window with the subsequent loss of keyboard and mouse in the working window.

While running updates on a series of servers over the weekend, one of the servers came up after a reboot into the Windows Recovery window. It had booted from the SBS 2008 DVD.

Now, after a heart stopping few minutes the processes of elimination started.

The first thought was that the RAID array was no good and thus the boot into the WinRE. Just in case, we shut down WinRE and this time watched the Dell POST and BIOS messages.

When it came to the PERC 6/i the RAID controller’s BIOS indicated that all was okay.

Once the entire POST session was complete we saw the following:

Press Any Key to Boot to CD or DVD . . .

We left the KVM session alone and sure enough SBS 2008 began its boot cycle.

Put two and two together and we figured out that the KVM session must have interjected into our other window session _right at the Boot to CD or DVD_ screen.

Go figure. :)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Saturday, 4 June 2011

Hyper-V 2x 1U/2U Node Setup – Document The SAS IDs

We had a change in plans for this weekend as the SBS 2003 to SBS 2011 migration we were supposed to be running this weekend will not start until this coming week.

So, we now have a day to test run putting together a Hyper-V Server 2008 R2 cluster based on the following:

  • Two Intel Server System SR1695GPRX2AC servers.
    • Intel Xeon Processor X3470, 32GB ECC Kingston RAM, RS2BL040 RAID + BBU, 300GB 15K SAS x4 in RAID 5, dual external Intel SAS connectors (2x AXXSASIOMOD).
  • One Promise VTrak E610sD RAID Subsystem.
    • Our demo purchase unit was the E610sD but the configuration will also work with the E310sD unit as they are identical other than the number of drives the unit can hold.
  • Four Adaptec 2231500-R mSASx4 cables.

When assembling the Intel Server Systems SR1695GPRX2AC it is important to note the SAS ID and position that particular SAS Module was installed into. We would then have a label with that SAS ID installed above the SAS port on the back of the server to simplify routing the Adaptec SAS cables to the Promise VTrak.

image

With that information in hand we will be better able to figure out the LUN Mapping when configuring the Promise VTrak unit storage for the cluster nodes.

Business Opportunity

The primary goal for this huge expenditure on our part in the way of time and product purchases is to verify and test it on behalf of our clients.

If our configuration and testing proves successful then we have three network refreshes over the next few months that we will be recommending this configuration for (or 1U/2U dual Intel Xeon Hex Core E5645/E5649 based nodes).

We see this High Availability configuration as a less expensive alternative to the Intel Modular Server where the IMS just does not make business sense or financial sense.

Cluster Node Configuration

  • NODE 1: IOMOD 1 SAS Address: _____________________________
  • NODE 1: IOMOD 2 SAS Address: _____________________________
  • NODE 2: IOMOD 1 SAS Address: _____________________________
  • NODE 2: IOMOD 2 SAS Address: _____________________________

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

ShadowProtect Backup Via USB 3.0

This is pretty neat:

image

A standard 500GB Seagate 7200 SATA drive is plugged into one of the NexStar USB 3.0 docks to run a backup of the drive.

It is averaging about 90MB/Second for the job as of now. The job finished in a little over three minutes averaging 87.5MB/Second!

Compare that to the average 20MB/Second that same drive would have run on a USB 2.0 connection and we can see the time savings benefits right away for the refresh we did on this Data Mule system (previous blog post).

NOTE: We could not get the Vantec NexStar USB 3.0 dock (NST-D300S3) to work when it was plugged directly into the USB 3.0 port on the back of the Intel Desktop Board DQ67SW. We needed to plug a Vantec USB 3.0 Hub (UGT-MH430U3) into the motherboard’s port and then the NexStar into that before any drive would be picked up.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Friday, 3 June 2011

Intel Server Board S3420GPRX At Full Capacity – 32GB RAM – A Great Virtualization Platform

After deliberating over which set of 8GB sticks of RAM to purchase to outfit our single socket virtualization platforms with a full 32GB compliment we decided to go with the following part:

  • Kingston Value RAM: KVR1066D3Q8R7S/8Gi

There is also a 1333MHz version of the Intel certified RAM from Kingston but there were some questions around whether that particular model would back itself down to 800MHz which is where a memory channel will go speed wise when two quad ranked sticks of RAM are installed.

image

The screenshot above is via an Intel Remote Management Module.

  • Intel Server Board S3420GPRX with I/O Shield (previous blog post)
  • Intel Xeon Processor X3470 at 2.93GHz
  • 32GB Kingston ECC 1066MHz
  • Intel RS2BL080 RAID + Battery Backup
  • 6x 300GB 15K Seagate SAS (5x RAID 5 + 1x Hot Spare)
  • Intel Server Chassis SC5650DP with hot swap backplane.

The system is fairly quiet and is quite quick. We are expecting this configuration to more than meet our client’s needs.

One thing to note when setting up standalone virtualization boxes with the full GUI OS installed is to change the power settings to High Performance.

image

This particular configuration will be running:

  • Windows Small Business Server 2011 Standard.
    • 2x vCPUs, 16GB RAM
  • Windows Server 2008 R2 Standard in RDS/RemoteApp mode.
    • 2x vCPUs, 4GB RAM
  • Windows Server 2003 R2 Standard (P2V) running legacy LoB.
    • 1x vCPU, 2GB RAM
  • Windows 7 Enterprise x64 (one to four or five desktops).
    • 2x vCPUs, 1.5GB-2GB RAM each.

Our client is a small non-profit with 8-11 seats depending on the time of year. We are quite confident that they will be happy with their new setup once we have migrated them from their current SBS 2003 R2 Premium.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer