Just want to say that this solution works. I was trying it on my @LAB and the problem was the SCCM policies refresh time + deployment recurrent time for the deployment.
Vicenç De: [email protected] [mailto:[email protected]] En nombre de Vicenc Rovira Torrens Enviado el: martes, 5 de julio de 2016 14:14 Para: [email protected] Asunto: [MDT-OSD] SCCM Collection variables + TS Dynamic application installation Hi all, I explain what I want to do and the issue I'm having. My customer don't have technical skills over SCCM and want that some of their employees will use it do the less possible actions on the console for deploying applications, as well as not creating single deployments for each of the applications they want to deploy to avoid human errors during the deployment. To simplify the use of SCCM, I've create a static custom task sequence that just installs applications based on collection variables and each of this variables has the name of the application to be installed. The deployment of this task sequence is configured to always rerun every week because if a new application version must to be upgraded, they should just upload the new application in SCCM and change the value of the existing variable to point to the new application name. The problem I'm facing is that if I modify the value of the collection variable for the application I want to upgrade to the new version, and the Task Sequence has already been executed on computers, the task sequence don't read properly the new variable value and always try to install the old version. Example: Collection A APPS01 Adobe Acrobat 9.0 APPS02 Microsoft Office 2013 After some weeks, we upgrade the Acrobat version and we modify the right collection variable Collection A APPS01 Adobe Acrobat 10.0 APPS02 Microsoft Office 2013 The task sequence that uses these variables and that is executed recursively every week don't install the Adobe Acrobat 10 but always tries to install the Adobe Acrobat 9.0 (in fact it don't install Adobe Acrobat 9.0 because it's already installed and the detection method for the application itself works like a charm). It's like the Task Sequence can't read the new value for the variable or, that the task sequence when it's executed on the computer, reuses the variable value from a previous execution. Someone knows if this is a product bug or it's the normal behavior of the interaction between recurring Task Sequences and Collection variables? Thank you all!! Vicenç
