SCCM Package Deployment Issue

[StephenHardy]

Hi There,

 

I have a SCCM 2012 R2 question.

 

Basically, I think everything is setup fine, client install the Config Manager & SCEP 2010 application, however when I try to push an application out the deployment sits 'In Progress' 'Waiting for Content'

 

The client machine which is a member of the collection I am pushing the MSI out to seems to know it needs to install the simple MSI application but never gets anywhere:

 

DCMAgent.log:

{F1EA6E6D-FB4D-4AF0-B64C-7636A8D3CF17}

'

]LOG]!>

 

Any ideas?

 

Thanks

 

Stephen

[zoohead]

Hi Stephen

 

Have you distributed the package to your distribution point and configured the package to either download from the DP or run directly from it?

 

Cheers,

Ian

[StephenHardy]

Hi Ian,

 

It is distributed to the DP - not sure what you mean by configuring the package to run from the DP or run directly from it - where is this setting?

Would it help if I put together some screen shots?

 

Thanks

 

Stephen

[StephenHardy]

Just found it I've set it to 'Download Content from DP and run locally'

[zoohead]

Hi Stephen

 

On the package properties, distribution settings tab, is it set to "Automatically download content when packages are assigned to distribution points"? I am no sccm expert but have had similar problems to yours when setting up.

 

Cheers,

 

Ian

 

- - - Updated - - -

 

Just missed your reply!!

[zoohead]

Some packages will only install when run directly from the DP. Worth a try?

[StephenHardy]

Getting this in the AppDiscovery.log file now:

 

 

Deployment Status in the Config Manager Console still showing as waiting for content however...

[StephenHardy]

Right, here's the Content Status:

 

 

 

 

 

Here's the DP Status:

 

 

Here's the Application Distribution Settings:

 

 

 

Deployment Options:

 

 

1 Question - does the 'Content Location' have to be a share visible to all?

 

Thanks

 

Stephen

[StephenHardy]

Now shows as content downloaded in the Deployment Status but not doing anything on the client station

 

[StephenHardy]

Bit of an update on this - the package (.msi) now sits on the client but doesn't do anything....

[StephenHardy]

It's installed now, but the deployment shows as failed... Not entirely sure how to get this to show as succeeded. Anyone have an idea?