SMS Client Push sms 2003 sp1 3

[ancientcontra]

Hi I have just installed SMS 2003 and sp1 onto a server (not a DC) in our company's network. On regular XP pro build I can push the advanced client out no problems. But on our company build (some services and strange software - etc) I cannot get the client to successfully push.

I was wondering what services need to be running on the client PC in order for a successful push of the client sms software. The installation log on the client mentions a WMI deletion error.

Any help would be greatly appreciated.

 

[globalstrata]

Yeap. You need WMI. WIthout that, the client won't install. Check at this article

http://myitforum.techtarget.com/articles/8/view.asp?id=8318

Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[globalstrata]

oops. That article is for the server. This is for the clients:

http://myitforum.techtarget.com/articles/8/view.asp?id=8624

Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[ancientcontra]

Thank you very much will give it a try shortly

 

[webcortech]

I'm having the same issue. I can not get this XP SP2 to push out. The client shows up in "Collections" in SMS, but the Site Code is not there, etc. If I right click on the box, and say "Install Client" It will not install.

In the CCM.Log, the machine does not show up.

it does show up in the DDM.log.

But here in the ringer.... throw this out there... This is a test lab.. not sure if this will hamper my results or not. It shouldnt, because everything is working in MS world that it should.

I have 2003 SP1 enterprised installed.
- SQL running correctly for SMS
- SMS2003 SP1
- SMS can discover the local server and audit it, etc. Advance client is running on it.
- VM2005 is running on this server.
- XP SP2 is loaded and running
- XP is joined to the 2003 domain and working correctly.

2003 server is on Subnet 192.168.150.0
XP is on 192.168.160.0
Both can talk back and forth and internet, etc Routing is working correctly.

When I try to run the capinst.exe as admin on the XP machine, the log file shows that
The client belongs to AD site: xxx
Ip Subnets 160.0
IP 160.50
Checking SLP Server03 (name of 2003 server) SLP returned no results. This client cannot match to any site boundaries known by that SLP.

So I checked my Site Boundaries. All the IP subnets are listed in the Site for SMS. So that would mean any Clients in subnet 192.168.160.0 should be able to join that SMS Site if requested to.

Any tips? newby here with SMS, but getting closer.

 

[globalstrata]

Do you get any errors in the SMS Console\Site Status Messages? What about in the logs files? (located in the SMS directory of the main server)


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[webcortech]

I looked in my Site Status
Compoenet Status shows:

Bunch of warnings.
- SMS_AD_System_Discovery_Agent
- SMS_AD_System_Group_Discovery
- ETC

The only thing has checked marked OK is SMS_exectutive.


Is this a timing thing. Will SMS and AD play catch up for awhile and eventually push this out.. I get antsy and try to force replications, etc....

thanks!
tc

 

[globalstrata]

Are the computers showing in the groups show as obsolete or do not show site information? Your discovery may have stopped working and the objects showed within the collectsion are not being considered as the same objects as the computers you have in the network. This means that the computers may not longer be talking to your system. To better help, I would need to know what those warnings show. It may be schema replication problems or that the accounts that you have setup for the clients may not longer have the correct permissions.


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[ancientcontra]

Well If have just got a new Laptop i thought I might push the client to.

It shows up using network discovery - but SMS cannot determine that it is running XPsp2. Its a standard IBM xp sp2 build with no other software on it. I run the upgrade repository test on it... got no errors.
The client will not push to the machine - my guess is becasue sms cannot determine the OS on it.. Any more ideas?

 

[globalstrata]

Is the laptop part of a Domain? Is the Discovery that you are using for the rest of the computers Active Directory? Is the client running under system accounts? (You can define accounts for the service to use to run) Does the accounts have access to your computer?


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[ancientcontra]

Its part of the same domain, even the same subnet. Ive tried a network discovery and an active directory discovery.

the accounts that SMS has, are the domain admin accounts.

What does SMS need to extract the information on the client.? just those wmi services and an appropriate account?

 

[ancientcontra]

changed the passwords on the accounts, And it worked now ! nice one.

One other issue, do I need to add another site to have a workgroup working along side the domain - this is to test packages on machines not on the domain.

 

[globalstrata]

You do not need to add another site. However, if you have a lot of objects, it may be better, especially since the network discovery returns every object that it finds, including printers. It depends on how much organization you want to have.


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[ancientcontra]

Oh man oh man. I just realised that the site codes are only being populated on the local subnet, in the collections.

I.e the same subnet that the sms server is on, is on our admin subnet, so no site code on my test machine which is on a different subnet.

We have not extended the schema yet, but I have added the WiNS entry manually to locate the MP_SMSSitecode and the SMS_SLP, but still the clients cannot get the site code.

If I install the client with out a sitecode, it cannot discover it... Any ideas?

 

[globalstrata]

Network Discovery has a lot of problems so this may be part of what you are having. You may need to use a GPO to run a script so it assigns the Site Code to the workstations. Microsoft has a white paper that gives this script. I will search later to see if I find it and post it in here. However, I do not think that the problem is the Site Code assignment. I think the problem is more that the server cannot find the computers to install them. If you have Windows XP SP2 or higher, you should look at this article:

http://support.microsoft.com/?kbid=886120.

However, I have the feeling that you need to look at the Network Discovery configuration so I would take a look at:

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/cpdg/plan810l.mspx

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/deploy/spgsms03/spsms14.mspx

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/tfaq04.mspx

Although this webcast is an SMS 2.0 Network Discovery, I think it would help understanding the requirements for the configuration:

http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc120800/wcblurb120800.asp

Hope this helps,




Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

http://www.busineshelpcentral.com

 

[ancientcontra]

OK OK. Figured it all out

We were using the schema updated, but I noticed that we only had one object created in the system management container.

I added the tick box for our sms server to be a locater point, and it then published the info to AD. (3 objects now )

All ok now.

Also the site codes were not being published to the other subnets, not becase of WINS or firewalls routing etc... becasue I had only defined the management scope.. Thanks for all your help.

 

[sencee]

I have tried everzthing to get the Distribution point to push out the client software for initial connection, but nothing will work, to any machine, XP SP1, 2 Win 2k or 03, and it's getting seriously aggrevating now. There seems to be no explanation, checked the WMI, the Schema, the Server Accounts, the push methods and the connections.

The two non servers on the test network that are being detected but both say Client : No and Assigned : No, but the two servers SMS (local) and the DNS/SQL server both say Client : No and Assigned : Yes......according to SMS, a client machine is assigned to a resource. How can these servers be assigned to a resource if they haven't got the client software installed?

 

[globalstrata]

What Discovery Method are you using? Is your Management Point working? Have you run the MP Troubleshooter from them SMS Toolkit (

http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.mspx)

to check that the Management Point is working correctly? Is your system inventorying the desktops correctly?



Gladys Rodriguez
GlobalStrata Solutions
Computer Repair, Website Design and Computer Consultant
Small Business Resources

 

[sencee]

At the moment, I am using Heartbeat with Active Directory, and the dekstop systems have been detected. I have just installed the client software manually on on of my test user machines, and the think actually installed correctly, however is still not showing up in the SMS Management Console that the client software is installed on the machine. However, I checked the logs of another machine, so there is obviously something getting through, because 1 the logs have been created and the software installed has appeared in the c:\windows\system32\CCMSetup folder, however, the logs say that the download is complete, that the service ran, then for apparently no reason it rolls back.

 

[sencee]

Results from the MP check.

Verify that the Distributed Transaction Coordinator Service is Running - PASSED

Verify that the Tesk Scheduler is running - PASSED

Verify that the Windows Management Instrumentation service is running - PASSED

Verify that the World Wide Web Publishing Service is running - PASSED

Verify that the SMS Agent Host Service is running - PASSED

Verify the Detault Website is Running

Verify the MPs Machine$account is a Member of the SQL servers SMS_SiteSystemToSQLConnection_<site_code> group - PASSED

Testing MPLIST HTTP request functionality - PASSED

Testing MPCERT HTTP request functionality - FAILED

If the MP is W2k3: Verify that the BITS Web Extensions are enabled - PASSED

Does the SMS Service account have administrative rights on the MP - SKIPPED - Not Applicable - Advanced Sercurity mode detected.


So the only one that failed is the MPCERT HTTP functionality test. Should that really make a difference in this problem?