Deploying Applications with SCCM 2007 R2 SP1

[CaptainJack]

I've followed the step-by-step instructions here for deploying an application using SCCM 2007 -- even going so far as to test with Firefox. I created the package, the application and the advertisement just as was laid out in AnyWeb's post. Followed every step exactly. Got nothing. I'm trying to use SCCM to deploy applications to Windows XP SP3 and it just isn't happenin'. I recognized my first mistake and went back blew the entire package setup away and started over from scratch. Reconstructed everything again exactly as the post recommended and lo-and-behold, same ol' thing ... nothin' again.

 

So, my questions is this...is SCCM not supposed to broadcast advertisements to WinXP? Or am I doing something else wrong? Everything goes up smoothly and just like it's supposed to. What doesn't happen is that when I turn on the advertisement, the WinXP box never acknowledges that the advertisement is there nor does it try to download the program to execute. I've even allowed as how SCCM might take its own sweet time replicating everything between the main SCCM server and the distribution point from which I want to receive the package.

 

Ideas???

[Peter van der Woude]

Did you already take a look at the execmgr.log?

 

Also for the next time when you are waiting on an advertisement, just go to the action tab (of the client) and iniatiate the machine policy cycle.

[CaptainJack]

Did you already take a look at the execmgr.log?

 

Also for the next time when you are waiting on an advertisement, just go to the action tab (of the client) and iniatiate the machine policy cycle.

 

I initiated the policy cycles and still nothing.

[Peter van der Woude]

Did you already take a look at the execmgr.log?

[CaptainJack]

Did you already take a look at the execmgr.log?

 

How do I do that?

[CaptainJack]

Here's what I have so far:

1) Under Advertisements, I have the advertisement I created, then what appears to be another advertisement that I don't remember creating. In both advertisements, the application (Firefox) is active.

 

2) I click on Software distribution and I see a graph labeled "Status for Selected Advertisements". The graph shows 1 object (as it should) colored yellow indicating "waiting". When I click on the name of the advertisement, I get Status of a Specific Advertisement. Down in the status window, I see Resource Receipt Status = Accepted; Number of Resources = 1 (this is correct); Percentage of Resources = 100 and Advertisement ID number. Below that is Status of Targeted Resources = Waiting. When I click on the open arrow next to Waiting, I get the correct NetBIOS name, User domain, etc. When I click the open arrow next to the NetBIOS name, I get the Advertisement Status Messages for a Particular Client and Advertisement report. The first Message State Name says: Accepted/Program Received. The second Message State Name says: Waiting/Waiting for content. I click on the open arrow of the Waiting name and get this description message:

 

"The program for advertisement "<Advertisement ID> has not yet started because the content for the package "<PACKAGE NAME>" - "Firefox" (version 6) has not been acquired. Possible cause: The content for this program must be downloaded into the computer's cache, or the content could not be located. Solution: If the program is being downloaded, no action is required. The program will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer. Distribution point availability can be affected by roaming boundary configuration which is used to determine whether distribution points are classified as local or remote, or by enabling distribution points as protected distribution points. Distribution point availability can also be affected if you are using branch distribution points and the advertisement is configured with the option Run program from distribution point instead of Download content from distribution point and run locally. This is because branch distribution points do not support advertisements that are configured to run directly from a distribution point."

 

So now I'm asking what does all of that mean?

[CaptainJack]

Oh, and one more thing...I have since discerned that we are using SP2 not SP1.

[YiannosG]

It looks like it cant find the program on a distribution point.

 

Have you create and updated your distribution points with the new package?

 

 

 

 

 

Check under distribution points if you see your distribution point and under package status to check if its installed correctly. Afterward you can update it.

 

Let me know how it goes

[CaptainJack]

YiannosG:

 

I did the update even after I recreated the package and the advertisement. The update seems to have taken (as before) but it's still not working. I even got a status message at the bottom of the window saying Action: Complete. When I open the distribution points folder in the ConfigMan Console, I see my distribution point but nothing seems to be happening. I initially set this up before I went to lunch, then when I came back, I had to go to a meeting, so the client and the server have been over two hours sitting around for the process to run uninterrupted. I'm losing my hair...

 

BTW: how did you manage to post the screen shots here? I've been trying and haven't had any luck.

[YiannosG]

Do you have the advertisment to run from distribution point or do you have it to download and run locally? If you go on the client computer to C:\windows\system32\ccm\cache do you see the package there?

 

Maybe you are not allowed due to low post count and since these are pictures from windows-noob.com so it might not count.

[CaptainJack]

Do you have the advertisment to run from distribution point or do you have it to download and run locally? If you go on the client computer to C:\windows\system32\ccm\cache do you see the package there?

 

I don't have a CCM folder under C:\Windows\system32...