SCCM Deployment Evaluation

[Geoff]

I'm trying to get my head round this and came up blank when searching.

 

If I have two deployments for something, say an application, that targets two collections with different deployment settings but a device is in both collections which one 'wins'?

Edited September 7, 2017 by Geoff

[sparkeh]

I'm trying to get my head round this and came up blank when searching.

 

If I have two deployments for something, say an application, that targets two collections with different deployment settings but a device is in both collections which one 'wins'?

Just to clarify what you mean, is the scenario that you have 1 application, with 2 different Deployment Types with different settings, deployed to 2 collections and there is a device in both collections?

 

If this is the case then the which Deployment gets in first won't matter as the same thing is going to happen either way (the same Deployment Type will run as Deployment Types are evaluated in priority order so the first Deployment Type that matches the requirements runs). When the second Deployment runs it will detect that the application is already installed.

 

Or do you mean something different?

Edited September 7, 2017 by sparkeh

[Geoff]

Ok, I'll be specific.

 

A single application with a single 'Script' delpoyment type that is deployed to a collection called 'Windows 10' with a deadline of next week. The same is also deployed to a collection called 'Test' with a deadline of 5pm.

 

Which deadline will apply?

[sparkeh]

Ahh well that's a different kettle of fish

 

Of course if it reaches the 5pm deadline before either deployment has run then that will should run. However... the dark art of which sccm clients run which deployments in which order is beyond my skills. I half suspect that you will find that some clients run one deployment first, and the others run the other one first. I haven't observed any discernible logic to this in all the years I have used sccm. :S