So if you are seeing this…try the following…

If you are installing SBS sp1 on an OEM machine and you get a message that says “

This computer cannot be upgraded to OEM version of small business server

First try this:

HKLM\software\microsoft\smallbusinessserver\IsRunFromWeb and set the value to Decimal 1 i.e. 0x1.

This can happen on an OEM install of SBS if the following file is the retail version.
C:\program files\Microsoft integration\windows small business server 2003\suiteinfo.dll

To see if you have the retail version of the file: When you view the properties of this file, sometimes you get a resource tab.  On the resource tab, expand string  If it is OEM version, it will have an entry that says 74995-OEM.  If it is the retail version, it will say just 74995

(I also opened it up in notepad and saw in my version of it…this so I could tell my SBS OEM thought it was an OEM and had the right dll file)



Usually this will happen if it has OEM PID in the registry and the file version of sutieinfo.dll is retail.  In this case replace the retail version with the OEM one and rerun the service pack.

So in the mailbag today comes the request that someone is “looking for “THE” this is how you install sbs 2003 sp1…any ideas?  All I see is bits and bobs here and there

Haven’t seen this, have you?

How to install Service Pack 1 for SBS 2003:

That’s THE how to install SP1 on a SBS box be all and end all documents.

Now these days we have been installing Exchange 2003 sp2 instead of SP1 with success as you get the 75 gig mail storage [18 gig default, bump up the rest via reg key]

Readme for Premium got updated for these:

After you have installed Windows SBS SP1 and you try to reinstall a Windows SBS component, you receive the message, “The drive contains a disc for Windows Small Business Server 2003 with no service packs…”

After you have installed Windows SBS SP1 and you try to install ISA Server 2004, you receive the error message, “The wizard cannot install ISA Server 2004 because the server is not running the ……..

Release notes got updated for the first message….

Readme for Standard got updated

SP1 for Windows SBS 2003 cannot be applied to evaluation versions of Windows SBS 2003 ……



Now if you were a Microsoft partner…. you’d be able to visit the Partner newsgroups and find these answers to top issues:

…now then…if you install SBS servers…why aren’t you a partner? Better yet…why not a Small Business Specialist?

1. Store.exe memory consumption alerts

After installing SBS 2003 SP1, a performance monitoring program that you run
may generate an alert or a report to indicate that the Store.exe process
uses much more memory than it did before you installed SP1. Typically, the
monitoring program reports that the Store.exe process uses more “private
bytes” memory than it used before you installed SP1.

This is actually the same issue described here:

867628 Monitoring programs report that the Store.exe process consumes

The problem is that the SBS SP1 package is not disabling the alert as
expected. So, when a customer goes through the process of installing
Exchange SP1 as a requirement for SBS SP1, it will start triggering these
errors that are not taken care by the SBS SP1.

If you re-run the Monitoring Configuration Wizard, the alert is going to be
disabled. Or disable the alert manually from the Monitoring page.

2. CEICW fails with error 0x800725ec in the CEICW log (ICWLOG.TXT)

When running the CEICW after installing SBS SP1 and ISA 2004, the wizard may
fail with the following errors in the ICWLOG.TXT:

Error 0x800725ec returned from call to Creating A record for publishing().
Error 0x800725ec returned from call to
Error 0x800725ec returned from call to Creating ISA2k4 Web publishing
Error 0x800725ec returned from call to
Error 0x800725ec returned from call to Creating Web publishing rules().
Error 0x800725ec returned from call to CStingrayCommit::CommitEx().
*** Enabling SSL with ISA returned ERROR 8000ffff
*** CCertCommit::EnableSSL returned ERROR 8000ffff
*** CCertCommit::CommitEx returned ERROR 8000ffff
The Firewall Configuration and the Secure Web Configuration will fail in the

The error 0x800725ec means:


The problem here is that the PUBLISHING record in DNS is a CNAME instead of
the expected A record.

Remove the CNAME Publishing record in DNS and create a new A record for
Publishing pointing to the proper internal IP.

3. CEICW may fail with error c0040393 in the CEICW log (ICWLOG.TXT)

When running the CEICW after installing SBS SP1 and ISA 2004, the wizard may
fail with the following errors in the ICWLOG.TXT:

Saving changes and restarting services returned ERROR c0040393
Publishing CompanyWeb through ISA2k4 returned ERROR c0040393
CCertCommit::EnableSSL returned ERROR c0040393
CCertCommit::CommitEx returned ERROR c0040393

The Firewall Configuration and the Secure Web Configuration will fail in the

This issue may occur if  the following  policy settings are not assigned to
the Network Service account on the domain controller:

– Adjust memory quotas for a process
– Generate security audits
– Log on as a service
– Replace a process level token

The Network Service account must be added to the policy settings in the
list. This issue may occur if Group Policy settings that were applied at the
domain level have modified the policy settings for the Network Service
account on the domain controller. This issue may occur after you promote a
member server to a domain controller, or on a migration from a Windows 2000
network where SBS 2003 was joined to the 2000 domain.

To resolve this issue, make sure that the Network Service account is added
to the following policy settings on the domain controller:

– Adjust memory quotas for a process
– Generate security audits
– Log on as a service
– Replace a process level token

4. SP1 reports error when Outlook 2003 files are missing from clientapps

When trying to setup SBS 2003 SP1, we may see the following symptoms:

1.  You will see the following service pack install error – “Windows Small
Business Server Service Pack 1 Setup has encountered an error. For more
information, review the most recent entry in the setup error log in
C:\Program Files\Microsoft Inetgration\Windows Small Business Server
2003\logs\setup.log. Then correct the error and run the Service pack 1 setup

2.  Setup.log will show all successes / no failures

3.  Errorlog.txt will show “Microsoft Office outlook 2003 (ServicePack1):
[2] : Error applying outlook sp1 MSP file to AIP

4.  Could be a slight variant of the errorlog.txt message depending on the
initial cause (not installed, removed, etc)

5.  You will also see the following in the KB885918.log

109.468: —- Old Information In The Registry ——
109.531: Source:C:\ClntApps\ClientApps5\Office2003_SP1\SETC.tmp
109.609: —- New Information In The Registry ——
109.609: Source:C:\ClntApps\ClientApps5\Office2003_SP1\SETC.tmp
109.609: DoInstallation: A reboot is required because RebootRequired=1 was
specified in the inf.
109.609: DoInstallation: A reboot is required because the
ProcessesToRunAfterReboot inf section was non-empty.
109.609: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
109.609: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
109.609: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to
751.656: RebootNecessary = 1,WizardInput = 0 , DontReboot = 1, ForceRestart
= 0

Outlook deployment files were not installed, uninstalled, moved, or just

1.  Install the client apps Outlook deployment.

2.  Correct the reg path to point to the proper location.

3.  Safely ignore the error and verify SP1 did install properly by:

a) All successes in the setup.log
b) The registry value states

5. Be prompted to insert CD with SBS 2003 SP1 when trying to reinstall a SBS

When trying to reinstall a SBS component, you are prompted to insert CD with
SBS 2003 SP1 and the original SBS 2003 CDs do not work.

SBS 2003 SP1 setup was downloaded from the web.

Check to see if the HKLM\Software\Microsoft\SmallBusinessServer\IsRunFromWeb
= 0x2 and if so, extract the SBS 2003 SP1 package and point it to the

6. Clients unable to get DHCP address after installing ISA 2004

Clients may no longer be able to get DHCP addresses assigned by SBS’s DHCP
server after ISA 2004 is installed.

The broadcast address for the subnet is not included in the Internal network

Check in the ISA MMC/ServerName/Configuration/Networks then on the Networks
tab, look at the Name Internal Address Ranges. If it’s not there, for
example range is up to .254 instead of .255, right click and select
Properties/click on the Addresses tab to change/correct the entries.

A email from the mailbag today reminded me that we need to revisit a few things about SBS 2003 sp1

  • On Dell boxes, as long as you either (a) have Dell Open Manage 4.4 [located here] or (b) remove Dell Open Manage we no longer are waiting on that piece that was holding us up from installing SP1 on Dell’s.

  • Charlie Anthe [SBS release manager] notes in a blog posting that there is a possible Blue Screen issue on Dell OEM boxes but honestly I haven’t seen a lot of dead bodies out here BSODing and for another… remember that any issue during the application of a service pack is a free call to either client machines if you are a partner or your own machine if you are a DIYer.

  • READ

  • You heard me READ.  We find that many of the issues are due to the fact that people don’t realize this isn’t a ‘one patch’ that installs on the system, but a collection of 5 patches.  After all we ARE a collection of software pieces right?  So naturally our service pack is made up of parts.  Then we put together a document of all the wacky things that might go wrong that we found along the way.  Personally I found that if you pretty much stuck to the way to install SBS you’ll do just fine.  In our MVP ranks we had some pretty beat up beta boxes so what you see there is a result of putting it on some messy boxes.

  • We totally blew it on the ‘don’t install Windows 2003 sp1’ messenging.  You see because we HAVE to install Windows 2003 sp1 first before the rest of the parts you DO install that service pack.  So for that we in the community screwed up. 

  • Don’t panic.  I’ll say it again.  DON’T PANIC.  No matter if the worst happens [Sharepoint won’t load, monitoring is a bit mixed up], I haven’t seen a box yet that hasn’t been able to be fixed up.  That said, don’t go into this service pack thinking it’s a trivial matter.  Ensure you have backed up your system.  If you are a DIYer unsure of this process, this is the time to call in someone who is versed in this.  Oh…how about … a Small Business Specialist.  Yup we now have a special credential for those crazed enough to be doing small businesses.  Seriously, as a person who I would call in the advanced stages of insanity of a DIYer, if you don’t feel confortable picking up a phone and calling Microsoft for help, maybe you should consider calling in an IT Pro that handles SBSers all the time.

So folks… those that are on OEMs or support OEMs?  Always remember, no matter what happens, we’ll leave the lights on in the newsgroup and listserves and be there for you.


Just a heads up to everyone…. the Windows Update/Microsoft Update that may be offering up to your servers right now that will have the v6 in it’s address, it is offering up to you the Windows 2003 sp1…that is NOT SBS 2003 sp1. It is merely the first part of what you need for a fully complete service pack.

Remember that SBS 2003 sp1 is

  • Windows 2003 sp1

  • Sharepoint sp1

  • Exchange sp1

  • XP sp2

  • and finally..the SBS specific parts of the patches

You can’t get ISA server or SQL server sp4 any other way than ordering the cdrom.

So if you’ve downloaded and installed it…just go to the SBS page and finish the SP installation


Got a lot of servers [or a lot of SBS servers] that you want to block Windows 2003 sp 1 from [so your clients/customers won’t automatically click and install it until YOU are ready?]

Click here for tools to block the deployment of Windows 2003 sp1 on automatic update on July 26, 2005 until March 30, 2006.

“While recognizing the security benefits of Windows Server 2003 Service Pack 1 (SP1), some organizations have requested the ability to temporarily disable the automatic delivery of this update through Automatic Updates (AU) and Windows Update (WU).”

Before anyone asks… I ‘think’ us SBSers will be blocked from AU offering up Windows 2003 sp1….but I think I’ll go check…I’ll let you know….

One of the very confusing things about this service pack is when you go to download it and you blondely click the download button it blondely only downloads the last patch of the series and does not direct you to install the five parts.  And of course if you don’t read..which of course none of us geeks do, when you go to install this … it says you need Windows 2003 sp1 first.

No wonder everyone is getting confused about this….

Order the cdroms…trust me.. you life will be a lot easier.  Then follow the how to on the site.

Someone in the newsgroup asked about that ‘thingy’ in the corner that is now in the system tray after the application of the Service pack.  Well for one, if you are just NOW noticing it because you never had it before…you kinda missed a critical patch along the way as this is caused by an update that came down on Windows Update ages ago.  KB 829358 is the one that brings down that \\ thingy.  But not to worry you can either just get used to it down there or delete it off.

I guess I’m a lazy bone because I’ve just ignored it. It’s only a cosmetic issue and you easily remove it from the start tray…but Windows did that one to us a long time ago… so if you’ve never had that before now… you might want to remember that second Tuesday of the month is Patch Tuesday and put in place a Patch Management process to ensure that you are getting patches on that Second Tuesday of each month.

Struck up a conversation in the plane back from Texas as a matter of fact with the lady who sat next to me who was in charge of application updates for her firm and she didn’t know that second Tuesday was patch Tuesday.  Guess I should warn people when they sit next to me on airplanes that you might get geek speak for the plane ride.