Re: site boundry problem

Sasi,

This newsgroup handles SMS Installer related questions. I see that you've
already posted this question to the SMS Admin newsgroup, which is the
correct place.
--
Thanks,
Jim Bradbury
This posting is provided AS IS with no warranties and confers no rights.

"Sasi" <Sasi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2CB2237-49DA-48A0-8FB8-B7D41C04E240@xxxxxxxxxxxxxxxx
>I have an sms server which belongs to Active Directory Forest A.my clients
> belong to Active Directory Forest B and there is no Trusting between them.
>
> my problem is that,although I have the correct password for Domain B
> domainAdmin and have defined it in client push installation account,the
> sms
> client cannot be installed from SMS in domain A to desktops in domain B.
>
> some additional information:
> 1.the clients are discovered using Network Discovery method.surprisingly
> some of them have their value under "Assigned" equal to Yes and some other
> No
> !
> (there is no difference in configuration between those with Yes value and
> those with no value,I wonder why they are detected with different
> properties.
> )
>
> 2.I tried to manually install the client on some of them using "capinst
> /SLP=XXX" command.nothing happened;but the following message was logged on
> %temp%\capinst.log file on the client:
>
> *** Starting Installation *** - Thu Apr 14 14:24:25 2005
> 2 Command line argument(s):
> \\194.225.13.253\SMSClient\i386\capinst.exe
> /SLP=194.225.13.253
> Checking OS Version:
> Windows 2000 or greater detected.
> Building SLP Query String:
> This client belongs to AD Site: Default-First-Site-Name.
> IP Subnets found: &ip=192.168.76.0.
> IP Addresses found: &ir=192.168.76.238.
> SLP 194.225.13.253 specified on the command line, AD will not be searched.
> Checking SLP 194.225.13.253 for site/caps
> Querying SLP:
> /sms_slp/slp.dll?cap&ad=Default-First-Site-Name&ip=192.168.76.0
> SLP 194.225.13.253 returned no results, This client cannot be matched to
> any site boundaries known by that SLP
> *** Installation Complete *** - Thu Apr 14 14:24:25 2005
>
> 3.the clients' IP address are all from those IP class that I defined as
> site
> boundry.
> 4.my SMS server is of different IP address (item 3 and 4 are comprehenable
> from the log I mentioned above.
>
> whats wrong ? how can I install the clients using network discovery and
> Client push installation?


.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
  • Re: Client Push Question - MVP Kim vs Microsoft ?!
    ... My ex-training colleagues referred to me as sms-knowledgeable because I am more often right then wrong when sms is concerned. ... secondary site, I install SMS, configure the site server to be a management ... regarding 3) that enabling both discovery and client push on secondaries will ... > client push installation to get the clients installed. ...
    (microsoft.public.sms.admin)
  • Re: unable to installed software. No rights
    ... installation or find a way in which program can be installed without user ... will indicate to you which program SMS started and when and in next few ... >> client logs which will indicate that SMS has ... >>>> where you add those DPs individually or user preload package tool to ...
    (microsoft.public.sms.swdist)
  • Re: Side by Side Upgrade of SMS 2003
    ... Yea -- I've found a couple SMS trainers that know nothing other than the ... > could just upgrade the client using a different site code. ... You CAN use the Client Push Installation Wizard to ... So you can control your upgrade using the client push ...
    (microsoft.public.sms.setup)