How To: Set up the Intel Remote Management Module (RMM)

We install the Intel Remote Management Module (RMM) into all of our Intel server based deploys. If deploying a Tier 1 box we install theirs and make sure the KVM over IP option is enabled (license purchased).

Having out-of-band management access to a server can save critical time in the event of a server problem. We no longer need to jump in a vehicle and run down to our client’s site or have someone on-site for our remote clients.

Out of the box the RMM needs to be properly configured.

Once the server has been assembled and all of its components have had their firmware updated (Intel Download Site) we configure our RMM via the server board’s BIOS.

1. Turn the server on and F2 into the BIOS.
2. Server Management Tab.
3. BMC LAN Configuration
4. Set the IP for the RMM
1. In the shop we leave it DHCP so that we can remote into the server while here.
2. Client’s site we tend to plug directly into the Internet and give it a static IP.
5. Set the BMC DHCP Host Name
1. Convention is a bit goofy (no special characters).
2. 
6. Choose User ID and hit [Enter]
1. Choose User3
• 
2. Privilege: Administrator
3. User Status: Enabled
4. Set the user name: JungleJim
5. Set the user password: Icanacc3ssthis (x2)
7. We end up with this.
• 
8. F10 to save settings and reboot the server.

If using DHCP then check the network’s DHCP Server console for the IP that the RMM has picked up.

Open a browser and navigate to the RMM IP.

Log on with the credentials set. Barring two left thumbs we should be able to log in.

Once in we are able to launch the KVM over IP, reset the server’s power, power it up or down, and check the server’s current status.

The cost on the Intel units and Tier 1 equivalents will cover one on-site visit.

We believe that an RMM/iLO Advanced/iDRAC Enterprise and other remote management module should be a part of _every_ server configuration.

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

Windows Live Writer

Intel Server Systems Remote Management Module 4 (RMM4) Display Resolution

Once the server with the RMM4 has been set up there is an important step that needs to happen to allow the RMM4 to establish a remote KVM over IP session:

Make sure the desktop display resolution after installing the graphics driver is set to 1440x900 or 1280x1024 before logging off the desktop the final time.

Otherwise the KVM over IP session will show a black screen after clicking the Launch Console button.

This is an especially important step for all servers with an RMM2/3/4!

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

Windows Live Writer

First Look at Dell’s iDRAC 6 Enterprise – Full KVM Over IP

We are working with a new Dell R510 2U server that will be used as a host for a virtualized SBS 2011, Remote Desktop Services, SQL, and other services.

We first log into the iDRAC console via the server’s POST sequence at the console. We have initially set up the iDRAC to pull an IP from the local DHCP server until we are ready to set it up with a public IP and DNS A record.

We then set up the username and password for the iDRAC.

Once done we rebooted the system and verified that it was pulling an IP from DHCP which it was. In our Web browser we were greeted with:

Once we were logged in we were able to view all of the

When we tried to launch the KVM over IP console we received the following:

As many ways as we tried we could not get the native ActiveX to work so we flipped the setting over to Java:

We were then good to go with the Java version spooling up:

Note that the file is transferring to the local client via HTTPS.

Once the transfer was complete we had console access to the newly powered up server:

We were then good to go with flattening the default RAID 5 arrays that Dell dropped onto the H700 RAID controller to set up our RAID 10 array and run with it.

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 Host in Workgroup and Management Client in Domain Error after Password Change: You do not have the required permission to complete this task . . .

The password for the domain account just rotated at one of our client sites where we have the beginnings of a two node cluster (1 node and 1 Promise VTrak).

After changing the password for the account on the node and then for the domain account we logged off the management machine. Once we logged back in we saw:

• Hyper-V Manager: Virtual Machines
• You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer “HV_Node”

We used John Howard’s HVRemote utility to configure the node which is currently in a workgroup and the management Windows 7 desktop VM that is a member of the SBS 2011 DC running as a guest on the node.

To start with, we ran the following command on the Windows 7 desktop:

• cmdkey /add:HV_Node /user:HV_Node\FirstLast /pass
• Enter the password for 'HV_Node\FirstLast' to connect to 'HV_Node':
• CMDKEY: Credential added successfully.

We then opened the MMC that we created using the domain user’s credentials that was synchronized with the node and we saw the following in the Hyper-V Management node:

We were then good to go and manage the node and its features along with the VMs on it.

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.

One Reason For Having a Remote Management Module In All Servers

Among the many reasons, having an Intel Remote Management Module (RMM), Dell iDRAC Enterprise, HP iLO Advanced, and other add-in remote management module is the ability to have console KVM access to that box under virtually any condition.

Caveat: Obviously, no power or Internet means no access. :)

The above screenshot is a snip taken on our back shop’s desktop.

We are in the process of setting up a 2 node cluster on behalf of a client. Because we have Intel RMM3 modules in both nodes we are able to have both consoles running side-by-side so as to run _all_ configuration steps at the same time.

Thus, besides full remote management capabilities we have the ability to work on both systems without messing around with a physical KVM (the servers are just behind the shop desktop).

Having this ability reduces the possibility that a mistake would be made configuring the nodes as we can keep an eye on both systems simultaneously.

Once the OS configuration has been complete up to the domain join point, all of the cluster components will be loaded up in their boxes and delivered to our client site for the next phase of the cluster setup . . . all done remotely once the systems are fired up and the remote connection is tested.

Static IPs

Note that we request that all of our clients have at least one static IP address with our preference being for two (Certain ISP’s DHCP reservation for the IP are _not_ static IPs IMNSHO).

One IP is configured for their remote access. The other IP would be used for the RMM.

For this particular client we just got off the phone with Nucleus (our preferred DSL provider here in Alberta and BC) to add a third static IP address that the new standalone DC’s RMM will be plugged into.

Once we have finished the migration and the original SBS 2003 server has been decommissioned we will call Nucleus and release the IP associated with the original SBS server’s RMM2.

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 SP USB Flash Drive Must Have Drivers & Utilities

There are a number of different little utilities that we drop into the _Drivers folder on the USB flash drives we use to load the Hyper-V Server 2008 R2 SP1 OS with. We also put these utilities on our Windows Server 2008 R2 SP1 USB flash drives for standalone Hyper-V deployments.

• ServerNameJoin.bat
• NOTE: We drop all Server Core and Hyper-V servers into their own OU where we have all aspects of UAC disabled. Core management does _not_ work with UAC enabled.
• Change OU structure to match your own.
• Pause is there to allow us to see if the process succeeded or failed.
• MYSERVERNAME: Must be the name of the Hyper-V server.
• MYDOMAIN: Must be the name of the domain.
• DomainAdmin: Must be the name of an admin account with permissions to join the domain.
• netdom join MYSERVERNAME /Domain:MYDOMAIN.local /OU:OU=SBSServers-ServerCore,OU=Computers,OU=MyBusiness,DC=MYDOMAIN,DC=local /userd:DomainAdmin /passwordd:*
• pause
• John Howard’s HVRemote utility
• This utility makes configuring the host for domain/domain, domain/workgroup, and the other iterations a breeze.
• Chris Eck’s VHDTool utility
• We use this utility to create fixed VHDs on _new_ LUNs/LDs or ones that have been properly initialized.
• It is fast and easy.
• NOTE: The size format is in bytes so add those zeroes!
• Intel’s most recent PROSet driver and command line utility.
• Intel Download Center: Intel Server Adapters search results.
• We use the prosetcl.exe utility to configure our adapter teaming and VLAN setup for each team.
• Appropriate drivers
• Intel AXXSASIOMOD (LSI) Driver
• LSI 3442 x64 Driver
• Intel RAID driver

With the above on our flash drive we are able to jump right into configuring the Hyper-V node for clustering or standalone VM guest delivery.

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

A First Look At Intel’s RMM4

We deploy Intel’s Remote Management Modules in all of our client’s Intel Product Dealer based servers.

We just finished installing the new RMM4 into the Intel Xeon E3 based server we received at the recent TST.

• MPECS Inc. Blog: Intel TST & Microsoft TS2 Registration Now Open

Note that we needed to re-run the integrated BIOS/BMC/SDR-FRU update since we installed the RMM4 and TPM modules after installing Windows Server 2008 R2 Standard with the Hyper-V Role on the box.

The log on page:

We enabled USER3 in the BIOS, setting a username, and setting a password for the RMM4’s administrator. We then set the RMM4 to obtain an IP address dynamically for now.

We were able to log on.

There look to be some new management and alerts features built into the BMC setup:

Having reports e-mailed to us to indicate a hardware problem is definitely a plus for this setup.

The key for us though is the remote KVM abilities:

Which give us complete out-of-band management of our servers:

We require RMM, iDRAC Enterprise, iLO Advanced, or other out-of-band management in all of our server deploys as their cost is paid for by saving us one or two visits to the client’s site.

We can even _fully recover_ the server using this ability.

Note that two ISP IPs are preferred for this setup. One for the gateway device and the other for a direct connection to the RMM.

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

Providing IT Support – Out-of-Band Management Required

A paraphrase of a post to the SBS2K Yahoo Group.

In our opinion a server should _never_ be deployed without iDRAC Enterprise, iLO Advanced, Intel RMM, or other out-of-band (OOB) device. Period.

Professional grade tools for professionals.

We get:

• KVM, USB, and drive redirection to the server.
• BIOS, Firmware, RAID BIOS, etc access.
• BMC Management and sensor logs/data.
• Power cycle and reset ability (frozen OS).
• At-a-glance view of all firmware versions.

What this does for us:

• Immediate access to the _console_
• No travel time delays ... response is quick.
• No need for client intervention in most cases.

When patching or working on servers we create two connections to the box. One via RD Gateway and one via OOB. It is our preference to have physical access to that box at all times.

With the lack of a speaker on the Dell PERC RAID controllers and Open Manage may or may not e-mailing us about a failed drive we prefer to watch all reboot cycles for any anomalies.

If there is a failure, we can recover that server without any client intervention after the tier 1 tech has done their stuff.

I am sorry, but there is something totally unprofessional about, "I am sorry Mr. Customer, but could you sit at the server and see why I am locked out?" Or having to call a client’s user or contact in before or after business hours to find out why something broke. As IT Professionals we need to set the bar higher than that.

With gas at $1.10/Litre (US Gal = 3.78L, IMP Gal = 4.54L) here and rising at this time _not_ having to travel to client sites for out of scope work is a great thing.

Why?

Because they then _do_ see us when we are there for _positive_ things like rotating their backups or our bi-weekly "how are things?" visit (billable as soon as they say, "Can you fix this?" :*) ).

This aspect more than reinforces our _good_ presence in their business. Thus it strengthens our business relationship with our client contact and their users as we are seen and heard when things are good.

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

Some Thoughts On Standalone, Cluster Host, and VM Recoverability

The following was our post to the Yahoo SBS2K list that we figured would be good to share here.

The question was: How to install ESXi on a Dell using DRAC on a remote server.

QUOTE

Having looked at all of the responses to virtualizing a server on VMWare or Hyper-V, the following is where we are at in this.

We use Hyper-V exclusively. Why? It is very simple to work with.

For standalone servers we run a GUI install of Windows Server 2008 R2 along with an Intel RMM, iDRAC Advanced, iLO Advanced, etc. This gives us full management of both the hardware and the software so that question is moot. As you have indicated.

For clustering, we utilize Hyper-V Server 2008 R2. Again, it is quite simple to set up (after six months of brain busting investigation since documentation stinks for both s/w and h/w) and manage.

The native tools that come with RSAT or built into Windows Server make management and monitoring fairly straight forward.

Now, as to your dilemma we do the following on both the standalone and Hyper-V Nodes:

1. Transcend 16GB TS16GJFV30 formatted NTFS and active.
• Good read speed which is important. We only write once so no worries there.
2. Copy Hyper-V Server 2008 R2 SP1 OS contents onto the flash. The flash will remain plugged into the server for the life of the box.
• CAVEAT: If Win2K8 R2 GUI then put that on the flash.
3. Place needed OS install ISO copies onto the Flash drive.
4. Place needed drivers and firmware on the flash drive.
5. If using Tier 1 have their bootable DVD in the optical drive.
6. RMM, iDRAC ADV, iLO ADV, etc gives us boot control between Optical, USB Flash, and and RAID array with host OS.

What does this do for us?

We have full control over full host recovery, full guest recovery, and more depending on how the backups are structured. As a rule we do _not_ back up the host. It is faster to rebuild the host and either restore the guests from backup or connect existing VHDs depending on the failure.

RMM/iDRAC: We have tried USB redirection to boot the host OS and install via IP KVM and the process is just too painful. BTDT. Send them a fully configured USB Flash drive.

END QUOTE

What the above requires is at least 2 IP addresses from the ISP. One for the Internet connection used by the internal network and the other for the RMM/DRAC/iLO device that will be used to manage the server or cluster 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

Configuring An Intel RAID Controller Via RMM JViewer

We are in the process of setting up a new server remotely.

We are logged in via the Intel Remote Management Module 3 that is installed on the Intel Server Board S3420GPLX.

In order to get the mouse to a liveable control level we had to close the KVM session and set the mouse configuration to RELATIVE:

Out of the box the mouse is set to ABSOLUTE mode which does not work very well at all.

Neither the Soft Keyboard nor the system’s keyboard that we are using allow for ALT+Key presses. The Keyboard menu at the top has some control over the ALT and CTRL key presses and holds but still it was not too reliable. It just worked to allow us to choose the drives for the disk group.

As long as we remained patient and moved the mouse about in a slow and fluid manner, controlling the RAID BIOS worked . . . just barely.

And finally we had our array:

So, it just takes a bit of patience to work through the process of setting up an array or arrays via the Intel Remote Management Console.

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

HP ProLiant MicroServer Remote Access Card

We just installed the HP ProLiant MicroServer Remote Access Card (RAC).

The piece of paper that comes with the RAC makes the process of installing the card a fairly straightforward one.

However, the document does not contain the default username and password that the RAC uses out of the box.

Thanks to SBS MVP Merv Porter (Bing Search) for ferreting out the following link:

• HP Support: HP ProLiant MicroServer - How to Reset Password for ProLiant MicroServer Remote Access Card.

Out of the box the default username and password is:

• Username: admin
• Password: password

Once we had logged in we saw the following Web based console:

As noted in the screenshot above the firmware level is version 1.2.

• HP ProLiant MicroServer RAC Firmware Update Page

The update is also available on the ProLiant MicroServer’s product support page.

• HP ProLiant MicroServer Drivers and Software

Since our firmware was up to date we went right to the Security section to generate an SSL certificate CSR for the URL that will be used to connect to the RAC via the Internet.

Once we have completed all of the needed configuration on the RAC we will then have remote based out-of-band management for the MicroServer meaning full BIOS and RAID controller management along with the ability to power cycle the machine:

Once the system had finished booting we had our console session:

We install out-of-band management in all of our client’s servers whether that client is up the block or half way around the world. Having direct access to the server’s console, BIOS, firmware, and more enables us to manage the box right down to doing a full bare metal restore if ever there was a need.

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

Huawei E5836 Mobile Wi-Fi (MiFi) on TELUS

While out and about whether travelling to or between clients, or working at a client site we always use a cellular modem to connect to the Internet.

There are times when there is a need for more than one Internet connection that is provided by a USB cellular based modem.

In the US, and perhaps other locations, folks have access to a small wireless device called a MiFi (Wikipedia) or mobile Wi-Fi. Up to recently we here in Canada have not had such a device available by our mobile carriers.

Since our switch to Bell Mobility to gain access to the HTC HD7 for a new phone we called a number of different Bell stores in the Greater Edmonton Area to purchase a Novatel MiFi unit that is listed on their Web site. All of the stores indicated that they had no stock and are no longer carrying them. Bell’s customer service rep that we spoke to indicated that they were having too many issues with the MiFi unit so it was pulled.

So, we headed down to our local TELUS store and picked up a Huawei E5836 Mobile Wi-Fi device.

Once we fired it up we were able to connect to it using the default WPA code that is on a sticker on the back of the unit.

We then opened a Web browser and navigated to http://e5.home.

• Huawei E5836 default admin password: admin

We logged into the admin console:

We side-stepped the Quick Setup wizard and went about configuring our desired subnet, SSID, WPA2 key, and other settings.

Once we were finished we saw the following in our available Wi-Fi list:

• Huawei E5836 SSID: MPECS_MiFi

The unit was really easy to set up and use.

One feature with regards to the screen that is appreciated is its ability to indicate the number of clients connected to the unit.

We anticipate having a laptop or three, the Tega, and perhaps the Zune HD connected simultaneously.

This post was published using the cellular data connection provided by the E5836.

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

Intel Remote Management Module – Black Screen Or No Screen Refresh

One one of our Intel Server Systems deployments we had a really strange behaviour start to show itself after the box was delivered and set up at the client site.

Many parts of the screen were blacked out like the above. When trying to log onto the console via the RMM3’s Web management portal from our office the SBS 2008 logon page would be almost completely black.

Hitting the video refresh would sometimes work to bring things up, but the only time we could really get anywhere with the RMM3 connection was just after a reboot.

While searching for some information on the new memory available for Intel Xeon 3400 series platforms we came across a mention of the black screens for certain Linux distros.

• Bing Search: Intel RMM3 Black

Once we knew what to look for we could see that there were other results showing that there is indeed an issue and that some platforms may have received a fix while others have not.

The cause of the problem turns out to be the colour depth the physical console was set to _before_ dropping the box into the enclosure and locking it up headless.

After an update on this particular box we were able to log on using the RMM3 and bring up the Display Settings window. Sure enough, our colour depth was 24bpp:

We managed to change the bit depth to 16bit:

And, with that we now have a full SBS 2008 desktop running on an Intel Server System SR1630HGPRX!

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

SBS 2011 – Event Viewer Error – RPC server is unavailable – GP Setting Fix

When we go to remote manage a computer in Active Directory Users & Computers on an SBS 2011 network we will see:

Event Viewer

Connecting, please wait . . .

After a short pause we will then see:

Event Viewer

Event Viewer cannot connect to computer ‘Computer.Domain.LOCAL’. The error reported is: The RPC server is unavailable (sic)

When the computer management console does come up the Event Viewer looks like:

Note the hole where an icon should be to the left of Event Viewer.

To fix this we make a change in a GPO that we create and link to the Computers OU called Windows Computers Policy.

The change would be as follows:

1. Computer Configuration –> Policies –> Windows Settings –> Security Settings –> Windows Firewall with Advanced Security –> Inbound Rules
2. Right click and left click on New Rule.
• 
3. Click the Predefined radio button.
4. Choose the Remote Event Log Management option in the drop down list.
• 
5. Click Next.
6. Leave the defaults and click Next.
• 
7. Choose Allow the connection and click Finish.

Please note that it may take anywhere up to 90 minutes for the machines on the network to refresh their Computer Configuration policies.

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

Remote Desktop Connection Manager – Multiple RDP Sessions Managed Easily

This is a pretty kewl utility:

We can set up all of the servers and desktops that we manage on a regular basis in the Connection Manager and have quick and easy access to them.

• Microsoft Download: Remote Desktop Connection Manager

The RDCM can store credentials as well so we will only allow that to happen on workstations or laptops that are BitLocker enabled.

Hat Tip: Jason Miller

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

Intel Remote Management 3 A Must

Today, the cost of adding in the Intel Remote Management 3 (RMM3) module in most Intel Server Systems or server boards is very low. To our clients it is actually worth about one visit. So, why not have one installed where we can so that on-site time is reduced?

For Dell we have the DRAC i6 Enterprise, HP has the iLO with Advanced license, and there are others.

What these components do for us is provide a number of out-of-band management features. That means that we do not need an OS to work with the server.

• Console access to the OS, BIOS, firmware, and other server components.
• This is done by redirected KVM session over HTTPS.
• Ability to reset the server, power it up, or power it down.
• Check the server’s sensor logs for errors.

The initial setup of the RMM3 is done in the BIOS of the server. We enable USER3, rename the user, give it a password, and make sure that it has Administrator permissions.

When we first hit the IP address of the RMM3 we need to log on using the above created user:

The page that we will be greeted with will be a summary of the system.

From an RMM3 on an SR1625URR Server System:

From an RMM3 on an SR1630HGPRX Server System:

The FRU Information link gives us our server’s PBA (Part/Model Number), serial number, and other needed information if we are in need of support or warranty replacement.

The Server Health tab gives us a view of the server’s sensor status along with access to the server’s internal Event Log.

The SR1625URR’s sensor readings:

The SR1630HGPRX sensor readings:

Note the difference in the number of sensors between the server systems. The SR1625URR is a dual Intel Xeon Nehalem 5000 series 1U server while the SR1630HGPRX is an Intel Xeon Nehalem 3000 series 1U server.

While all of the above features are very helpful as far as keeping an eye on the server’s health and for troubleshooting purposes the key RMM3 feature is its ability to give us console access to the server’s OS.

Once we click the Launch Console button we will need to approve some Java security warnings before the redirected KVM session begins.

Once we do get our session we are “sitting in front of the server”.

This is a screenshot of the SR1625URR’s KVM session:

We currently have both 1U server’s RMM3 network ports connected to our own internal network. Once we have plugged in the needed optical disk for the OS install if needed and/or USB flash drives we no longer need to be standing at the workbench to run a fresh OS install as is the case in the above screenshot.

We can have a technician run several OS installs and post install configurations while working at their own station.

Once these servers are ready to go into production, the RMM3 Ethernet ports will be set with an ISP delivered static IP address and a GoDaddy certificate will be installed to eliminate the SSL warnings for the Web portal.

When it comes to a standard access method such as Terminal Services/Remote Desktop Services or TS/RDS via TS/RDS Gateway we are stuck if the underlying services get knocked out by an update or something breaks along the way.

Using the RMM3/DRAC/iLO to run those updates means that we do not need to be concerned about the underlying services plus we can watch the server reboot through its BIOS POST as well as RAID Controller POST status indicators.

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