Month: July 2014

In the spirit of ‘eating your own dog food’ I often test new deployments on my team’s client devices – to make this easier I’ve created a WQL, query-based collection of all of their client devices based upon Primary User’s group membership. The nice thing about this group is that any new devices we’re testing will automatically be added.

{code lang:text showtitle:false lines:false hidden:false}Select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client
FROM SMS_R_System
JOIN SMS_UserMachineRelationship ON SMS_R_System.Name=SMS_UserMachineRelationship.ResourceName
JOIN SMS_R_User ON SMS_UserMachineRelationship.UniqueUserName=SMS_R_User.UniqueUserName
WHERE SMS_UserMachineRelationship.Types=1 AND SMS_R_User.UserGroupName=”DOMAIN\\GroupName” AND SMS_R_System.OperatingSystemNameandVersion like “Microsoft Windows NT Workstation%”{/code}

Issues with the Network Access Account following an SCCM 2012 R2 upgrade are not uncommon:

• http://social.technet.microsoft.com/Forums/en-US/7926a4ff-6ace-434b-bbba-7ddd00f3fda2/2012-r2-osd-refresh-winpe-network-access-account-issue?forum=configmanagerosd
• http://anoopcnair.com/2013/10/29/sccm-configmgr-2012-r2-known-issues/

Despite creating a new account, deleting the old account and recreating boot images we were still running into issues on some refresh scenarios with Task Sequences failing with a 80070002 error code – bare-metal deployments of new machines were fine, using the same boot images.

It turns out that the clients targeted by the refresh Task Sequence we’re still running the legacy, non-R2, SCCM client. After upgrading the client to the R2 version all Task Sequences ran without issue.

A revised version of a script I found here:
http://ccmexec.com/2012/02/installing-multiple-windows-7-hotfixes-msu-with-sccm/

Use this script in an SCCM package that contains MSU fuiles to mass install updates. You can include as many MSU files as you like.