Installing System Center Essentials in SBS 2003 R2 Standard Edition
There has been a good deal of Community conversation about the suitability of System Center Essentials 2007 for installation on Small Business Server 2003 SP1 / R2 and while I maintain the opinion that all SCE 2007 installs in SBS 2003 Networks should be done on dedicated Windows 2003 R2 Standard Edition servers, this build has (so far) not shown to cause significant issues with the Features or Functionality of the SBS 2003 R2 Server.
UPDATE: 1/1/2008 Also Tested on Dual NIC behind a Local Router
This guide has been written with a Default Installation of an un-patched version of SBS 2003 R2 as the base. The configuration is Single NIC with Local Router.
This build does not meet all the prerequisites of a SCE 2007 Installation but does allow me to demonstrate the flexibility of the Install as this entire build was conducted with only one reboot and all items were guided by the Installation Process or the System Center Managed Forums without aborting the Installation.
 | Launch Setup from a Patched SCE 2007 Installation Source |
 | The Installer detects the absence of MS XML Core Services 6.0 and Launches the install automatically |
 | Press Next |
 | Accept the License Agreement;
Press Next |
 | Confirm the Registration Details;
Press Next |
 | Press Install |
 | Press Finish |
 | The SCE 2007 Installer will continue automatically
Press Next |
 | Select the Upgrade WSUS check box;
Press Next |
 | The Installation Prerequisites will fail;
Press the More button next to the .NET Framework 3.0 Components |
 | The Prerequisite Details dialog appears;
Click the X86 version download Link |
 | When the download completes press Open |
 | Carefully read through the license agreement (go on humour me);
Click I have read and ACCEPT the terms of the License Agreement;
We all want to help make better products so check the Send anonymous information box;
Click Install |
 | Press Exit |
 | Your feedback is automatically sent to Microsoft |
 | Click Recheck, Notice the .NET failure is now cleared;
Press the More button next to the Checking for Pending Reboots item |
 | The resolution says to Reboot the Machine;
In every SBS based build I have conducted this DOES NOT clear the issue |
 | Run Regedit.exe;
Delete the HKLM\System\CurrentControlSet\
Control\Session Manager\
PendingFileRenameOperations key |
 | Press Yes |
 | The Installation Prerequisites test now passes;
Press Next |
 | Now I'm pretty sure you didn't read the .NET Framework EULA, Read this one and click "I have read, understood and agree to ..";
Press Next |
 | Check the Name and Organisation Details are correct;
Press Next |
 | Press Next |
 | Choose a Database location, I put mine with the other SBS Database data files;
Press Next |
 | The Installation will now block due to the Self Signed Certificate on the Default web |
 | Select the Default web and Right Click Properties |
 | Select the Directory Security Tab;
Click Server Certificate |
 | Click Next > |
 | Click Remove the current certificate;
Click Next > |
 | Click Next > |
 | Click Finish |
 | Choose an Administration Account;
Click Next > |
 | Select all three check boxes, (why not help improve this great product?);
Click Next > |
 | Click Install |
 | The Installation continues, (not a cut lunch and a 6 Pack, but certainly go make coffee, you deserve it) |
 | Click I do not wish to check for updates, (I modify WSUS to use our upstream WSUS server to Sync the current updates before shipping, we set it back when delivered);
Click Next > |
 | Click OK |
 | Uncheck Launch the Essentials Console and Complete the configuration process, (we need to put back the self signed certificate first);
Click Finish |
 | Click No |
| Select the Default web and Right Click Properties |
| Select the Directory Security Tab;
Click Server Certificate |
| Click Next > |
 | Click Assign and existing certificate;
Click Next > |
 | Click Next > |
 | Click Next > |
 | Click Next > |
 | Click Finish |
 | Reboot the server |
Known Issues
These are the Issues experienced post Installation
WSUS no longer gives a Green Check
Windows Small Business Server (Windows SBS) Update Services is not running because it automatically turns off if you customize Windows Server Update Services (WSUS). For a list of specific settings that cause Windows SBS Update Services to turn off, see the Microsoft Web site. Even if WSUS is managing updates for your network, the accuracy of the status in the Windows SBS monitoring report or on the Update Services home page cannot be guaranteed. To use Windows SBS Update Services, reverse the changes that you have made to WSUS or reinstall Windows SBS 2003 R2.
WSUS Synchronisation Fails
Content download has failed. BITS service is not starting or is stopping during downloads.
- Open a command window.
- Type sc config bits start= auto
- Type net stop bits & net start bits
- Type net stop wsusservice & net start wsusservice
- Start WSUS 3.0: Click Start, click Administrative Tools, then click Microsoft Windows Server Update Services v3.0.
- Click Synchronization Results.
- In the Action pane, click Synchronize Now