We have a problem that Run Advertised Programs is empty on some of our computers. We use the same task sequence on all of our machines, and on most of them it works fine, but on occations the Run Advertised Programs is empty, and the computer does not install any programs. We have several programs assigned to all computers, some mandatory and other optional. When I first check the Configuration manger on these machines, the actions tab only display 4 actions: Machine Policy, Software Updates, Deployment, Software Updates Scan and User Policy Retrieval. After running the Machine policy a few times the other Actions usually get available, but Run Advertised Programs is still blank.
When I check execmgr.log, I see that the policies for the different advertisements are listed
Policy arrived for parent package x program xxx
<snip>
Successfully submitted event to the Status Agent.
The strange thing is that I do get the Run Advertised program icon in Systray and on mouseover I get a popup saying "A new program is available to be run" but Run Advertised Programs is gray with the text "No programs are available on the network" and the mandatory programs are not being installed.
The machine looks normal from SCCM, and I get access to the event logs on the machine etc. There are no errors in the clientlocation.log on the client.
If I reinstall the computer, the problem is usually fixed (same user, same hardware, same machine name, same OS Task sequence).
I would be grateful if anyone has any hints and tips on how to resolve this.
- Proposed as answer by MAMK Tuesday, February 23, 2010 11:45 AM
yes, quite a lot of errors there. I've cut out the red and yellow parts:
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)
Could not connect to machine policy WMI namespace to get service settings.
39 times:
Error unregistering notification query.
Error waiting for tasks (0x80040213), will shut down anyway.
Error registering hosted class '{E67DBF56-96CA-4e11-83A5-5DEC8BD02EA8}'. Code 0x80040154
Failed to retrieve current (user,session) pair (0x80070002).
RemoteTools: Failed to get Remote Control settings len of UpdateEnabled reg key, err = 2
System task 'ClientIDManagerStartup' returned error code 0x80004005.
System task 'SMSSHA_Startup' returned error code 0x80070005.
Failed to get logging settings for 'FileSystemFile' from Registry (80070002)
Could not load logging configuration for component FileSystemFile. Using default values.
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)That's WMI related errors / problems. See http://blogs.technet.com/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx for further information.
Could not connect to machine policy WMI namespace to get service settings.
- Marked as answer by Eric C. MattoonModerator Friday, October 09, 2009 4:07 AM
Did you find a resolution on this? I am having a exactly the same issue with newly built machines.
I found that machines that have the SCCM agent installed via a client Push were able to recieve the program advertisements successfully.
Have you tried uninstalling the client, restarting and reinstalling the client?
Be sure that the above errors in your logs arent from the time that you sysprep'd your machine to capture the image. The client throws a number of errors as it is prepared for imaging.
ITSNO,
An update that may help you and others...
If you are sure that your program advertisements are working correctly (I.e. can see that the advertisements are received by the client in logs or client spy, and are tested OKon othermachines) but do not seem to work on newly SCCM OSD deployed machines, check that your machines are not still in Provisioning Mode.
I had an issue where my OSD Task sequence was not correctly resetting the SCCM client out of provisioning mode at completion, therefore all other advertisements were being received, and not being processed by the client.
To see if you clients are in provisioning mode, check the Reg Key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec]
Check if the values ProvisioningMode and SystemTaskExcludes exists.
ProvisioningModeshould be set to 'False' for normal operation, or 'True' if they are stuck in provisioning mode.
SystemTaskExcludes will be blank for normal operation, or contain various values if its stuck in provisioning mode.
As soon asI corrected these values, the newly deployed machines displayed the program advertisements in the Run Advertised programs window.
Hope this helps people down the track! It cost me a call to Microsoft Pro Support to resolve.
- Proposed as answer by Ma.Schmidt Monday, December 13, 2010 1:14 PM
Hi All,
I am facing same issue in sccm 2007 enviroment exactly same scenarion
As Scotty said I checked the Registry value but its value is false and Blank respectively
Still not resolved issue and working on high SLA please help some one