AD System Group Discovery Trouble

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Olov (anonymous_at_discussions.microsoft.com)
Date: 05/03/04 

Date: Mon, 3 May 2004 14:01:02 -0700

Hello !

I have a SMS 2003 server running with AD System and AD System Group Discovery.
I am fairly new to SMS, so please excuse me if my questions are somewhat odd.
I am setting up collections based on AD group membership, and the discovery works fine - except :

When I remove a computer from a group .. the AD Group discovery doesn´t reflect the changes.
For example .. I have one computer that i want to distribute two programs to.
I add the computer to the two groups, and it shows up in both collections in SMS.
I then decide to remove the computer from the AD groups .. but when i click properties on the computer object in SMS .. the two groups are still listed in SystemGroupName[1] and SystemGroupName[2] and it is still in the collections ( of course ). However .. if i just change the membership of the computer into two different groups .. it reflects correctly in SMS. What am i missing here .. because i cannot imagine that this behaviour is by design ?!?!?!

Relevant Pages

  • Re: AD System Discovery driving me nuts.... Help!
    ... ~Last Run time is 8/11/2007 12:00:06 AM Eastern Daylight Time ... The below offending PC's are new, and exhibit the problem of showing up in All Systems, but not in the AD OU Collection I created in SMS. ... Ad system group discovery discovers ou and group information for systems ...
    (microsoft.public.sms.admin)
  • Re: All User Groups collection is blank
    ... One good piece of news is that SMS 2003 SP2 will have a new discovery ... The DDRs it generates will go into the "All User Groups" collection ... allowing admins to target user groups with out using NT User group discovery ... >> before data start populating the All User Groups collection? ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 and AD User Groups
    ... - Policy Request cycle ... - Collection update membership. ... - Depth SMS hierarchy. ... >> The fastest way would be to use group discovery to go against AD. ...
    (microsoft.public.sms.swdist)
  • Re: SMS 2003 Application Distribution Secuirty (how to restrict who can see an Advertised App)
    ... > need to do in restricting who can ... The access acounts that you can set for a package actually control NTFS ... Permissions on SMS objects on the other hand are effective when managing ... Active Directory Security Group discovery method that does the same ...
    (microsoft.public.sms.admin)
  • Re: AD group membership collection
    ... SMS 2003 SP1. ... remember correctly you have a column in the AD System Group discovery UI ... > group discovery does not query the sub OUs in AD. ... >> the information for both it's systems and the child secondary sites. ...
    (microsoft.public.sms.admin)