|
|
All of our Windows 2008 Server machines are showing that KB948018 WSUS 3.0
SP1 is needed even though none of these servers have the WSUS roll installed.
When I click "Check for Updates" or run wuauclt /detectnow I am told that
there are no updates available and that everything is up to date.
All other updates that have been approved have installed successfully. This
one continues to stick around.
|
|
I'm experiencing the same problem.
Multiple 2008 servers, WSUS says that they need KB948018 but no update shows
up.
The only 2008 server that doesn't show this update in WSUS is the
WSUS-Server itself (already 3.0 SP1).
....Nico...
"Jordan" wrote:
[Quoted Text] > All of our Windows 2008 Server machines are showing that KB948018 WSUS 3.0
> SP1 is needed even though none of these servers have the WSUS roll installed.
>
> When I click "Check for Updates" or run wuauclt /detectnow I am told that
> there are no updates available and that everything is up to date.
>
> All other updates that have been approved have installed successfully. This
> one continues to stick around.
>
>
|
|
I've bounced this question up to the WSUS team and they're looking into it.
"Nico" <Nico[ at ]discussions.microsoft.com> wrote in message
news:4390CBD6-BFF0-474C-A3D5-B685FA36E236[ at ]microsoft.com...
[Quoted Text] > I'm experiencing the same problem.
> Multiple 2008 servers, WSUS says that they need KB948018 but no update
> shows
> up.
> The only 2008 server that doesn't show this update in WSUS is the
> WSUS-Server itself (already 3.0 SP1).
>
> ...Nico...
>
>
> "Jordan" wrote:
>
>> All of our Windows 2008 Server machines are showing that KB948018 WSUS
>> 3.0
>> SP1 is needed even though none of these servers have the WSUS roll
>> installed.
>>
>> When I click "Check for Updates" or run wuauclt /detectnow I am told that
>> there are no updates available and that everything is up to date.
>>
>> All other updates that have been approved have installed successfully.
>> This
>> one continues to stick around.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
Jordan wrote:
[Quoted Text] > All of our Windows 2008 Server machines are showing that KB948018 WSUS 3.0
> SP1 is needed even though none of these servers have the WSUS roll installed.
I think you mean KB948014 (as in the subject) rather than KB948018 (which as far
as I can tell doesn't exist).
There are two pairs of WSUS packages referencing KB948014. One pair updates
existing WSUS installations to SP1, and should only apply to the server with
WSUS installed. The other pair allow WSUS 3 SP1 to be offered as a role on a
Windows 2008 server, and these apply to all servers - except perhaps if WSUS is
already installed, and/or Server Core installations.
> When I click "Check for Updates" or run wuauclt /detectnow I am told that
> there are no updates available and that everything is up to date.
That suggests the package being detected as needed isn't approved. If you go to
the updates view and look for needed updates, you should be able to find the
package easily and check whether or not it is approved for the relevant group.
Harry.
|
|
"Harry Johnston [MVP]" <harry[ at ]scms.waikato.ac.nz> wrote in message
news:OPAJKmzLJHA.4452[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Jordan wrote:
>
>> All of our Windows 2008 Server machines are showing that KB948018 WSUS
>> 3.0 SP1 is needed even though none of these servers have the WSUS roll
>> installed.
>
> I think you mean KB948014 (as in the subject) rather than KB948018 (which
> as far as I can tell doesn't exist).
>
> There are two pairs of WSUS packages referencing KB948014. One pair
> updates existing WSUS installations to SP1, and should only apply to the
> server with WSUS installed. The other pair allow WSUS 3 SP1 to be offered
> as a role on a Windows 2008 server, and these apply to all servers -
> except perhaps if WSUS is already installed, and/or Server Core
> installations.
This being the case, and I hadn't considered it to be... it would seem to be
a serious flaw that the ROLE package installer references the KB article ID
assigned to the Service Pack!
I'll pass along this extra info to the team.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
You are right, I got the KB number wrong. The correct number is KB948014.
I checked WSUS again and the update was already approved for installation a
few days ago.
Why the servers are not downloading and installing it I am not sure. I
manually ran a check for updates on one of the servers this morning. It
again told me that there were no updates available and that everything was up
to date.
Thanks for looking into the problem.
"Lawrence Garvin" wrote:
[Quoted Text] > "Harry Johnston [MVP]" <harry[ at ]scms.waikato.ac.nz> wrote in message > news:OPAJKmzLJHA.4452[ at ]TK2MSFTNGP05.phx.gbl... > > Jordan wrote: > > > >> All of our Windows 2008 Server machines are showing that KB948018 WSUS > >> 3.0 SP1 is needed even though none of these servers have the WSUS roll > >> installed. > > > > I think you mean KB948014 (as in the subject) rather than KB948018 (which > > as far as I can tell doesn't exist). > > > > There are two pairs of WSUS packages referencing KB948014. One pair > > updates existing WSUS installations to SP1, and should only apply to the > > server with WSUS installed. The other pair allow WSUS 3 SP1 to be offered > > as a role on a Windows 2008 server, and these apply to all servers - > > except perhaps if WSUS is already installed, and/or Server Core > > installations. > > This being the case, and I hadn't considered it to be... it would seem to be > a serious flaw that the ROLE package installer references the KB article ID > assigned to the Service Pack! > > I'll pass along this extra info to the team. > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus> My Websites: http://www.onsitechsolutions.com;> http://wsusinfo.onsitechsolutions.com> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> > |
|
Jordan wrote:
[Quoted Text] > I checked WSUS again and the update was already approved for installation a
> few days ago.
Just to be absolutely clear, all four updates are approved? And have finished
downloading?
Harry.
|
|
I will check.
Do you have the exact KB numbers I should check for?
"Harry Johnston [MVP]" wrote:
[Quoted Text] > Jordan wrote:
>
> > I checked WSUS again and the update was already approved for installation a
> > few days ago.
>
> Just to be absolutely clear, all four updates are approved? And have finished
> downloading?
>
> Harry.
>
|
|
Jordan wrote:
[Quoted Text] > I will check.
>
> Do you have the exact KB numbers I should check for?
There are four update packages (two x86, two x64) listing KB948014 as their KB
number.
Harry.
|
|
Thanks, I just wanted to verify that there was only one KB number to worry
about.
All of those updates were approved previously.
It does not appear that any of the updates have installed on any of the
Windows 2008 x64 servers.
WSUS 3.0 SP1 did install on a Windows 2003 Server.
WSUS 3.0 SP1 for x64 did install on the Vista machine that I use to manage
the WSUS server.
The dynamic installer has not installed on any machine.
I have no Windows 2008 32 bit servers.
I took some screenshots of my WSUS console and posted them at
http://www.mhsaa.com/temp/screenshots/
I hope they will be helpful.
MHSIDS2 is our current Windows 2003 32bit WSUS Server
"Harry Johnston [MVP]" wrote:
[Quoted Text] > Jordan wrote:
>
> > I will check.
> >
> > Do you have the exact KB numbers I should check for?
>
> There are four update packages (two x86, two x64) listing KB948014 as their KB
> number.
>
> Harry.
>
|
|
I have the exact same problem. KB948014 are aproved and needed on all my W2K8
servers. Will not install..
Regards
"Jordan" wrote:
[Quoted Text] > All of our Windows 2008 Server machines are showing that KB948018 WSUS 3.0
> SP1 is needed even though none of these servers have the WSUS roll installed.
>
> When I click "Check for Updates" or run wuauclt /detectnow I am told that
> there are no updates available and that everything is up to date.
>
> All other updates that have been approved have installed successfully. This
> one continues to stick around.
>
>
|
|
Jordan wrote:
[Quoted Text] > It does not appear that any of the updates have installed on any of the
> Windows 2008 x64 servers.
OK, there's definitely something fishy going on. Lawrence, have you heard
anything back from MS yet?
Jordan, please look in Update File Information for the package that is detecting
as needed, and then see if the file listed (under File URI) is actually present
in the content store.
If it is, go to one of the affected servers and type:
wuauclt /detectnow
wait 30 minutes then post the contents of WindowsUpdate.log starting from the
time just before you issued the wuauclt command.
Harry.
|
|
The contents of my wsuscontent\39 folder are as follows.
08/12/2008 07:32 AM 28,738
766D385C29137DF6E33414BE268E7DD34F888E39.txt
02/18/2007 06:34 PM 142,329
8701BF4C0A2232BD3EEB954605674BB934AF3139.cab
03/21/2008 03:14 PM 86,308,464
E49552A4A96E0F2F065F39001C2F8A9FDFFEF739.exe
When I browse to the URI listed in the file information with by browser I am
prompted to download the exe file, so I am pretty sure that the servers would
have no problem accessing this location.
I will run the detectnow command and post the contents of the log file
shortly.
"Harry Johnston [MVP]" wrote:
[Quoted Text] > Jordan wrote:
>
> > It does not appear that any of the updates have installed on any of the
> > Windows 2008 x64 servers.
>
> OK, there's definitely something fishy going on. Lawrence, have you heard
> anything back from MS yet?
>
> Jordan, please look in Update File Information for the package that is detecting
> as needed, and then see if the file listed (under File URI) is actually present
> in the content store.
>
> If it is, go to one of the affected servers and type:
>
> wuauclt /detectnow
>
> wait 30 minutes then post the contents of WindowsUpdate.log starting from the
> time just before you issued the wuauclt command.
>
> Harry.
>
|
|
"Harry Johnston [MVP]" <harry[ at ]scms.waikato.ac.nz> wrote in message
news:uPOqLfuMJHA.1160[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > Jordan wrote:
>
>> It does not appear that any of the updates have installed on any of the
>> Windows 2008 x64 servers.
>
> OK, there's definitely something fishy going on. Lawrence, have you heard
> anything back from MS yet?
I have not -- just that they were looking into it and an "answer" was
forthcoming.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
Jordan wrote:
[Quoted Text] > It does not appear that any of the updates have installed on any of the
> Windows 2008 x64 servers.
Stupid question - they're not Windows Core Server installations, are they?
Harry.
|
|
No.
All of them are Windows 2008 Ent. VMs running under hyperV except one which
is a hardware based Windows 2008 Data Center Machine.
It seems like all the Windows 2008 Servers regardless of hardware or edition
is having the problem.
BTW: I will have that log for you by 9AM ET.
"Harry Johnston [MVP]" wrote:
[Quoted Text] > Jordan wrote:
>
> > It does not appear that any of the updates have installed on any of the
> > Windows 2008 x64 servers.
>
> Stupid question - they're not Windows Core Server installations, are they?
>
> Harry.
>
|
|
For easy reading I have also posted this at
http://www.mhsaa.com/temp/screenshots/windowsupdate.txt
2008-10-21 08:22:30:667 308 be0 AU Triggering AU detection through
DetectNow API
2008-10-21 08:22:30:667 308 be0 AU Triggering Online detection
(non-interactive)
2008-10-21 08:22:30:667 308 aa4 AU #############
2008-10-21 08:22:30:667 308 aa4 AU ## START ## AU: Search for updates
2008-10-21 08:22:30:667 308 aa4 AU #########
2008-10-21 08:22:30:682 308 aa4 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {71284434-C52F-4475-8B18-EBEE4D573DA7}]
2008-10-21 08:22:30:682 308 414 Agent *************
2008-10-21 08:22:30:682 308 414 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-21 08:22:30:682 308 414 Agent *********
2008-10-21 08:22:30:682 308 414 Agent * Online = Yes; Ignore download
priority = No
2008-10-21 08:22:30:682 308 414 Agent * Criteria = "IsInstalled=0 and
DeploymentAction='Installation' or IsPresent=1 and
DeploymentAction='Uninstallation' or IsInstalled=1 and
DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and
DeploymentAction='Uninstallation' and RebootRequired=1"
2008-10-21 08:22:30:682 308 414 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-10-21 08:22:30:682 308 414 Setup Checking for agent SelfUpdate
2008-10-21 08:22:30:682 308 414 Setup Client version: Core: 7.1.6001.65
Aux: 7.1.6001.65
2008-10-21 08:22:30:682 308 414 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2008-10-21 08:22:30:682 308 414 Misc Microsoft signed: Yes
2008-10-21 08:22:30:682 308 414 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2008-10-21 08:22:30:682 308 414 Misc Microsoft signed: Yes
2008-10-21 08:22:30:682 308 414 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2008-10-21 08:22:30:698 308 414 Misc Microsoft signed: Yes
2008-10-21 08:22:30:698 308 414 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2008-10-21 08:22:30:698 308 414 Misc Microsoft signed: Yes
2008-10-21 08:22:30:713 308 414 Setup Determining whether a new setup
handler needs to be downloaded
2008-10-21 08:22:30:713 308 414 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2008-10-21 08:22:30:713 308 414 Misc Microsoft signed: Yes
2008-10-21 08:22:30:713 308 414 Setup SelfUpdate handler update NOT
required: Current version: 7.1.6001.65, required version: 7.1.6001.65
2008-10-21 08:22:30:713 308 414 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65"
2008-10-21 08:22:30:776 308 414 Setup Setup package
"WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65" is already
installed.
2008-10-21 08:22:30:776 308 414 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
2008-10-21 08:22:30:792 308 414 Setup Setup package
"WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is
already installed.
2008-10-21 08:22:30:792 308 414 Setup Evaluating applicability of setup
package
"WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
2008-10-21 08:22:30:838 308 414 Setup Setup package
"WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is
already installed.
2008-10-21 08:22:30:838 308 414 Setup SelfUpdate check completed.
SelfUpdate is NOT required.
2008-10-21 08:22:31:698 308 414 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-10-21 08:22:31:698 308 414 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://mhsids2/ClientWebService/client.asmx
2008-10-21 08:22:33:401 308 414 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-10-21 08:22:33:401 308 414 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://mhsids2/ClientWebService/client.asmx
2008-10-21 08:22:34:652 308 414 Agent * Found 0 updates and 41 categories
in search; evaluated appl. rules of 326 out of 384 deployed entities
2008-10-21 08:22:34:652 308 414 Agent *********
2008-10-21 08:22:34:652 308 414 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-21 08:22:34:652 308 414 Agent *************
2008-10-21 08:22:34:667 308 ab8 AU >>## RESUMED ## AU: Search for updates
[CallId = {71284434-C52F-4475-8B18-EBEE4D573DA7}]
2008-10-21 08:22:34:667 308 ab8 AU # 0 updates detected
2008-10-21 08:22:34:667 308 ab8 AU #########
2008-10-21 08:22:34:667 308 ab8 AU ## END ## AU: Search for updates
[CallId = {71284434-C52F-4475-8B18-EBEE4D573DA7}]
2008-10-21 08:22:34:667 308 ab8 AU #############
2008-10-21 08:22:34:667 308 ab8 AU AU setting next detection timeout to
2008-10-21 14:12:29
2008-10-21 08:22:34:667 308 ab8 AU Setting AU scheduled install time to
2008-10-26 06:00:00
2008-10-21 08:22:39:652 308 414 Report REPORT EVENT:
{62025668-6139-467A-9B34-E2A21BF43E07} 2008-10-21
08:22:34:652-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2008-10-21 08:22:39:652 308 414 Report REPORT EVENT:
{39FD0159-A241-46DE-8341-C8FD7BDA531A} 2008-10-21
08:22:34:652-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2008-10-21 08:32:45:872 308 414 Report Uploading 2 events using cached
cookie, reporting URL =
http://mhsids2/ReportingWebService/ReportingWebService.asmx
2008-10-21 08:32:45:887 308 414 Report Reporter successfully uploaded 2
events.
"Harry Johnston [MVP]" wrote:
[Quoted Text] > Jordan wrote:
>
> > It does not appear that any of the updates have installed on any of the
> > Windows 2008 x64 servers.
>
> Stupid question - they're not Windows Core Server installations, are they?
>
> Harry.
>
|
|
Any new info on this one?
|
|
I am having the same issue with a server that has W2k8 (Full
installation) reporting all Windows Updates are complete but Wsus 3.0
SP1 is reporting that it needs KB948014.
In Wsus it is Approved for install, I have another Server 2k8 server
that has the update installed but it is a WSUS 3.0 SP1 Upstream server.
The other Server 2k8 server that is having the problem is just a file
server that is not a Upstream or Downstream server with Wsus service
running on it and only the Wsus client installed.
All other WSUS Approved install associations for KB948014 are reporting
Not Applicable
Any word from MS?
--
mixont70706
------------------------------------------------------------------------
mixont70706's Profile: http://forums.techarena.in/members/mixont70706.htm
View this thread: http://forums.techarena.in/server-update-service/1055407.htm
http://forums.techarena.in
|
|
Jordan wrote:
[Quoted Text] > Any new info on this one?
I'm out of ideas, I'm afraid.
Harry.
|
|
I noticed when I try to install the update manually it attempts to run the
installer for WSUS Server. If I select Full Install I am told that IIS must
be installed in order for the installer to run. If I select admin console
only the installer runs however the update still shows as "needed" in WSUS.
Since this update appears to actually install WSUS as opposed to enabling
the server in question to provide WSUS as a server roll I am simply going to
decline the update and manually install WSUS on the servers I actually want
it on.
"mixont70706" wrote:
[Quoted Text] > > I am having the same issue with a server that has W2k8 (Full > installation) reporting all Windows Updates are complete but Wsus 3.0 > SP1 is reporting that it needs KB948014. > > In Wsus it is Approved for install, I have another Server 2k8 server > that has the update installed but it is a WSUS 3.0 SP1 Upstream server. > The other Server 2k8 server that is having the problem is just a file > server that is not a Upstream or Downstream server with Wsus service > running on it and only the Wsus client installed. > > All other WSUS Approved install associations for KB948014 are reporting > Not Applicable > > Any word from MS? > > > -- > mixont70706 > ------------------------------------------------------------------------ > mixont70706's Profile: http://forums.techarena.in/members/mixont70706.htm> View this thread: http://forums.techarena.in/server-update-service/1055407.htm> > http://forums.techarena.in> > |
|
"Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message
news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com...
[Quoted Text] >I noticed when I try to install the update manually it attempts to run the
> installer for WSUS Server. If I select Full Install I am told that IIS
> must
> be installed in order for the installer to run. If I select admin
> console
> only the installer runs however the update still shows as "needed" in
> WSUS.
>
> Since this update appears to actually install WSUS as opposed to enabling
> the server in question to provide WSUS as a server roll I am simply going
> to
> decline the update and manually install WSUS on the servers I actually
> want
> it on.
KB948014 =is= WSUS 3.0 Service Pack 1.
http://support.microsoft.com/kb/948014
The only reason this update should detect is if you have WSUS installed
(or previously had some version of WSUS installed and it wasn't fully
uninstalled).
The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 system is
KB940518 and is titled "Update for Windows Server 2008 Server Manager
(KB940518)".
And, despite all of our previous discussions in this newsgroup (which took
place before I was syncing Win2008 content to my system), my WSUS Server
shows no confusion at all between these two updates.
KB940518 successfully installed to my Windows Server 2008 Web Edition
system, and was reported as "Not Applicable" on my Windows Server 2008
Standard Edition CORE installation (as is should have been, since WSUS
cannot run on a core server install), I didn't approve the update for my
Windows Server 2003 based WSUS Server, so no conclusion can be drawn there.
If anybody has indications there's a potential issue here, I'll be happy to
approve the update and observe the behavior.
KB948014 is not applicable in my entire environment, as I installed WSUS 3.0
SP1 as a baseline installation.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
I observed the issue on all (as in every single one) of our new Windows 2008
servers which have been set up for less than two months and have never had
WSUS installed.
In fact some of them don't actually do anything yet, they are simply running
with the default installation with no, I repeat NO, rolls installed as we
have not had time to migrate everything from 2003 to 2008 yet.
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message > news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com... > >I noticed when I try to install the update manually it attempts to run the > > installer for WSUS Server. If I select Full Install I am told that IIS > > must > > be installed in order for the installer to run. If I select admin > > console > > only the installer runs however the update still shows as "needed" in > > WSUS. > > > > Since this update appears to actually install WSUS as opposed to enabling > > the server in question to provide WSUS as a server roll I am simply going > > to > > decline the update and manually install WSUS on the servers I actually > > want > > it on. > > KB948014 =is= WSUS 3.0 Service Pack 1. > http://support.microsoft.com/kb/948014> > The only reason this update should detect is if you have WSUS installed > (or previously had some version of WSUS installed and it wasn't fully > uninstalled). > > The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 system is > KB940518 and is titled "Update for Windows Server 2008 Server Manager > (KB940518)". > > And, despite all of our previous discussions in this newsgroup (which took > place before I was syncing Win2008 content to my system), my WSUS Server > shows no confusion at all between these two updates. > > KB940518 successfully installed to my Windows Server 2008 Web Edition > system, and was reported as "Not Applicable" on my Windows Server 2008 > Standard Edition CORE installation (as is should have been, since WSUS > cannot run on a core server install), I didn't approve the update for my > Windows Server 2003 based WSUS Server, so no conclusion can be drawn there. > If anybody has indications there's a potential issue here, I'll be happy to > approve the update and observe the behavior. > > KB948014 is not applicable in my entire environment, as I installed WSUS 3.0 > SP1 as a baseline installation. > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus> My Websites: http://www.onsitechsolutions.com;> http://wsusinfo.onsitechsolutions.com> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> > |
|
This goes for mee too. No roles have been applyed on the servers. Its W2K8
Ent. & std x32 servers AND one W2K8 Ent. x64 server. All with the same issue
(948014 needed & will not install).
"Jordan" wrote:
[Quoted Text] > I observed the issue on all (as in every single one) of our new Windows 2008 > servers which have been set up for less than two months and have never had > WSUS installed. > > In fact some of them don't actually do anything yet, they are simply running > with the default installation with no, I repeat NO, rolls installed as we > have not had time to migrate everything from 2003 to 2008 yet. > > > > "Lawrence Garvin (MVP)" wrote: > > > "Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message > > news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com... > > >I noticed when I try to install the update manually it attempts to run the > > > installer for WSUS Server. If I select Full Install I am told that IIS > > > must > > > be installed in order for the installer to run. If I select admin > > > console > > > only the installer runs however the update still shows as "needed" in > > > WSUS. > > > > > > Since this update appears to actually install WSUS as opposed to enabling > > > the server in question to provide WSUS as a server roll I am simply going > > > to > > > decline the update and manually install WSUS on the servers I actually > > > want > > > it on. > > > > KB948014 =is= WSUS 3.0 Service Pack 1. > > http://support.microsoft.com/kb/948014> > > > The only reason this update should detect is if you have WSUS installed > > (or previously had some version of WSUS installed and it wasn't fully > > uninstalled). > > > > The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 system is > > KB940518 and is titled "Update for Windows Server 2008 Server Manager > > (KB940518)". > > > > And, despite all of our previous discussions in this newsgroup (which took > > place before I was syncing Win2008 content to my system), my WSUS Server > > shows no confusion at all between these two updates. > > > > KB940518 successfully installed to my Windows Server 2008 Web Edition > > system, and was reported as "Not Applicable" on my Windows Server 2008 > > Standard Edition CORE installation (as is should have been, since WSUS > > cannot run on a core server install), I didn't approve the update for my > > Windows Server 2003 based WSUS Server, so no conclusion can be drawn there. > > If anybody has indications there's a potential issue here, I'll be happy to > > approve the update and observe the behavior. > > > > KB948014 is not applicable in my entire environment, as I installed WSUS 3.0 > > SP1 as a baseline installation. > > > > > > -- > > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > > Principal/CTO, Onsite Technology Solutions, Houston, Texas > > Microsoft MVP - Software Distribution (2005-2009) > > > > MS WSUS Website: http://www.microsoft.com/wsus> > My Websites: http://www.onsitechsolutions.com;> > http://wsusinfo.onsitechsolutions.com> > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> > > > |
|
I have the same issue...
2 new W2K8 Entr x64 servers, both report into my WSUS.
In WSUS console: 1 says needs WSUS 3.0 SP1, the other does not.
Tracked this down to the installed/available Roles on the servers,
the 1 has- Windows Server Update Services Role available, the other
does not.
When run wuauclt /detectnow - the one does not "get" the SP1
Deleted the machine from my WSUS console.
Then ran wuauclt /resetauthorization /detectnow on the server.
It rereported into WSUS and said need the SP, but still cannot get it
to download/etc from my WSUS server.
and when run manual MS updates in IE... does not show up either.
==
Can remove the available role from the server?
--
MALeonard
------------------------------------------------------------------------
MALeonard's Profile: http://forums.techarena.in/members/maleonard.htm
View this thread: http://forums.techarena.in/server-update-service/1055407.htm
http://forums.techarena.in
|
|
addendum #2...
I compared the Updates installed between the two servers...
The one with the problem had additional...
KB940518 - Update for Windows Server 2008 Server Manager (WSUS)
"Install this update to enable full integration of Windows Server
Update
Services (WSUS) 3.0 SP1 into Server Manager on a system running Windows
Server 2008."
I uninstalled the KB.
The WSUS role is no longer listed as available.
Reran wuauclnt /detectnow.
The server no longer lists the WSUS SP as being needed.
--FINI--
--
MALeonard
------------------------------------------------------------------------
MALeonard's Profile: http://forums.techarena.in/members/maleonard.htm
View this thread: http://forums.techarena.in/server-update-service/1055407.htm
http://forums.techarena.in
|
|
I have this same error on a SCE machine running WSUS 3.0 with SP1 and when I
try applying KB940518 to the system it tells me this patch does not apply to
it. I have tried apply it to all my Windows 2008 servers reporting the same
issue and received the same response (This patch does not apply to this
system).
"Dag Arne Kirkerød" wrote:
[Quoted Text] > This goes for mee too. No roles have been applyed on the servers. Its W2K8 > Ent. & std x32 servers AND one W2K8 Ent. x64 server. All with the same issue > (948014 needed & will not install). > > "Jordan" wrote: > > > I observed the issue on all (as in every single one) of our new Windows 2008 > > servers which have been set up for less than two months and have never had > > WSUS installed. > > > > In fact some of them don't actually do anything yet, they are simply running > > with the default installation with no, I repeat NO, rolls installed as we > > have not had time to migrate everything from 2003 to 2008 yet. > > > > > > > > "Lawrence Garvin (MVP)" wrote: > > > > > "Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message > > > news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com... > > > >I noticed when I try to install the update manually it attempts to run the > > > > installer for WSUS Server. If I select Full Install I am told that IIS > > > > must > > > > be installed in order for the installer to run. If I select admin > > > > console > > > > only the installer runs however the update still shows as "needed" in > > > > WSUS. > > > > > > > > Since this update appears to actually install WSUS as opposed to enabling > > > > the server in question to provide WSUS as a server roll I am simply going > > > > to > > > > decline the update and manually install WSUS on the servers I actually > > > > want > > > > it on. > > > > > > KB948014 =is= WSUS 3.0 Service Pack 1. > > > http://support.microsoft.com/kb/948014> > > > > > The only reason this update should detect is if you have WSUS installed > > > (or previously had some version of WSUS installed and it wasn't fully > > > uninstalled). > > > > > > The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 system is > > > KB940518 and is titled "Update for Windows Server 2008 Server Manager > > > (KB940518)". > > > > > > And, despite all of our previous discussions in this newsgroup (which took > > > place before I was syncing Win2008 content to my system), my WSUS Server > > > shows no confusion at all between these two updates. > > > > > > KB940518 successfully installed to my Windows Server 2008 Web Edition > > > system, and was reported as "Not Applicable" on my Windows Server 2008 > > > Standard Edition CORE installation (as is should have been, since WSUS > > > cannot run on a core server install), I didn't approve the update for my > > > Windows Server 2003 based WSUS Server, so no conclusion can be drawn there. > > > If anybody has indications there's a potential issue here, I'll be happy to > > > approve the update and observe the behavior. > > > > > > KB948014 is not applicable in my entire environment, as I installed WSUS 3.0 > > > SP1 as a baseline installation. > > > > > > > > > -- > > > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > > > Principal/CTO, Onsite Technology Solutions, Houston, Texas > > > Microsoft MVP - Software Distribution (2005-2009) > > > > > > MS WSUS Website: http://www.microsoft.com/wsus> > > My Websites: http://www.onsitechsolutions.com;> > > http://wsusinfo.onsitechsolutions.com> > > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> > > > > > |
|
Hello,
KB948014 is WSUS 3.0 Service Pack 1. So, if you are already running WSUS
SP1, there is no need to install this.
948014 Description of the Windows Server Update Services 3.0 Service Pack 1
package
http://support.microsoft.com/default.aspx?scid=kb;EN-US;948014
Diana
Diana Smith [MSFT] <diasmith[ at ]hotmail.com>
CSS Security Team
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Harris" <JonHarris[ at ]discussions.microsoft.com> wrote in message
news:9435E0A3-8386-4AC4-95C8-B7A9FEBEA28A[ at ]microsoft.com...
[Quoted Text] >I have this same error on a SCE machine running WSUS 3.0 with SP1 and when >I > try applying KB940518 to the system it tells me this patch does not apply > to > it. I have tried apply it to all my Windows 2008 servers reporting the > same > issue and received the same response (This patch does not apply to this > system). > > "Dag Arne Kirkerød" wrote: > >> This goes for mee too. No roles have been applyed on the servers. Its >> W2K8 >> Ent. & std x32 servers AND one W2K8 Ent. x64 server. All with the same >> issue >> (948014 needed & will not install). >> >> "Jordan" wrote: >> >> > I observed the issue on all (as in every single one) of our new Windows >> > 2008 >> > servers which have been set up for less than two months and have never >> > had >> > WSUS installed. >> > >> > In fact some of them don't actually do anything yet, they are simply >> > running >> > with the default installation with no, I repeat NO, rolls installed as >> > we >> > have not had time to migrate everything from 2003 to 2008 yet. >> > >> > >> > >> > "Lawrence Garvin (MVP)" wrote: >> > >> > > "Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message >> > > news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com... >> > > >I noticed when I try to install the update manually it attempts to >> > > >run the >> > > > installer for WSUS Server. If I select Full Install I am told that >> > > > IIS >> > > > must >> > > > be installed in order for the installer to run. If I select >> > > > admin >> > > > console >> > > > only the installer runs however the update still shows as "needed" >> > > > in >> > > > WSUS. >> > > > >> > > > Since this update appears to actually install WSUS as opposed to >> > > > enabling >> > > > the server in question to provide WSUS as a server roll I am simply >> > > > going >> > > > to >> > > > decline the update and manually install WSUS on the servers I >> > > > actually >> > > > want >> > > > it on. >> > > >> > > KB948014 =is= WSUS 3.0 Service Pack 1. >> > > http://support.microsoft.com/kb/948014>> > > >> > > The only reason this update should detect is if you have WSUS >> > > installed >> > > (or previously had some version of WSUS installed and it wasn't >> > > fully >> > > uninstalled). >> > > >> > > The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 >> > > system is >> > > KB940518 and is titled "Update for Windows Server 2008 Server Manager >> > > (KB940518)". >> > > >> > > And, despite all of our previous discussions in this newsgroup (which >> > > took >> > > place before I was syncing Win2008 content to my system), my WSUS >> > > Server >> > > shows no confusion at all between these two updates. >> > > >> > > KB940518 successfully installed to my Windows Server 2008 Web Edition >> > > system, and was reported as "Not Applicable" on my Windows Server >> > > 2008 >> > > Standard Edition CORE installation (as is should have been, since >> > > WSUS >> > > cannot run on a core server install), I didn't approve the update for >> > > my >> > > Windows Server 2003 based WSUS Server, so no conclusion can be drawn >> > > there. >> > > If anybody has indications there's a potential issue here, I'll be >> > > happy to >> > > approve the update and observe the behavior. >> > > >> > > KB948014 is not applicable in my entire environment, as I installed >> > > WSUS 3.0 >> > > SP1 as a baseline installation. >> > > >> > > >> > > -- >> > > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP >> > > Principal/CTO, Onsite Technology Solutions, Houston, Texas >> > > Microsoft MVP - Software Distribution (2005-2009) >> > > >> > > MS WSUS Website: http://www.microsoft.com/wsus>> > > My Websites: http://www.onsitechsolutions.com;>> > > http://wsusinfo.onsitechsolutions.com>> > > My MVP Profile: >> > > http://mvp.support.microsoft.com/profile/Lawrence.Garvin>> > > >> > >
|
|
I am aware of that but 3 of my 2008 servers including my WSUS 3.0 SP 1 server
all report the same error and all of them will also respond that KB940518
does not apply. I am simply trying to get my SCE server and my 2008 WSUS
server to agree on what is needed by my clients and not report missing
patches that are not needed or are already installed. Sorry if I sound a bit
grumpy but it has already been a long tiring day for me and this is getting
on to 3 weeks of fighting this same issue.
Jon
"Diana" wrote:
[Quoted Text] > Hello, > > KB948014 is WSUS 3.0 Service Pack 1. So, if you are already running WSUS > SP1, there is no need to install this. > > > 948014 Description of the Windows Server Update Services 3.0 Service Pack 1 > package > http://support.microsoft.com/default.aspx?scid=kb;EN-US;948014> > > Diana > > Diana Smith [MSFT] <diasmith[ at ]hotmail.com> > CSS Security Team > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Jon Harris" <JonHarris[ at ]discussions.microsoft.com> wrote in message > news:9435E0A3-8386-4AC4-95C8-B7A9FEBEA28A[ at ]microsoft.com... > >I have this same error on a SCE machine running WSUS 3.0 with SP1 and when > >I > > try applying KB940518 to the system it tells me this patch does not apply > > to > > it. I have tried apply it to all my Windows 2008 servers reporting the > > same > > issue and received the same response (This patch does not apply to this > > system). > > > > "Dag Arne Kirkerød" wrote: > > > >> This goes for mee too. No roles have been applyed on the servers. Its > >> W2K8 > >> Ent. & std x32 servers AND one W2K8 Ent. x64 server. All with the same > >> issue > >> (948014 needed & will not install). > >> > >> "Jordan" wrote: > >> > >> > I observed the issue on all (as in every single one) of our new Windows > >> > 2008 > >> > servers which have been set up for less than two months and have never > >> > had > >> > WSUS installed. > >> > > >> > In fact some of them don't actually do anything yet, they are simply > >> > running > >> > with the default installation with no, I repeat NO, rolls installed as > >> > we > >> > have not had time to migrate everything from 2003 to 2008 yet. > >> > > >> > > >> > > >> > "Lawrence Garvin (MVP)" wrote: > >> > > >> > > "Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message > >> > > news:6C29F968-BA88-4DC6-AEA1-E9F94CDF5FAC[ at ]microsoft.com... > >> > > >I noticed when I try to install the update manually it attempts to > >> > > >run the > >> > > > installer for WSUS Server. If I select Full Install I am told that > >> > > > IIS > >> > > > must > >> > > > be installed in order for the installer to run. If I select > >> > > > admin > >> > > > console > >> > > > only the installer runs however the update still shows as "needed" > >> > > > in > >> > > > WSUS. > >> > > > > >> > > > Since this update appears to actually install WSUS as opposed to > >> > > > enabling > >> > > > the server in question to provide WSUS as a server roll I am simply > >> > > > going > >> > > > to > >> > > > decline the update and manually install WSUS on the servers I > >> > > > actually > >> > > > want > >> > > > it on. > >> > > > >> > > KB948014 =is= WSUS 3.0 Service Pack 1. > >> > > http://support.microsoft.com/kb/948014> >> > > > >> > > The only reason this update should detect is if you have WSUS > >> > > installed > >> > > (or previously had some version of WSUS installed and it wasn't > >> > > fully > >> > > uninstalled). > >> > > > >> > > The update to install the WSUS 3.0 ROLE onto a Windows Server 2008 > >> > > system is > >> > > KB940518 and is titled "Update for Windows Server 2008 Server Manager > >> > > (KB940518)". > >> > > > >> > > And, despite all of our previous discussions in this newsgroup (which > >> > > took > >> > > place before I was syncing Win2008 content to my system), my WSUS > >> > > Server > >> > > shows no confusion at all between these two updates. > >> > > > >> > > KB940518 successfully installed to my Windows Server 2008 Web Edition > >> > > system, and was reported as "Not Applicable" on my Windows Server > >> > > 2008 > >> > > Standard Edition CORE installation (as is should have been, since > >> > > WSUS > >> > > cannot run on a core server install), I didn't approve the update for > >> > > my > >> > > Windows Server 2003 based WSUS Server, so no conclusion can be drawn > >> > > there. > >> > > If anybody has indications there's a potential issue here, I'll be > >> > > happy to > >> > > approve the update and observe the behavior. > >> > > > >> > > KB948014 is not applicable in my entire environment, as I installed > >> > > WSUS 3.0 > >> > > SP1 as a baseline installation. > >> > > > >> > > > >> > > -- > >> > > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > >> > > Principal/CTO, Onsite Technology Solutions, Houston, Texas > >> > > Microsoft MVP - Software Distribution (2005-2009) > >> > > > >> > > MS WSUS Website: http://www.microsoft.com/wsus> >> > > My Websites: http://www.onsitechsolutions.com;> >> > > http://wsusinfo.onsitechsolutions.com> >> > > My MVP Profile: > >> > > http://mvp.support.microsoft.com/profile/Lawrence.Garvin> >> > > > >> > > > |
|
We too have this problem at client site. The installation is:
- One SBS 2003 Server running WSUS 3 SP 1 (and numerous other roles as per
SBS norms);
- Two Windows 2008 Servers (hereafter called W2K8) set up only as data
servers; and,
- 30 XP and 2 Vista workstations.
All the above has always run fine until the introduction of the W2K8
servers. Simply put the problem is:
- WSUS (running on SBS 2003) persists in reporting KB948014 as still
required on both the W2K8 Servers but the servers cannot be persuaded that
there are any patches needed, much less install them.
Manually checking for required patches does not help.
I suppose we can just decline the update and the nagging yellow pie segment
in the WSUS console will go away, but that's essentially sweeping dust under
the carpet. WSUS 3.1 and the W2K8 Servers should agree on whether or not a
patch is required.
|
|
I agree with this. Why ignore a problem, if one exist, that my come back to
bite us later. I would prefer it is fixed rather than ignored.
Jon
"Alatar" wrote:
[Quoted Text] > We too have this problem at client site. The installation is:
> - One SBS 2003 Server running WSUS 3 SP 1 (and numerous other roles as per
> SBS norms);
> - Two Windows 2008 Servers (hereafter called W2K8) set up only as data
> servers; and,
> - 30 XP and 2 Vista workstations.
>
> All the above has always run fine until the introduction of the W2K8
> servers. Simply put the problem is:
>
> - WSUS (running on SBS 2003) persists in reporting KB948014 as still
> required on both the W2K8 Servers but the servers cannot be persuaded that
> there are any patches needed, much less install them.
>
> Manually checking for required patches does not help.
>
> I suppose we can just decline the update and the nagging yellow pie segment
> in the WSUS console will go away, but that's essentially sweeping dust under
> the carpet. WSUS 3.1 and the W2K8 Servers should agree on whether or not a
> patch is required.
|
|
"Alatar" <Alatar[ at ]discussions.microsoft.com> wrote in message
news:43D8E249-BEA7-4C04-8679-0945F625869A[ at ]microsoft.com...
[Quoted Text] > We too have this problem at client site. The installation is:
> - One SBS 2003 Server running WSUS 3 SP 1 (and numerous other roles as per
> SBS norms);
> - Two Windows 2008 Servers (hereafter called W2K8) set up only as data
> servers; and,
> - 30 XP and 2 Vista workstations.
>
> All the above has always run fine until the introduction of the W2K8
> servers. Simply put the problem is:
>
> - WSUS (running on SBS 2003) persists in reporting KB948014 as still
> required on both the W2K8 Servers but the servers cannot be persuaded that
> there are any patches needed, much less install them.
>
> Manually checking for required patches does not help.
>
> I suppose we can just decline the update and the nagging yellow pie
> segment
> in the WSUS console will go away, but that's essentially sweeping dust
> under
> the carpet. WSUS 3.1 and the W2K8 Servers should agree on whether or not a
> patch is required.
Okay... some reality here.... WSUS is reporting a patch is needed because
the =WUA= on those machines is reporting as such. So they do agree. The
statement "the servers cannot be persuaded that there are any patches
needed" is contradictory, because it's the =servers= (W2K8) who have
actually (and erronously, I agree) reporting this update as needed. I'm not
sure what you're basing that statement on, but the mere fact that the update
is reported as "Needed" in the WSUS Console is based on the fact that the
client-side Windows Update Agent reported that as fact to the WSUS Server.
(Or, put another way, the WSUS Server is a *passive* device. It does not do
any analysis and it has very little intelligence. All of the intelligence
involved in update processing is contained in either the Windows Update
Agent, or the update installer itself.)
Now, the servers *should* be reporting KB940518 as Needed, as that's the
installer for the W2K8 WSUS Server ROLE package.
You're not the first, however, to report W2K8 servers as erronously
reporting KB948014 as needed.
I have two possible suggestions to address this (and other related)
scenario:
Create a target group for your WSUS Server as a subgroup of your master
Servers group. Place your WSUS Server in this group. Approve KB948014 ONLY
for the "WSUS Server" group.
=or=
Create a target group in WSUS for Windows Server 2008 systems. Place your
Windows Server 2008 systems in this group. Mark KB948014 as "Not Approved"
for the Windows Server 2008 systems.
=or=
Consider doing both! :-)
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
Hi Lawrence, thanks for the info.
I understand what you mean -- and hadn't realized -- when you say that "the
WSUS server is a passive device". I also will implement, failing an even
better solution resulting from this thread, one or both of your suggested
solutions.
However, your explanation shifts the location of the discrepancy somewhat
further down the pipeline but doesn't really alleviate the problem we have.
The fact remains that at this very moment the WSUS Detailed Status Report
shows (Slightly paraphrased):
samoa.<domain>.local
===============
Needed
---------
Title: Windows Server Update ..... (KB948018)
Classification: Updates
Approval: Install
Status: Not Installed
while Windows Update on samoa.<domain>.local says:
"Windows is up to date"
No new updates are available for your computer.
Note that the former also means that there is yellow pie slice on the WSUS
control display and it cannot be made to be all green without some fudge
along the lines you describe.
The issue is causing the (junior) technical people at our customer to go
nuts as they've been told that anytime they see yellow pie slices their work
of running updates / checking for machines awaiting reboot (automatic reboot
is not an option in this application) etc. is incomplete. Also, it makes them
less likely to take other yellow pie slices seriously.
Again, I realize your suggestion is a good work-around, but we have 15
customers in this boat; this particular one is the first with W2K8 Data
Servers, but you can understand that I'm not looking forward to having to set
up special target groups in a dozen different sites just because an internal
misconfiguration error in one update causes it to endlessly show as needed in
the WSUS console.
Thanks again for your comments,
Alatar
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > > Okay... some reality here.... WSUS is reporting a patch is needed because > the =WUA= on those machines is reporting as such. So they do agree. The > statement "the servers cannot be persuaded that there are any patches > needed" is contradictory, because it's the =servers= (W2K8) who have > actually (and erronously, I agree) reporting this update as needed. I'm not > sure what you're basing that statement on, but the mere fact that the update > is reported as "Needed" in the WSUS Console is based on the fact that the > client-side Windows Update Agent reported that as fact to the WSUS Server. > > (Or, put another way, the WSUS Server is a *passive* device. It does not do > any analysis and it has very little intelligence. All of the intelligence > involved in update processing is contained in either the Windows Update > Agent, or the update installer itself.) > > Now, the servers *should* be reporting KB940518 as Needed, as that's the > installer for the W2K8 WSUS Server ROLE package. > > You're not the first, however, to report W2K8 servers as erronously > reporting KB948014 as needed. > > I have two possible suggestions to address this (and other related) > scenario: > > Create a target group for your WSUS Server as a subgroup of your master > Servers group. Place your WSUS Server in this group. Approve KB948014 ONLY > for the "WSUS Server" group. > > =or= > > Create a target group in WSUS for Windows Server 2008 systems. Place your > Windows Server 2008 systems in this group. Mark KB948014 as "Not Approved" > for the Windows Server 2008 systems. > > =or= > > Consider doing both! :-) > > > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus> My Websites: http://www.onsitechsolutions.com;> http://wsusinfo.onsitechsolutions.com> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> > |
|
"Alatar" <Alatar[ at ]discussions.microsoft.com> wrote in message
news:1A1D7550-1EF2-4125-83C8-1DA5ACE391A8[ at ]microsoft.com...
[Quoted Text] > The fact remains that at this very moment the WSUS Detailed Status Report
> shows (Slightly paraphrased):
>
> samoa.<domain>.local
> ===============
> Needed
> ---------
> Title: Windows Server Update ..... (KB948018)
> Classification: Updates
> Approval: Install
> Status: Not Installed
>
> while Windows Update on samoa.<domain>.local says:
> "Windows is up to date"
> No new updates are available for your computer.
There is no KB948018 in the system.
Taking from the subject line, rather than the text (i.e. KB948014), this is
the WSUS Service Pack 1 update. There are *KNOWN* issues with the detection
logic in this package, and this newsgroup is replete with threads reporting
that the package has improperly detected on machines that do not have WSUS.
Suggestion: Create a SUBGROUP just for WSUS Servers. Approve KB948014 only
for the WSUSServers group. Better yet, BASELINE your WSUS Servers at WSUS
3.0 SP1 and DECLINE this update. Problem solved.
> Note that the former also means that there is yellow pie slice on the WSUS
> control display and it cannot be made to be all green without some fudge
> along the lines you describe.
>
> The issue is causing the (junior) technical people at our customer to go
> nuts as they've been told that anytime they see yellow pie slices their
> work
> of running updates / checking for machines awaiting reboot (automatic
> reboot
> is not an option in this application) etc. is incomplete. Also, it makes
> them
> less likely to take other yellow pie slices seriously.
This is a *training* issue. The WSUS server will ALWAYS show yellow slices
in the default view unless your organization is in the habit of approving
and installing every available update for every system -- which is the only
way you'll ever get a pie at 100% green. The pies on the WSUS Updates page
report status based on all synchronized updates -- regardless of their
approval status.
If you need pies with 100% green, then you'll need to create custom Update
Views which are based on updates Approved for specified group(s).
It's unfortunate that the junior admins are being sent on such wild goose
chases. A bit of appropriate product training would have saved a lot of
people a lot of wasted time trying to achieve the impossible.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|