Search This Blog

Loading...

Wednesday, June 8, 2016

System Center Configuration Manager Cmdlet Library 5.0.8373.1189

Microsoft has released a new update for the SCCM cmdlet Library 5.0.8373.1189

image

Release History:

6/6/2016 - Update Release, version 5.0.8373.1189. Contains bug fixes
5/16/2016 - Update Release, version 5.0.8373.1182. Contains bug fixes and support for Configuration Manager (current branch - version 1602)
1/25/2016 - Update Release, version 5.0.8328.1155. Contains bug fixes and support for Configuration Manager (current branch - version 1511)
9/9/2015 - Update Release, version 5.0.8249.1128. Contains bug fixes and support for Configuration Manager SP2/R2 SP1
4/13/2015 - Initial Release, version 5.0.8231.1004.

Update check logic

In previous releases, the check for an updated version of the Cmdlet Library was performed on cmdlet execution if a certain time limit had passed. This check now occurs only when a new CMDrive instance is created. This change was made to reduce the number of warnings that may be written when there is an update available. For more information on this feature and how to configure it, please see the documentation at https://technet.microsoft.com/en-us/library/dn958404.

Download link

The System Center Configuration Manager Cmdlet Library Documentation

 

image

image

Thursday, May 19, 2016

Task Sequence error code (0x80070002)

You might se this error when deploying Windows from a SCCM 1511 task Sequence:

Task Sequence: xxx has failed with the error code (0x80070002)

image

If we take a closer look at the smsts.log file, you will in this specific case find the message No credential information in environment.

image

The reason will probably be that no Network Access Account has been defined, go to Administration, Overview, Site Configuration, Sites, in the top select Configure Site Components and Software Distribution.

image

Select the tab Network Access Account, an enter a account to use when access network locations.

image

See more information about this account here https://technet.microsoft.com/en-us/library/hh427337.aspx (search for Network Access Account)

Also see this post http://larslohmann.blogspot.dk/2016/01/task-sequence-error-code-0x80070002.html for another possible solution for the same error.

Monday, May 9, 2016

Citrix Receiver for Windows 4.4.1000.16 (CU1)

Citrix has released a new version of Citrix Receiver for Windows, new version is 4.4.1000.16 (CU1)

image

You will find ADMX/ADML files in the installation folder (C:\Program Files (x86)\Citrix\ICA Client\Configuration) or here https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

image

Download installation file :

https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

Changes is this version and documentation:

http://docs.citrix.com/en-us/receiver/windows/4-4.html

Thursday, April 28, 2016

Windows 10 and Office 2013

When deploying Windows 10 and Office 2013 with SCCM (here 1602) you might see that the update progress stops and the task sequence hangs.

image

If you take a closer look at the WUAHandler.log you will also notice that the installation progress has stopped.

image

Opening the event viewer will reveal that updates are actually still being installed.

image

Right now one workaround is to wait for all updates to be installed.

This is when you no longer see updates being installed in the Event Viewer and the Windows Update service change status to stopping.

Now the task sequence will hang for real.

image

Find the process ID for the Windows Update Service and terminate the process.

sc queryex wuauserv | find "PID"

taskkille /PID <ID from sc queryex> /F

image

This will of course change the status to not running.

image

The SMS Agent Host  will now change status to Stopping.

image

Stop this process as well:

sc queryex ccmexec | find "PID"

taskkille /PID <ID from sc queryex> /F

image

The task sequence should now continue:

image

Not pretty but ………..