Re: Problems with site assignment

The problem was attempting to run the client wizard when connected to the
parent site server instead of the direct site server..

"Rune Norberg" <runeno@xxxxxxxxxxxxxxxx> wrote in message
news:eBvsGy7SHHA.600@xxxxxxxxxxxxxxxxxxxxxxx
Have you checked the ccm.log file at the site server? And on those problem
clients - do you see anything related to the install under
%SystemRoot%\System32\ccmsetup or %SystemRoot%\System32\ccm? If yes -
check for more clues in those log files.

/Rune

"P" <p@xxxxx> wrote in message
news:%231cxEAySHHA.5060@xxxxxxxxxxxxxxxxxxxxxxx
Yah I have now done that and confirmed that I have all the AD properties
that the system group discovery returns..

But an attempt to do a client install results in the behaviour described
here:

http://support.microsoft.com/kb/886129

The client cannot be installed.

I have tried the workaround and all that does is make the collection
empty.

So it seems I have a problem with site boundaries, only I can't see where
that problem is..

regards

P





"Rune Norberg" <runeno@xxxxxxxxxxxxxxxx> wrote in message
news:eXyY9cuSHHA.2212@xxxxxxxxxxxxxxxxxxxxxxx
For me it seems like you need to run AD System Discovery at site 2 to
cover those clients. Remember that discovery only flows UP in the SMS
hierarchy, so you need to run the discovery process at the site closest
to the client.

AD System Group discovery only ad some extra info (ou and group info) to
the clients you already have discovered by any other method.

/Rune

"P" <p@xxxxx> wrote in message
news:OovNykoSHHA.1552@xxxxxxxxxxxxxxxxxxxxxxx
Hi

Two SMS primary sites (SP2). Their boundaries are linked to AD Sites.
Subnets are:

SMS Site 1 is linked to 5 AD sites with the following subnets

SMS Site 1 AD Site 1 10.140.0.0/16
10.2.35.0/24
10.253.2.0/24
AD Site 2 10.150.0.0/21
AD Site 3 10.180.16.0/24
AD Site 4 10.180.24.0/24

SMS Site 2 AD Site 5 10.180.0.0/21

SMS Site 2 is a child of SMS Site 1

As you can see above, none of these subnets overlap

I originally set up AD System discovery at "SMS site 1" and all
machines were discovered. Also machines in "AD Site 5" were not
assigned to SMS site 1 as expected since it wasn;t in the boundary
configuration.

I then configured AD System Group Discovery on Site 1 and that worked
fine, except that it never grabbed the extra properties for SMS Site 2
clients as explained here..
http://groups.google.com.au/group/microsoft.public.sms.admin/browse_thread/thread/ec6d0a4f3abb1d97/f004040232f884b7?lnk=st&q=Active+Directory+System+Group+only+creates+DDRs+for+Systems&rnum=1&hl=en#f004040232f884b7)

So I configure AD System Group Discovery on SMS Site 2, and the logs
show its confused.. specifially...

Did not find xxxx in the Index Table.
SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 2007/02/07 09:08:55 AM 6536
(0x1988)
xxxx is not in the list of assigned systems.
SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 2007/02/07 09:08:55 AM 6536
(0x1988)
Did not find xxx in the Index Table.
SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 2007/02/07 09:08:55 AM 6536
(0x1988)
xxxx is not in the list of assigned systems.
SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 2007/02/07 09:08:55 AM 6536
(0x1988)

But the machines it is complaining about are in Site B, and show up as
assigned in SMS Admin Console.

So I'm not sure what I am doing wrong here..

Basically SMS Site 1 clients are assigned and working fine. On SMS Site
2 they show up as assigned but I cannot install the SMS Client

Any suggestions?








.

Relevant Pages

  • Re: Problems with site assignment
    ... The client cannot be installed. ... AD System Group discovery only ad some extra info to ... SMS Site 1 is linked to 5 AD sites with the following subnets ... Also machines in "AD Site 5" were not assigned to SMS ...
    (microsoft.public.sms.admin)
  • Re: Secondary site clients
    ... > Hi i have finally created some of my sms site but cannot seem to get the ... The primary site client push form the site server works fine and there ... > are no error messages or anything relating to the client install in the logs ...
    (microsoft.public.sms.setup)
  • Re: I have to click on the discover button for the site code to detect
    ... If you do not set the SMSSITECODE property (to either AUTO or a ... but the client is not assigned to an SMS site. ... I install the client manually from this ...
    (microsoft.public.sms.setup)
  • Re: Event 10035
    ... I have just configured a new SMS site, installed the Advanced Client through ... install due to the content for the program not being downloaded in cache yet). ...
    (microsoft.public.sms.swdist)
  • Re: ADV Client Status
    ... Assigned simply means that the client is inside you SMS site boundaries. ... you are using push installation to install the agents, ... If you are using other means to install the agent (ccmesetup, ...
    (microsoft.public.sms.setup)
Loading