I have a couple of SCCM XP clients that receive advertisements but dont run them, the advertisement works and runs OK on other clients.The clients have access to the DP and other clients on the same subnet etc. are running fine, this is a client issue.
The client downloads policy it would appear correctly, I even used client center tool to reset all the policies on the client, the advertisement appears in the advertisement list in client center and then nothing.
What can I check to see where it is stopping?
If i use client center to force the advertisement to run, it will run OK
you can perform the steps show in this article to find out where your advertisement stuck
hope it helps
Syed Kasif | My blogs: http://syedtechblog.wordpress.com | Linkedin: /syedkashif
Hi, thanks for the replies.I enabled logging on the clients.
Unable to copy/past the log files on this issue as they are on a secure site.
The execmanager log reports:
Policy arrived for parent package xxx0100 program program 1.
SMS code page 850 sms locale id 2057
advertisement id xxx
client id xxx
process id xxx
thread id xxx
execmgr 01/12/2011 3132 (0x0c3c)
And then nothing happens, in the locaiton services log, there is nothing associated with the package, and only mentions two old packages.I appreciate theres not much info to go on, but to me, it looks like the SCCM client is not functioning.
What is funny, is that you can use the System Center tools, right click the advertisement and the jobs will run when forced but do not run if advertised.