Wednesday, August 24, 2005 - Posts

If you have an OEM installation of SBS 2003, you must use a special procedure to install WSUS

-------- Original Message --------

Subject: If you have an OEM installation of SBS 2003, you must use a special procedure to install WSUS

Date: Wed, 24 Aug 2005 17:13:33 -0700

From: Tim Elhajj (MSFT)

Newsgroups: microsoft.public.windows.server.sbs

 

There is a problem with installing WSUS on SBS 2003 and this message offers a work around to this problem.

 

 

BACKGROUND: Here is a description of the problem with OEM installation of SBS 2003:

 

 

During the SBS OEM mini setup the domain name is entered by the customer and added to the AD.  This property is set in the AD as lowercase.  During WSUS installation, the instance of WMSDE is set to case sensitive.  During the setup process an attempt is made to give access to a security account which fails because it can't find the account in the AD. The check is doing a case sensitive check (since the instance of WMSDE is set to case sensitive).Since the AD has the domain in lower case and the process is looking for an upper case entry, it fails. Example: Setup process is looking for

SJMPC\IWAM_DELL-OFV7446Y6N , but the AD shows sjmpc\IWAM_DELL-OFV7446Y6N ,since the instance is case sensitive, the install fails.

 

WORKAROUND: To work around this problem, use the following special procedures for downloading the WSUS installer file, extracting WMSDE from the WSUS installer file, installing WMSDE from the command line, and then

installing WSUS.

 

To download the WSUS installer to your server

 

1.   On the computer running Windows SBS, create a folder named WSUSFiles on the local hard disk.

 

2.   Read how to register to download the latest version of WSUSSetup.exe from the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=51144.

 

3.   Answer all of the required questions on the Windows Server Update Services Registration Wizard Web page, and then click Continue.

 

4.   When the file download security warning appears, click Save.

 

5.   In the Save As dialog box, browse to the WSUSFiles folder, and then click Save.

 

 To prepare the WSUS database

 

1.   Extract the WSUS Setup files.

 

a.   Click Start, click Run, and then type C:\WSUSFiles\WSUSSetup.exe /X, where C: is the letter of your local hard disk.

 

b.   When prompted for a location to extract the files, select the WSUSFiles folder.

 

2.   Type the following command, where C: is the letter of your local hard disk, and then press Enter:

 

CD C:\WSUSFiles\wmsde

 

3.   Type the following command with consideration to the points listed below, and then press Enter:

 

Sqlrun03.msi InstanceName=WSUS BlankSAPwd=1 Reboot=ReallySuppress

DisableNetworkProtocols=1 DisableAgentStartup=1 DisableThrottle=1

 

* If you want to specify the drive letter where the database instance will be located, you must add the DataDir="Path" argument to the command line, where Path is the path to the target directory in the file system.

 

* The command line implies that your WSUS database will have a blank password. However, during the actual installation of WSUS, a randomly generated password is set. You do not need to specify a password.

 

* The command line is not case sensitive.

 

4.   Start the MSSQL$WSUS service. To do this, click Start, click Run, and then type Services.msc. Right-click MSSQL$WSUS, and then click Start. If the service is not listed, rerun the command in Step 4 of this procedure.

 

To install WSUS

 

1.   Click Start, click Run, and then type C:\WSUSFiles\WSUSSetup.exe, where C: is the letter of your local hard disk.

 

2.   On the Welcome page of the wizard, click Next.

 

3.   Read the terms of the license agreement carefully, click I accept the terms of the License Agreement, and then click Next.

 

4.   On the Select Update Source page, you can specify where the client computers get updates. If you select the Store updates locally check box, updates are stored on the server and you can select a location in the file system to store updates. If you do not store updates locally, the client computers connect to Microsoft Update to get approved updates. Keep the default option to store updates locally, either choose a location to store updates or accept the default location, and then click Next.

 

5.   On the Database Options page, keep the default options, and then click Next. Because you installed WMSDE in the previous procedure, changing the options on this page of the wizard has no effect.

 

6.   On the Web Site Selection page, specify a Web site for WSUS to use.This page also lists two important URLs based on this selection: the URL to which you will point WSUS client computers to get updates, and the URL for the WSUS console where you can configure WSUS. Keep the default option and click Next.

 

7.   On the Mirror Update Settings page, keep the default option and click Next. If you want to use multiple WSUS servers in a central management topology, see "Deploying Microsoft Windows Server Update Services."

 

8.   On the Ready to Install Windows Server Update Services page, review the selections, and then click Next.

 

9.   If the final page of the wizard confirms that WSUS installation was successfully completed, click Finish.

 

Note:  After you install WSUS, you can delete the C:\WSUSFiles folder However, do not delete the C:\WSUS folder, which is created when WSUS is installed. [Susan's note..or whereever you stuck the WSUS.  You may NOT want to place it on C: in case you are tight on space.]

At this rate Dr. Tom will be an honorary SBSer

 The SBS community may just have a new family member today.  Dr. Tom just may be our next SBSer.  And this link has been flying around the communities today and making a buzz.  Check it out.....

Dr. Tom of isaserver.org may be an SBSer yet....

I've always joked...that if it's on my box.... it's a family member.  .

 

Just about ready to rant.. I mean talk...

On the podium at the Ilinois Business and Tech show about to talk about SBS 2003 to a bunch of CPAs....

...oooh I'm going to have fun....

 

 

So.. how about telling your CPA clients about the MS accounting network?

So Elijah in my comments to the blog writes...

 re: ...not the success they thought it was going to be...

What blows my mind away is why doesn't every small business accountant in the US jump on this partnership?  Signing up for the Microsoft Accounting Network and its corresponding Action Pack seems like a no brainer to me.  You are getting 'tons' of “free” ($299) that allows you to upgrade ten of your ancient technologies to Windows XP.  Not only that, there is a form of Software Assurance built into the Action Pack.  It seems like you can do this with little or no obligations to Microsoft, other than keeping the Action Pack coming.  Is there some sort of loop hole that I am missing?

No kidding Elijah...I don't get it either ...and that's exactly what I said today in the presentation to the audience.  If you are a CPA, help your clients with Accounting software [who doesn't these days] why wouldn't you be a part of this program?