I'm new to SCCM and have got several things working on it despite my lack of experience. I've been able to get machines to accept operating system advertisements but as far as getting clients to accept software advertisements it's been really stubborn. My site is in mixed mode. It's running SCCM 2007 R2. The clients are installing via push. They are reporting back to the manager console as installed and approved. When I look in the "PolicyAgent.log" on the client it says, "Received full policy update with 0 assignments" over and over again. Other logs seem to be fine. Except "execmgr.log" shows three errors: Software Distribution Site Settings for the client are missing from WMI. execmgr 4/28/2011 1:22:13 PM 6756 (0x1A64) Software Distribution Site Settings for the client are missing from WMI. execmgr 4/28/2011 1:22:13 PM 6756 (0x1A64) Common Client Agent Settings for the client are missing from WMI. execmgr 4/28/2011 1:22:13 PM 6756 (0x1A64) Software distribution agent was enabled execmgr 4/28/2011 1:22:32 PM 2968 (0x0B98) This is when the client was first installed. Other posts have said that the this is common for a newly installed client. I'm really stumped as to why the operating system deployment is working fine but the software isn't. I'm thinking it's some setting in Software Distribution Package or Program. Thanks for your help.

Do the clients see the site code?Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler

Are you seeing the site code in the client? 1. was AD extended and 2. are the boundaries setup correctly?Jay Parekh Project Leadership Associates

Yes. They are seeing the site code. Yes the boundaries are set up correctly I think... The boundaries are set up via subnet of the network. 3 subnets. One for workstations, one for servers, and another for a T1 connection that we have going to another location. UPDATE: I Rebooted the machine and it's seeing the policy updates for the software package. I changed the option that the software advertisement was assigned to no assigned (now I can't find where that option went) and it's now working. I would like it to be an assigned program. This probably helps with determining what the problem is.

You need to give us a lot more details about how you have configured things and how you are testing things because its meaningless to just say it doesn't work. Things like (but not limited to): Does the advert have a schedule; i.e., is it mandatory? Is the content on an accessible DP? Have you refreshed the policy on the client? Is your MP functional? Are you targeting users or systems? Have you verified that the target in in the collection? This is just a handful of possible/obvious questions; as mush detail as you can provide helps us help you.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I thank you for your patience with me. As I said before, I'm new to this whole thing. Thanks for letting me know what you need to know. To answer the your questions: Does the advert have a schedule; i.e., is it mandatory? It's not mandatory (the option to assign it as mandatory is the part that's not working.) It's not on a schedule. When I test it out by setting it to mandatory I set it to "As soon as possible" Is the content on an accessible DP? Yes, I browse to the package location with windows explorer and can access it. Is there another method to test this? Have you refreshed the policy on the client? Yes. I'm doing this by going to the "Configuration Manager (32-bit)" properties in the control panel and initiating the "Machine Policy Retrieval & Evaluation Cycle" and the "User Policy Retrieval & Evaluation Cycle" actions Is your MP functional? yes I'm getting a "Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK" from mpcontrol.log Are you targeting users or systems? Systems Have you verified that the target in in the collection? What do you mean by verified? When I look at the machines in the test environment in the Configuration Manager Console I see in the Approved Column "Approved" for all the machines. If there is another status I should be looking for somewhere else where should I look? Thanks for all the help you're giving me!

This issue can be caused by the WMI corrupted in the clients. You may rebuild WMI in batch mode and reinstall the client to check. 1. Log on with the built-in Administrator account 2. Run ccmclean /client 3. please use the following batch mode to register the WMI: @echo off sc config winmgmt start= disabled net stop winmgmt /y %systemdrive% cd %windir%\system32\wbem for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s wmiprvse /regserver winmgmt /regserver net start winmgmt 4. after that, to reregister modules: At a command prompt (cmd), change to the WBEM folder. cd %windir%\system32\wbem please go to use the following command to register the MOF and MFL files: for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s 5. please push the client installation again. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.