Hello,

Kind of a weird question here, so it seems like I'm seeing that if you install an application on a system during its OSD task sequence, then you later manually uninstall that application, that SCCM considers that system now out of compliance?  And then reinstalls the application as indicated in AppEnforce.log?  Is this true?  If so, how do you get around this behavior?  I guess I thought that this application compliance only took effect when you actually deploy an application to a system, through an actual deployment.  I didn't realize that it would enforce compliance even if an application was installed during a task sequence.  So if you have hundreds of systems that were imaged with the same task sequence and you have a small handful of machines that can't have application X on it (so you want to uninstall it), which was installed via the task sequence, how do you disable this compliance enforcement and disable its automatic reinstall?

Thanks for any help you can provide.

Interesting issue we are realizing on Servers deployed from SCCM 2012. 8dot3names are not created for Program Files and Program Files (x86). they are created for other files/folders at the root of C and below Program Files and Program Files (x86). This is causing issues when programs are installed and the path is then created with 8dot3 filenames for program files and program files (x86)

Hi all,

I'm using CM2012 with SP1 to deploy Windows 7 with SP1, and I need to enable the 8.3 file & folder names in the file system.  I know I have to do this right at the beginning immediately after the format step.

I know MS have recently changed the 8.3 names to be disabled by default, as outlined here: http://scug.be/sccm/2013/01/15/configmgr-2012-sp1-the-8dot3name-settings-are-disabled-on-the-volumes-upon-partitioning-and-formatting-of-the-local-disk/

I hope my question is a simple one. 

What files do I need to create an fsutil package (or what components to I need to add to my WinPE image) in order to be able to run the "fsutil 8dot3name set 0" command. 

I've already attempted to create the package myself by copying the fsutil.dll and fsutil.exe files from C:\Windows\System32 on a Windows 8 machine, but when I execute it in WinPE 4.0, I get the error "Unable to format message for id 400002710 - 13d".  I thought I'd then get sleuthy and use procmon to monitor what dll's fsutil.exe calls from the command prompt on a fully built workstation, then I copied all those DLL's, but alas, I still get the same error.

According to that link above, "Steve' (in the comments) has created a package. My comment on there is awaiting moderation, so in lieu of that I thought I would also ask here incase someone has done this before.

Likewise, if fsutil isn't the best way to do this from WinPE 4.0, but someone has a powershell/vbscript that does the same thing - please post up here.

Any help is greatly appreciated.

http://www.dreamension.net

mdt 2013 processing bootstrap settings someone help me

sccmghost@hotmail.com

sccmghost@hotmail.com

Hi everyone,

I am experiencing some problems regarding running a task sequence for unknown computers.

When I boot certain computers from PXE, I will receive an abortpxe.com

I have verified the following in my environment:

• No duplicate "SMBIOS GUID" in my  environment
• No duplicate "MAC-addresses" in my enviroment
• x64 & x86 unkown computer is located in collection "Unknown Computers"
• Correct TS (with correct boot image) is targetted for this collection

In SMSPXE.log I can find the following:

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: No boot action. Rejected. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: Not serviced. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 7/07/2014 12:37:53 2052 (0x0804)

Item key "2046820***" is the corresponding "x64 Uknown Computer". Sometimes this will be "x86 Unkown Computer" for the same device.

When looking at previous entries in the logfile, this computer was once unkown and wa able to receive a PXE:

3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: device is not in the database. SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820***" ServerName="" ServerRemoteName=""><Machine><ClientID>96de0ff0-0bc2-4f21-ac90-***********</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Looking for bootImage D3000019 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)

What could be the issue? Is it possible that there is still some record referring to this PC and how can I trace/delete it?

Would restarting the WDS server solve this issue?

Thanks in advance!

if I install sap after OSD, it exit code is 0.

but if I runn during OSD, it exit code is 0x80070081, and then I checked the sap, I found it seem to work fine.

Here is the logs of application installation

Install by SMS CMClient ---succeed
http://1drv.ms/1kzt4LG

Install by OSD  ---failed
http://1drv.ms/1kzuoye

-----------------------------

Waiting for job status notification...InstallSoftware2014/4/11 12:57:553864 (0x0F18)
Waiting for job status notification...InstallSoftware2014/4/11 12:58:253864 (0x0F18)
Waiting for job status notification...InstallSoftware2014/4/11 12:58:553864 (0x0F18)
CompleteExecution receivedInstallSoftware2014/4/11 12:59:093132 (0x0C3C)
CompleteExecution processedInstallSoftware2014/4/11 12:59:093132 (0x0C3C)
Received job completion notification from Execution ManagerInstallSoftware2014/4/11 12:59:093864 (0x0F18)
Installation completed with exit code 0x80070081InstallSoftware2014/4/11 12:59:093864 (0x0F18)
Installation failed with error (0x80070081)InstallSoftware2014/4/11 12:59:093864 (0x0F18)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_00100021_0012000A_SAP'=''InstallSoftware2014/4/11 12:59:093864 (0x0F18)
GetExecRequestMgrInterface successfulInstallSoftware2014/4/11 12:59:093864 (0x0F18)
Releasing job request, jobID='{B8D6032A-D2A4-4C9F-85EB-99E3773589CF}'InstallSoftware2014/4/11 12:59:093864 (0x0F18)
Releasing of Job Request successfulInstallSoftware2014/4/11 12:59:093864 (0x0F18)
CompleteJob successfulInstallSoftware2014/4/11 12:59:093864 (0x0F18)
ReleaseSource() for C:\_SMSTaskSequence\Packages\00100021.InstallSoftware2014/4/11 12:59:093864 (0x0F18)
reference count 1 for the source C:\_SMSTaskSequence\Packages\00100021 before releasingInstallSoftware2014/4/11 12:59:093864 (0x0F18)
Released the resolved source C:\_SMSTaskSequence\Packages\00100021InstallSoftware2014/4/11 12:59:093864 (0x0F18)
pInstall->Install(sPackageID, sProgramName), HRESULT=80070081 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)InstallSoftware2014/4/11 12:59:093864 (0x0F18)
Install Software failed, hr=0x80070081InstallSoftware2014/4/11 12:59:093864 (0x0F18)
Process completed with exit code 2147942529 TSManager2014/4/11 12:59:092068 (0x0814)
!--------------------------------------------------------------------------------------------!TSManager2014/4/11 12:59:092068 (0x0814)
Failed to run the action: SAP. 
The  application cannot be run in Win32 mode. (Error: 80070081; Source: Windows)TSManager2014/4/11 12:59:092068 (0x0814)
MP server http://PRI1.ABC.COM. Ports 80,443. CRL=false.TSManager2014/4/11 12:59:092068 (0x0814)
Setting authenticatorTSManager2014/4/11 12:59:092068 (0x0814)
Set authenticator in transportTSManager2014/4/11 12:59:092068 (0x0814)
Sending StatusMessageTSManager2014/4/11 12:59:092068 (0x0814)
Setting message signatures.TSManager2014/4/11 12:59:092068 (0x0814)
Setting the authenticator.TSManager2014/4/11 12:59:092068 (0x0814)
CLibSMSMessageWinHttpTransport::Send: URL: PRI1.ABC.COM:80  CCM_POST /ccm_system/requestTSManager2014/4/11 12:59:092068 (0x0814)
Request was successful.TSManager2014/4/11 12:59:102068 (0x0814)
Set a global environment variable _SMSTSLastActionRetCode=-2147024767TSManager2014/4/11 12:59:102068 (0x0814)
Set a global environment variable _SMSTSLastActionSucceeded=falseTSManager2014/4/11 12:59:102068 (0x0814)
Clear local default environmentTSManager2014/4/11 12:59:102068 (0x0814)

sccmghost@hotmail.com

Hey fellow CM'ers,

I'm trying to get pre staged media working with configuration manager 2012 R2 and a Windows 8.1 image.

I've created a PSM WIM file with the primary deployment task sequence as its source. Imported the wim file as an operating system and created a new task sequence. This new task sequence contains the following information:

- Partition disk
- Apply data image
- bcdboot to create boot files
- shutdown

After booting the system, regular Windows setup is started instead of Windows PE. 

using this manual and these steps:

bcdboot.exe C:\Windows /s S: /f UEFI
DEL S:\EFI\Microsoft\Boot\BCD /f /q
COPY C:\EFI\Microsoft\Boot\BCD S:\EFI\Microsoft\Boot /y

BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {ramdiskoptions} ramdisksdidevice partition=C:
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {Default} device ramdisk=[C:]\sources\boot.wim,{ramdiskoptions} 
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {Default} osdevice ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD -set {bootmgr} device partition=S:

I am able to boot to Windows PE, however immediately after WinPE starts the task sequence wizard fails with the following error: 

Unable to read task sequence configuration disk.

I have followed every single manual I could find. Also tried Win 8.1 on UEFI, Win 8.1 on BIOS and Win 7 SP1 on BIOS. All with the same result, every single time Windows instead of WinPE boots and with the fiddling above it boots WinPE but does not continue the task sequence.

Very strange as it worked perfectly on our ConfigMgr 2007 environment a couple of years ago (same task sequence setup)

What am I doing wrong?

Michiel

Hi All,

I have recently attempted to perform OSD using SCCM 2012. Bare metal deployments seem to be working fine, but now that I have tried to create a refresh task sequence using USMT 5 the TS fails during Scanstate.

From looking at the errors USMT is trying to load the MigSys.dll file from C:\_SMSTaskSequence\Packages\0010005A\MigSys.dll but that file is actually in C:\_SMSTaskSequence\Packages\0010005A\x86\MigSys.dll". I don't know why it knows to run scanstate.exe from the proper architecture folder, but ignores that and looks for all of the other files at the root of the package id folder.

Here is the scanstate.log:

2013-07-18 13:31:42, Info                  [0x000000] SCANSTATE.EXE Version 6.2.9200.16384[gle=0x000000b7]
2013-07-18 13:31:42, Info                  [0x000000] USMT Started at 2013/07/18:13:31:42.569
2013-07-18 13:31:42, Info                  [0x000000] Command line: C:\_SMSTaskSequence\Packages\0010005A\x86\scanstate.exe \\SMP\SMPSTOREE_35137197$\4198A4A7DB1F8C89ECD956761335080BCBF8CF8B9FF9666C94A498762FDBF164 /o /localonly /encrypt /keyfile:**** /efs:copyraw /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\scanstateprogress.log /i:C:\_SMSTaskSequence\Packages\0010005A\MigUser.xml /i:C:\_SMSTaskSequence\Packages\0010005A\MigDocs.xml /i:C:\_SMSTaskSequence\Packages\0010005A\MigApp.xml /uel:30 /ue:*
2013-07-18 13:31:42, Info                  [0x000000] Script file specified: C:\_SMSTaskSequence\Packages\0010005A\MigUser.xml[gle=0x00000002]
2013-07-18 13:31:42, Info                  [0x000000] Script file specified: C:\_SMSTaskSequence\Packages\0010005A\MigDocs.xml[gle=0x00000002]
2013-07-18 13:31:42, Info                  [0x000000] Script file specified: C:\_SMSTaskSequence\Packages\0010005A\MigApp.xml[gle=0x00000002]
2013-07-18 13:31:42, Info                  [0x000000] Starting the migration process[gle=0x00000006]
2013-07-18 13:31:42, Warning               [0x080404] AdjustPrivilege: LookupPrivilegeValue failed (Error:0x521)
2013-07-18 13:31:42, Warning               [0x08040c] Failed to create SMI engine
2013-07-18 13:31:43, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:31:43, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 19)...
2013-07-18 13:31:49, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:31:49, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 18)...
2013-07-18 13:31:55, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:31:55, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 17)...
2013-07-18 13:32:01, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:01, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 16)...
2013-07-18 13:32:08, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:08, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 15)...
2013-07-18 13:32:14, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:14, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 14)...
2013-07-18 13:32:20, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:20, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 13)...
2013-07-18 13:32:26, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:26, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 12)...
2013-07-18 13:32:33, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:33, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 11)...
2013-07-18 13:32:39, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:39, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 10)...
2013-07-18 13:32:45, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:45, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 9)...
2013-07-18 13:32:51, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:51, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 8)...
2013-07-18 13:32:57, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:32:57, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 7)...
2013-07-18 13:33:04, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:04, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 6)...
2013-07-18 13:33:10, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:10, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 5)...
2013-07-18 13:33:16, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:16, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 4)...
2013-07-18 13:33:22, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:22, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 3)...
2013-07-18 13:33:28, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:28, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 2)...
2013-07-18 13:33:35, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:35, Warning               [0x0803da] Waiting 6000 msec to retry hive load (tries remaining: 1)...
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4519,C:\Documents and Settings\rdailey\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\rdailey. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4739,C:\Documents and Settings\tbramha\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-4739,C:\Documents and Settings\tbramha\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\tbramha. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-5351,C:\Documents and Settings\tmorrow\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-5351,C:\Documents and Settings\tmorrow\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\tmorrow. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-6572,C:\Documents and Settings\jburhan\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-6572,C:\Documents and Settings\jburhan\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\jburhan. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-6688,C:\Documents and Settings\lmking\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-6688,C:\Documents and Settings\lmking\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\lmking. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:41, Warning               [0x0803d9] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-9658,C:\Documents and Settings\oresearcher\NTUSER.DAT) failed (3)
2013-07-18 13:33:41, Warning               [0x0803db] IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-3399602010-199635127-1747905980-9658,C:\Documents and Settings\oresearcher\NTUSER.DAT) failed; giving up (3)
2013-07-18 13:33:41, Warning               [0x0809c0] Incomplete user profile detected and ignored:C:\Documents and Settings\oresearcher. Error: 3. Subsequent missing profiles will be immediately ignored.
2013-07-18 13:33:50, Error                 [0x08055d] MXE Agent: Loading migration XML C:\_SMSTaskSequence\Packages\0010005A\MigApp.xml threw an exception.: Win32Exception: Failed to load library "C:\_SMSTaskSequence\Packages\0010005A\MigSys.dll". Error: 0x0000007E: The specified module could not be found. [0x0000007E] void __thiscall Mig::CMXEScriptHandler::AddScriptFactory(class UnBCL::String *,class UnBCL::String *,int)
2013-07-18 13:33:50, Error                 [0x000000] EngineStartup caught exception: Win32Exception: Failed to load library "C:\_SMSTaskSequence\Packages\0010005A\MigSys.dll". Error: 0x0000007E: The specified module could not be found. [0x0000007E] void __thiscall Mig::CMXEAgent::AddXmlFile(class UnBCL::String *)
void __thiscall Mig::CMXEScriptHandler::AddScriptFactory(class UnBCL::String *,class UnBCL::String *,int)
2013-07-18 13:33:50, Error                 [0x000000] Error while trying to start the migration process[gle=0x00000006]
2013-07-18 13:33:50, Warning               [0x000000] Internal error 4 was translated to a generic error
2013-07-18 13:33:50, Info                  [0x000000] Failed.[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000]   Software malfunction or Unknown exception[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] USMT Completed at 2013/07/18:13:33:50.478[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] * USMT error code 26: [gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] | Software malfunction or Unknown exception, please check the following possible solutions:[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] | - Check log for any errors found in loaded migxml files[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] | - Verify config xml file is not loaded using /i[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] | - If duplicate SID exists from temp profile – use environment variable or delete temp profile[gle=0x00000006]
2013-07-18 13:33:50, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

In the settings for PXE on a DP, there is an option for user device affinity with three possible choices.  Do not use UDA, use UDA with manual approval or use UDA with automatic approval.  What exactly do these settings do?  The TechNet info is a bit vague.

• Select Do not use user device affinity to not associated users with the destination computer.
• Select Allow user device affinity with manual approval to wait for approval from an administrative user before users are associated with the destination computer.
• Select Allow user device affinity with automatic approval to automatically associate users with the destination computer without waiting for approval.

If I select do not use user device affinity, does that mean that the machine will not participate in UDA regardless of client settings?

Hi all,

This issue is already resolved, so I thought I'd just write about my experience in case it helps someone else.

We recently upgraded from Configuration Manager 2012 SP1 CU3 to Configuration Manager 2012 R2 CU1 and immediately began having problems with OS deployment. Most of the problems were easy to fix (like needing to update our MDT boot images and change our task sequences so that they use the R2 client instead of the SP1 client), but one issue was very difficult to identify and resolve.

We have a lot of Lenovo W540 and Dell Precision M4700 laptops. We are using the latest official driver packs from Lenovo and Dell for these models, and everything worked fine while we were on SP1 CU3. After upgrading to R2, these two models started failing OS deployment. The symptoms varied, but typically included a corrupt Segoe UI font:

We would also see these errors while setting up the Configuration Manager client during the task sequence:

"This application requires one of the following versions of the .NET Framework: v4.0.30319 Do you want to install this .NET Framework version now?"

So since this was only occuring on two specific models, I assumed it was driver related (even though the exact same drivers had worked in SP1). I initially disabled the steps that install drivers for the W540 and M4700 and just added a step to install their network drivers. Without the machine-specific drivers loaded, OSD worked, but I had to manually load drivers after it finished, which was not ideal. I concluded there must be some sort of conflict with something new in the R2 CU1 client and one of the drivers, but narrowing down which driver was causing the problem was too time consuming, so I gave up on it.

I tried using a base OS image that was not built using Configuration Manager, so it wouldn't have any version of the CM client in it. This worked fine, even with all the drivers enabled. I also tried using one of my old base OS images that had the SP1 CU3 client in it, and this also worked. So that made me suspect the 2012 R2 CU1 client was to blame for sure.

I finally tried re-building my base OS images using the 2012 R2 client, but without CU1 (I just removed the PATCH= argument from the "Setup Windows and ConfigMgr" step and re-ran the build and capture task sequence). This worked fine, and is the solution I'm settling on. I can still include the PATCH= argument when I deploy this newly-captured base image.

I don't know the full root cause, but it appears to be some sort of conflict with the device drivers used by these two specific models and something included in CU1. I suspect one of the drivers tries to upgrade .NET framework while a reboot is in progress, or something like that, but that's as far as I got.

I hope this helps someone else, or if you have any ideas on what's broken, I'd love to hear about it.

--Russel Riley

I have searched many posts and havent found a clear solution for my question.

Basically, I have OSD task sequence ready to go on my SCCM 2012 R2. It is fine to run it as "Available".

If I deploy the OSD through Software Center as "Required" and "ASAP", then I login the client, the client will run OSD task sequence sometime after about 30Min-1 hour later, not sure. And there will be no user interaction needed. However this means I need remotely log into each computer to let OSD happen.

If I deploy the same TASK Sequence as "Required" and "ASAP" through "PXE", it will first ask PXE Password(Which I set in DP->PXE Panel), then I need hit "Next" again to start the assigned OSD, which means I need physically go to each computer to do this. (EDIT: If needed, I can remove PXE password and add VB scripts in other Task Sequence, however I want to know if I still need press NEXT to start the OSD).

The clients are not AMT enabled but Lan Wake up enabled and also can be set to LAN WAKE UP Enabled with boot from LAN. I can wake up/shutdown the whole collection with command if needed. 

Is there a way that I can Re-image one collection of Computers without any interaction on client side?  

The other question is how long to wait for OSD when it is set to "ASAP"?

RockyOZ

Good Day folks!

I have come across an interesting issue that I have not been able to find a quick fix as such I am looking for some ideas where to trouble shoot my issue moving forwards.

So the Issue:

I have a TS that deploys a Windows 8.1 SOE image, this is done first by using a PXE boot PE image for an “unknown” systems to load a Custom HTA. This HTA allows me manually add the system to SCCM and add it to a required deployments collection that has the 8.1 SOE deployed to it.

The HTA also sets a few custom variables for the system resource things like system location, Machine Domain etc. Once the HTA has run the system then has a delay to allow for the resource to show up tin the 8.1 deployment collection and then closes.

Now all this appears to work fine, the system is added to the collection, reboots and the deployment runs from start to finish without error. I can also check the system resource and the variables are present.

The problem I have found is that the custom variables for this resource are not being used by the TS after reboot.. upon further investigation I found that these variables are not even being retrieved ( ran a VB script to save all the variables from the TS to a txt file to check this )  Because of this the TS is bypassing some needed TS Tasks.

A few interesting things to note:

-         System appears to be added again when AD discovery is run…. So it causes a Duplicate.

-         Client Dose connect to SCCM server after deployment but is not receiving deployments ( is getting some policy )

-         Worked with SCCM 2012 but not 2012 R2

So it appears that when the system reboots from the HTA PE step it has identified itself as an unknown system again…. Even though it has been manually added…  I am interested to know if first of all if others would agree with this and second how SCCM while running a TS matches itself up to a system to retrieve the custom set variables before client install etc... Or a good place to start looking to dig up more information!  Or anything else!

Thanks

Stuart.

I have this enviroment, where retriving IP from DHCP requires certificate. The certificate script and package is already done, and it has been working earlier, but when I try to create new boot image media, the script executes too fast and IP is not retrived. If I then execute the script manualy from WinPE, it goes OK and IP is retrived. So problem is here, that for some reason I cannot create the prestage command right.

I have tried 4 different ways;

1. In boot image properties -> customization -> run prestage command.

2. In boot image properties -> customization -> run prestage command with cmd /c

3. While creating boot media, set prestage command.

4. While creating boot media, set prestage command with cmd /c

I have checked, that package sourse and folder directories are porperly set, there is no typo or missleading paths.

Also problem is, that X:\Windows\Temp\smsts.log does not show anything about executing prestage command. 

Everyone,

I was attempting to setup my SCCM 2012 environment to be able to manage our mac devices in the district, and in the process somehow it/I broke our PXE imaging process.  I know it has something to do with the certificates, for here is the error message I get REPEATEDLY after I try to PXE image a computer:

CryptVerifySignature failed, 80090006SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
untrusted certificate: 308202E5308201CDA003020102021019460FC13CB7D69D44548650ED8F503C300D06092A864886F70D01010B050030213111300F060355040313084D50532D5343434D310C300A06035504031303534D533020170D3133303630323231323130335A180F32313133303531303231323130335A30213111300F060355040313084D50532D5343434D310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100A3A7988105F6743150E6C69AE5D1A24EC88C328DE41EABB0234949E41921CBF843F4D3ECE46DF03B6F1BA9EC4AAC628761F9009B9E21C962BE5DB7A36BAC6EAE33BD9FD15EB7283E97913413D2CE252C83A628AB41A92CF12C959CE7976F1AC037AAF28019B04907A2CE26475B418159E499AC2EAB940314970EC8782380583456A3AF2BDDF6795C3ECA28BA13FDD3A89BFB6EE8E1A48BCB535EFE49C92A457D458078E14E112B2E0AA3C45ACE49DE4959FF480AF7AA6154E5A2574A0A817B6E72C2DA9A0BE2FDD4D06583F78BFB1D03856DFF2F72ECB672EC352849811EEE360438ADB00A08D10E36175C05D14B3DAC410665528548DFB48B37BCBC25446AC30203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010B050003820101000B8E74E9DAAD6179E54F961F520FEBE6D96B866E3EA22AD93D6B86338EAFBF29B30D0AC97E94BF833511EC8DDE562B8F916CC9BBF3FF376E46D432F5039AE8E3697F118F51698206BBC064157026E51B169C3433A4217623185BDB5F18045ED9EA9898DD22BC423F55117A363957B58F9BF8934C7C6BCC5A0FF8D678F519C3EB9BCE5A6FADFBC1E184FE4B7DBFCC1C30A51FA978FE92FF49F4DD564C47CE8FFD08DB79F3C41A2989E39B73D83E8174DDB1139E61411E17218DFF76872B3D3754E7FDAC27F97AFFC54F6AF7515B5C1467A77F472921D9D823A5B956DBB335F0F80CC15A22AC4D809082E3E8A0C9CBA4DD862B4AF7A9DCFF4965D3536CEF0049EC, , 0602000000A400005253413100080000010001008796A654272DD93BC692FF3B352F58E6F371EF4330E6788FB5ACBC18E31223D8A07A26C88210DE05624B336BFDB3E150944A4C2150A150DEA5DE3485FF0701488758A4F77335842708190AA0FED41F1A09758C1D6965CB138F60B119ECADD8252B1846902200EDD5455C907EA95184C1148DDA7108EF55F436F8E3FC456ADE010514503157E1CBF0D62979E4C450A1FBEA46D506722960CDB5E670205DD80AC9A3B065247C7FA194C64BC3BD915857D30FAF8CF475A84A208E953607F183E5DFFD74979C2DFA41C7CA59D30C8C6B87D0591EFDC6B40342093A790E42B8FB4F41E44B8AD6AE764CF330C07CAD6C2FF27BA48036F22DA865F87E4AC023C32F9FB7SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
Failed to get information for MP: http://MPS-SCCM.magnoliaschools.net. 80090006.SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
PXE::MP_LookupDevice failed; 0x80004005SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
CryptVerifySignature failed, 80090006SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
untrusted certificate: 308202E5308201CDA003020102021019460FC13CB7D69D44548650ED8F503C300D06092A864886F70D01010B050030213111300F060355040313084D50532D5343434D310C300A06035504031303534D533020170D3133303630323231323130335A180F32313133303531303231323130335A30213111300F060355040313084D50532D5343434D310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100A3A7988105F6743150E6C69AE5D1A24EC88C328DE41EABB0234949E41921CBF843F4D3ECE46DF03B6F1BA9EC4AAC628761F9009B9E21C962BE5DB7A36BAC6EAE33BD9FD15EB7283E97913413D2CE252C83A628AB41A92CF12C959CE7976F1AC037AAF28019B04907A2CE26475B418159E499AC2EAB940314970EC8782380583456A3AF2BDDF6795C3ECA28BA13FDD3A89BFB6EE8E1A48BCB535EFE49C92A457D458078E14E112B2E0AA3C45ACE49DE4959FF480AF7AA6154E5A2574A0A817B6E72C2DA9A0BE2FDD4D06583F78BFB1D03856DFF2F72ECB672EC352849811EEE360438ADB00A08D10E36175C05D14B3DAC410665528548DFB48B37BCBC25446AC30203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010B050003820101000B8E74E9DAAD6179E54F961F520FEBE6D96B866E3EA22AD93D6B86338EAFBF29B30D0AC97E94BF833511EC8DDE562B8F916CC9BBF3FF376E46D432F5039AE8E3697F118F51698206BBC064157026E51B169C3433A4217623185BDB5F18045ED9EA9898DD22BC423F55117A363957B58F9BF8934C7C6BCC5A0FF8D678F519C3EB9BCE5A6FADFBC1E184FE4B7DBFCC1C30A51FA978FE92FF49F4DD564C47CE8FFD08DB79F3C41A2989E39B73D83E8174DDB1139E61411E17218DFF76872B3D3754E7FDAC27F97AFFC54F6AF7515B5C1467A77F472921D9D823A5B956DBB335F0F80CC15A22AC4D809082E3E8A0C9CBA4DD862B4AF7A9DCFF4965D3536CEF0049EC, , 0602000000A400005253413100080000010001008796A654272DD93BC692FF3B352F58E6F371EF4330E6788FB5ACBC18E31223D8A07A26C88210DE05624B336BFDB3E150944A4C2150A150DEA5DE3485FF0701488758A4F77335842708190AA0FED41F1A09758C1D6965CB138F60B119ECADD8252B1846902200EDD5455C907EA95184C1148DDA7108EF55F436F8E3FC456ADE010514503157E1CBF0D62979E4C450A1FBEA46D506722960CDB5E670205DD80AC9A3B065247C7FA194C64BC3BD915857D30FAF8CF475A84A208E953607F183E5DFFD74979C2DFA41C7CA59D30C8C6B87D0591EFDC6B40342093A790E42B8FB4F41E44B8AD6AE764CF330C07CAD6C2FF27BA48036F22DA865F87E4AC023C32F9FB7SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
Failed to get information for MP: http://MPS-SCCM.magnoliaschools.net. 80090006.SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
PXE::MP_ReportStatus failed; 0x80004005SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)
PXE Provider failed to process message. 
Unspecified error (Error: 80004005; Source: Windows)SMSPXE7/10/2014 2:31:35 PM5144 (0x1418)

I'm at a loss as to where to start on this...can someone out there help me please?

Thank you! 

Hi,

I have created the UDI task sequence. In the wizard I have mentioned windows 7 32 and 64 bit drop down option. While running the task sequence , even if I select the 64 bit image , it only install the 32 bit(default while creating task sequence was set)

Please guide me how OS can be changed using task sequence variable.

Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

Having issues with our SCCM 2012 setup with injecting drivers into an OSD.

I have created a x86 Windows 7 image for our organization and downloaded the drivers for the Lenovo L412 laptop that I'm trying to deploy it out to and added them into SCCM. I've then deployed the image and gotten this error in the logs:

<![LOG[Failed to resolve content for driver "Intel(R) 5 Series/3400 Series Chipset Family Virtualization Engine Controller - 3B53". Code 0x800700b7]LOG]!><time="10:11:16.096-660" date="11-27-2012" component="OSDDriverClient" context="" type="3" thread="884" file="driverinstaller.cpp:615">

<![LOG[Failed to find a suitable device driver for device 'PCI to PCI Bridge'.]LOG]!><time="10:11:16.096-660" date="11-27-2012" component="OSDDriverClient" context="" type="2" thread="884" file="driverinstaller.cpp:799">

<![LOG[Failed to resolve content for driver "Intel(R) QuickPath Architecture Generic Non-Core Registers - 2C50". Code 0x800700b7]LOG]!><time="10:11:16.361-660" date="11-27-2012" component="OSDDriverClient" context="" type="3" thread="884" file="driverinstaller.cpp:615">

Now the weird issue is that I then tested out these drivers and deployed them to a clean x86 Windows 7 image using SCCM and all the drivers went through fine.

I would also like to point out that the image is not corrupt as I've deployed the same image to our desktops and it installs its drivers for them fine.

I've tried using both "Apply Device Drivers" and "Apply Device Package" sequences but neither worked.

So if my drivers and image isn't the problem what is?