locked
PCs not assigned to group on WSUS RRS feed

  • Question

  • Hi,

    I have configured WSUS server and set client-side targeting.
    I created Computer group X on WSUS.

    I created Group policy and link to OU in AD. I put pc inside this OU.
    Group policy sets WSUS server and enables client-side targeting to this specific group X.
    I checked Resultant Set of Policy on this PC and it's correctly set.

    The problem is that I don't see computer inside group X on WSUS.
    I see the PC in Unassigned Computers, but not in group X.

    What could be the problem ?

    Thank you..

    Wednesday, September 24, 2014 12:56 PM

Answers

  • I think that I found the solution.

    Replica server does not download Computer Options from Upstream server.

    I had set "Use Group Policy or registry settings on computers" only on Upstream server and thought that Replica server downloaded this.

    Thanks to all for answering.

    • Marked as answer by Steven_Lee0510 Wednesday, October 8, 2014 6:56 AM
    Friday, September 26, 2014 10:23 AM

All replies

  • Hi,

    on a client computer, open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

    What do you see for the value "TargetGroup"?

    Does your Computer Group is a 'Sub-Group" ? Like "Computers/All Computers/HeadQuarter/Test Group".


    David COURTEL

    IT Technician

    Wsus Third-Party Softwares Publishing : Wsus Package Publisher

    Outlook 2013 PST Backup : Pst Backup 2013

    Wednesday, September 24, 2014 5:53 PM
  • I see the PC in Unassigned Computers, but not in group X.

    What could be the problem ?

    To properly diagnose this we need to look at a WindowsUpdate.log segment.

    Please do the following:

    1. Record the system time of the client.
    2. Reboot the client.
    3. After reboot run this command: wuauclt /resetauthorization /detectnow
    4. Wait 30 minutes.
    5. Starting at the time recorded in Step #1, post ALL of the entries from the WindowsUpdate.log.

    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, September 25, 2014 2:09 AM
  • On Client - registry - TargetGroup: X

    On WSUS server - Update Services console - Group: Computers/All Computers/X

    • Edited by LL159159 Thursday, September 25, 2014 7:08 AM
    Thursday, September 25, 2014 5:14 AM
  • Here is log, somewhere I put ... instead of real data to protect privacy.

    2014-09-24 19:18:06:390  740 818 Misc ===========  Logging initialized (build: 7.9.9600.16403, tz: +0200)  ===========
    2014-09-24 19:18:06:409  740 818 Misc   = Process: C:\Windows\system32\svchost.exe
    2014-09-24 19:18:06:409  740 818 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-09-24 19:18:06:380  740 818 Service *************
    2014-09-24 19:18:06:409  740 818 Service ** START **  Service: Service startup
    2014-09-24 19:18:06:409  740 818 Service *********
    2014-09-24 19:18:06:639  740 818 Agent   * WU client version 7.9.9600.16403
    2014-09-24 19:18:06:639  740 818 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-09-24 19:18:06:639  740 818 Agent   * Access type: No proxy
    2014-09-24 19:18:06:640  740 818 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2014-09-24 19:18:06:640  740 818 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-09-24 19:18:06:640  740 818 Agent   * Network state: Connected
    2014-09-24 19:18:06:728  740 818 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2014-09-24 19:18:06:728  740 818 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-09-24 19:18:07:402  740 818 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-09-24 19:18:07:402  740 818 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-09-24 19:18:07:402  740 818 Agent   * WSUS server: http://wsusserver:8530
    2014-09-24 19:18:07:402  740 818 Agent   * WSUS status server: http://wsusserver:8530
    2014-09-24 19:18:07:402  740 818 Agent   * Target group: Server-group
    2014-09-24 19:18:07:403  740 818 Agent   * Windows Update access disabled: No
    2014-09-24 19:18:07:494  740 818 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-09-24 19:18:07:607  740 818 WuTask WuTaskManager delay initialize completed successfully..
    2014-09-24 19:18:07:942  740 818 Report CWERReporter::Init succeeded
    2014-09-24 19:18:07:942  740 818 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-09-24 19:18:07:946  740 818 DnldMgr Download manager restoring 0 downloads
    2014-09-24 19:18:07:962  740 818 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-09-24 19:18:08:002  740 818 AU AIR Mode is disabled
    2014-09-24 19:18:08:003  740 818 AU   # Policy Driven Provider: http://wsusserver:8530
    2014-09-24 19:18:08:008  740 818 AU   # Detection frequency: 22
    2014-09-24 19:18:08:008  740 818 AU   # Target group: Server-group
    2014-09-24 19:18:08:009  740 818 AU   # Approval type: Scheduled (Policy)
    2014-09-24 19:18:08:009  740 818 AU   # Auto-install minor updates: Yes (User preference)
    2014-09-24 19:18:08:009  740 818 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-09-24 19:18:08:025  740 818 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-09-24 19:18:08:025  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:18:08:078  740 818 AU AU finished delayed initialization
    2014-09-24 19:18:08:078  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:18:08:149  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:18:08:155  740 950 DnldMgr Asking handlers to reconcile their sandboxes
    2014-09-24 19:22:56:767  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:22:56:768  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:22:59:693  740 818 AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.
    2014-09-24 19:22:59:695  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:22:59:696  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:24:50:560  740 3d0 AU Triggering AU detection through DetectNow API
    2014-09-24 19:24:50:567  740 3d0 AU Triggering Online detection (non-interactive)
    2014-09-24 19:24:50:593  740 818 AU #############
    2014-09-24 19:24:50:593  740 818 AU ## START ##  AU: Search for updates
    2014-09-24 19:24:50:593  740 818 AU #########
    2014-09-24 19:24:50:603  740 818 IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 18; does use network; is not at background priority
    2014-09-24 19:24:50:603  740 818 IdleTmr Incremented PDC RefCount for Network to 1
    2014-09-24 19:24:50:603  740 818 IdleTmr Incremented idle timer priority operation counter to 1
    2014-09-24 19:24:50:766  740 818 Report ***********  Report: Initializing static reporting data  ***********
    2014-09-24 19:24:50:766  740 818 Report   * OS Version = 6.3.9600.0.0.196880
    2014-09-24 19:24:50:766  740 818 Report   * OS Product Type = 0x00000007
    2014-09-24 19:24:50:771  740 818 Report   * Computer Brand = ...
    2014-09-24 19:24:50:771  740 818 Report   * Computer Model = ...
    2014-09-24 19:24:50:771  740 818 Report   * Platform Role = 1
    2014-09-24 19:24:50:771  740 818 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-09-24 19:24:50:773  740 818 Report   * Bios Revision = ...
    2014-09-24 19:24:50:773  740 818 Report   * Bios Name = ...    
    2014-09-24 19:24:50:773  740 818 Report   * Bios Release Date = ...
    2014-09-24 19:24:50:773  740 818 Report   * Bios Sku Number unavailable.
    2014-09-24 19:24:50:773  740 818 Report   * Bios Vendor = ...
    2014-09-24 19:24:50:773  740 818 Report   * Bios Family unavailable.
    2014-09-24 19:24:50:773  740 818 Report   * Bios Major Release = ...
    2014-09-24 19:24:50:773  740 818 Report   * Bios Minor Release = ...
    2014-09-24 19:24:50:773  740 818 Report   * Locale ID = 1033
    2014-09-24 19:24:50:822  740 818 Agent *** START ***  Queueing Finding updates [CallerId = Windows Update Command Line  Id = 1]
    2014-09-24 19:24:50:822  740 818 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {...} ServiceId = {...}]
    2014-09-24 19:24:50:822  740 ed4 Agent ***  END  ***  Queueing Finding updates [CallerId = Windows Update Command Line  Id = 1]
    2014-09-24 19:24:50:822  740 ed4 Agent *************
    2014-09-24 19:24:50:822  740 ed4 Agent ** START **  Agent: Finding updates [CallerId = Windows Update Command Line  Id = 1]
    2014-09-24 19:24:50:822  740 ed4 Agent *********
    2014-09-24 19:24:50:822  740 ed4 Agent   * Online = Yes; Ignore download priority = No
    2014-09-24 19:24:50:822  740 ed4 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-09-24 19:24:50:822  740 ed4 Agent   * ServiceID = {...} Managed
    2014-09-24 19:24:50:822  740 ed4 Agent   * Search Scope = {Machine & All Users}
    2014-09-24 19:24:50:822  740 ed4 Agent   * Caller SID for Applicability: ...
    2014-09-24 19:24:50:845  740 ed4 EP Got WSUS Client/Server URL: "http://wsusserver:8530/ClientWebService/client.asmx"
    2014-09-24 19:24:52:479  740 ed4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-09-24 19:24:52:479  740 ed4 PT   + ServiceId = {...}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx
    2014-09-24 19:24:52:499  740 ed4 PT WARNING: Cached cookie has expired or new PID is available
    2014-09-24 19:24:52:499  740 ed4 EP Got WSUS SimpleTargeting URL: "http://wsusserver:8530"
    2014-09-24 19:24:52:508  740 ed4 PT Initializing simple targeting cookie, clientId = ..., target group = Server, DNS name = wsusserver.mydomain
    2014-09-24 19:24:52:508  740 ed4 PT   Server URL = http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-09-24 19:25:02:534  740 ed4 Agent Reading cached app categories using lifetime 604800 seconds
    2014-09-24 19:25:02:534  740 ed4 Agent Read 1 cached app categories
    2014-09-24 19:25:06:613  740 ed4 Agent   * Found 0 updates and 68 categories in search; evaluated appl. rules of 565 out of 867 deployed entities
    2014-09-24 19:25:06:639  740 ed4 Agent Reporting status event with 98 installable, 2 installed,  0 installed pending, 0 failed and 0 downloaded updates
    2014-09-24 19:25:06:640  740 ed4 Agent *********
    2014-09-24 19:25:06:640  740 ed4 Agent **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line  Id = 1]
    2014-09-24 19:25:06:640  740 ed4 Agent *************
    2014-09-24 19:25:06:640  740 ed4 IdleTmr WU operation (CSearchCall::Init ID 1, operation # 18) stopped; does use network; is not at background priority
    2014-09-24 19:25:06:640  740 ed4 IdleTmr Decremented PDC RefCount for Network to 0
    2014-09-24 19:25:06:640  740 ed4 IdleTmr Decremented idle timer priority operation counter to 0
    2014-09-24 19:25:06:640  740 f88 AU >>##  RESUMED  ## AU: Search for updates [CallId = {...} ServiceId = {...}]
    2014-09-24 19:25:06:691  740 f88 AU   # 0 updates detected
    2014-09-24 19:25:06:714  740 f88 AU #########
    2014-09-24 19:25:06:718  740 f88 AU ##  END  ##  AU: Search for updates  [CallId = {...} ServiceId = {...}]
    2014-09-24 19:25:06:718  740 f88 AU #############
    2014-09-24 19:25:06:719  740 f88 AU All AU searches complete.
    2014-09-24 19:25:06:720  740 f88 AU AU setting next detection timeout to 2014-09-26 08:23:25
    2014-09-24 19:25:06:729  740 f88 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:25:06:731  740 f88 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:25:11:701  740 950 Report REPORT EVENT: {...} 2014-09-24 19:25:06:639+0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2014-09-24 19:25:11:702  740 950 Report REPORT EVENT: {...} 2014-09-24 19:25:06:639+0200 1 156 [AGENT_STATUS_30] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Pre-Deployment Check Reporting client status.
    2014-09-24 19:25:11:807  740 950 Report CWERReporter finishing event handling. (00000000)
    2014-09-24 19:32:59:800  740 818 AU User login event timer expired for session id: 2.
    2014-09-24 19:32:59:809  740 818 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-09-24 19:32:59:809  740 818 AU #############
    2014-09-24 19:32:59:809  740 818 AU ## START ##  AU: Install updates
    2014-09-24 19:32:59:809  740 818 AU #########
    2014-09-24 19:32:59:809  740 818 AU   # Initiating scheduled install
    2014-09-24 19:32:59:982  740 818 AU WARNING: There are no approved updates to install
    2014-09-24 19:32:59:982  740 818 AU   # Exit code = 0x8024000C
    2014-09-24 19:32:59:982  740 818 AU #########
    2014-09-24 19:32:59:982  740 818 AU ##  END  ##  AU: Install updates
    2014-09-24 19:32:59:982  740 818 AU #############
    2014-09-24 19:39:58:788  740 950 EP Got WSUS Client/Server URL: "http://wsusserver:8530/ClientWebService/client.asmx"
    2014-09-24 19:39:58:833  740 950 PT WARNING: Cached cookie has expired or new PID is available
    2014-09-24 19:39:58:833  740 950 EP Got WSUS SimpleTargeting URL: "http://wsusserver:8530"
    2014-09-24 19:39:58:833  740 950 PT Initializing simple targeting cookie, clientId = 07baaad3-1ae4-4f14-895e-ecd098f08a43, target group = Server, DNS name = wsusserver.mydomain
    2014-09-24 19:39:58:833  740 950 PT   Server URL = http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-09-24 19:39:58:845  740 950 EP Got WSUS Reporting URL: "http://wsusserver:8530/ReportingWebService/ReportingWebService.asmx"
    2014-09-24 19:39:58:845  740 950 Report OpenReportingWebServiceConnection, reporting URL = http://wsusserver:8530/ReportingWebService/ReportingWebService.asmx
    2014-09-24 19:39:58:845  740 950 Report Uploading 2 events using cached cookie.
    2014-09-24 19:39:59:162  740 950 Report Reporter successfully uploaded 2 events.
    2014-09-24 19:40:59:844  740 950 Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2014-09-24 19:43:00:850  740 818 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-09-24 19:43:00:851  740 818 WuTask Uninit WU Task Manager
    2014-09-24 19:43:01:000  740 818 Service *********
    2014-09-24 19:43:01:000  740 818 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-09-24 19:43:01:000  740 818 Service *************

    Thursday, September 25, 2014 12:54 PM
  • 2014-09-24 19:18:07:402  740 818 Agent   * Target group: Server-group
    2014-09-24 19:18:08:008  740 818 AU   # Target group: Server-group

    That's why you don't see it in the group named 'X'.

    somewhere I put ... instead of real data to protect privacy.

    And a totally pointless effort it was at that; what you deleted was essentially meaningless data (for purposes of a human reading the logfile anyway).

    2014-09-24 19:24:52:508  740 ed4 PT Initializing simple targeting cookie, clientId = ..., target group = Server, DNS name = wsusserver.mydomain
    2014-09-24 19:39:58:833  740 950 PT Initializing simple targeting cookie, clientId = 07baaad3-1ae4-4f14-895e-ecd098f08a43, target group = Server, DNS name = wsusserver.mydomain

    But if you are going to delete data from the logfile, you probably should use the REPLACE ALL function in your text editor.

    Now, the curiosity here is why the group name in the initialization entries at 19:18 (Server-group) doesn't match the targeting cookie entries at 19:24 and 19:39 (Server) .. although, as noted, NONE of them put the client in group 'X'.

    The problem is that I don't see computer inside group X on WSUS.
    I see the PC in Unassigned Computers, but not in group X.

    But referring back to your original statement. The reason why you're seeing this client in "Unassigned Computers" in the console is almost certainly because you did not properly configure the Options -> Computers setting on 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.

    • Proposed as answer by Keith_C_Gordon Thursday, November 28, 2019 1:01 AM
    Thursday, September 25, 2014 8:56 PM
  • Sorry, Server-group and Server is the same, I manually corrected later in notepad but obviously I'm not good at that :-)

    Yes, but server has target group Server, clients have target group X, and that X is nowhere in log file.

    Here the server probably tries to add itself to Server group, but it doesn't try to add clients to X group.

    Friday, September 26, 2014 5:08 AM
  • Hi,

    - Open the Wsus Console

    - Go to "Options" -> "Computers" and select the option "Use settings from GPO or registry" (2nd option)

    On the client where you have pick the log file, open regedit and look at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

    , check that the "TargetGroup" value is set to X and not "Server-Group"


    David COURTEL

    IT Technician

    Wsus Third-Party Softwares Publishing : Wsus Package Publisher

    Outlook 2013 PST Backup : Pst Backup 2013


    • Edited by DCourtel Friday, September 26, 2014 7:35 AM mistype
    • Proposed as answer by Keith_C_Gordon Thursday, November 28, 2019 1:01 AM
    Friday, September 26, 2014 7:34 AM
  • I think that I found the solution.

    Replica server does not download Computer Options from Upstream server.

    I had set "Use Group Policy or registry settings on computers" only on Upstream server and thought that Replica server downloaded this.

    Thanks to all for answering.

    • Marked as answer by Steven_Lee0510 Wednesday, October 8, 2014 6:56 AM
    Friday, September 26, 2014 10:23 AM
  • Sorry, Server-group and Server is the same, I manually corrected later in notepad but obviously I'm not good at that :-)

    Yeah.. if you don't provide *accurate* information in your posts, it is *impossible* for us, who can only read what you post, to provide any sort of accurate responses.

    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.

    Saturday, September 27, 2014 2:31 AM
  • Yes, but server has target group Server, clients have target group X, and that X is nowhere in log file.

    THAT machine is not assigned to the group X.

    It doesn't get any simpler than that.

    It's assigned to the WRONG group. Fix the GPO!


    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.

    Saturday, September 27, 2014 2:32 AM
  • Yes, but server has target group Server, clients have target group X, and that X is nowhere in log file.

    THAT machine is not assigned to the group X.

    It doesn't get any simpler than that.

    It's assigned to the WRONG group. Fix the GPO!


    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.

    That machine does not have to be assigned to the X group because this is a server itself.
    The other client PCs were assigned to the X group.

    And as I said, the problem was that I did not set "Use Group Policy or registry settings on computers" on Replica server (because PCs were on Replica server's side). I thought that Replica downloads this setting from Upstream server. But it does not.

    Now everything is fine. I can see PCs now in the X group.

    Thanks for helping.


    • Edited by LL159159 Thursday, October 2, 2014 10:56 AM
    Thursday, October 2, 2014 10:55 AM
  • That machine does not have to be assigned to the X group because this is a server itself.

    Then I'm totally lost as to what your problem is.

    Originally the issue apparently was that you did not set the Options->Computers configuration correctly, which was resulting in the computer being dropped into "Unassigned Computers" rather than the GPO-configured Target Group.

    But crossing the path of that conversation, I asked you for the WindowsUpdate.log of a client that was supposed to be in the group 'X' but was appearing in "Unassigned Computers", and you provided a logfile with these entries:

    2014-09-24 19:18:07:402  740 818 Agent   * Target group: Server-group
    2014-09-24 19:18:08:008  740 818 AU   # Target group: Server-group

    Which identified a SECOND (apparent) defect.

    THAT system is NEVER going to appear in group 'X' because it's not assigned to group 'X'.

    What I think you're now saying is that (in addition to not setting Options->Computers), you also provided a logfile from the WRONG client system, completely confusing the conversation.


    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, October 2, 2014 5:26 PM
  • Lawrence, sorry for confusing the conversation.

    I didn't know what exactly my problem is. But now everything works fine.

    Thanks again for the effort.

    Thursday, October 16, 2014 6:21 AM