Wsus

Mikdilly

What version of WSUS is covered on this exam?
Is there anywhere you can get updated exam objectives?

TechJunky

Heh, ok.. I have to do it..

You are the network administrator of contoso.com. All Servers run Windows 2003 Server. Your test is on 2003 Server. If you are deploying a windows update service application which one would you use and or study for? (Please choose 2)

A. WSUS 2.0 works on Windows 2000 Server SP4 and later, though it would work on 2003 server you would have to be half brain dead to choose this one.

B. WSUS 3.0 works on Windows 2003 Server and later and is the most obvious choice.

C. Did I mention this test is testing you on Windows 2003 Server and thats why answer B would work great with this answer?

D. This is defiantly not the answer.

Please choose answer's B and C and you can then view the following link.

http://technet2.microsoft.com/windowsserver/en/library/94d1385f-4872-4c29-8822-3a4ec5e45ae41033.mspx?mfr=true

sprkymrk

I think the exam, which hasn't been updated in a while, still tests you on WSUS 2.0.
WSUS 3 didnt come out until what, a year and half ago? Anyway it would be nice if someone who has recently taken 290 could verify one way or the other.

To answer your other question, the objectives can be found here:

Skills being measured

It does mention "Manage software update infrastructure" but does not mention the version. And really, I'm pretty sure WSUS is hit hard in 291, but not much in 290.

kmfinegan1

Just recently took the 290. It did not test any any specific version, just the basic concepts of WSUS which are pretty much the same through all versions of SUS / WSUS

undomiel

It wasn't version specific for me either when I took it. Just the basic concepts as kmfinegan1 has said.

Now that I think about it in the 291 there wasn't really anything version specific either as I recall.

KGhaleon

I found TechJunky's post highly helpful in studying for this exam. 10/10

TechJunky

Sorry, I was a little worked up last night and felt like being a tool.

sprkymrk

TechJunky wrote:

Sorry, I was a little worked up last night and felt like being a tool.

I loved the WAY you answered, I just wasn't sure if it was the CORRECT answer.
Say, isn't it about this time of year that you get like 20 hours of daylight in Alaska?

TechJunky

Yes. It seems its bright all the time. Dont confuse that with sunny...

We have only had 2 days this summer over 70 degrees. Just set a state record. The last time was 1980 with 3 days over 70 degrees. This has been a lousy summer.

NetAdmin2436

I took 290 and 291 in the past couple months and yeah, I don't remember them specifying any version. Just a general WSUS question or four.

TechJunky

Lucky you... I must have had 8 sims, no WSUS on mine.

Mikdilly

Should an xp machine with sp3 be able to be seen by a wsus server using 2.0? The only computer that will show up is a 2003 server.

undomiel

Assuming your policy is set up correctly I would then check on BITS and make sure you are using 2.0. I know that I had to update the clients over here before they would recognize the WSUS server.

http://www.wsuswiki.com/WSUSFAQ

Mikdilly

While enabling the setting for Automatic Updates in the gpo, at the bottom of the box a line said:

Supported in Server 2003, xp sp1 and Win 2000 sp3.

Is a gpo required to get clients to show up in wsus? I tried deleting the gpo, did a gpupdate, the server 2003 machine continues to show in wsus but the xp sp3 machine doesn't.

Does BITS need to be installed on the xp machine? I thought i read somewhere that BITS came along with SP3.

BITS 2.0 is installed on wsus server.

undomiel

You need the gpo to point the clients toward the server. Make sure the clients can communicate with the server properly. BITS 2.0 you need installed on the clients

http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE

This contains the clientdiag.exe tool. Run this on one of the clients and see what it spits out. It will help give you some info to work with for why the client isn't updating.

Check the WindowsUpdate.log file in the windows directory on one of the clients. Check against this list: http://pagesperso-orange.fr/doc.jm/WU5-ERR.htm

It translates some of the error codes you may see.

Mikdilly

undomiel wrote:

You need the gpo to point the clients toward the server. Make sure the clients can communicate with the server properly. BITS 2.0 you need installed on the clients

http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE

This contains the clientdiag.exe tool. Run this on one of the clients and see what it spits out. It will help give you some info to work with for why the client isn't updating.

Check the WindowsUpdate.log file in the windows directory on one of the clients. Check against this list: http://pagesperso-orange.fr/doc.jm/WU5-ERR.htm

It translates some of the error codes you may see.

Thanks for your post, i'll try these.

Mikdilly

Group Policy was re-configured, it's applying to server it was setup on as Automatic updates is grayed out in control panel.

Results of clientdiag on xp sp3 machine:

C:\wsus>clientdiag

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.4.3790.5512 . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 0: Not Configured. . . . . . . . . . . . . FAIL
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
AU does not have Policy Set
AU does not have Policy Set
UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL

Press Enter to Complete

bjaxx

Mikdilly wrote:

Group Policy was re-configured, it's applying to server it was setup on as Automatic updates is grayed out in control panel.

Results of clientdiag on xp sp3 machine:

C:\wsus>clientdiag

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.4.3790.5512 . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 0: Not Configured. . . . . . . . . . . . . FAIL
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
AU does not have Policy Set
AU does not have Policy Set
UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL

Press Enter to Complete

send me what you have in place for your group policy settings

computer config/admin templates/windows components/windows update

what do you have set for specify intranet microsoft update service location

Another thing is open up IIS and right click default website and go to properties, what do you have set for IP address and TCP port?

Mikdilly

It wasn't applying the group policy because of a dns problem, it's working now, thanks for your help.

Mikdilly

Workstation is not installing or prompting to install updates. Have 9 approved updates. Pasted portion of WindowsUpdate log. Can anyone tell what these entries mean?

2008-08-02 21:59:46-0400 1020 6b8 Service Main starts
2008-08-02 21:59:48-0400 1020 6b8 Using BatchFlushAge = 26730.
2008-08-02 21:59:48-0400 1020 6b8 Using SamplingValue = 207.
2008-08-02 21:59:49-0400 1020 6b8 Successfully loaded event namespace dictionary.
2008-08-02 21:59:49-0400 1020 6b8 Successfully loaded client event namespace descriptor.
2008-08-02 21:59:49-0400 1020 6b8 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2008-08-02 21:59:49-0400 1020 6b8 Successfully initialized NT event logger.
2008-08-02 21:59:49-0400 1020 6b8 Successfully initialized event uploader 0.
2008-08-02 21:59:49-0400 1020 6b8 Successfully initialized event uploader 1.
2008-08-02 21:59:49-0400 1020 6b8 WU client with version 5.4.3790.5512 successfully initialized
2008-08-02 21:59:49-0400 1020 6b8 Service status is now SERVICE_RUNNING
2008-08-02 21:59:50-0400 1020 724 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3999A56E-7F7A-463E-A7B0-6EFFC10A4613}.bin for reading.
2008-08-02 21:59:51-0400 1908 778 Trying to make out of proc datastore active
2008-08-02 21:59:58-0400 1908 778 Out of proc datastore is now active
2008-08-02 21:59:58-0400 1020 724 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-08-02 21:59:58-0400 1020 724 Failed to obtain cached cookie with hr = 80248008.
2008-08-02 21:59:58-0400 1020 724 Failed to upload events with hr = 80248008.
2008-08-02 22:00:11-0400 1020 400 Service received logon notification
2008-08-02 22:00:11-0400 1020 400 Service received connect notification
2008-08-02 22:00:42-0400 1020 6b8 start delayed initialization of WU client
2008-08-02 22:00:42-0400 1020 6b8 Client Call Recorder finished delayed initialization
2008-08-02 22:00:42-0400 1020 6b8 Setting next AU detection timeout to 2008-08-03 02:00:42
2008-08-02 22:00:42-0400 1020 6b8 Setting AU scheduled install time to 2008-08-03 03:00:00
2008-08-02 22:00:42-0400 1020 6b8 AU finished delayed initialization
2008-08-02 22:00:42-0400 1020 6b8 AU received event of 1
2008-08-02 22:00:42-0400 1020 6b8 WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {4FB498A3-F28C-42A2-B3F5-9FC730E106FB}
2008-08-02 22:00:42-0400 1020 b0 WU client executing call {4FB498A3-F28C-42A2-B3F5-9FC730E106FB} of type Search Call
2008-08-02 22:01:02-0400 1020 b0 DownloadFileInternal failed for http://contoso-mb-wsus/wsusadmin/SelfUpdate/wuident.cab: error 0x80190191
2008-08-02 22:01:02-0400 1020 b0 IsUpdateRequired failed with error 0x80244017
2008-08-02 22:01:03-0400 1020 b0 OS Version = 5.1.2600.3.0.65792
2008-08-02 22:01:05-0400 1020 b0 Computer Brand = VMware, Inc.
2008-08-02 22:01:05-0400 1020 b0 Computer Model = VMware Virtual Platform
2008-08-02 22:01:05-0400 1020 b0 Bios Revision = 6.00
2008-08-02 22:01:05-0400 1020 b0 Bios Name = PhoenixBIOS 4.0 Release 6.0
2008-08-02 22:01:05-0400 1020 b0 Bios Release Date = 2004-04-21T00:00:00
2008-08-02 22:01:05-0400 1020 b0 Locale ID = 1033
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: iuengine.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuapi.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuauclt.exe = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuauclt1.exe = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuaucpl.cpl = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuaueng.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuaueng1.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wuauserv.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 ClientVersion: wucltui.dll = 5.4.3790.5512
2008-08-02 22:01:05-0400 1020 b0 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-08-02 22:01:05-0400 1020 b0 WU client failed Searching for update with error 0x80248008
2008-08-02 22:01:05-0400 1020 b0 Search Callback Failed, hr is 0x80248008
2008-08-02 22:01:05-0400 1020 b0 Setting next AU detection timeout to 2008-08-03 07:01:05
2008-08-02 22:01:05-0400 1020 b0 Setting AU scheduled install time to 2008-08-03 03:00:00
2008-08-02 22:01:05-0400 1020 b0 WU client calls back to search call AutomaticUpdates with code Call failed and error 0x80248008
2008-08-02 22:01:05-0400 1020 b0 WU client completed and deleted call {4FB498A3-F28C-42A2-B3F5-9FC730E106FB}
2008-08-02 22:01:11-0400 1020 b0 REPORT EVENT: {2370686F-1C88-4630-BE7B-4F111CC0A0CE} 28 2008-08-02 22:01:03-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244017 SelfUpdate Failure Software Synchronization Error: Agent failed detecting with reason: 0x80244017
2008-08-02 22:01:11-0400 1020 b0 REPORT EVENT: {44B0FFF5-28A0-4D80-AA55-FC28BB704A3D} 29 2008-08-02 22:01:05-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248008 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248008
2008-08-02 22:01:11-0400 1020 b0 Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{566A4B8B-F7F6-4BC7-A5E8-D2A225726606}.bin for writing.
2008-08-02 22:01:11-0400 1020 b0 Reopened existing event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{B6586DF9-0A9D-4F78-A36F-794BCB262759}.bin for writing.
2008-08-02 22:07:22-0400 1908 778 Out of proc datastore is shutting down
2008-08-02 22:07:23-0400 1908 778 Out of proc datastore is now inactive
2008-08-02 22:11:37-0400 1020 4d4 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3999A56E-7F7A-463E-A7B0-6EFFC10A4613}.bin for reading.
2008-08-02 22:11:37-0400 1052 43c Trying to make out of proc datastore active
2008-08-02 22:11:37-0400 1052 43c Out of proc datastore is now active
2008-08-02 22:11:37-0400 1020 4d4 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-08-02 22:11:37-0400 1020 4d4 Failed to obtain cached cookie with hr = 80248008.
2008-08-02 22:11:37-0400 1020 4d4 Failed to upload events with hr = 80248008.
2008-08-02 22:16:50-0400 1052 43c Out of proc datastore is shutting down
2008-08-02 22:16:51-0400 1052 43c Out of proc datastore is now inactive
2008-08-02 22:22:05-0400 1020 724 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3999A56E-7F7A-463E-A7B0-6EFFC10A4613}.bin for reading.
2008-08-02 22:22:05-0400 752 3e8 Trying to make out of proc datastore active
2008-08-02 22:22:05-0400 752 3e8 Out of proc datastore is now active
2008-08-02 22:22:05-0400 1020 724 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-08-02 22:22:05-0400 1020 724 Failed to obtain cached cookie with hr = 80248008.
2008-08-02 22:22:05-0400 1020 724 Failed to upload events with hr = 80248008.