Skip to main content

Problem WSUS update shows not approved in downstream but it's approved at upstream already

 Problem WSUS update shows not approved in downstream but it's approved at upstream already


Four WSUS servers, one is acting as WSUS upstream server (WSUS1) and othre three are acting as WSUS downstream servers (WSUS2, WSUS3 and WSUS4) on sites. For some reason if I approve an update at WSUS1 the approval does not replicate to the downstream servers. This is causing the situation that on WSUS downstream servers there are multiple updates showing their approval status as "Not approved" even though these same updates are approved on the upstream server. Automatic daily synchronizations show as "Succeeded" result on every server.

Could you please advice on how start troubleshooting this issue?


Solution
1. Ensue that your downstream server is on a replica mode with port 8530 not 80.



2. let's perform the following tests to further narrow down the issue:

On Upstream server, connect to problematic downstream server via Connect to another server as below to check the result:




3. Install WSUS console on a client and connect to the problematic downstream WSUS server from the client WSUS console to check the result.

4. If it shown the update as approved, then it's an issue with your downstream server console. then do the following..

5.I understand that the issue will not occur when connecting from other console. Based on current situation, please following the instruction on the problematic WSUS server:
right click to server name in the console > choose "remove from console"


Reconnect to the WSUS: right click and connect to server and type "LocalHost" with port 8530, click connect.




6. ensure The client side targeting should be enabled on the WSUS server side. By default, it is disabled.
We could follow below steps to verify.
7. On the WSUS, create the computer group. For example, servers.
8.In the WSUS Administration console, click Options, and then click Computers. In the Computers dialog box, select Use Group Policy or registry settings on client computers. Click OK to save your settings.

9. On the client, deploy the GPO or manually create the registry keys to set the client's computer group as servers. Trigger the scan on the client. Wait for 10 minutes, check if the WSUS has automatically put the clients to the servers group.

The documents you may refer to http://technet.microsoft.com/en-us/library/dd939829(v=ws.10).aspx and http://technet.microsoft.com/en-us/library/dd939933(v=ws.10).aspx

Enable client-side targetingEnables users of client computers to add themselves to precreated computer groups on a WSUS server. This option is valid only when Automatic Updates is redirected to a WSUS server. If the Specify intranet Microsoft update service location policy is not enabled, this policy has no effect.
The available setting options offer the following results:
Option
Result
EnabledThe computer identifies itself as a member of a particular computer group when it sends information to the WSUS server. The WSUS server uses this information to determine which updates should be deployed to this computer. You can assign a client computer to more than one computer group by separating the computer group names with a semicolon and a space.
DisabledNo computer group information is sent to the WSUS server.
Not ConfiguredNo computer group information is sent to the WSUS server. A local administrator can change this setting by using local policy.




Enable client-side targetingEnables users of client computers to add themselves to precreated computer groups on a WSUS server. This option is valid only when Automatic Updates is redirected to a WSUS server. If the Specify intranet Microsoft update service location policy is not enabled, this policy has no effect.
The available setting options offer the following results:
Option
Result
EnabledThe computer identifies itself as a member of a particular computer group when it sends information to the WSUS server. The WSUS server uses this information to determine which updates should be deployed to this computer. You can assign a client computer to more than one computer group by separating the computer group names with a semicolon and a space.
DisabledNo computer group information is sent to the WSUS server.
Not ConfiguredNo computer group information is sent to the WSUS server. A local administrator can change this setting by using local policy.
Enable client-side targetingEnables users of client computers to add themselves to precreated computer groups on a WSUS server. This option is valid only when Automatic Updates is redirected to a WSUS server. If the Specify intranet Microsoft update service location policy is not enabled, this policy has no effect.
The available setting options offer the following results:
Option
Result
EnabledThe computer identifies itself as a member of a particular computer group when it sends information to the WSUS server. The WSUS server uses this information to determine which updates should be deployed to this computer. You can assign a client computer to more than one computer group by separating the computer group names with a semicolon and a space.
DisabledNo computer group information is sent to the WSUS server.
Not ConfiguredNo computer group information is sent to the WSUS server. A local administrator can change this setting by using local policy.


10. If that doesn't help so please uninstall the downstream server and check all options to uninstall, DB, Logs and Contents.
11. reinstall WSUS 3.0 with hotfixes needed like KB2734608 & KB2720211 and then ensure all the above settings are exist.

Comments

Popular posts from this blog

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Question كيفية عمل share للـ outlook conntact لكل الـ Domain Users

  الحل بسيط جدا عايز الكونتاكت تتحدث دايما بحيث انك لما تضيف يوزر جديد يسمع في الكونتاكت اول حاجه بتدخل علي in office 2003 tools --- email account ---- add address book --- internet directory service (LDAP) type your server name then login info . mark this server require me to logon type any user on active directory and its password then save and close outlook and open it again now you will find all your active directory users in address book

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output