• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 588
  • Last Modified:

SMS 2003 - Pushing Client

I'm new to SMS but have managed to set up a server and db and perform discovery.

I'm trying to push client out but no matter how I try it's just not going.
What I need are some instructions and a checklist of things to check.  
0
Conchial
Asked:
Conchial
  • 6
  • 4
1 Solution
 
NJComputerNetworksCommented:
1) make sure that you have some computers listed in the ALL Systems collection.  this will verify that your discovery is working.  I assume this part is functioning.

2) In order to use the PUSH type of client installation, you must specify an account that has local admin rights on each machine.  This could be a domain account or a local admin account.  You can specify more then one account.

Do this here..

SMS Aministrator Console --> Site Hierarchy --> Site name --> Site Settings --. Client installation methods...  View properties of the "client push installation"  On the general tab, select Enable Client Push IInstallation to assigned resourceds, under system types, highlight the types of clients the SMS client should be pushed to, and enable client push installation to site systems..  Then pick your client types....try to stick with Advanced client if you can...to platform dependant.

Click the Accounts tab...here is where you need to specify one or more account names that have admin rights on your clients.  if this is a local account, use this formation %machinename%\useraccount  or domain account domain\user

3) Go to the all systems collection, right click and choose all tasks --> Install client.

-done.
0
 
NJComputerNetworksCommented:
By the way, your discovered clients must show ASSIGNED when you view them in the Collection...  This means that they are in your SMS Site boundaries and can have the SMs client pushed to them.
0
 
ConchialAuthor Commented:
Thanks NJ,

All Systems is indeed showing all the systems I want.

Quick question , where can I specify secondary and tiertiary accounts to try ?
Will it work so that if Domain Admin fails it will try a local admin accoutn I specify ?

Once I have sent the command to push to all , how loing do I wait ?
Do i need to rediscover ? Wait for systems to reboot ?

I'm off now ot try your suggestions , thanks.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
ConchialAuthor Commented:
Okay , read your answer properly on the accoutns now , nvm
0
 
NJComputerNetworksCommented:
No, you don't have to reboot...or rediscover.  There is log on the SMS Site Server you can check...  Errors that occur when trying to push the client are logged here:  \\Siteserver\SMS_XXX\inboxes\ccrretry.box

Also, you can look on the client machines for information about the push here:  C:\windows\system32\CCMSETUP\logs  <-- these logs are for the push  and c:\windows\system32\CCM\LOGS  <-- these logs are for the SMS client functionality
0
 
NJComputerNetworksCommented:
You do have to update the All Systems collection periodically because this is static data.  So, after 15 minutes are so after the push, right click the collection --> all tasks --> Update Collection Membership.  After this, right click the collection again and choose REFRESH from the drop down list.  The MMC contains static data, and this is how you can refresh the data seen in the SMS Administrator console...

0
 
ConchialAuthor Commented:
"By the way, your discovered clients must show ASSIGNED when you view them in the Collection...  This means that they are in your SMS Site boundaries and can have the SMs client pushed to them."

Okay , thats my issue then , none of them are assigned, how to change ?
0
 
NJComputerNetworksCommented:
You need to setup your SMS Site Boundaries...

Open the SMS Admin Console --> Site Hierachy --> and right click your SMS Site name with the globe on it and choose properties.  Click the Site Boundaries tab...


Click the gold STAR --> Choose IP subnet ... enter the subnets where your clients exist on.  No need to put subnet mask and they clients subnet mask will be used to determine if the client is in the subnet that you are listing here...  As an alternative, you can use Acitve Directory Site name..

click OK..to save

0
 
ConchialAuthor Commented:
I have clients that are now correctly in an "assigned" state but still ...nothing changes when I push


Here are some sample errors from the CCRETRY.BOX
I have two types of entry , one is Machinename.ccr , the other is machinename.domainname.ccr

The errors typically look like this (***'s are mine)

[NT Client Configuration Request]
   Client Type=1
   Forced CCR=TRUE
   PushClientEvenIfDC=FALSE
   Info CCR=FALSE
   Machine Name=************
   Initial Request Date=05/25/2006 12:34:22

[Request Processing]
   Latest Processing Attempt=05/29/2006 16:37:09
   Last Error Code=53
   Number of Processing Attempts=98
   Error Event Created=05/26/2006 13:28:48

[IDENT]
   TYPE=Client Config Request File


This error 53 keeps popping up , another example


[NT Client Configuration Request]
   Machine Name=**********
   Domain=*******
   IP Address 1=
   IP Address 2=*.*.*.*
   IP Address 3=*.*.*.*
   Initial Request Date=05/25/2006 09:38:15

[IP Address ]
   IP Address 1=
   IP Address 2=*.*.*.*
   IP Address 3=*.*.*.*

[Request Processing]
   Latest Processing Attempt=05/29/2006 16:36:47
   Last Error Code=53
   Number of Processing Attempts=107
   Error Event Created=05/26/2006 22:53:07

[IDENT]
   TYPE=Client Config Request File



I've also seen this error


[NT Client Configuration Request]
   Client Type=1
   Forced CCR=TRUE
   PushClientEvenIfDC=FALSE
   Info CCR=FALSE
   Machine Name=*********
   Initial Request Date=05/25/2006 12:34:13
   Last Connection Mask=0x0

[Request Processing]
   Latest Processing Attempt=05/29/2006 16:36:43
   Last Error Code=2
   Number of Processing Attempts=98
   Error Event Created=05/26/2006 13:28:45

[IDENT]
   TYPE=Client Config Request File



You got any insight to those codes ?
I could not locate client side logs , but im still looking
0
 
NJComputerNetworksCommented:
You can download the SMS ToolKit and install in on your SMS Site Server of your local workstation.  One of the tools is the SMS Trace.... it makes it easier to look at SMs logs...  http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.mspx

You can also lookup error codes on the SMS Trace...  

Error 53 means that the Site Server and the Client can not RESOLVE each other...  You need to make sure that the SMS Site Server is registered in DNS and/or WINS..  And that all clients can ping the SMS Site server by name.

0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now