Unable to detect updates from WSUS

The computers that connect to my WSUS can't seem to detect that they need
updates

The server console shows that the computers have sent reports and that they
are requiring some updates.

If I go on one of those clients and type in "wuauclt.exe /detectnow", it is
not getting any updates. I have been trying to find a solution for the past 2
days without any luck.

I have tried deleting %windir%\softwaredistribution, no luck there either.

Here is a copy of my %windir%\windowsupdate.log

Anyone has a clue what could be the cause of this?

2008-02-28 09:20:13:868 4168 e70 AU Triggering AU
detection through DetectNow API
2008-02-28 09:20:13:868 4168 e70 AU Triggering
Online detection (non-interactive)
2008-02-28 09:20:13:868 4168 380 AU #############
2008-02-28 09:20:13:868 4168 380 AU ## START ##
AU: Search for updates
2008-02-28 09:20:13:868 4168 380 AU #########
2008-02-28 09:20:13:868 4168 380 AU <<## SUBMITTED
## AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
2008-02-28 09:20:13:868 4168 8cc Agent *************
2008-02-28 09:20:13:868 4168 8cc Agent ** START **
Agent: Finding updates [CallerId = AutomaticUpdates]
2008-02-28 09:20:13:868 4168 8cc Agent *********
2008-02-28 09:20:13:868 4168 8cc Agent * Online =
Yes; Ignore download priority = No
2008-02-28 09:20:13:868 4168 8cc Agent * Criteria
= "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and
IsAssigned=1 or IsHidden=0 and IsPresent=1 and
DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and
IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and
RebootRequired=1 or IsHidden=0 and IsInstalled=0 and
DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2008-02-28 09:20:13:868 4168 8cc Agent *
ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-02-28 09:20:13:868 4168 8cc Misc Validating
signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w uident.cab:
2008-02-28 09:20:13:868 4168 8cc Misc Microsoft
signed: Yes
2008-02-28 09:20:13:868 4168 8cc Misc Validating
signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w uident.cab:
2008-02-28 09:20:13:883 4168 8cc Misc Microsoft
signed: Yes
2008-02-28 09:20:13:883 4168 8cc Misc Validating
signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w sus3setup.cab:
2008-02-28 09:20:13:883 4168 8cc Misc Microsoft
signed: Yes
2008-02-28 09:20:13:899 4168 8cc Setup ***********
Setup: Checking whether self-update is required ***********
2008-02-28 09:20:13:899 4168 8cc Setup * Inf
file: C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w sus3setup.inf
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\cdm.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuapi.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuapi.dll.mui: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuauclt.exe: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuaucpl.cpl: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuaueng.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuaueng.dll.mui: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wucltui.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wucltui.dll.mui: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wups.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wups2.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
required for C:\WINNT\system32\wuweb.dll: target version = 7.1.6001.65,
required version = 7.1.6001.65
2008-02-28 09:20:13:899 4168 8cc Setup *
IsUpdateRequired = No
2008-02-28 09:20:15:649 4168 8cc PT +++++++++++
PT: Synchronizing server updates +++++++++++
2008-02-28 09:20:15:649 4168 8cc PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://<ServerURL:Port>/ClientWebService/client.asmx
2008-02-28 09:20:17:680 4168 8cc Agent WARNING:
Failed to evaluate Installed rule, updateId =
{03FF1EBE-C1CF-4DBA-ACDA-5C3BFBD9133D}.100, hr = 80041017
2008-02-28 09:20:18:384 4168 8cc PT +++++++++++
PT: Synchronizing extended update info +++++++++++
2008-02-28 09:20:18:384 4168 8cc PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://<ServerURL:Port>/ClientWebService/client.asmx
2008-02-28 09:20:19:040 4168 8cc Agent * Found 0
updates and 34 categories in search; evaluated appl. rules of 807 out of 1044
deployed entities
2008-02-28 09:20:19:040 4168 8cc Agent *********
2008-02-28 09:20:19:040 4168 8cc Agent ** END **
Agent: Finding updates [CallerId = AutomaticUpdates]
2008-02-28 09:20:19:040 4168 8cc Agent *************
2008-02-28 09:20:19:056 4168 180 AU >>## RESUMED
## AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
2008-02-28 09:20:19:056 4168 180 AU # 0 updates
detected
2008-02-28 09:20:19:056 4168 180 AU #########
2008-02-28 09:20:19:056 4168 180 AU ## END ##
AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
2008-02-28 09:20:19:056 4168 180 AU #############
2008-02-28 09:20:19:056 4168 180 AU AU setting next
detection timeout to 2008-02-29 11:16:14
2008-02-28 09:20:19:056 4168 180 AU Setting AU
scheduled install time to 2008-03-05 08:00:00
2008-02-28 09:20:24:040 4168 8cc Report REPORT
EVENT: {2A884C3B-03C0-4B4A-8AAD-1739224ED6FB} 2008-02-28
09:20:19:040-0500 1 147 101
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
Success Software Synchronization Windows Update Client
successfully detected 0 updates.
2008-02-28 09:20:24:040 4168 8cc Report REPORT
EVENT: {46F370AB-3743-4F24-8C5C-CB5198883B0C} 2008-02-28
09:20:19:040-0500 1 156 101
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
Success Pre-Deployment Check Reporting client status.

Crossposted to the WSUS newsgroup for the OP's convenience:

news://msnews.microsoft.com/microsof...pdate_services

http://www.microsoft.com/technet/com...pdate_services


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



Michel Deschenes wrote:

> The computers that connect to my WSUS can't seem to detect that they need
> updates
>
> The server console shows that the computers have sent reports and that they
> are requiring some updates.
>
> If I go on one of those clients and type in "wuauclt.exe /detectnow", it is
> not getting any updates. I have been trying to find a solution for the past 2
> days without any luck.
>
> I have tried deleting %windir%\softwaredistribution, no luck there either.
>
> Here is a copy of my %windir%\windowsupdate.log
>
> Anyone has a clue what could be the cause of this?
>
> 2008-02-28 09:20:13:868 4168 e70 AU Triggering AU
> detection through DetectNow API
> 2008-02-28 09:20:13:868 4168 e70 AU Triggering
> Online detection (non-interactive)
> 2008-02-28 09:20:13:868 4168 380 AU #############
> 2008-02-28 09:20:13:868 4168 380 AU ## START ##
> AU: Search for updates
> 2008-02-28 09:20:13:868 4168 380 AU #########
> 2008-02-28 09:20:13:868 4168 380 AU <<## SUBMITTED
> ## AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
> 2008-02-28 09:20:13:868 4168 8cc Agent *************
> 2008-02-28 09:20:13:868 4168 8cc Agent ** START **
> Agent: Finding updates [CallerId = AutomaticUpdates]
> 2008-02-28 09:20:13:868 4168 8cc Agent *********
> 2008-02-28 09:20:13:868 4168 8cc Agent * Online =
> Yes; Ignore download priority = No
> 2008-02-28 09:20:13:868 4168 8cc Agent * Criteria
> = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and
> IsAssigned=1 or IsHidden=0 and IsPresent=1 and
> DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and
> IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and
> RebootRequired=1 or IsHidden=0 and IsInstalled=0 and
> DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
> 2008-02-28 09:20:13:868 4168 8cc Agent *
> ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> 2008-02-28 09:20:13:868 4168 8cc Misc Validating
> signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w uident.cab:
> 2008-02-28 09:20:13:868 4168 8cc Misc Microsoft
> signed: Yes
> 2008-02-28 09:20:13:868 4168 8cc Misc Validating
> signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w uident.cab:
> 2008-02-28 09:20:13:883 4168 8cc Misc Microsoft
> signed: Yes
> 2008-02-28 09:20:13:883 4168 8cc Misc Validating
> signature for C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w sus3setup.cab:
> 2008-02-28 09:20:13:883 4168 8cc Misc Microsoft
> signed: Yes
> 2008-02-28 09:20:13:899 4168 8cc Setup ***********
> Setup: Checking whether self-update is required ***********
> 2008-02-28 09:20:13:899 4168 8cc Setup * Inf
> file: C:\WINNT\SoftwareDistribution\SelfUpdate\Default\w sus3setup.inf
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\cdm.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuapi.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuapi.dll.mui: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuauclt.exe: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuaucpl.cpl: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuaueng.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuaueng.dll.mui: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wucltui.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wucltui.dll.mui: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wups.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wups2.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup Update NOT
> required for C:\WINNT\system32\wuweb.dll: target version = 7.1.6001.65,
> required version = 7.1.6001.65
> 2008-02-28 09:20:13:899 4168 8cc Setup *
> IsUpdateRequired = No
> 2008-02-28 09:20:15:649 4168 8cc PT +++++++++++
> PT: Synchronizing server updates +++++++++++
> 2008-02-28 09:20:15:649 4168 8cc PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://<ServerURL:Port>/ClientWebService/client.asmx
> 2008-02-28 09:20:17:680 4168 8cc Agent WARNING:
> Failed to evaluate Installed rule, updateId =
> {03FF1EBE-C1CF-4DBA-ACDA-5C3BFBD9133D}.100, hr = 80041017
> 2008-02-28 09:20:18:384 4168 8cc PT +++++++++++
> PT: Synchronizing extended update info +++++++++++
> 2008-02-28 09:20:18:384 4168 8cc PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://<ServerURL:Port>/ClientWebService/client.asmx
> 2008-02-28 09:20:19:040 4168 8cc Agent * Found 0
> updates and 34 categories in search; evaluated appl. rules of 807 out of 1044
> deployed entities
> 2008-02-28 09:20:19:040 4168 8cc Agent *********
> 2008-02-28 09:20:19:040 4168 8cc Agent ** END **
> Agent: Finding updates [CallerId = AutomaticUpdates]
> 2008-02-28 09:20:19:040 4168 8cc Agent *************
> 2008-02-28 09:20:19:056 4168 180 AU >>## RESUMED
> ## AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
> 2008-02-28 09:20:19:056 4168 180 AU # 0 updates
> detected
> 2008-02-28 09:20:19:056 4168 180 AU #########
> 2008-02-28 09:20:19:056 4168 180 AU ## END ##
> AU: Search for updates [CallId = {4EF99D99-4A56-465D-8E64-8E3EEE30168E}]
> 2008-02-28 09:20:19:056 4168 180 AU #############
> 2008-02-28 09:20:19:056 4168 180 AU AU setting next
> detection timeout to 2008-02-29 11:16:14
> 2008-02-28 09:20:19:056 4168 180 AU Setting AU
> scheduled install time to 2008-03-05 08:00:00
> 2008-02-28 09:20:24:040 4168 8cc Report REPORT
> EVENT: {2A884C3B-03C0-4B4A-8AAD-1739224ED6FB} 2008-02-28
> 09:20:19:040-0500 1 147 101
> {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
> Success Software Synchronization Windows Update Client
> successfully detected 0 updates.
> 2008-02-28 09:20:24:040 4168 8cc Report REPORT
> EVENT: {46F370AB-3743-4F24-8C5C-CB5198883B0C} 2008-02-28
> 09:20:19:040-0500 1 156 101
> {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
> Success Pre-Deployment Check Reporting client status.

Michel Deschenes wrote:

> The computers that connect to my WSUS can't seem to detect that they need
> updates

The log says no updates are available. This probably means that the updates
aren't approved, or that they haven't been downloaded to the server.

Harry.

Hi Harry,

Thanks for the reply, unfortunately, the updates have been downloaded on the
server and are approved for installation on my workstation. The WSUS server
says there are 12 available updates that are all approved for installation
but the workstation detects that there are 0 availble, which is my issue.

"Harry Johnston [MVP]" wrote:

> Michel Deschenes wrote:
>
> > The computers that connect to my WSUS can't seem to detect that they need
> > updates
>
> The log says no updates are available. This probably means that the updates
> aren't approved, or that they haven't been downloaded to the server.
>
> Harry.
>

Michel Deschenes wrote:

> Thanks for the reply, unfortunately, the updates have been downloaded on the
> server and are approved for installation on my workstation. The WSUS server
> says there are 12 available updates that are all approved for installation
> but the workstation detects that there are 0 availble, which is my issue.

Are the updates approved for all computer groups?

The WSUS server is saying that these updates are needed by that particular
workstation? Is the "last report" date for the workstation up to date?

Which specific updates are needed?

Harry.

Hi,

Both status report and windowsupdate.log could have updated date.

This new WSUS is running on 2003 std edition and on WSUS 3.0 SP1. After
setup, I get updates from another old WSUS connecting with Internet. I
already unchecked the option "only download after got approval" so possible
to get all updates from old WSUS. Also I have executed "wsusutil reset" to
check the updates match those in metadata.

Then, I configure the new WSUS to get updates from itself (http://localhost)
and another client PC to get updates from this new WSUS. After run the
"wauctl /detectnow", both new WSUS and client PC are appeared in the console.
Then, I approve some updates to both new WSUS and client PC. But waited
for a number hours, still not able to download and installed.

Then, I tried reboot them a few times, reconfigure automatic update via
gpedit.msc (plus change the detect frequency) a few times and also run
"wsusutil reset" and "wauclt /detectnow" a few times. But
windowupdates.log indicated that "updates detected = 0". The status report
for both new WSUS and client PC indicate approval => installed, but status =>
not installed.

When configure both new WSUS and client PC to download/install updates from
old WSUS, it could detect very fast.

Please help to check what problems are?

Best Regards,

Ivan Tsui







"Harry Johnston [MVP]" wrote:

> Michel Deschenes wrote:
>
> > Thanks for the reply, unfortunately, the updates have been downloaded on the
> > server and are approved for installation on my workstation. The WSUS server
> > says there are 12 available updates that are all approved for installation
> > but the workstation detects that there are 0 availble, which is my issue.
>
> Are the updates approved for all computer groups?
>
> The WSUS server is saying that these updates are needed by that particular
> workstation? Is the "last report" date for the workstation up to date?
>
> Which specific updates are needed?
>
> Harry.
>

Ivan Tsui wrote:

> This new WSUS is running on 2003 std edition and on WSUS 3.0 SP1. After
> setup, I get updates from another old WSUS connecting with Internet. I
> already unchecked the option "only download after got approval" so possible
> to get all updates from old WSUS. Also I have executed "wsusutil reset" to
> check the updates match those in metadata.

You don't mention approving any updates on the new server. Did you overlook
this step?

> The status report
> for both new WSUS and client PC indicate approval => installed, but status =>
> not installed.

Was this report from the new server or the old one?

This could also happen if the client doesn't realise what group it is supposed
to be in, if the updates aren't approved for all groups. Are the updates in
question approved for all groups?

Harry.

Hi Harry,

Thank for your quick reply.

> This new WSUS is running on 2003 std edition and on WSUS 3.0 SP1. After
> setup, I get updates from another old WSUS connecting with Internet. I
> already unchecked the option "only download after got approval" so possible
> to get all updates from old WSUS. Also I have executed "wsusutil reset" to
> check the updates match those in metadata.

You don't mention approving any updates on the new server. Did you overlook
this step?

> The status report
> for both new WSUS and client PC indicate approval => installed, but status =>
> not installed.

Was this report from the new server or the old one?

[Ivan] The status report is from the new WSUS server. Both new WSUS and
client PC also indicated (after detectnow), their windowsupdate.log could
contact this new WSUS servers, but "updates detected = 0".

This could also happen if the client doesn't realise what group it is
supposed
to be in, if the updates aren't approved for all groups. Are the updates in
question approved for all groups?

[Ivan] I put the new WSUS and client PC into separate groups and approved
for whole group. And already run detectnow to have reports on updated date /
time.

==> How soon both new WSUS and client PC detected an updates after approval
in console and then the client side detect an updates ready for download and
installed?

==> How to verify (if Ok for wsusutil reset) that the updates are inside
.../WSUScontent so I could approval this in console as in metadata? I could
see the new updates in the console and then approve this and also uncheck
"only download after got approval"? If this mean that the updates is in
WSUScontents?



"Harry Johnston [MVP]" wrote:

> Ivan Tsui wrote:
>
> > This new WSUS is running on 2003 std edition and on WSUS 3.0 SP1. After
> > setup, I get updates from another old WSUS connecting with Internet. I
> > already unchecked the option "only download after got approval" so possible
> > to get all updates from old WSUS. Also I have executed "wsusutil reset" to
> > check the updates match those in metadata.
>
> You don't mention approving any updates on the new server. Did you overlook
> this step?
>
> > The status report
> > for both new WSUS and client PC indicate approval => installed, but status =>
> > not installed.
>
> Was this report from the new server or the old one?
>
> This could also happen if the client doesn't realise what group it is supposed
> to be in, if the updates aren't approved for all groups. Are the updates in
> question approved for all groups?
>
> Harry.
>

Ivan Tsui wrote:

> [Ivan] I put the new WSUS and client PC into separate groups and approved
> for whole group.

Do you mean you approved the update for the All Computers group?

> ==> How soon both new WSUS and client PC detected an updates after approval
> in console and then the client side detect an updates ready for download and
> installed?

I'm not sure what you mean. Once an update is approved and downloaded from
Microsoft to the WSUS server, it is available for the clients to detect within
seconds - if you execute "wuauclt /detectnow" on the clients to initiate a
detection. Otherwise the clients will detect new updates approximately every 22
hours.

> ==> How to verify (if Ok for wsusutil reset) that the updates are inside
> ../WSUScontent so I could approval this in console as in metadata? I could
> see the new updates in the console and then approve this and also uncheck
> "only download after got approval"? If this mean that the updates is in
> WSUScontents?

I'm not sure what you mean. If you have approved updates, you can tell whether
they've downloaded by looking at the update from the Updates view, or by going
to the WSUS server console front page and looking for the entry reading
something like "Files to download".

Harry.

Hi Harry,

Sorry for miss questions.

My new WSUS get updates from another WSUS, not direct from windows update
via Internet. How I could ensure that the updates is available the new
WSUS? I have found and could approve this update in new WSUS console,
uncheck the option "download only got approval" in "updates and languages"
and execute "wsusutil reset" to verify updates with metadata.

If I unchecked "download only got approval", if mean that the updates will
be available when I could find this in console? How I know that the
updates is not available in the new WSUS and must be download from another
WSUS?

Please help.


"Harry Johnston [MVP]" wrote:

> Ivan Tsui wrote:
>
> > [Ivan] I put the new WSUS and client PC into separate groups and approved
> > for whole group.
>
> Do you mean you approved the update for the All Computers group?
>
> > ==> How soon both new WSUS and client PC detected an updates after approval
> > in console and then the client side detect an updates ready for download and
> > installed?
>
> I'm not sure what you mean. Once an update is approved and downloaded from
> Microsoft to the WSUS server, it is available for the clients to detect within
> seconds - if you execute "wuauclt /detectnow" on the clients to initiate a
> detection. Otherwise the clients will detect new updates approximately every 22
> hours.
>
> > ==> How to verify (if Ok for wsusutil reset) that the updates are inside
> > ../WSUScontent so I could approval this in console as in metadata? I could
> > see the new updates in the console and then approve this and also uncheck
> > "only download after got approval"? If this mean that the updates is in
> > WSUScontents?
>
> I'm not sure what you mean. If you have approved updates, you can tell whether
> they've downloaded by looking at the update from the Updates view, or by going
> to the WSUS server console front page and looking for the entry reading
> something like "Files to download".
>
> Harry.
>