Microsoft SMS 2003, Setting up and deploying packages (basic help)

Once set up properly, the advertisment should show in "Add Remove Programs", under the "Add New Program" section right? Where currently it says "No programs are available on the network"?

Ok, I've added the distribution point (the SMS server itself, the only one listed).

I chose to include the source file directory, and pointed it to the directory with the MSI file.

I changed my collection to include a resource by netbios name, entered the name of the PC, it listed the PC and i checked the box to include the PC in the collection.

I changed the advertisement to use the "per-system attended" program rather than the "per-user attended". These were both already existing programs (created by default?).

The command for "per-system attended" is :

msiexec.exe ALLUSERS=2 /m MSI5JDA0 /i "7z465.msi"



I have tried rebooting again, tried a gpupdate /force (not sure if this is neccisary), and am still getting "No programs are available on the network"

Any ideas? Do i need to configure the domain client in any way to look for these advertisments? Do i need to install the SMS client on the client PC?

Thanks.

I believe "Add New Program" is based off of GPOs, not SCCM.

To run SCCM based programs, you would use the "Run Advertised Program" applet in the Control Panel.

The adveristment would also need to set to "Allow users to run program independently of assignments" to show up in RAP.

I do not have a "Run Advertised Program" at all in Control Panel. I am running SMS 2003, not SCCM, not sure if it would be the same.

Is the SMS Advanced Client required for SMS deployment?

I've installed the SMS Advanced client by running the client.msi located on SMS server CIFS share for the site. I now have a "Run Advertised Programs" icon in control panel, however, when i launch it there are no programs listed.

I noticed this server was not previously enabled as a Management point, so i enabled this role on the SMS server. Still no programs in "Run Advertised Programs".

Is the client even registered to your MP?  Check C:\windows\system32\ccm\logs\ClientIDManager.log.

I would suggest picking up a book on SMS from Amazon.  The MS Press books are pretty good. SMS is not just something you can wing by trial and error.  Well, you can I guess...until the VP's laptop reboots while he's working on a document :)

The LocationServices.log file shows what you are referring to (I think):

Current AD site of machine is: (my site name)
Retreived local Management Point from AD: (SMS server name)

For both local management point and proxy MP.

I have found the following error in the execmgr.log: <![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!>

I have checked that it is set as "Use this site system as a distribution point" in Site Settings>Site Systems

I found a "ClientIDMAnagerStartup.log" file, but do not see any references to registering with the MP.

I will be doing some reading, but i'd like to do a little hands on approach to see how things work first. I'm not too worried about disruption, they don't current use SMS and i am only testing with a very specific collection containing my test accounts/test computers.

I see no lines like that in any of the log files (tried searching for "RegTask", "Client is not registered")..

I did find when running the MP Troubleshooter there were errors on two things:

Verify Default Website Is Running ( Solution: Cannot create ActiveX component. )

If the MP is W2k3: Verify that Background Intelligent Transfer Service is enabled. ( Solution: Cannot create ActiveX component. )



Thanks for your help thus far.

Have you enabled the Advertised Programs Client Agent. You find it under Site management - site code - site settings - client agents?

After you enabled it, update the machine policy on your client.

Yes i did try that.

I think there was quite a bit wrong with the install. For one the previous IT person set this machine up as a domain controller. I removed the DC role from the machine, removed SMS, IIS, and SQL, and started from scratch. Things are now working somewhat as I expected, I have successfully deployed a package to a test client. I am still running into some problems here and there, but I am going to award points for this one as the two of you have been helpful in troubleshooting.