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.

Crazy old post but, is anonymous access permitted on that DP? Is Anonymous Authentication Enabled in IIS for SMS_DP_SMSPKG$?

When applying updates via schedule updates, they're all failing with ErrorCode 2096 / Return Code 0x800f0803 / Error Code -2146498512 I imported a stock Windows 7 Enterprise with SP1 (x64) WIM last night I performed scheduled updates which successfully applied 93 updates. This morning, I went through Scheduled Updates again, and it shows 71 updates need to be applied. I'm trying to apply those updates via Scheduled Updates but they're all failing with the same set of errors. I've checked the following but I'm still having trouble: Running SCCM 2012 R2 (5.0.7958.1000) DISM version is 6.3.9600.16384 There's enough disk space even with the WIM mounted (90+GB) NTFS permissions are fine for %windir%\temp and D:\ConfigMgr_OfflineImageServicing SCEP is installed:exclusions have been created for %windir%\temp, D:\ConfigMgr_OfflineImageServicing, both 32-bit and 64-bit dism.exe and dismhost.exe (among others: 1, 2) real-time protection is disabled No other AV installed No other third-party suites installed (e.g.: AV or Firewall) that interfere with files, processes etc. Checked state of 'Exclusive' & 'TotalSessionPhases' by loading the registry of the WIM (reg load HKLM\mykey D:\mount\windows\system32\config\software); Both were set to 0. I can upload the offline serving log in its entirety but its more of what I pasted above. My objective is to fully patch the WIM before I apply other updates offline (e.g.: KB277551-v2, KB2732673, KB2728738). This way I can begin test deployments with a fully patched WIM as of 'now' and create our reference image which will have Office 2010 installed and fully patched. From there, the WIM will be updated either quarterly (or monthly) via Schedule Updates, after we've performed our regression tests. I guess the question I should be asking is: What's the proper/correct process for getting a stock WIM (be it Windows 7, Server 2008 R2, Server 2012 etc) fully up to date? What does that process look like and what does the Task Sequence look like? Help!

I'm now applying the dual-reboot specific updates offline via: cmd.exe /c x:\windows\system32\dism.exe /ScratchDir:%OSDisk%\Mount /Image:%OSDisk%\ /Add-Package /PackagePath:%_SMSTSMDataPath%\Packages\<PACKAGE_ID>\<PACKAGE_MSU>.msu If I have any issues beyond that I suppose I'll create a new thread.

Thanks for the reply - I apologize for being so vague; wasn't my intention. I was posting in an effort to get feedback on whether or not my new proposed Build & Capture TS was sound process wise. How does it stack against 'best practices' or what others are doing? (And so on) At the time of posting I was incredibly frustrated and struggling with a couple of issues that were driving me insane. I suspect the order in which I was doing things and the extra reboots were to blame. While I don't necessarily understand why it wasn't working, I moved onto the TS I outlined above. In the interest of full disclosure should someone else stumbles across this thread, I've outlined my two issues I was having using the old TS. Issue 1: When I ran Windows Updates after Step 6 the packages below failed to install. The TS would fail with a 80004005 error. SMSTS log shows that the first package (.NET) failed to install because the "application download failed". What's really odd is that I have packages that executed successfully prior to this step, the only difference (at the time) being Windows Updates & reboots in between those packages and the one that failed. I "merged" all the logs into one view so I can see what happened chronologically, highlighting the application id to make it easier to spot. Errors of concern are: failed to resolve version for ScopeID_whatever/application_ProblematicApplication Conformant Rule:whatever_ScopeId_whatever_ProblematicApplication_version_Configuration_PolicyDocument not found GetLogonUserSid failed at GetTokenSids 0x800703f0 Failed to send Location Request Message Failed to create Location Request Message body GetLocationSyncEx failed with error 0x8000000a Unable to get locations, no need to continue with download CheckLocations failed. Error = 0x87d00607 No location available : CTaskConsumer(application scopeid) State transition to (Failure), Param(-2016410105) : CTaskConsumer(application scopeid) Unable to retrieve AD site membership Boundaries and Boundary Groups are set: After all, I was able to select & start the TS, image came down, packages prior to that step came down fine. Other OSD's (e.g.: vanilla Windows 7, another image I captured months ago) on the same physical switch & same VLAN succeed. Installation properties of ConfigMan Installation had the following set: SMSMP=Server.FQDN FSP=Server.FQDN DNSSUFFIX=FQDN Issue 2: If I rebooted after Step 7.3, Windows Updates would run and at some point the machine would just boot into Windows. I believe this may have been the cause: http://support.microsoft.com/kb/2894518 BUT LETS NOT FOCUS ON THE ABOVE: I'VE MODIFIED THE TS SO I THINK THE ABOVE IS NO LONGER AN ISSUE! I don't mean to be rude, just don't want anyone to spend time on those issues since the TS has changed! [Very] Late last night I kicked off the process using the following TS and it completed successfully. Right now (27-06-2014) the only problem I'm seeing is that after the capture, I cannot login due to a user profile service error. After capture, the reference machine reboots & goes through OOBE. I fill in the information (username, username, time zone etc.) It automatically logs on but fails with: The User Profile Service service failed the logon User profile cannot be loaded. I'm aware of this http://support.microsoft.com/kb/947215 but here's what I'm doing to fix it: Reboot into safe mode Browse to C:\Users Show hidden folders Right click C:\Users\Default Properties Security tab Advanced Change permissions Check the box 'Replace all child object permissions with inheritable permissions from this object' Apply Yes OK OK OK Restart Its a brand new profile - just finished OOBE; its the very first login of any kind I didn't do anything special during the deployment or capture, like use a customsettings.ini or unattended.xml, beyond what's in the TS shown above. There's something fundamentally wrong somewhere. I suspect maybe KB2728738 is to blame based on a quip made about the User Profile service on this page but that's not conclusive. I'm aware the profile issue goes beyond the scope of this forum so to honor everyone's time, I'll post about that specific issue in the TechNet forums.

Hi all - New to the forums but anonymously lurking for quite some time. I'm also quite new to SCCM so I'm hoping for a little grace & mercy. I'm really struggling here & I can't figure out what I'm doing wrong. I need the help of some more seasoned SCCM admins. My main objective is to automate the build of my reference image. Something I can reuse: when office-wide core applications change (e.g.: Office 2007 to 2010 to 2013, Adobe Acrobat vs Nuance etc.) to roll-up all the other updates/patches/hotfixes Microsoft released over the past n months (e.g.: Office updates, SQL Express 2005 and up, Report Viewer, Visual C++ & Visual Studio for Office etc.) when I create a brand new image be it Windows 7, 8/8.1, Server etc. From my perspective, the task sequence should look something like this (see photo) Start with a vanilla Windows 7 SP1 WIM straight from the ISO Use Schedule Updates to patch it fully Create a new Build & Capture TS Apply patched vanilla Windows 7 SP1 WIM Apply offline hotfixes (e.g.: KB277551-v2, KB2732673, KB2728738, KB2878378, KB2459268, KB2522623, KB2581608, KB2729094, KB2731771, KB2533623, KB2670838, KB2786081, KB2834140, KB2639308, KB2888049, KB2882822) (source: 1,2 - can't find the other link) Setup ConfigMan with SMSMP, FSP, DNSSUFFIX set Install application set 1 .NET 4.5.2 WMF 4.0 (KB2819745) Application dependencies: Visual C++ 2005/08/10, Visual Studio Tools for Office Runtime, MSXML6 [Parser] etc. Opt-in to Microsoft Updates Scan for updates: WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE (source: 1, 2, 3 & more) Install updates Run steps 7 & 8 again to ensure its fully patched (source) Install application set 2 Internet Explorer 11 (customized via IEAK) Office 2010 Scan for updates again Install updates again Run steps 11 & 12 ... again Re-arm Office Prepare CM Client Prepare OS Capture Reference Image Is this a valid configuration?

Obligatory bump... Between fires, adhoc projects & tasks, I've been researching and learning more about SCCM. When installing/uninstalling applications, I'm looking at task manager to view the actual command line being run for the install, and in some situations, its incorrect. In other situations the command line is correct, but, the actual install batch file (in c:\windows\ccmcache\random) is not the most recent one and/or its missing additional files that were recently added. Perhaps this is the source of all my problems: The DP is not up to date/doesn't contain the latest changes made to the batch files. (Because remember, as I mentioned above, the install/uninstall batch files currently work without issue when executed manually or via login script deployments.) So maybe my question should be: If the below isn't the proper method for 'refreshing' the DP with the latest application data (updates to the install package, updated files etc), what is the proper method for doing so? Right click on Application > Deploy Content & complete wizard (if I haven't already done so) Right click on Application > Properties > Content Locations > Select location > Click Redistribute > Click OK I hate to be a pain - just in need of some guidance.

As I mentioned above, the install & uninstall errors vary: The software change returned error code 0x1(1). The software change returned error code 0x4(4). The software change returned error code 0xFF(255). The software change returned error code 0x87D00213(-2016411117). The software change returned error code 0x87D00325(-2016410843). The software change returned error code 0x87D01107(-2016407289). Running the batch file to install/uninstall completes without error so either something unexpected is happening that SCCM interprets as an error, or I made a mistake in the way I created the application. I want to believe its something very simple that I'm missing or just not doing right. I'm a big log person. All the batches log each operation and redirects the results (1> and 2>) to a log file for review. It makes it super simple to see where something failed down the road. SCCM includes a wealth of log files for various operations, and, in my humble opinion, its a bit overwhelming! I know that the client logs are all stored in C:\Windows\CCM\Logs but there are over 100 logs in there and its not inherently obvious which log corresponds to which component of CM. So, all that said, I'm happy to comb through with cmtrace to troubleshoot deeper & get a better understanding of the process, but I'm in need of help finding a good place to start. Is there a resource available that provides a breakdown/definition of each of the logs in C:\Windows\CCM\Logs? What about the logs on the SCCM server itself? Thanks again!

Just in case this is relevant, here's what the install script looks like: @echo off rem cls echo. & echo Installing FileSite 8.5 SP3 U5 "%~dp0Full_Installer\setup.exe" /S /v"/qb SERIALNUMBER=0004321 /l*vx c:\Logs\Installs\Autonomy-FileSite85SP3U5.log" echo. Applying Default User Configurations echo. Copying NRTDDE.INI if not exist "C:\Users\default\AppData\Local\Interwoven\WorkSite" md "C:\Users\default\AppData\Local\Interwoven\WorkSite" xcopy /r /y "%~dp0NRTDDE.INI" "C:\Users\default\AppData\Local\Interwoven\WorkSite\" echo. Disabling QuickView Pane (Default USer^) if not exist "C:\Users\default\AppData\Local\Interwoven\QuickSearch\Config" mkdir "C:\Users\default\AppData\Local\Interwoven\QuickSearch\Config" xcopy /r /y "%~dp0MinerSettings.xml" "C:\Users\default\AppData\Local\Interwoven\QuickSearch\Config\" echo. Merging FileSite Customizations reg load HKEY_USERS\DefUser "c:\Users\Default\NTUSER.DAT" regedit /s "%~dp0BRCoFileSite Customize-defuser.reg" reg unload HKEY_USERS\DefUser echo. Applying Current User Configurations echo. Copying NRTDDE.INI if not exist "%userprofile%\AppData\Local\Interwoven\WorkSite" md "%userprofile%\AppData\Local\Interwoven\WorkSite" xcopy /r /y "%~dp0NRTDDE.INI" "%userprofile%\AppData\Local\Interwoven\WorkSite\" echo. Disabling QuickView Pane if not exist "%localappdata%\Interwoven\QuickSearch\Config" mkdir "%localappdata%\Interwoven\QuickSearch\Config" xcopy /r /y "%~dp0MinerSettings.xml" "%localappdata%\Interwoven\QuickSearch\Config\" echo. Merging FileSite Customizations regedit /s "%~dp0BRCoFileSite Customize-hkcu.reg" echo. Setting Express Search to Run on Startup reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /v "WSSearch" /t reg_sz /d "\"C:\Program Files\Interwoven\WorkSite\WESClient.exe\" -background" /f rem echo. Copying Customized Views rem xcopy /r /y "%~dp0Default Views" "C:\Program Files\Interwoven\WorkSite\iOutlook" rem echo. Copying Filing Status Icons rem if not exist "%userprofile%\AppData\Local\iOutlook\Config" md "%userprofile%\AppData\Local\iOutlook\Config" rem if not exist "C:\Users\Default\AppData\Local\iOutlook\Config" md "C:\Users\Default\AppData\Local\iOutlook\Config" rem xcopy /r /y "%~dp0DefaultCFG" "%userprofile%\AppData\Local\iOutlook\Config\" rem xcopy /r /y "%~dp0DefaultCFG" "C:\Users\Default\AppData\Local\iOutlook\Config\" rem echo. & echo Copying Worksite Macros rem xcopy /r /Y "C:\Program Files\Interwoven\WorkSite\Macros\imanO2k.dot" "C:\Program Files\Microsoft Office\Office12\Startup\" rem xcopy /r /Y "C:\Program Files\Interwoven\WorkSite\Macros\imanO2k.xla" "C:\Program Files\Microsoft Office\Office12\xlstart\" :end And here's the uninstaller: @echo off rem cls echo. & echo Uninstalling FileSite 8.5 SP3 U5 MsiExec.exe /X{C2B80D37-7690-4172-A5C2-423564CE8616} /qb- /l*vx c:\Logs\Uninstalls\Autonomy-FileSite85SP3U5.log echo. Removing Express Search from Startup reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /v "WSSearch" /f :worksitemacros if exist "C:\Program Files\Microsoft Office\Office12\Startup\imano2k.dot" ( echo. Removing Worksite Word Macro del /q "C:\Program Files\Microsoft Office\Office12\Startup\imano2k.dot" ) if exist "C:\Program Files\Microsoft Office\Office12\xlstart\imano2k.xla" ( echo. Removing Worksite Excel Macro del /q "C:\Program Files\Microsoft Office\Office12\xlstart\imano2k.xla" ) :end

First of all thanks for the reply! Sorry for taking a bit of time to respond - I've been quite busy. That was my understanding as well and here's the process I've been following that's resulting in errors in SCCM but *not* in the script [read: batch] file I'm calling: Build the batch file that calls the installer and does the post installation configuration: Calls setup file (actual MSI or setup.exe etc) via relative path and any necessary parameters/arguments etc: "%~dp0Full_Installer\setup.exe" /S /v"/qb SERIALNUMBER=12345 /l*vx c:\Logs\ApplicationName.log" Performs a variety of operations: xcopy /r /y, md/mkdir, reg add/delete, regedit /s; Each operation is redirected to >>!logfile! 2>>&1 Test each batch file the follow this process: confirm no errors on screen during install confirm no errors in logs after install confirm application successfully installed, which means: checking the location of where the app is expected to install to verify its there and it works checking that all applicable changes were made successfully so I'm looking for registry entries, configuration files, directory creation etc - everything in the batch checking Programs and Features to validate its presence I repeat this process (all of Step 2 above) for the uninstall batch file to confirm it too completes successfully With the batch files tested & confirmed working I create new Application in SCCM Select Windows Installer (*.msi file) Choose msi file from \\unc\path\application\fullinstaller\file.msi Make any necessary adjustments to the General information screen Close Application Wizard Edit Properties of newly created Application Go to Deployment Types tab Select the MSI entry in there & click Edit Go to the Content tab & alter directory During creation its pointed to \\unc\path\application\fullinstaller\file.msi While not always the case, the batch file actually lives one directory up in \\unc\path\application, so I'm adjusting it to point to that directory. instead Go to Programs tab Change Installation program to the batch file: install_myapp.cmd Change Uninstall program to the batch file: uninstall_myapp.cmd Click Apply & click OK Ok, now that all my changes are made, I need to get this into the DP: I Deploy Content (if I haven't already done so) Right click on Application > Distribute Content > Add DP > Continue through Wizard Redistribute Content (especially if edits were made to existing applications) Right click on Application > Properties > content Locations > Select location > Click Redistribute Verify deployment/redistribution via Content Status > View Status Wait a little while (usually just a few minutes <5) With that now complete, I'm ready to test the install/uninstalls via SCCM. So I go to client workstation, load up Software Center & Locate application & click 'Install', and this is where things get strange. Misreported FailureIt successfully downloads but installation fails with a variety of errors (see below): Unable to make changes to your software. There was a problem applying changes to the software. You can try again. Or, if the problem continues, the information that is shown in the following section can assist your help desk in troubleshooting. Click OK to return to Software Center More Information The software change returned error code 0xVARIES(n). I check "Program Files (x86)" and I see the program installation directory & its populated with files. I check "Programs and Features" and I see the application listed. I can uninstall, change & repair. I restart software center, refresh it a few times and the application is still listed under 'Available Software' and 'Installation Status'. If I click 'Retry' it immediately disappears from view What that means is: If I'm looking at 'Available Software' or 'Installation Status', the application vanishes from that 'tab', and appears under 'Installed Software' within 'Software Center' I reviewed the MSI manually but saw no "return value 3" entries; Passed the same log through WiLogUtil.exe and its not isn't showing any problems either. So it actually did install successfully, yet something 'failed', or was translated as a failure, causing Software Center to believe the install failed. Outright FailureWith application 'X' installed, from the 'Installed Software' tab I click 'Uninstall' and like before I get an error: Unable to make changes to your software. There was a problem applying changes to the software. You can try again. Or, if the problem continues, the information that is shown in the following section can assist your help desk in troubleshooting. Click OK to return to Software Center More Information The software change returned error code 0xVARIES(n). I check "Program Files (x86)" and the other tasks - its still installed and everything is still in place. I don't create uninstall log files so I don't have anything to view, but again: running the uninstall batch file manually results in success. I'm quite perplexed!

Super new to SCCM - still trying to figure things out. Nearly all of our applications have post installation steps like applying a registry configuration (via either `regedit /s` or `reg add`), creating directories and/or copying files (license file, configuration file) and so on. Since I've already created a bunch of applications, leveraging SCCM's nifty little feature that grabs all the app info from the MSIs, I'm now looking for how to accomplish 'the next step': applying the proper configurations. What's the best method for applying post application installation configurations?