How to use Collection Variables outside of Task-Sequences

Out of the box, Collection and Device Variables are only usable from within Task-Sequences. To get the Variables outside of Task-Sequences, you can install an additional WMI Provider (https://gallery.technet.microsoft.com/ConfigMgr-Collection-1650d5bc) that provides the Variables and Values in a separate WMI Class (root\ccm\clientsdk:EXT_CollectionVariables ) Example to get all Variables assigned to the local device: Get-WMIObject -Namespace ‘root\ccm\clientsdk’ -Class ‘EXT_CollectionVariables’ Example to get...

Read More»

10 Tips for a More Successful Windows Image Build & Capture

In a recent build and capture (b&c) task sequence for ConfigMgr 2012 R2 that I was helping a customer with, I decided it was worthwhile to list the top things that can be overlooked.  If these are done prior to beginning the process, then it can help to shorten and troubleshooting time involved. Create an […]

Read More»

Multiple copy of Applications during ConfigMgr Task Sequence

SCCM Task Sequence issue in stand alone media I am currently working with a customer that has a strange issue during ConfigMgr standalone media Task Sequences provided to remote workers. The issue is happening during installation of applications, which are installed as part of the Task Sequence. The issue is around the copy of sources into the cache and with this customer is happening since version 2012 SP1 and is still there in R2. What’s happening is that all the applications inside the Task Sequence get copied into the client’s cache multiple times. Right now there are 24 applications inside this Task Sequence, they are put into 4 different “Install … Continue reading

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»

Workaround for OSD Stand-alone Media with Client Hotfix Installs

When using stand-alone media to image a computer, you may potentially run into a failure with the Task Sequence with SMSTS.log message “Client installation failed, code 1 – The client GUID must be set in an environment variable”.  Checking further into the client.msi.log file, you could see the source problem similar to “Unable to create […]

Read More»