SMS 2.0, Will Not Distribute Client to Domain Computers

[Smudgens]

I have recently set-up a new Primary Site. I have configured the Client Agents and set the Client Installation Methods of Windows Network Logon Client and Windows NT Remote Client. Even though the Client Agents and Installation Methods are set SMS will not distribute to the members of the Domain. I can see all the members through Discovery but I am unable to even install using the Manual Client Installation Method.<br>
<br>
Can anybody help me please.<br>
<br>
Smudgens

 

[Trunk]

This may be too obvious, but it sounds like the subnet boundaries have not been entred into the Site properties or they are incorrect. <p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>

 

[Smudgens]

Hi Trunk,<br>
<br>
Thanks for the help, although I have checked the setting and it seems to be OK. Do I need to enter the Subnet Mask as well as the Subnet IP?. If not What else could this be?<br>
<br>
Regards<br>
<br>
Smudgens

 

[Trunk]

Let's use this as an example.<br>
<br>
Suppose you have a client with an IP address of 167.125.118.213 and the client has a subnet mask of 255.255.255.0. Then the IP subnet that you would enter into the SMS Site Boundaries would be 167.125.118.0.<br>
<p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>

 

[Smudgens]

The subnet mask I am using is 255.255.255.0 and the Subnet IP I am using is ???.???.???.0. This has been in place from the start. Does the Subnet mask need to be added in addition to the Subnet IP?. I have used three of the discovery methods (Windows Networking Logon, windows NT User Account and Network Discovery), and this has given me a list of all relevent resources on our Domain. I have used Network Logon and NT Remote Client for my installation methods and have had no luck. Is the mechanism used for delivery different from discovery?.<br>
<br>
Thanks for your continuing assistance.<br>
<br>
Regards<br>
<br>
Neil Smith

 

[Henri2]

verify you have logon point (requiered for client installation)you can also test the addsysgui.exe from backoffice ressource kit

 

[Rolstead]

Henri2 is right on the money here.&nbsp;&nbsp;This question was on the test.&nbsp;&nbsp;No Logon point means to client install manually or otherwise.&nbsp;&nbsp;The Logon server tells the client where the CAP is.<br><br>John Rolstead