locked
want to immediately update "Computer" information work with ActiveDirectory RRS feed

  • Question

  • I try move computer node "COM1"  from "A" OU to "B" OU in ActiveDirectory. In this OUs, add different WSUS policy. "A" OU's policy write of "Target Group A'", "B" OU's policy write of "Target Group B'". I have hope computer node "COM1" move from "A'" to "B'" in WSUS, but not reflected in WSUS during few hours.

    I want to know how method of move "A'" to "B'", immediately(command line? GUI work?). Please tell me.

    Wednesday, August 20, 2014 5:45 AM

Answers

  • Hi,

    To confirm if group policy has been applied to the client, please follow the steps below,

    1. gpresult /h C:\gpreport.html
    2. Check the report.

    Note: Privilege of Administrator is required for this procedure.

    If the policy has been applied to the client, try to click Check the updates in client.

    Best Regards.



    Steven Lee

    TechNet Community Support

    Monday, August 25, 2014 9:16 AM
  • 2014-08-27 15:37:43:656 884 a44 Agent * Found 0 updates and 76 categories in search; evaluated appl. rules of 838 out of 1534 deployed entities

    There are no updates available from the WSUS server for this client.

    But the client *IS* communicating with the WSUS Server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sunday, August 31, 2014 12:58 AM

All replies

  • Hi,

    Have you tried to use "gpupdate /force"? This command is used to refresh the Group Policy. You can run this command in the WSUS server and client.

    If issue persists, please try to reboot the client. After rebooting, client will refresh the policy automatically.

    Besides, make sure that the Specify intranet Microsoft update service location has been enabled.

    If it still doesn't work, please post the windowsupdate.log here. It is useful for further trouble shooting.

    Here is a document about How to Configure Client Side Targeting in WSUS,

    http://gallery.technet.microsoft.com/How-to-Configure-Client-506e0275

    Best Regards.



    Steven Lee

    TechNet Community Support

    Thursday, August 21, 2014 6:54 AM
  • thanks for reply.

    I know "gpupdate /force". work "gpupdate /force" to under-following server and target Client "COM1". But not reflected in AD and WSUS.

    My problem is not "communicate between WSUS serer to Client "COM1"".

    My environment, AD's DC server and WSUS server is same 1 server. So, I'll hope to "If move "COM1" in OU "A" to OU "B" in AD's DC, immediately move "COM1" in Group "A'" to Group "B'" in WSUS.

    (OU"A" add of WSUS policy "Target Group "A'", OU"B" add of WSUS policy "Targe Grou "B'"").

    this situation is in same 1 server.

    please teach more hints.

    Best Regards.



    Thursday, August 21, 2014 2:11 PM
  • I want to know how method of move "A'" to "B'", immediately(command line? GUI work?). Please tell me.

    Is Options -> Computers set to "Use Group Policy..." ?

    Have you CONFIRMED that the GPOs from OU "B" have actually BEEN APPLIED to the computer "COM1"?


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, August 22, 2014 12:58 AM
  • thanks for reply.

    1. I try to "gpupdate /force" after move "COM1" from OU"A" to OU"B" on AD/WSUS server. but not reflected "COMPUTER" in WSUS console. wait to 1 min. 

    2. and I try to "gpupdate /force" on "COM1". so confirmed relfect for "COMPUTER" in WSUS consle, about 5sec.

    I understanding, operation to computer node in AD, execute "gpupdate /force" to WSUS server AND tagret client. Correct this understanding?

    Best regards,

    Saturday, August 23, 2014 8:55 AM
  • 1. I try to "gpupdate /force" after move "COM1" from OU"A" to OU"B" on AD/WSUS server. but not reflected "COMPUTER" in WSUS console. wait to 1 min. 

    2. and I try to "gpupdate /force" on "COM1". so confirmed relfect for "COMPUTER" in WSUS consle, about 5sec.

    I understanding, operation to computer node in AD, execute "gpupdate /force" to WSUS server AND tagret client.

    None of which answers the questions that I asked.

    Q1: Is the Options -> Computers setting in the WSUS console set correctly?

    Q2: If you look at HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate are the correct values present?


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sunday, August 24, 2014 5:32 AM
  • thanks for reply.

    A1: confirm check "Use group policy of Computer OR registry" in Option -> Computers

    A2: confirm correct of COM1's HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate


    Sunday, August 24, 2014 12:23 PM
  • Hi,

    To confirm if group policy has been applied to the client, please follow the steps below,

    1. gpresult /h C:\gpreport.html
    2. Check the report.

    Note: Privilege of Administrator is required for this procedure.

    If the policy has been applied to the client, try to click Check the updates in client.

    Best Regards.



    Steven Lee

    TechNet Community Support

    Monday, August 25, 2014 9:16 AM
  • A1: confirm check "Use group policy of Computer OR registry" in Option -> Computers

    I'm a bit nervous about your response, since that's not the actual wording of the option, but I'll take the chance.
    A2: confirm correct of COM1's HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

    Okay, so what's recorded in the WindowsUpdate.log when the WUAgent tries to communicate with the WSUS server?

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, August 28, 2014 11:20 PM
  • Okay, so what's recorded in the WindowsUpdate.log when the WUAgent tries to communicate with the WSUS server?

    Yes, confirm recorded "AU" Work in theWindowsUpdate.log. For part of WindowsUpdate.log

    2014-08-27 15:37:32:018 884 d08 AU #############
    2014-08-27 15:37:32:018 884 d08 AU ## START ##  AU: Search for updates
    2014-08-27 15:37:32:018 884 d08 AU #########
    2014-08-27 15:37:32:033 884 d08 AU <<## SUBMITTED ## AU: Search for updates [CallId = {FC8E8B31-3355-42A2-A3F7-AAFAAB352AB7}]
    2014-08-27 15:37:32:033 884 a44 Agent *************
    2014-08-27 15:37:32:033 884 a44 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-27 15:37:32:033 884 a44 Agent *********
    2014-08-27 15:37:32:033 884 a44 Agent  * Online = Yes; Ignore download priority = No
    2014-08-27 15:37:32:033 884 a44 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"
    2014-08-27 15:37:32:033 884 a44 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-08-27 15:37:32:033 884 a44 Agent  * Search Scope = {Machine}
    2014-08-27 15:37:32:189 884 a44 Setup Checking for agent SelfUpdate
    2014-08-27 15:37:32:236 884 a44 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-08-27 15:37:32:236 884 a44 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-08-27 15:37:32:267 884 a44 Misc Microsoft signed: Yes
    2014-08-27 15:37:32:267 884 a44 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-08-27 15:37:32:267 884 a44 Misc Microsoft signed: Yes
    2014-08-27 15:37:32:283 884 a44 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-08-27 15:37:32:283 884 a44 Misc Microsoft signed: Yes
    2014-08-27 15:37:32:283 884 a44 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-08-27 15:37:32:299 884 a44 Misc Microsoft signed: Yes
    2014-08-27 15:37:32:330 884 a44 Setup Determining whether a new setup handler needs to be downloaded
    2014-08-27 15:37:32:330 884 a44 Setup SelfUpdate handler is not found.  It will be downloaded
    2014-08-27 15:37:32:330 884 a44 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-08-27 15:37:34:514 884 a44 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-08-27 15:37:34:514 884 a44 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-08-27 15:37:34:530 884 a44 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-08-27 15:37:34:530 884 a44 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-08-27 15:37:34:545 884 a44 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-08-27 15:37:34:545 884 a44 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-08-27 15:37:38:352 884 a44 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-08-27 15:37:38:352 884 a44 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus-sv:8530/ClientWebService/client.asmx
    2014-08-27 15:37:42:845 884 a44 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-08-27 15:37:42:845 884 a44 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus-sv:8530/ClientWebService/client.asmx
    2014-08-27 15:37:43:656 884 a44 Agent  * Found 0 updates and 76 categories in search; evaluated appl. rules of 838 out of 1534 deployed entities
    2014-08-27 15:37:43:656 884 a44 Agent *********
    2014-08-27 15:37:43:656 884 a44 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-27 15:37:43:656 884 a44 Agent *************


    Friday, August 29, 2014 12:13 AM
  • Okay, so what's recorded in the WindowsUpdate.log when the WUAgent tries to communicate with the WSUS server?

    Yes, confirm communicate log recorded in the WindowsUpdate.log.

    ----------

    tell you the truth, this problem (policy not reflect to COM1) was resolved.

    When problem has occurred, Do I should be  "gpupdate /force" in COM1 AND AD server for policy reflect to COM1? (before post first question in this forum, I think that only work "gpupdate /force" in AD server)

    Friday, August 29, 2014 12:37 AM
  • 2014-08-27 15:37:43:656 884 a44 Agent * Found 0 updates and 76 categories in search; evaluated appl. rules of 838 out of 1534 deployed entities

    There are no updates available from the WSUS server for this client.

    But the client *IS* communicating with the WSUS Server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sunday, August 31, 2014 12:58 AM