ADVANCED CLIENT DILEMMA

[jrdebug]

guys please help!

i have been trying to install advanced clients via PUSH and LOGIN SCRIPTS methods; neither will work.

First off, PUSH method does not give anything at all! not even logs in the client end.

LOGIN SCRIPT method gives me the following message.

*** Starting Installation *** - Mon Mar 27 17:05:24 2006
Unable to open the client version registry key (0).
8 Command line argument(s):
\\gdmw_dc02\netlogon\CAPINST.EXE
/ADVCLI
/SLP=GDMW_SMS
/ADVCLICMD
Passing the remaining command line parameters to CCMSetup:
/SMSSITECODE=AUTO
CCMENABLELOGGING=TRUE
CCMLOGMAXSIZE=1000000
CCMLOGLEVEL=0
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=130.1.0.0.
IP Addresses found: &ir=130.1.1.80.
SLP GDMW_SMS specified on the command line, AD will not be searched.
Checking SLP GDMW_SMS for site/caps
Querying SLP: /sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=130.1.0.0&ir=130.1.1.80
SLP GDMW_SMS returned no results, This client cannot be matched to any site boundaries known by that SLP
*** Installation Complete *** - Mon Mar 27 17:05:24 2006

can anyone help?

thanks!

Jeffrey Rebong
Computer Engineer/Network Administrator

 

[tbrennans]

yup do you have boundaries configured in SMS?

Have you extended the schema in ad?

if you havent extended the schema did you manually add the slp and MP to wins?

Tim B

 

[jrdebug]

TIM,

i succesfully extended the schema and the system container in the AD has been updated. if this is the case, there is no need to manually add the SLP and MP to wins right? just in case, how do i check on this to confirm if they really were added?

currently, the SMS server is appearing in the WINS records as Fileserver and Workstation. How should i enter it? Should i enter a different record type?

thanks!


Jeffrey Rebong
Computer Engineer/Network Administrator

 

[tbrennans]

To verify your schema extension, you would open ad users and computers, change the view to advanced, go to the system container then the system management container and you should see what was added.

To manually add the server locator point entry to WINS
At the command prompt, type netsh, and then press ENTER.
Type wins, and then press ENTER.
Type server, and then press ENTER. To manage a remote WINS server, type server [\\servername or XXX.XXX.XXX.XXX].
Type the appropriate command, as in the following example:
add name Name=SMS_SLP endchar=1A rectype=0 ip={static IP of your SLP}

To verify that the server locator point WINS entry was added correctly
At the command prompt, type netsh, and then press ENTER.
Type wins, and then press ENTER.
Type server, and then press ENTER. To manage a remote WINS server, type server [\\servername or XXX.XXX.XXX.XXX].
Type the appropriate command, as in the following example:
show Name name=SMS_SLP endchar=1A

 

[jrdebug]

TBRENNANS,

i did just that and confirmed the new entries but i am still getting the same results in the log files. MP and SLP setup logs indicate successfull installations during initial configurations.

you know, the funny thing is, my own workstation and the SMS server itself are already registered sa clients. i don't know how i did it but it has been there since the beginning.





Jeffrey Rebong
Computer Engineer/Network Administrator

 

[tbrennans]

so then we are back to your boundaries, are you using an AD site or an ip subnet as your boundary?

In your log I see:

Querying SLP: /sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=130.1.0.0&ir=130.1.1.80
SLP GDMW_SMS returned no results, This client cannot be matched to any site boundaries known by that SLP
*** Installation Complete *** - Mon Mar 27 17:05:24 2006

It looks like the site has 130.1.0.0 subnet but the client is in 130.1.1.0 subnet if your mask is say 255.255.0.0 then your ok if its 255.255.255.0 then you need to include that subnet. (130.1.1.0)

 

[tbrennans]

in 2.0 you couldnt do supernetting, in 2003 you can (I think) if your supernet is in the AD site subnets list, but not if your using ip addresses as as your boundaries.

To be honest I have seen people claim they did use supernetting in the boundary and it worked....but I wont beleieve it until I actually try it...or I see a more reliable source tell me :-D

 

[jwolfe529]

I'm having the same problem with using capinst.
here is my capinst.log
*** Starting Installation *** - Thu May 04 12:08:09 2006
Unable to open the client version registry key (0).
2 Command line argument(s):
capinst
/AdvCli
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=10.38.74.0.
IP Addresses found: &ir=10.38.74.208.
Searching AD for Server Locator Points.
3 SLP(s) found in AD
Checking SLP KCDCSMS03 for site/caps
Querying SLP: /sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=10.38.74.0&ir=10.38.74.208
SLP KCDCSMS03 returned no results, This client cannot be matched to any site boundaries known by that SLP
Checking SLP EMPCCFS02 for site/caps
Querying SLP: /sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=10.38.74.0&ir=10.38.74.208
SLP EMPCCFS02 returned no results, This client cannot be matched to any site boundaries known by that SLP
Checking SLP KCDCOFM00 for site/caps
Querying SLP: /sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=10.38.74.0&ir=10.38.74.208
SLP KCDCOFM00 returned no results, This client cannot be matched to any site boundaries known by that SLP
*** Installation Complete *** - Thu May 04 12:08:10 2006

And here is results from a query of one of the SLP's
HTTP/1.1 200 OK
Date: Thu, 04 May 2006 17:08:10 GMT
Server: Microsoft-IIS/6.0
Content-type: text/html

Could Not Initialize


I have my site "Default-First-Site-name" set in Boundaries, SMS_SLP set in WINS, The Scema is extended, Help! I'm lost here. The client installs fine with the Client Push Installation, but I'm trying to put it in the Logon script so it can catch systems that are on the wire for a shorter time.

 

[jwolfe529]

Nevermind - I fixed my own issue. It was with DCOM and IUSER_Server did not have Local Activation priviledges on the Server Locater Point DCOM service.