Phylum

What guide(s) are you following for doing this? I can understand this completely. Just curious, is Win 11 on the roadmap? What are the blockers to upgrading/deploying machines with Win 11?

Thanks for the reply Niall! By the way congrats on the book! I did see your post prior to posting but a. I was hoping to avoid having to create new boot media b. The time is already correct before getting the list of Task Sequences c. Although running the following will 'update' the time, the underlying problem still exists net use \\server_name\ipc$ /user:domain\user Passw0rd! net time \\server_name /set /y d. Once he TS starts, its process is to default to the Time Zone already set in WinPE and update the date/time accordingly. Wish there was an option to simply use the BIOS date/time versus trying to 'fix it'. I ended up going in a slightly different direction to set the correct time zone in WinPE and update the time. I'll consider posting details later once I've put it through its paces.

Consider the following: The BIOS date & time are correct Date & time remain correct up until the Task Sequence selection screen Once a Task Sequence is selected, the date & time are updated to the built-in WinPE timezone, thus making it the incorrect time. Is this normal and expected behavior?

Thanks for the reply GarthMJ. I updated the original post but in short Attended: One or more users is logged into it, be it physically or via RDP. The machine may be actively being used (e.g.: user is doing something) OR it may just be locked (e.g.: user locked the workstation before going to lunch) Unattended: Machine is powered up and no users are logged into it; Presumably sitting at the login screen.

Is it possible for ConfigMgr to determine whether or not a machine is attended or unattended? Attended: One or more users is logged into it, be it physically or via RDP. The machine may be actively being used (e.g.: user is doing something) OR it may just be locked (e.g.: user locked the workstation before going to lunch) Unattended: Machine is powered up and no users are logged into it; Presumably sitting at the login screen. If so, what would the query look like? There are several possible scripted solutions online but I was hoping to tap into a built-in SCCM attribute class/attribute pair to retrieve this information on demand versus executing a script to crawl AD and query machines individually.

Agreed - nice find and we do appreciate you sharing! I do have some questions if you can recall any details at this point: What was the troubleshooting process that led you there? What update(s) failed? What process is responsible for writing out those keys: The updates themselves? Windows Update Agent? Windows? Do all three keys need to be present for this condition (problem) to exist, or is it any combination of one or more? Thanks!

I encountered this today after upgrading from: SCCM 2012 R2 SP1 MDT 2013 ADK 8.1 To: SCCM 2012 R2 SP1 + CU1 KB3074875 + Hotfix KB3084586 MDT 2013 Update 1 ADK 10 As crazy as this sounds, a reboot solved the issue. You see, after applying the SCCM updates, we bounced the box but didn't bounce it after installing the ADK and MDT. We attempted to build several boot images but it always failed with: Started processing. Creating boot image. Copying WIM file. Mounting WIM file. WIM file mounted. Setting Windows PE system root. Set Windows PE system root. Set Windows PE scratch space. Adding standard components. Adding component: winpe-dismcmdlets Adding component: winpe-mdac Adding component: winpe-netfx Adding component: winpe-powershell Adding component: winpe-securebootcmdlets Adding component: winpe-storagewmi Adding component: dart8 Adding extra content from: C:\Users\USERNA~1\AppData\Local\Temp\2\a21hk3ml.g4n Unmounting WIM. Copying WIM to the package source directory. Creating boot image package. Error while importing Microsoft Deployment Toolkit Task Sequence. Failed to verify that the WIM file has a valid compression type. Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Put(PutOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) --- End of inner exception stack trace --- at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data) Interestingly, a WIM was created but when we attempted to import the WIM, it complained that the WIM needed to be compressed. (Sorry, I lost the clip with the error text.) Several permutations later, after ruling out the possibility of a share/permissions or networking issue, or an issue with our extra files and pre-start commands etc., we bounced the box. It came up and worked fine. Crazy that a restart solved the issue.

I went through a number of tests using diskpart, bootrec and mbrwiz. Yesterday I had a troubleshooting session with Microsoft who provided me with two versions of dskprobe (v2 & v3). They were able to witness that every time, the commands 'succeeded' but the MBR was still intact. In DskProbe we can see exactly what's in sector 0, re-write it or copy from another sector to sector 0, and here's where it gets interesting. DskProbe shows the bootguard data in sector 0 (as expected) so we tried leveraging DskProbe's builtin utilities to manipulate sector 0: write zeros to sector 0 save another zeroed out sector to a file then import that file to sector 0 copy another zeroed out sector to sector 0 Each time, it completed successfully and DskProbe showed all zero's in the UI. However, upon refreshing the disk or re-reading sector 0 or restarting DskProbe and re-reading the disk, sector 0 is intact! Its as if we never touched it. However: performing the same steps on the same machine to an unencrypted volume, like a 1GB VHD,all the tools work as expected. booting a Windows ISO and running bootrec or diskpart works also Therefore, we all had to assume that since: the MBR/sector 0 wipe commands don't work from machines that have PGP installed the MBR/sector 0 wipe commands don't work from our WinPE WIM (which has the PGP drivers baked in for recovery purposes) But the stock Windows ISO's (7, 8, 8.1) do work, it must be PGP. There seems to be something about Symantec Encryption Desktop/PGP, perhaps their filter driver, that prevents one from wiping the MBR or sector 0. I've circled back to Symantec's support team and I hope they can tell me there's a way to bypass this. The only thing that does wipe the MBR, and we confirmed this yesterday, is running 'convert gpt noerr' & 'convert mbr noerr' in diskpart. But adding that step to the Task Sequence causes the imaging process to break, and I don't yet know why: Task Sequence Starts Before the format & partition step I run the diskpart script that cleans, converts to gpt then converts back to mbr The format & partition step runs WIM is applied Reboots Windows does its hardware detection Reboots Windows boots and I see the 'Wizard Error' message: Unable to find the Task Sequencer. The deployment will not proceed. I'm able to reproduce this on 3 out of 4 machines. If I take that diskpart step out, all machines image successfully every time. And, in case anyone is wondering, it doesn't matter of the machines were encrypted to begin with or not prior to imaging. Adding that script results in a high failure rate and I don't know why. At this point, I think this thread can be closed since its not a Microsoft issue, but a third-party that's preventing the tools from functioning correctly. If I find a solution to why adding the diskpart script creates that 'Wizard Error' then I'll update this post.

Thanks for the reply. Do you have suggestions on such apps, especially ones that work in a 64-bit PE environment? I used to use mbrwiz back when we were still using Ghost in WinPE 2 & 3, and although it appears to work in WinPE 5 (no errors when executing; claims it completed successfully) it doesn't appear to be doing anything. There wouldn't happen to be a x64 fdisk executable floating around, right?

As the title suggests: I'm looking for guidance on how to wipe the MBR via Task Sequence during an OSD. Any suggestions? We use Symantec Encryption Desktop (aka PGP) and it adds a bootguard to the MBR which needs to be cleared out (we need to wipe the MBR) in order for the machines to boot successfully. If I boot a Win8.1 amd64 ISO, select Repair > Advanced > Command Prompt > Run bootrec.exe /fixmbr, it works fine and corrects the issue so I thought "Why not add bootrec to our amd64 WinPE.wim?" I copied what I thought were the necessary files into our amd64 winpe.wim, based on the following sites: https://channel9.msdn.com/forums/TechOff/456721-Windows-PE-with-BOOTRECEXE/ http://gregwoods.co.uk/2010/04/creating-a-winpe-boot-dvd-for-disk-cloning/ http://www.audiodude.nl/?p=1217 I even pulled in the MUI's from WinSxS into the WIM And although it appears to run successfully, it executes and produces no errors, it doesn't seem to actually be doing anything as the problem persists on a reboot. Running bootrec /fixmbr and/or bootrec /fixboot multiple times in our amd64 WinPE media doesn't work; but booting a amd64 Win8.1 ISO and running bootrec /fixmbr once works. I've tried the following with no positive results: Creating a diskpart script to sel dis 0 and clean isn't sufficient; doesn't wipe the MBR Converting the disk to GPT then back to MBR, but prior to the format & partition step, will remove bootguard. HOWEVER, it causes the TS to fail once it gets into Windows with the following error: "Wizard Error: Unable to find the SMS Task Sequencer. The deployment will not proceed." I've tried doing this two ways, and while it clears the MBR, I get the 'Wizard Error' above. 1) Via a Task Sequence step that runs a diskpart script (again, prior to the format & partition step), and 2) Adding 'oUtility.RunCommandWrite oExec, "CONVERT GPT NOERR"' to around line 340 of the ZTIDiskPart script. Symantec says that uninstrumenting the drive should correct this, but you cannot uninstrument an encrypted disk and the decryption process takes way too long. (About 24 hours) Secure wiping the disk (e.g.: via WipeDisk, DBAN) works but takes way too long. (Several hours) Thoughts?

Pre-Thanksgiving Bump!

We're fine with backing up themes, wallpapers and other display customizations (DPI, window color & appearance etc.) because it gives us something to go back to or restore if its truly need. However, we do not want to restore the aforementioned on the destination PC by default. I must be doing something wrong and I can't figure out what and need some help. I've read some great write ups on the subject: USMT Custom XML the Free and Easy Way USMT 4.0 Custom Sample - Blocking Wallpaper and Theme Migration from Windows Vista and Windows 7 Blocking Wallpaper Migration with USMT (or: you are a jerk) and used part of their example XML in my own, but everything (wallpaper, themes and other display customizations) is still coming over. Now I'm trying to use MigXmlHelper.DestinationPriority() but really its just a last ditch effort. From an elevated command prompt in C:\USMT\amd64\, I'm executing: scanstate.exe E:\USMTBackup /config:nothemeuiconfig.xml /i:MigApp.xml /i:MigDocs.xml /i:MigUser.xml /i:unconditionalexclusions.xml /i:blockwallpaperandthemev3.xml /i:getlocalpsts.xml /i:inclusions.xml /ui:domain1\user1 /ue:*\* /vsc /c /o /nocompress /localonly /v:13 /l:\\path\to\scanstate.log /progress:\\path\to\scanstate_progress.log /listfiles:\\path\to\scanstate_listfiles.log The blockwallpaperandthemev3.xml contains: <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/blockwallpaperandthemev3"> <component type="Documents" context="User"> <displayName>Block Wallpaper, Theme and Display Registry Settings</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <!-- Blocks wallpaper, themes (which include wallpaper) and other display/visual customizations (DPI, Screen Saver, Window Color & Appearance etc.) in the registry when migrating from Vista, 7 and beyond --> <pattern type="Registry">HKCU\Control Panel\Appearance\* [*]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [Pattern]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [TileWallpaper]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaperStyle]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop\Colors [*]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop\WindowMetrics [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\* [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\ThemeManager\* [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern> </objectSet> </unconditionalExclude> <merge script="MigXmlHelper.DestinationPriority()"> <objectSet> <pattern type="Registry">HKCU\Control Panel\Appearance\* [*]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [Pattern]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [TileWallpaper]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaperStyle]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop\Colors [*]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop\WindowMetrics [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\* [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\ThemeManager\* [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern> </objectSet> </merge> </rules> </role> </component> <!-- This component blocks wallpaper & screen saver files --> <component type="Documents" context="User"> <displayName>Block Wallpapers and Theme Files</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <content filter="MigXmlHelper.ExtractSingleFile(NULL, NULL)"> <objectSet> <pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern> </objectSet> </content> </objectSet> </unconditionalExclude> <merge script="MigXmlHelper.DestinationPriority()"> <objectSet> <content filter="MigXmlHelper.ExtractSingleFile(NULL, NULL)"> <objectSet> <pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern> <pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern> </objectSet> </content> </objectSet> </merge> <unconditionalExclude> <objectSet> <pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern> <pattern type="File">%CSIDL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Resources\Ease of Access Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Resources\Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Web\Wallpaper\* [*]</pattern> </objectSet> </unconditionalExclude> <merge script="MigXmlHelper.DestinationPriority()"> <objectSet> <pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern> <pattern type="File">%CSIDL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Resources\Ease of Access Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Resources\Themes\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Web\Wallpaper\* [*]</pattern> </objectSet> </merge> <unconditionalExclude> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Local\Microsoft\Windows\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Roaming\Microsoft\Windows\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Ease of Access Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Web\Wallpaper\* [*]","Fixed")</script> </objectSet> </unconditionalExclude> <merge script="MigXmlHelper.DestinationPriority()"> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Local\Microsoft\Windows\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Roaming\Microsoft\Windows\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Ease of Access Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Themes\* [*]","Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Web\Wallpaper\* [*]","Fixed")</script> </objectSet> </merge> </rules> </role> </component> </migration> I generated a config.xml called nothemeuiconfig.xml and changed this: <component displayname="Microsoft-Windows-themeui" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-themeui/microsoft-windows-themeui/settings"/> To this: <component displayname="Microsoft-Windows-themeui" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-themeui/microsoft-windows-themeui/settings"/> Opened a case with Microsoft, sent them: the XML's I'm using the command I used to generate the config.xml the command I used for scanstate the log files generated by scanstate the command I used for loadstate the log files generated by loadstate Summary result of the MS case: After much review & scrutiny, the command line and XML files are syntactically correct and rules are sound. The articles I referenced in the ticket are indeed old and speak of an older version of USMT, so I can accept the possibility that something may have changed between USMT versions that render those suggested rules & instructions invalid. Despite using unconditionalExclude to unconditionally globally exclude objects, something else is trumping that rule, and there’s no way around that. Even using MigXmlHelper.DestinationPrioity() won’t help us here because, like above, something else trumps that rule, and there’s no way around that. The last proposed suggestion is to disable the shmig component, which may or may not break or otherwise adversely affect the backup/restore of other things. (This may be too difficult to detect easily or in initial testing and the uncertainty doesn’t give us confidence problems won’t arise as a result of this change. Also, Ned Pyle's post says NOT to, but then again that's an old post.) Is this no longer possible or am I'm just doing it wrong?

Correct, .NET is an app. Software updates seems to break the installation of any application. If I skip the .NET install and go to IE11 or Office 2010 it fails the same way. What updates am I installing? That's good & somewhat difficult question to answer. I imported a fresh Windows 7 SP1 Enterprise WIM, performed Schedule Updates which installed 93 successfully. I went back to Schedule updates it again, only this time it said 71 were needed. However, whether I do all 71, half or even just 2, all the updates fail with the same errors: Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:02:32 PM 10352 (0x2870) Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\12300119\updated-install.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\12300119\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:02:32 PM 10352 (0x2870) Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:25:03 PM 10352 (0x2870) Checking if update (1 of 71) with ID 16811634 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:25:04 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\fc38fd35-1f4f-4c53-ba73-090c80368750\windows6.1-kb2835364-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:11 PM 10352 (0x2870) Applying update with ID 16811634 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:11 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:33.398 2014 ISTR0="16811634" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870) Failed to install update with ID 16811634 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870) Checking if update (2 of 71) with ID 16811689 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\28ed6c22-0b13-4202-a27a-17618cc6728e\windows6.1-kb2840631-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:40 PM 10352 (0x2870) Applying update with ID 16811689 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:40 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:48.430 2014 ISTR0="16811689" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870) Failed to install update with ID 16811689 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870) Checking if update (3 of 71) with ID 16812324 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\62ad16de-b149-43c7-83ff-5e68fad8de26\windows6.1-kb2847927-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:55 PM 10352 (0x2870) Applying update with ID 16812324 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:55 PM 10352 (0x2870) Failed to install update with ID 16812324 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:03 PM 10352 (0x2870) Checking if update (4 of 71) with ID 16815183 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:03 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\5096a2f8-d460-4cc9-9b84-5bb1c4a22255\windows6.1-kb2862966-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:10 PM 10352 (0x2870) Applying update with ID 16815183 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:10 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:17.208 2014 ISTR0="16815183" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870) Failed to install update with ID 16815183 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870) Checking if update (5 of 71) with ID 16815205 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\bea7d7ae-09fe-486a-8a84-6190970c7779\windows6.1-kb2861855-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:24 PM 10352 (0x2870) Applying update with ID 16815205 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:24 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:31.452 2014 ISTR0="16815205" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870) Failed to install update with ID 16815205 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870) Checking if update (6 of 71) with ID 16815279 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\88cc81ec-b8b5-4c60-8dfa-ce430024142d\windows6.1-kb2849470-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:38 PM 10352 (0x2870) Applying update with ID 16815279 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:38 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:46.081 2014 ISTR0="16815279" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870) Failed to install update with ID 16815279 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870) Checking if update (7 of 71) with ID 16815432 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\f3497d26-7995-4f66-8b3e-fdb692093111\windows6.1-kb2844286-v2-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:54 PM 10352 (0x2870) Applying update with ID 16815432 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:54 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:01.719 2014 ISTR0="16815432" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870) Failed to install update with ID 16815432 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870) Checking if update (8 of 71) with ID 16815924 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\1287f24a-6df3-4845-9181-451e37873202\windows6.1-kb2803821-v2-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:08 PM 10352 (0x2870) Applying update with ID 16815924 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:08 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:15.544 2014 ISTR0="16815924" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870) Failed to install update with ID 16815924 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870) Checking if update (9 of 71) with ID 16816368 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\46953317-9ed4-49b3-9d2e-0463dffec251\windows6.1-kb2853952-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:22 PM 10352 (0x2870) Applying update with ID 16816368 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:22 PM 10352 (0x2870) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:29.568 2014 ISTR0="16816368" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870) Failed to install update with ID 16816368 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870) Checking if update (10 of 71) with ID 16816380 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:30 PM 10352 (0x2870) I tried again today just to see, but its still failing even with just 2 updates, so its not a quantity issue. Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:27 PM 2920 (0x0B68) Checking if update (1 of 2) with ID 16811634 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:27 PM 2920 (0x0B68) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\fc38fd35-1f4f-4c53-ba73-090c80368750\windows6.1-kb2835364-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:41 PM 2920 (0x0B68) Applying update with ID 16811634 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:41 PM 2920 (0x0B68) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:47 PM 2920 (0x0B68) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:47 PM 2920 (0x0B68) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=siteserver.f.q.d.n SITE=AP2 PID=6300 TID=2920 GMTDATE=Sat Jul 05 16:07:47.367 2014 ISTR0="16811634" ISTR1="AP200119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:47 PM 2920 (0x0B68) Failed to install update with ID 16811634 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:47 PM 2920 (0x0B68) Checking if update (2 of 2) with ID 16811689 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:47 PM 2920 (0x0B68) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\28ed6c22-0b13-4202-a27a-17618cc6728e\windows6.1-kb2840631-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:52 PM 2920 (0x0B68) Applying update with ID 16811689 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:52 PM 2920 (0x0B68) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:56 PM 2920 (0x0B68) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:56 PM 2920 (0x0B68) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=siteserver.f.q.d.n SITE=AP2 PID=6300 TID=2920 GMTDATE=Sat Jul 05 16:07:56.409 2014 ISTR0="16811689" ISTR1="AP200119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:56 PM 2920 (0x0B68) Failed to install update with ID 16811689 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:56 PM 2920 (0x0B68) UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 7/5/2014 12:07:56 PM 2920 (0x0B68) So to workaround that specific Schedule Update problem, I created a Build & Capture TS that will apply the WIM that has the 93 updates already Opt-in to Microsoft Updates scan for updates via 'WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE' Install updates Reboot Repeat steps 3,4 & 5 three more times to be sure its fully up to date Install other things that should be 'baked in' like .NET 4.5.2 & IE11 Run steps 3,4 & 5 to be sure those packages are up to date Capture image At Step 4 it shows 157 updates are needed (!) so I don't have an exact list. However, everything works fine until I get down to step 7. The AppEnforce.log doesn't exist, and the execmgr.log only contains these lines: Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client. If the client is not yet registered, this is expected behavior. execmgr 7/2/2014 6:28:00 PM 2256 (0x08D0) Software distribution agent was enabled execmgr 7/2/2014 6:28:01 PM 2372 (0x0944) Service startup. execmgr 7/2/2014 6:46:12 PM 2940 (0x0B7C) Service startup. execmgr 7/2/2014 6:47:59 PM 2748 (0x0ABC) Service startup. execmgr 7/2/2014 6:50:19 PM 2752 (0x0AC0) Service startup. execmgr 7/2/2014 6:52:45 PM 2752 (0x0AC0) Service startup. execmgr 7/2/2014 6:55:10 PM 2772 (0x0AD4) Being very new to SCCM, I'm open to the possibility that I've done or am doing something wrong. I'm curious, when SCCM admins prepare for a new OS deployment (specifically Windows 7 but it I'm sure it would also apply to Windows 8+, Server 2008+ etc.): How are people keeping their WIM's up to date with Windows (OS/CBS) and Microsoft (other Microsoft products like Office) updates? How are people creating that 'gold' WIM that's used throughout the organization?

After dropping the WIM on the workstation I'm running Windows Updates (a few times) and manually rebooting for good measure before moving onto application installations. When the machine comes back up & begins the Application Installation section, it fails on the first application installation which happens to be .NET 4.5.2. The error presented is a not-very-helpful 0x80004005. Selection from smsts.log I opened a bunch of other logs (see attached) and found some alarming errors like: Note: I just selected a handful of errors via cmtrace & copied so there's a bunch of extra stuff in between these lines hence the ...'s When booting from media: it finds the right TS' exposed to that device collection it drops the image downloads the offline updates all of which are packages downloads & executes other scripts which are also packages I'm concerned this may be an indication of a configuration issue versus a problem with the TS itself or the steps within the TS. Perhaps its a configuration item that's not set [correctly] that manifests itself this way. Some details: SCCM 2012 R2 CU1 on Server 2008 R2 Servers (Site & DP/MP/FSP) and clients are physically in the same site Deploying Windows 7 Enterprise with SP1 This is a Build & Capture TS so the machine isn't joined to the domain Verified MP was published in AD in DNS & via nslookup -type=srv _mssms_mp_ap2._tcp.F.Q.D.N Boundary Groupsenabled "use this boundary group for site assignment" specified correct assigned site (only one) added the correct site system server under content location (only one) added all the boundaries for this location Boundarieshave been defined by IP Address Range and Active Directory Site have been added to the Boundary Group (always many boundaries to one boundary group; not many to many) site systems tab shows correct site system (just the one) boundary groups shows correct boundary group (just the one) checked a handful of boundaries for this specific office - they're all the same. while several IP ranges have been explicitly defined for this and other offices, its not an exhaustive list; for instance my specific range (10.1.37.0-255) hasn't been specified. however, an over-arching IP address range does exist (10.1.0.1-10.1.255.254) which should catch everything, right? If no, then how does anything work on this vlan? Client Installation Settings > Client Push Installation Properties:Client Push Installation Account specified Installation Properties: SMSSITECODE=AP2 FSP=dpmpfsp.f.q.d.n SMSMP=dpmpfsp.f.q.d.n DNSSUFFIX=f.q.d.n Setup Windows and Configuration Manager TS step properties:SMSMP=dpmpfsp.f.q.d.n FSP=dpmpfsp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp" Offline Updates are applied via DISM right after the WIM is appliedEnterprise roll up and 3 regression hotfixes Windows 7 updates that are known to require multiple reboots (See: http://support.microsoft.com/kb/2894518) Some other known required hotfixes (prevent BSOD's after resuming from sleep, slow login time fix etc.) .NET Package is sound:Manual installation by running the batch/command line is successful Push of .NET 4.5.2 to existing clients is successful Installing .NET 4.5.2 via OSD TS without doing Windows Updates & reboots is successful Could it be because I have both IP Address Ranges and AD Sites boundaries specified? I would like to think that if it was a site assignment/boundary/boundary group issue, nothing would work (i.e.: it wouldn't locate TS' so the process would fail from the very beginning) and it would fail all the time, regardless of whether or not windows updates & reboots are in the mix; Right? What have I missed? smsts.log CAS.log CIAgent.log CIDownloader.log CIStateStore.log LocationServices.log CITaskMgr.log

Thanks for the reply simulacra75! We frequently get requests for custom builds of Windows 7 (some with Office 2007, others 2010 or 2013 or no office suite; completely locked down or with non-standard applications etc.) so I wanted to have a fully OS patched WIM I could use over & over. As the year goes on, I'd like to keep that WIM patched (OS wise) so as not to lengthen the imaging process. (They're sticklers when it comes to 'lengthy' imaging times!) From there I would create another Build & Capture Task Sequence to install our standard apps (office, flash, reader etc.), capture that WIM & use that for our main OSD in the next month or so. However that being said, I don't disagree with your comment and that's how I worked around this problem in the mean time. Scheduled Update'd WIM as much as possible B&C TS to deploy said WIM Apply a bunch of known required hotfixes offline (via dism) Apply all updates (ran that 2 or 3 times to be sure) Capture WIM My concern was that this could be an indication of a larger issue. Or that maybe I somehow 'broke' something in the WIM or I did something wrong process wise.