patch

Build and Capture fails if KB3160005 IE sec cumulative update is installed


Update: Adding more scratch space to the boot wim seems to have resolved the problem on Windows 10, Windows 7 seems to still have issues.

Update: This update is also in Windows 10 CU 3163018, causing the same error. No workaround yet 

If your build and capture is failing at the capture step make sure you don't have the cumulative Security Update for IE11 KB3160005. It's somehow stopping the registry load part of the step.

The task sequence execution engine failed executing the action (Capture the Reference Machine) in the group (Capture the Reference Machine) with the error code 2147943850
Action output: ... software" into HKLM\OfflineRegistry1
RegLoadKey( oRegKeyHKLM, sRegKey, sRegHivPath), HRESULT=800705aa (e:\qfe\nts\sms\framework\osdcore\offlineregistry.cpp,68)
LoadHive( szPathBuffer, m_sRegKeySoftware, m_oRegKeySoftware ), HRESULT=800705aa (e:\qfe\nts\sms\framework\osdcore\offlineregistry.cpp,190)
m_oOfflineRegistry.Init(pszSystemRoot), HRESULT=800705aa (e:\qfe\nts\sms\framework\osdcore\offlineos.cpp,737)
rDefaultOs.initialize(sTargetSystemRoot), HRESULT=800705aa (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,613)
VerifySystemForCapture(DefaultOs), HRESULT=800705aa (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,859)
Finished with error code 0x800705AA
Failed to load "C:\WINDOWS\system32\config\software" (0x800705aa).
Failed to load the offline SOFTWARE registry (0x800705aa).
Failed to validate for capture. 
nsufficient system resources exist to complete the requested service. (Error: 800705AA; Source: Windows). The operating system reported error 2147943850: Insufficient system resources exist to complete the requested service.

 

Creating Collections to deploy ConfigMgr client updates (the easy way)

main

Get the Servicing Exstension from Microsoft NOW as it does all the work!!! http://blogs.technet.com/b/configmgrteam/archive/2014/12/09/now-available-microsoft-system-center-2012-configuration-manager-servicing-extension.aspx

Once you have this, in the Admin node, there's a site servicing section -> client targeting. You click 'Create Query' and it makes a nice query for your collections.

CreateColls

Then you go about creating your collection.

Screenshot 2015-02-05 09.39.11

click next. Select Add Rule -> Query Rule

 

Click Import Query Statement and choose the nice query microsoft made for you.

Screenshot 2015-02-05 09.44.29

Deploy the cumulative update to the clients.

 

 

How To: Create Automatic Deployment Rules for Patch Tuesday Software Updates

automate

Automatic deployment of updates is one of the best features of SCCM. Automation in general is awesome.

The best way to use Automatic deployment rules (ADR) is to have them run on Patch Tuesday which is the second Tuesday of the month when Microsoft releases their updates generally before 11:00 PST/PDT (I am Australian based so I set ADRs to run Wednesday Morning).

In this example I am deploying Windows 8.1 x64 critical, security and 'updates' updates.

1. Under the Software Library Node Software Updates click Automatic Deployment Rules then select 'Create Automatic Deployment Rule' from the Ribbon

adr1

2. In the Wizard name your ADR 'ADR: Windows 8.1 x64 Updates'

ADR2

3. Click Browse and select your target collection

4. Change the Option to 'Create a new Software Update Group'. The other Option should really be called 'Wipe previous updates from Software Update Group' as that's what it does.

5. Click Next.

6. Ensure 'Automatically deploy all software updates found by this rule, and approve any license agreements. Also optionally enable the Wake-on-LAN tickbox.

adr3

7. Click Next

8.  Choose Date Released or Revised, set it to Last 3 weeks.

adr4

9. Choose Product, set it to 'Windows 8.1'

10. Choose Update Classification, set it to “Critical Updates” OR “Security Updates” OR
“Updates”

11. Choose Title, set it to 'x64'. This is to filter out x86 updates.

12. Click Preview, if you are doing this on Patch Tuesday you will see all the applicable updates that will be deployed. Otherwise you can change the date range for the example.

adr5

13. Click Next

14. Choose 'Run the rule on a schedule.

adr6

15. Click Customize and choose to run the rule every second Tuesday at the appropriate time depending what time zone you are in. Click OK (Not to important for the demo as you can run it manually)

adr7

16. Click Next

17. Customize the Deadline to 'As soon as possible'.

adr8

18. Click Next

19. Change the User Experience to 'Display in Software Center and show all notifications'

adr9

20. Tick 'Software Installation'.

21. Click Next.

22. Click Next.

23. Click Next

24. Choose Create a new deployment package.

adr12

25. Name it 'ADR: Windows 8.1 x64 Updates' and select a UNC share for storage of the software updates.

26. Add Distribution Points.

adr13

27. Click Next.

28. Click Next

29. Select desired languages, click Next

adr15

30. Click Next, then Close.

31. Right click on your newly created ADR and click 'Run Now'. You can monitor progress on the site server checking Program FilesMicrosoft Configuration ManagerLogsruleengine.log

adr18

32. Give it some time to download updates and distribute them then on the client machine run a machine policy update and verify updates install using Software Center

adr19

 

33. After having a play check out this post for some best practices to setting up all your Automatic Deployment Rules including Piloting your updates to a pilot group for 7 days.

34. Also check out this post to automate sending a report out on what updates are being deployed.

 

 

 

How I automate patching desktops

update automation

It takes a long time to setup but worth it, computers should
not get policies they don’t need, at some point things will start stuffing up. I
have split desktops into 3 categories that suit our environment. Pilot get updates straight away and will reboot at night. Prod and PUC get updates 7 days later and have different reboot requirements.

Group

Deadline

User notifications

Deadline behaviour outside maintenance window

Device restart behaviour

Pilot

Asap

All

SW Updates Install

Yes

Prod

7 days

None

SW Updates Install

Suppressed

PUC (Public Use computers such as Labs)

7 days

None

SW Updates Install

Yes

I then split these groups into collections based on OS or
Office version requirements, so we have Office 2007, Office 2010, Office 2013,
Windows XP, Windows 7 x86, Windows 7 x64, Windows 8 x64.

A Pilot, PUC and PROD collection should be made so you can
limit the collections with it. These collections will vary in your environment.

Based on that you should have 21 collections - see ‘rules
and queries’ at the end for the messy queries

SUM-WORKSTATIONS-PROD–Office 2007

SUM-WORKSTATIONS-PROD–Office 2010

SUM-WORKSTATIONS-PROD–Office 2013

SUM-WORKSTATIONS-PROD–Windows XP

SUM-WORKSTATIONS-PROD–Windows 7 x86

SUM-WORKSTATIONS-PROD–Windows 7 x64

SUM-WORKSTATIONS-PROD–Windows 8 x64

SUM-WORKSTATIONS-PILOT–Office 2007

SUM-WORKSTATIONS- PILOT–Office 2010

SUM-WORKSTATIONS- PILOT–Office 2013

SUM-WORKSTATIONS- PILOT–Windows XP

SUM-WORKSTATIONS- PILOT–Windows 7 x86

SUM-WORKSTATIONS- PILOT–Windows 7 x64

SUM-WORKSTATIONS- PILOT–Windows 8 x64

SUM-WORKSTATIONS-PUC–Office 2007

SUM-WORKSTATIONS- PUC–Office 2010

SUM-WORKSTATIONS- PUC–Office 2013

SUM-WORKSTATIONS- PUC–Windows XP

SUM-WORKSTATIONS- PUC –Windows 7 x86

SUM-WORKSTATIONS- PUC–Windows 7 x64

SUM-WORKSTATIONS- PUC–Windows 8 x64

Update: 

Limit your pilot collections to a group of user's primary computers using this collection query

 

[code language="sql"]
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\SCCM Software Updates Pilot User Group"
[/code]

 

Thanks Powersheller

Next you create a Software Update Group (the current
baseline of approved updates) for each Office/OS Version and a deployments for
each based on the rules from the first table.

Then you create Automatic Deployment rules for each
collection based (to run on Patch Tuesday/Wednesday Australia time) on the
rules from above and what type updates you want released in the last 3 weeks.  They should be set to create a new software update group each time. See ‘rules and queries’ for what I have used.

You can also create an EndPoint Protection definitions ADR, however that should be set to use the existing software update group as the updates always superseed each time.

Rules and Queries:

Query Name

Query

Office 2007

See attachment

Office 2010

See attachment

Office 2013

See attachment

Windows XP

See attachment

Windows 7 x86

See attachment

Windows 7 x64

See attachment

Windows 8 x64

See attachment

Attachment - Download

Rule Name

Rules

Office 2007

Date Released or revised: Last 3 weeks

Product: “Office 2007”

Title: 32-Bit

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates” OR “Definition Updates”

Office 2010

Date Released or revised: Last 3 weeks

Product: “Office 2010”

Title: 32-Bit

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates” OR “Definition Updates”

Office 2013

Date Released or revised: Last 3 weeks

Product: “Office 2013”

Title: 32-Bit

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates” OR “Definition Updates”

Windows 7 x86

Date Released or revised: Last 3 weeks

Product: “Windows 7”

Title: -x64

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates”

Windows 7 x64

Date Released or revised: Last 3 weeks

Product: “Windows 7”

Title: x64

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates”

Windows 8 x64

Date Released or revised: Last 3 weeks

Product: “Windows 8” OR “Windows 8.1”

Title: x64

Update Classification: “Critical Updates” OR “Security Updates” OR
“Updates”