Re: Assigned sites and Advanced Client

From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 10/13/04 

Date: Wed, 13 Oct 2004 08:21:33 +0200

First of all, your boundaries should not be set to your active directory
DOMAIN, but to your active directory SITE.
If you don't know what your active directory site is, I would gamble it
is called Default-First-Site-Name (Which is the default value if nothing
was modified in Active Directory, I know it 's a strange name).

As far as the user agent error, it is something fairly common, but non-
critical if you don't plan on deploying software to groups. It actually
tells you that it cannot find the memberof property for your user
account, it's actually a problem with some adsi call. I should verify,
but this might be solved in SP1.

Kim Oppalfens
In article <eQ$wf6JsEHA.2484@TK2MSFTNGP15.phx.gbl>,
nkafer@homesteaderslife.com says...
> I have installed SMS 2003 on Windows 2003 Server. I configured the site
> boundaries to be my AD domain. I configured my roaming boundaries to be both
> an IP subnet and my AD domain. I have AD System discovery, User discovery
> and System Group discovery scheduled to run each day. When I look at the
> collections I see my machines with the domain set to my AD domain, however
> the client is set to "NO" and the Assigned is set to "NO". I would like to
> push out the advanced client to these clients using the site distribution
> settings however I know that I need to get the assigned to be "YES".
>
> My questions are:
>
> 1) When do clients get assigned? Is it at discovery time?
> 2) It seems to me that my boundaries must be set if the discovery is working
> at all so why are my clients not assigned?
>
> I look at the component status log for the AD discovery and it says
>
> "SMS Active Directory User Discovery Agent reported errors for 58 objects.
> DDR's were generated for 58 objects that had errors while reading
> non-critical properties. DDR's were not generated for 0 objects that had
> errors while reading critical properties.
>
> Possible cause: The SMS Service might not have access to some properties of
> this object. The container specified might not have the properties
> available.
> Solution: Please verify the Active Directory schema for properties that are
> not replicated or locked. Refer to the discovery logs for more information."
>
> I have set up the computer to have all rights on the AD container at the top
> of the domain so I'm confused.
>
> Thanks.
>
> Nancy
>
>
> 

-- 
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default
.mspx

Relevant Pages

  • Re: Assigned sites and Advanced Client
    ... I'll install SP1 to see if that fixes the user ... your boundaries should not be set to your active directory ... >> boundaries to be my AD domain. ... I have AD System discovery, ...
    (microsoft.public.sms.setup)
  • Re: Deploying to Groups of Computers
    ... For Active Directory System Group Discovery I setup a custom LDAP ... SW_PaintShopPro8_Licensed - Based on the below query ... Where did you create your Active Directory Security Group? ...
    (microsoft.public.sms.swdist)
  • Re: Deploying to Groups of Computers
    ... Discovery methods enabled: Windows User Account Discovery, Windows User Group Discovery, Active Directory System Discovery, Active Directory User Discovery and Active Directory System Group Discovery. ...
    (microsoft.public.sms.swdist)
  • Re: System OU Problems
    ... Did you enable the Active Directory System Group discovery method? ... I find the computers that should be assigned to the ...
    (microsoft.public.sms.admin)
  • Active Directory System Group Discovery
    ... Boundaries for primary and secondary site: Site Boundaries: Type: ... Windows User Group Discovery ... Active Directory system discovery: source: domain root, recursive:yes, ... Primary site server has "full control" permissions on "System Management" ...
    (microsoft.public.sms.setup)