mqh7

We reimage about 5000-8000 clients each summer. Last summer we were still at RTM, but have since moved on to R2. We build images (Win7 SP1) in vsphere and capture via capture media TS. Last year's image didn't get SCCM client uninstalled prior to capture so we would have random issues with computers going to unmanaged status and some that would show up without a client cert. To avoid this issue we stripped the client out prior to capture this year.

I believe this is how we handled the reimage process last year as well, but I am not positive on that. We were also dealing with a lot of new laptops last summer, where as they obviously have existing records this summer. Since SCCM replaces the wired MAC address with the wireless MAC (laptops) we can't just toss these into an OSD collection because it won't pickup the OSD advertisement / PXE. (Is there any workaround for this?) Since this is the case, we are blowing away each client's AD account and DDR in SCCM, then doing mass import of hostname and wired MAC into SCCM, dumping them into the appropriate OSD collection, and they image unless they happen to pickup last year's PXE deployment that first has to be cleared, or unless they had a motherboard replaced and our MAC database didn't get updated. We did the mass import a week ago and the manual entries are listed with hostname and MAC and entry date of 7/9/2014. This week we started imaging. Almost immediately after reimaging (at which time the AD record is created upon rejoining domain) we see a second account show up in SCCM from AD Discovery with dates of 7/14/2014 and 7/15/2014. Neither account is managed or shows that SCCM client is installed, but it shows a site code.

The manual entry lists an agent name, agent site, wired MAC, name, NetBIOS name, Resource ID of 167xxxxx, assigned site, and CCM GUID.

The AD Discovery record shows agent name, agent site, domain, IPv4 and IPv6 addresses, name, NetBIOS name, primary group ID, domain, Resource ID of 20971xxxxx, resource name and type, SID, assigned sites, container name, UAC, etc.

Why won't these records merge and show up as being properly managed? I am not yet sure if they fix themselves after one record or the other is deleted. Obviously this process isn't working well and it removes the clients from their direct membership collections and AD groups. I'd think that all of this could be avoided if we just had the wired MAC persist in the DDR.

Hi guys,

I'm stumped, and probably missing something obvious, need your thoughts on this please.

We have a CM12SP1CU2 hierarchy, and often battle the networking team when it comes to having content boundaries that serve well. (network guys change stuff and we don't know early enough).

So, I'm quite used to clients not being serviced for content due to lack of a boundary.

But this week, we have some clients which are being serviced for content and there seems to be no matching boundary.

This hierarchy has 19 DP's, and when these particular clients begin to look for content, CAS.log shows that all 19 DP's are returned as eligible. I expected there would be zero DP's returned as eligible.

We are using a combination of AD site boundaries and ip range boundaries, and the subnet in question 10.74.82.0/24 has no matching boundary records.

Maybe I'm tripping over the old "CM doesn't really do CIDR" thing ?

I didn't want this subnet to be serviced. Instead, it is serviced by any/all of the DP's (which is pretty disturbing and not likely to win me any friends in the networking team :(

Appreciate any ideas you might have. Happy for you to call me dumb if necessary ;)

Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCCM 2012 CU2

Hi

I've read a ton of stuff on this issue and I'm still no closer to solving it.

At the point of enabling Bitlocker, my OSD deployment (which has been working for nearly 2 years) has started failing, going straight to the logon screen and not completing the rest of the task sequence.

My smsts.log from the client shows the following.

'IsSrkAuthCompatible' failed (2150105094)    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
Tpm does not have compatible SRK    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
Tpm has EK pair    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
Initial TPM state: 44    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
(dwTpmState & Tpm::State_Enabled) != 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,434)    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
TPM cannot be enabled without physical presence    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
InitializeTpm(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1284)    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
ConfigureKeyProtection( keyMode, pwdMode, pszStartupKeyVolume ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1489)    OSDBitLocker    04/07/2014 15:46:13    3880 (0x0F28)
pBitLocker->Enable( argInfo.keyMode, argInfo.passwordMode, argInfo.sStartupKeyVolume, argInfo.bWait ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\main.cpp,382)    OSDBitLocker    04/07/2014 15:46:13   3880 (0x0F28)
Process completed with exit code 2147500037    TSManager    04/07/2014 15:46:13    1952 (0x07A0)
!--------------------------------------------------------------------------------------------!    TSManager    04/07/2014 15:46:13    1952 (0x07A0)
Failed to run the action: Enable BitLocker.
Unspecified error (Error: 80004005; Source: Windows)    TSManager    04/07/2014 15:46:14    1952 (0x07A0)

I read that it may be because I need to specify a BDEDrive in the task sequence, which I have done, but this has not made any difference.

Its also not affecting every version of device that I attempt to image, so far only a DELL Latitude E6430 and E6440 seem to be affected.

I'm a beginner when it comes to SCCM as I have inherited it from a colleague so appreciate any help.

Thanks

Matt

In my master image i have no windows update availabe.

After having captured it and deployed on any other computer i find 46 updates ready to be installed, why?

Thanks

Hello,

I’m having trouble with SCCM 2012’s UEFI support. I’m working with a ‘Deploy Win7’ task sequence I created to run on both a VMWare VM and a Dell OptiPlex 990 – both set to EFI mode. I already upgraded WinPE to version 3.1.

Here’s what I tried first:

• Followed the SCCM task sequence creation wizard, and changed the ‘Partition Disk’ step to GPT. In this case, the TS fails at the step ‘Apply Operating System’.  The error I get is "Marking partitions as active is only supported by MBR disks" and "Unable to activate partition (0x80004001)". I initiated the TS through PXE.
• Disabled the default “Partition Disk” step and added a “Run Command Line” action to run a script similar to the one found here: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/a6679550-a343-463c-9301-1bf9706ad9af. This attempt was also initiated by PXE. In this case, the machine showed an error of “Unable to find a partition on the system disk that can be set as active” within the prestaging environment.  This happened in the TSPxe component.  It also showed “Failed to stage WinPE” with an error code 0x80070490

These errors indicated to me that the system was not PXE booting in UEFI mode. I was reading that UEFI PXE booting was not supported by WDS by default, so I created “Standalone” task sequence media from the above TS.  The .ISO that the GUI process created was not recognized as being bootable by the UEFI boot menu. I looked at the files in the ISO and I can see "bootmgr.efi", but when I try to boot to the CD even though the EFI prompt it fails to boot.

I then decided to try out MDT 2012 and see if it supports UEFI. The task sequence I made with MDT initiated through MDT boot media worked _perfectly_.  It created litetouch.iso, from which I was able to boot to and install windows 7 on a UEFI based machine with no problems.  So MDT is working great, I just need to translate this work to SCCM.

I then thought that the problem might be with the GUI-based SCCM boot media ISO, so I tried to create my own bootable ISO from the SCCM task sequence’s boot media WIM via the guide here: http://technet.microsoft.com/en-us/library/dd744537(v=ws.10).aspx.

I was able to boot from this .iso in UEFI mode, but no task sequences showed up.  It started up, and shut down immediately.  I checked the smsts.log files and noticed the error "Failed to open PXE registry key. Not a PXE boot." 

It seems my new WinPE UEFI ISO is booting properly, but once it loads the environment it expects a PXE boot and shuts down.

Has anyone actually had success with SCCM Deploy Windows 7 to a system in UEFI mode? 

Thanks in advance,

Josh

I'm currently attempting to deploy Windows 8.1 Enterprise to a new batch of Surface Pro 3's but am encountering an issue after it loads the boot image. I can get the Surface Pro to connect to the DP to download the boot.wim but as soon as it starts to load before any dialog boxes appear it crashes and reboots to start Windows normally. I have updated the firmware on the Surface to the latest version and injected the Ethernet Adapter drivers from here: http://www.microsoft.com/en-us/download/details.aspx?id=38826 into the boot image.

I am currently using SCCM 2012 R2 installed on Windows server 2008 R2. Any assistance to get me pointed in the right direction would be appreciated.

Good Afternoon!

I have had much experience with SCCM 2007, but am still getting used to SCCM 2012.  Today, I set up and deployed my first test OSD deployment.  

Everything worked fine except one little thing - the computer did not join to the domain.

Below is what I've tried to get this resolved...

- Verified credentials in TS were correctly entered

- Tested and was able to join the same computer TS was run on to the domain using the same credentials (including their formatting) which are in the TS.

- Checked the NetSetup.log in C:\Windows\Debug - It didn't exist.  After joining the domain manually in the step above, it did, though.

- I didn't see anything that stood out in the smsts.log.

I'll be happy to attach any log files if needed.   Any suggestions?  THanks!

Ben K.

hi

in my environment I have a primary and a secondary server ,pxe role  and WDS  enabled on both  location ,osd is working fine

as for a test we have shutdown the primary server and tried OSD from Secondary site location we have found boot image was not loading and got error showing BCD error why this is happening even though images we available on secondary dp ,while looking smspxe .log found below error in secondary ,after bringing up primary osd working fine

PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 7/18/2014 1:02:36 PM 3996 (0x0F9C)
reply has no message header marker SMSPXE 7/18/2014 1:02:57 PM 3992 (0x0F98)
Failed to send status message (80004005) SMSPXE 7/18/2014 1:02:57 PM 3992 (0x0F98)
Failed to send the status message SMSPXE 7/18/2014 1:02:57 PM 3992 (0x0F98)

ankith

sccmghost@hotmail.com

sccmghost@hotmail.com

Having SCCM 2012 SP1 CU3 I attempted to do a pretty simple task.

Create a capture media for Windows 8 64 Bit and capture the OS.

The system in question is a Dell Latitude 6430u and OEM Windows 8.

The system ran as expected, the capture went as expected, but when I deploy the image (Back to the same laptop mind you)

The following occurs:

Windows could not complete the installation. To install Windows on this computer, restart the installation.

---

Things that I've tried:

 Set the SATA to various modes as it was on RAID on as speculated in some posts

 Saw a posting that suggests pressing SHIFT F-10 to get in to some prompt and run oobe; doesn't work here, I think.

 Added Dell Driver Packs for the system

As for log files, I'll check C:\Windows\Panther and see what's there.

Any ideas on how to correct this? Is there a way to go in to the image itself to do so?

I am using SCCM 2012 RTM and have started seeing an issue with our Build and Capture Task Sequence.  When performing a build and capture the system will not install anything for a day or so and anything that is advertised to it gets stuck in a "Waiting to Install..." status in the Software Center UI.

When looking at the execmgr log for the client I see the following items that stick out to me:

<![LOG[On policy activation ignore disabled policy Configuration Manager Client Upgrade Program]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="2" thread="3956" file="execreqmgr.cpp:7489">
<![LOG[Mandatory execution requested for program Configuration Manager Client Upgrade Program and advertisement CM120000]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="execreqmgr.cpp:3533">
<![LOG[Creating mandatory request for advert CM120000, program Configuration Manager Client Upgrade Program, package CM100003]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="execreqmgr.cpp:3658">
<![LOG[Program Configuration Manager Client Upgrade Program change to state WAITING_ENABLED]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="executionrequest.cpp:4618">
<![LOG[Execution Request for advert CM120000 package CM100003 program Configuration Manager Client Upgrade Program state change from NotExist to WaitingDisabled]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM100003",ProgramID="Configuration Manager Client Upgrade Program", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="event.cpp:410">
<![LOG[Policy arrived for child program insNCR-MPOSUIControls-1.0]LOG]!><time="10:57:50.240+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:50.287+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
<![LOG[Mandatory execution requested for program * and advertisement CM120006]LOG]!><time="10:57:50.865+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:3533">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.037+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="event.cpp:410">
<![LOG[Creating mandatory request for advert CM120006, program *, package CM10001F]LOG]!><time="10:57:51.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:3658">
<![LOG[Policy arrived for child program insRCS-FLIB_2_PlatformRuntime-5.5.5007]LOG]!><time="10:57:51.084+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
<![LOG[The created request is a Task Sequence request]LOG]!><time="10:57:51.115+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:1065">
<![LOG[Execution Request for advert CM120006 package CM10001F program * state change from NotExist to WaitingDependency]LOG]!><time="10:57:51.678+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.678+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
<![LOG[An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task.]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="executionrequest.cpp:8829">
<![LOG[Request a MTC task for execution request of package CM10001F, program * with request id: {7BCB5674-DC91-49D8-9C52-0765E9D86984}]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="executionrequest.cpp:8848">
<![LOG[Execution Request for advert CM120006 package CM10001F program * state change from WaitingDependency to Ready]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
<![LOG[MTC task with id {7BCB5674-DC91-49D8-9C52-0765E9D86984}, changed state from 0 to 1]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2932" file="execreqmgr.cpp:6268">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.959+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="event.cpp:410">
<![LOG[Policy arrived for child program insRCS-Software_Retrieval_Agent_TAB-5.4.1]LOG]!><time="10:57:53.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
<![LOG[MTC queeued a task for SWD execution request with program id: *, package id: CM10001F for execution.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2932" file="execreqmgr.cpp:6481">
<![LOG[Package CM10001F, program * is ready but can not be started because package , program  is currently running.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2932" file="executionrequest.cpp:9083">

When I use the same Task Sequence (or any other deployment) on a system built from our old .WIM created with the same Build and Capture Task Sequence they always install immediately.  I am thinking it has something to do with the default SCCM Client upgrade package available by default, but I had our SCCM owner verify that has been disabled in the hierarchy.

The deployments are set to ignore maintenance windows and things of that nature.  It appears to be an issue with the agents state when it comes up out of the build process.  It checks in with the Site and processes assignments for Compliance (DCM) without issues as well.  The build and capture new WIM/System builds just seem to not want to install anything.

What makes this issue even more odd is that if I leave the system on for several days sitting at the "Waiting to Install..." state, the agent finally works out whatever issue it is stuck on and begins to work without issues.  If I don't use the WIM for several days after it was created, the WIM will also stop experiencing the issue too.

Has anyone else run into this too?  This was working a couple months back and I went to create a new WIM in December and it hasn't work correctly since.

Thanks..Jon

Jon Kaloz

I am experiencing some inconsistent behavior when it comes to OSD and driver package injection. We are using explicit driver packages for each model of machine, and applying those packages based on WMI queries in the task sequence. 

Frequently, we are seeing failures when injecting drivers, which result in BSOD after the first reboot (these are SCCM 2012R2+MDT 2013 task sequences).

In the smsts.log we have these entries:

Setting %SystemRoot% to "E:\WINDOWS"	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "amd64"	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Added list item with key value '1'	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Writing configuration information to E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Successfully saved configuration information to E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Setting temporary directory to 'E:\_SMSTaskSequence\PkgMgrTemp'.	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Calling Package manager to add drivers to the offline driver store.	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Command line for extension .exe is "%1" %*	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Set command line: "X:\windows\system32\dism.exe" /image:"E:" /windir:"WINDOWS" /apply-unattend:"E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"E:\_SMSTaskSequence\PkgMgrTemp\dism.log"	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Executing command line: "X:\windows\system32\dism.exe" /image:"E:" /windir:"WINDOWS" /apply-unattend:"E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"E:\_SMSTaskSequence\PkgMgrTemp\dism.log"	OSDDriverClient	7/18/2014 10:17:18 AM	1184 (0x04A0)
Process completed with exit code 2147500037	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,548)	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
Dism failed with return code -2147467259	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658)	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
Failed to add driver to driver store. Code 0x80004005	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
Failed to provision driver. Code 0x80004005	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)
Exiting with return code 0x80004005	OSDDriverClient	7/18/2014 10:17:20 AM	1184 (0x04A0)

In the dism.log I have these entries:

2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SOFTWARE' from path '\\?\E:\Windows\System32\config\SOFTWARE'.
2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SYSTEM' from path '\\?\E:\Windows\System32\config\SYSTEM'.
2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SECURITY' from path '\\?\E:\Windows\System32\config\SECURITY'.
2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SAM' from path '\\?\E:\Windows\System32\config\SAM'.
2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/COMPONENTS' from path '\\?\E:\Windows\System32\config\COMPONENTS'.
2014-07-18 10:17:20, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/DEFAULT' from path '\\?\E:\Windows\System32\config\DEFAULT'.
2014-07-18 10:17:20, Info                  CBS    Failed to open the registry root: n/a, key: Microsoft\Windows NT\CurrentVersion\ProfileList. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Info                  CBS    Failed to query for path to user profiles directory. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Info                  CBS    Failed to load the default user profile registry hive. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Error                 DISM   DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80004005

Are there any other logs I can look at to determine why dism is having these registry issues? The cbs.log on the hard drive is not current. The setupapi.offline.log only lists the successful driver injections, so it isn't much help.

Where can I get more detail on what is happening here?

I have several Lab computers that we reimage often.  I have setup a task sequence and advertised it to the lab computers and it shows up in software center.  This is great and I would like it to show up there for just local admins and not local users.  Is it possible to only show task sequences for local admins only?

I want to keep the ability to be able to call my OSD task sequence from Software Center, but somehow hide it from normal users so only my staff can see it when they log in as the local admin on the computer.

Is this possible or is there some other way I can restrict this task sequence while still being able to run it from software center?

Hi,

I have built my Windows 8.1 golden image that I will be deploying shortly. Is it ok to use the capture media to capture it?,  or are there known issues I should be aware of. Have anyone of you captured a Windows 8.1 image using the capture media yet if so how did it go.

Because as I post task sequence command I have a shutdown command

cmd /c shutdown /s /t 120

but none of my computers shutdown, yet the task sequence reports 100% SUCCESS.