RE: Branches Clients?!Assigned=yes, Clients=NO!!!!

Hi Matt, thanks alot for ur detailed reply.
in fact i did extend the AD Schema while setup sms site, & it is ok.
actually, with local clients at same office, it works perfectly, but the
problem is with the clients outside the main office at branches!!!!
may be is somthing to do with ports??!!
can i have the link for the white paper u mention?!

Thanks.

"Matt Goedtel [MSFT]" wrote:

> Hi Saeed,
>
> It appears that your problem is due to the Advanced Client not being able to
> find a Management Point to communicate with. When you setup and configured
> your Site Server, did you extend the AD Schema? This can be performed during
> setup if you are logged in with credentials that is a member of the Schema
> Admins group or before/after setup by executing ExtADSch.exe in the
> \SMSSETUP\BIN\I386 folder on the SMS 2003 product CD.
>
> If you did not extend the Schema and enable publishing, then you need to add
> two records in the WINS database for the Server Locator Point (SLP) and
> Management Poing (MP). This can be performed by following KB Article -
> 883620. The benefits of extending the schema in AD to support SMS is:
>
> 1. You want to use global roaming for Advanced Clients.
> 2. You want to use the most secure method available for authenticating
> management points to Advanced Clients.
> 3. You want to use automatic key exchange for secure site-to-site
> communication.
> 4. You want clients to automatically detect the server locator points and
> management points without requiring Windows Internet Name Service (WINS). If
> you do not extend the schema, WINS is required for automatic site assignment,
> roaming, and selection of a local management point.
>
> For further information on schema modifications for SMS, please review the
> whitepaper - "Active Directory Schema Modifications and Publishing for SMS
> 2003" . This whitepaper will guide you in properly extending the schema and
> configuring permissions, containers, and verifying everything is configured
> correctly.
>
> If you need further help, please let me know.
>
> Matt Goedtel [MSFT]
> "This posting is provided AS IS with no warranties and confers no rights."
>
> "Saeed Khalaf" wrote:
>
> > Hi Again;
> >
> > i had checked the logs files: the ClientLocation.log seems ok, but in
> > LocationServices.log there are some errors:
> >
> > "Failed to resolve IP address from WINS"
> > "No NLB default managment point is present"
> >
> > the logs:
> > <![LOG[Retrieved Default Management Point through WINS:
> > 128.127.200.140]LOG]!><time="12:37:19.241+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:2070">
> > <![LOG[Persisting the default management point in
> > WMI]LOG]!><time="12:37:19.241+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:2545">
> > <![LOG[Persisted Default Management Point Location
> > locally]LOG]!><time="12:37:19.256+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:2551">
> > <![LOG[Attempting to retrieve proxy MP from
> > AD]LOG]!><time="12:37:19.288+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsproxymp.cpp:828">
> > <![LOG[Current AD site of machine is
> > Default-First-Site-Name]LOG]!><time="12:37:19.475+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:195">
> > <![LOG[Current AD site of machine is
> > Default-First-Site-Name]LOG]!><time="12:37:19.881+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:195">
> > <![LOG[Attempting to retrieve local MP from
> > AD]LOG]!><time="12:37:19.960+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:2484">
> > <![LOG[Current AD site of machine is
> > Default-First-Site-Name]LOG]!><time="12:37:20.022+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5672"
> > file="lsad.cpp:195">
> > <![LOG[Executing Task LSTimeOutRequestsTask]LOG]!><time="12:37:23.850+000"
> > date="10-18-2005" component="LocationServices" context="" type="1"
> > thread="5672" file="scheduledcleanupendpoint.cpp:125">
> > <![LOG[Executing Task LSRefreshDefaultMPTask]LOG]!><time="12:37:23.881+000"
> > date="10-18-2005" component="LocationServices" context="" type="1"
> > thread="5952" file="scheduledcleanupendpoint.cpp:125">
> > <![LOG[Attempting to retrieve default management point from
> > AD]LOG]!><time="12:37:23.991+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5952"
> > file="lsad.cpp:2020">
> > <![LOG[Attempting to retrieve default management point from
> > WINS]LOG]!><time="12:37:24.006+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5952"
> > file="lsad.cpp:2044">
> > <![LOG[Attempting to retrieve NLB default management point from
> > WINS]LOG]!><time="12:37:24.006+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="5952"
> > file="lsad.cpp:2050">
> > <![LOG[Executing Task LSRefreshLocationsTask]LOG]!><time="12:37:24.241+000"
> > date="10-18-2005" component="LocationServices" context="" type="1"
> > thread="5972" file="scheduledcleanupendpoint.cpp:125">
> > <![LOG[Attempting to retrieve default management point from
> > AD]LOG]!><time="12:37:25.366+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="4704"
> > file="lsad.cpp:2020">
> > <![LOG[Attempting to retrieve default management point from
> > WINS]LOG]!><time="12:37:25.381+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="4704"
> > file="lsad.cpp:2044">
> > <![LOG[Attempting to retrieve NLB default management point from
> > WINS]LOG]!><time="12:37:25.381+000" date="10-18-2005"
> > component="LocationServices" context="" type="1" thread="4704"
> > file="lsad.cpp:2050">
> > <![LOG[Failed to resolve IP address from WINS]LOG]!><time="12:37:26.257+000"
> > date="10-18-2005" component="LocationServices" context="" type="3"
> > thread="5952" file="lswins.cpp:313">
> > <![LOG[No NLB default management point is present, attempting to resolve
> > default management point from WINS]LOG]!><time="12:37:26.257+000"
> > date="10-18-2005" component="LocationServices" context="" type="1"
> > thread="5952" file="lsad.cpp:2056">
> >
> > hope that will help.
> > Thanks.
> >
> > "Matt Goedtel [MSFT]" wrote:
> >
> > > Saeed,
> > >
> > > When you configured the SMS Site Server after you ran setup and installed
> > > it, did you configure the site boundaries for the remote site - 128.125.x.x?
> > > If you did, is it entered via IP Subnet or by AD Site Boundary?
> > > Also are we talking about the Legacy or Advanced Client? Regardless, how
> > > did you deploy the client to the systems in the branch office? To
> > > troubleshoot further, I would check the
> > > %SystemRoot%\System32\CCM\Logs\ClientLocation.log file, LocationServices.Log,
> > > and CCMExec.log files.
> > >
> > > Any filtering of traffic between the branch office and the main office? Adv
> > > Clients use HTTP Port 80 by default to communicate with the MP on the Site
> > > server. Also, what OS are the clients running?
> > >
> > > Regards,
> > >
> > > Matt Goedtel
> > > "This posting is provided AS IS with no warranties and confers no rights."
> > >
> > > "Saeed Khalaf" wrote:
> > >
> > > > Hi;
> > > >
> > > > am using SMS2003, single site & one distribution point.
> > > > my clients are @ main Office & branches. the main office clients are
> > > > installed as client normally. but the branched clients are not, they are
> > > > discoverd & the site code are assigned for the normally, but they still not
> > > > shown as clients.
> > > > the Domain @ Ip subnet are the same.
> > > >
> > > > Example: at main office client IP start with 128.127.x.x, subnet
> > > > 255.255.0.0. @ branch IP 128.125.x.x, subnet 255.255.0.0.
> > > > are there any special configuration at site boundaries or roaming boundries?
> > > > or any idea or help to install these branches clients as clients?!
> > > >
> > > > Plz help.
.

Relevant Pages

  • RE: Verifying AD Publication
    ... The schema has been extended and validated in the ... SMS3 Active Directory Scema Modification and Publishing ... SMS server and or the system account created for SMS3 to ... >can extend the Active Directory schema during SMS 2003 ...
    (microsoft.public.sms.setup)
  • Re: error 5436 & 4913
    ... You can extend the schema afterwards by running extadsch.exe. ... >> Requirements to Publish SMS Information to Active Directory ... >> Hierarchy Manager and SMS Site Component Manager use the SMS Service ...
    (microsoft.public.sms.setup)
  • Re: Why SMS is writing in Active Directory?
    ... If you don't want to install a wins server, than extending the schema ... > If I understand what you say, is it really needed to extend the schema if I ... > only have one SMS in one site? ...
    (microsoft.public.sms.admin)
  • RE: Branches Clients?!Assigned=yes, Clients=NO!!!!
    ... With SP1 for SMS 2003, you can change that port number for all ... >> in fact i did extend the AD Schema while setup sms site, ...
    (microsoft.public.sms.setup)
  • Re: Cant remote control over a subnet
    ... I have extended the AD schema, can you point me in the right direction to ... the system management container in AD ... Did you extend the AD schema when you ... Did you give the SMS Service account rights to the System ...
    (microsoft.public.sms.setup)
Loading