/build/static/layout/Breadcrumb_cap_w.png

SMS 2.0 Help

I am fairly new to creating and distributing packages through SMS. I am currently working on creating and deploying Project and Visio 2003 to a limited number of users throughout the network. Users request the program and then are added to a new collection and the advertisement is sent to that collection. My problem is that the advertisement seems to be lost somewhere between SMS and the client. I sent the advertisement out to 3 machines (all test machines) and it was recieved quickly by one of the machines and was installed with no problems/errors. The other 2 machines never got the advertisement. I am basically looking for any tips/tricks/ideas on how to troubleshoot where the problem is. I have checked the package/advertisement status in SMS Admin console and no problems exist. I have used advertview and again, no problems exist. I checked the log files at winnt\MS\.....\logs\ and couldnt see any problems (the log files are pretty ugly, so I might need help on WHAT to look for). I also checked out where the jobs are stored after completion (C:\WINNT\MS\SMS\clicomp\apa\Data) to see if they were getting there and failing out. I am not really sure where to go from this point. Any help would be greatly appreciated as I am stuck on this and running out of ideas....

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ