?
Solved

Windows Update Services ..XP store not populated.

Posted on 2005-03-24
8
Medium Priority
?
563 Views
Last Modified: 2010-04-18
Hello,
Have recently installed WUS and am attempting to get it working,have covered most things,clients are connecting and attemptingh to download but failing.It seems that the Self Update\AU\x86\XP\EN folder has no files in it other than winhttp.cab.
Can i download the necessary files?or will a reinstall be required?
Any help would be great.

Teddy
0
Comment
Question by:mangoteddy
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
8 Comments
 
LVL 57

Expert Comment

by:Pete Long
ID: 13620762
Installing Windows Update Services

WUS needs to be on a server running IIS, it will need about 2-3Gb spare hard drive space to hold the updates, it also needs a few things installed before you can run it,

1. A database server either SQL or MSDE (MSDE is free and you can download it from Microsoft)
http://www.microsoft.com/sql/msde/downloads/default.asp NOTE I've seen papers that say it will install MSDE during the install process, but every time I tried it wouldn't start until the database service was already there.

2. Bits (Background intelligent Transfer service) Version 2
http://support.microsoft.com/default.aspx?kbid=842773

3. .Net Framework package (get this by simply doing a routine update at http://v4.windowsupdate.microsoft.com/ )


Now you need to download the WUS installer (about 79Mb) http://www.microsoft.com/windowsserversystem/wus/trial.mspx

Download and run it (WUSSetup.exe)

At the welcome screen click next
Ensure the box is ticked and check the location where you want to hold the updates (c:\wus is the default though you can choose another volume if you want to)
Next is the database bit, if you managed to get this far without installing SQL or MSDE then your doing better than I did and can tick the default (Install SQL server Desktop Engine) or like me you can choose the other option of "Use existing database" - Click Next
The following few pages set up the connection to SQL or MSDE
Now it wants to create a website choose "Create a Windows Update Services Website" Click Next
At the summary click next
When its done click finish.

Now open a WUSAdmin session, launch internet explorer and go to
http://<your_server_name_>:8530/Wusadmin/

Click Options (Top right)
Click Synchronisation options
The top box "Schedule" lets you set up when you want the server to synchronise with Microsoft - for now leave it on synchronise manually
The next box down "Products and Classifications" you will see two Change buttons - Press the one under Products

Remember WUS does things other than windows so pick the correct options for your network

When you’ve done click OK

Now click the other change button under "Update Classifications" again tick what you want - Note Service packs is NOT selected by default!

When you’re done click OK


Scroll to the bottom of the page and click the "advanced" button (under update files and languages)

Ensure Store Files locally on this server is ticked
and tick "download only when updates are approved" <-- this is much better than the old SUS that used to download everything :)
Unless you use a lot of languages then tick the box that says "Download only the updates that match the locale of this server (English)" Again this is better than SUS that downloaded the same thing in 30 languages.

When you’re done click OK

Finally Pay attention to the Proxy settings (you need HTTP and HTTPS) out for it to work, if you need to authenticate then give it a username and password to get out under.

NB If you’re using ISA as a proxy you might need to change the port number to 8080 or it may fail (took me 15 mins to work that out)

If it doesn’t save the settings automatically - click save settings.

Click Synchronise now - look down and make sure you see the current state say running (percent) and make sure it is running, this is going to take a while so time for a coffee and a sandwich..............

.........All done? remember your still set to manual so scroll to the top of the page and set "Synchronise daily at <time>" and make sure that ticked. (don't forget to save settings again)

OK now you need it to start seeing the clients before you do anything else...........



------------Now you need to configure the client PC's---------------

You can do this in two ways either by LOCAL policy that means you need to configure it on each client or through Domain Policy.

1. If you are setting this up on the Domain skip to number 2, On the client click Start > Run > gpedit.msc {enter}

2. If you are doing this on a Local PC skip to number 3, On a domain controller open administrative tools > Active directory users and computers, right click the domain (you can do this on an OU too if you wish) and select Properties > Group Policy > select the "default Domain Policy" and click Edit.

3. Navigate to Computer Configuration > Administrative Templates >Windows Components > Windows Update. On the right pane locate "Configure Automatic Updates" and right click it, select properties.

4. Select Enabled, in the first drop down box you set the action for the updates, I prefer not to frighten my users so I select "4 - Auto download and schedule the install" you can now set the schedule by default its set to 0300 which isn’t no good if all your PC's are shut down at that time (set it to 1400)

5. Click "Next Setting" > Enable > in both box's type the URL of your SUS server (i.e. http://<your_server_name>:8530). then Click "Next Setting" > if you see a "enable client side targeting properties page click "Next Setting" the next screen shout ask for a wait period after start-up for the updates to run select enables and enter 5 minutes.

6. Click "Next Setting" this comes in to play if an update requires a reboot, for an explanation click the "Explain" tab, I set this to Enable. that meant it will inform the user but not reboot.

7. Click OK exit the policy editor, you can force the policy to take effect, by clicking..

XP and server 2003: Start > run > gpupdate {enter}
2000: Start > run > SECEDIT /REFRESHPOLICY MACHINE_POLICY /ENFORCE  

You can test to see if they have applied by right clicking "My computer" > Properties > Automatic Updates, and the time you set in policy should be shown and all the options "greyed out"

----------------------------------------------------------------------

Now I suggest you create some groups – I’m my case I create a "Live" Group and a "Test" Group that way I can test the updates on a few PC's (The ones in my office) before I fire them at everyone.

Click Computers > Create a Computer Group
Select the PC's you want in that group (usual multi-select rules apply) - (It may take a while for it to find computers don’t worry)
Click "Move the selected computer"
From the drop down select the group you want to move to > click OK

----------------------------------------------------------------------


While you are waiting for population to occur click the UPDATES button.
By default it displays "Critical and security updates" remember there’s a different tab called "All Updates" select this one!

Firstly everything is set to "Detect Only" you need to select the updates you want to "Farm out" then click "Change approval" I know there are millions of them but you can do lots at a time by multiple selecting them. and change then to install (Note if you find one breaks something toy can set it to "Remove")

SET THE OPTIONS DEPENDING ON WHAT GROUP YOU WANT TO DEPLOY THE UPDATES TO

WARNING - I didn’t write the updates, Microsoft did, if you approve something that breaks your clients then moan at them not me.

----------------------------------------------------------------------


By this time your database should have started populating (It can take a few days) Click Computers
you can move the computers from "unassigned" to the groups you set up earlier.


*****Possible Problems*****
1. Update client wont update - one of the first things your clients do is try to update the update client - this may fail if it does go to the WUS server and run

c:\Program Files\Microsoft Windows Update Services\Setup

and Run installselfupdateonport80.vbs

2. Clients wont import or partially import - On the WUS server open administrative tools > Internet Information Services Manager > locate the "WUS Administration" Website > right click > Properties > "web Site" > change the TCP Port from 8530 to 80

3. Also make sure "Authenticated Users" have permissions to the C:\WUS directory on the server.
0
 
LVL 1

Author Comment

by:mangoteddy
ID: 13621590
Pete,
thanks for your response,an excellent document for anyone interested in WUS.
Having looked at one of your questions regarding WUS recently,I had managed to eradicate some of the problems I had been having .As it stands,the server is synchronising,the computers are populating,the website is on port 80 and the installselfupdateonport80 script has been run succesfully.Our GPO only needed a small modification as we had it set up to use out SUS server so that end of it is also covered.
My problem ,and maybe I should have been more detailed in my question,is that in the selfupdate\au\x86\xp\en  directory there is only the winhttp.cab file.The w2k directories are full with the correct list of files.So my clients connect to my server but find nothing to download.I get this error in my log:
2005-03-24      13:36:36-0000       824      444      DownloadFileInternal failed for http://wusserver.mydomain.net/SelfUpdate/AU/x86/XP/en/wusetup.cab: error 0x80190194
2005-03-24      13:36:36-0000       824      444      IsUpdateRequired failed with error 0x80244019
Its not a permissions error,i can get to the directory in a browser window.The list of files in the w2k directory is cdm,iuengine,wuapi,wuauclt,wuauclt1,wuaucomp,wuaucpl,wuaueng,wuaueng1,wuauserv,wucltui,wups,wups2,wusetup,wuweb.(all .cabs).I'm assuming the XP versions need to be in the XP directory, but they aren't.
Where do i get them,is it a bad WUS install or is there something else I can do,
thanks again.
0
 
LVL 57

Expert Comment

by:Pete Long
ID: 13628799
Ill check mine..............................
0
 
LVL 1

Accepted Solution

by:
mangoteddy earned 0 total points
ID: 13650984
Pete,I reinstalled WSUS and the problem is resolved.
Thanks for your comments anyway.
0
 
LVL 57

Expert Comment

by:Pete Long
ID: 13651833
.........................sorry for the late follow up Ive been off work - glad you are fixed :)
0

Featured Post

New benefit for Premium Members - Upgrade now!

Ready to get started with anonymous questions today? It's easy! Learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question