I'm having a weird issue when initiating OSD from the Configuration Manager Client.  It works fine from PXE and boot media, but fails from the Software Center.  After the system reboots into WinPE, the install fails on the applying OS step and the following is logged in the smsts.log:

[TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
[TSMESSAGING]                : dwStatusInformationLength is 4
    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
[TSMESSAGING]                : *lpvStatusInformation is 0x8
    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
[TSMESSAGING]            : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
[TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
Error. Received 0x80072f8f from WinHttpSendRequest.    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
hr, HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919)    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)
sending with winhttp failed; 80072f8f    TSManager    12/3/2013 3:49:20 PM    1116 (0x045C)

I am using SCCM 2012 R2 in native mode.  The error sounds like it doesn't trust my PKI.  However, I'm perplexed b/c this isn't a problem with PXE or boot media.  Do I need to import my CA into the WinPE image?  Any help would be appreciated.

Hi all,

I have recently run into some sporadic issues with our Windows 7 migration that I hope someone can shed some additional light on.  On some of the machines we're upgrading we are seeing the behavior that after USMT backs up user data and then initiates the reboot into Windows PE the machine and task sequence seems to "stall."  When the computer is in this state our field techs have said that most of the time they can press the space bar or another keyboard key and the machine seems to "wake up" and continue at that point.

The machine models this has happened on are sporadic so I do not believe it is a driver issue in WinPE.  Some machines in the deployment collection image with absolutely no issues and are also the same models as one's that have the problem.  Also the tech can boot with a SCCM USB boot drive and the machine will image fine, using the same boot image as the task sequence.

One of the techs was finally able to pull the logs from a machine in that state and I noticed a particular error that I did not see on a different machine that imaged fine.  Of note though is the machine that did not exhibit this error was an existing Windows 7 PC that I refreshed.  The one that showed the error was XP being upgraded to Windows 7.  Not sure at this point if that has any affect on what was logged.  Anyways, the smsts.log file snippet is below:

Start executing an instruction. Instruction name: Restart to Windows PE. Instruction pointer: 43    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSCurrentActionName=Restart to Windows PE    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=43    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a local default variable SMSRebootMessage    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a local default variable SMSRebootTimeout    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSLogPath=C:\WINDOWS\CCM\Logs\SMSTSLog    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Expand a string: smsboot.exe /target:WinPE    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Expand a string:     TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Start executing the command line: smsboot.exe /target:WinPE    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
!--------------------------------------------------------------------------------------------!    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Expand a string: WinPEandFullOS    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Executing command line: smsboot.exe /target:WinPE    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
========================= [ smsboot.exe ] =========================    Reboot    11/22/2013 7:08:04 PM    4744 (0x1288)
SMSTSRebootDelay=1    Reboot    11/22/2013 7:08:04 PM    4744 (0x1288)
SMSTSRebootMessage=Initiating system reboot    Reboot    11/22/2013 7:08:04 PM    4744 (0x1288)
SMSTSRebootRequested=WinPE    Reboot    11/22/2013 7:08:04 PM    4744 (0x1288)
Process completed with exit code 0    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
!--------------------------------------------------------------------------------------------!    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set authenticator in transport    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSLastActionRetCode=0    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSLastActionSucceeded=true    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Clear local default environment    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence.    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Save the current environment block    TSManager    11/22/2013 7:08:04 PM    2792 (0x0AE8)
Executing command line: "bcdedit.exe"    TSManager    11/22/2013 7:08:05 PM    2792 (0x0AE8)
CreateProcess failed. Code(0x80070002)    TSManager    11/22/2013 7:08:05 PM    2792 (0x0AE8)
Command line execution failed (80070002)    TSManager    11/22/2013 7:08:05 PM    2792 (0x0AE8)
Staging boot image ITC0009A    TSManager    11/22/2013 7:08:05 PM    2792 (0x0AE8)
ResolveSource flags: 0x00000000    TSManager    11/22/2013 7:08:07 PM    2792 (0x0AE8)
SMSTSPersistContent: . The content for package ITC0009A will be persisted    TSManager    11/22/2013 7:08:07 PM    2792 (0x0AE8)
Set authenticator in transport    TSManager    11/22/2013 7:08:07 PM    2792 (0x0AE8)
WinHttp credentials set    TSManager    11/22/2013 7:08:07 PM    2792 (0x0AE8)
List of files to be downloaded    TSManager    11/22/2013 7:08:07 PM    2792 (0x0AE8)
Downloaded file from http://<Server Name>:80/SMS_DP_SMSPKG$/ITC0009A/sccm?/WinPE.ITC0009A.wim to C:\_SMSTaskSequence\Packages\ITC0009A\WinPE.ITC0009A.wim     TSManager    11/22/2013 7:08:12 PM    2792 (0x0AE8)
VerifyContentHash: Hash algorithm is 32780    TSManager    11/22/2013 7:08:12 PM    2792 (0x0AE8)
Found boot image C:\_SMSTaskSequence\Packages\ITC0009A\WinPE.ITC0009A.wim    TSManager    11/22/2013 7:08:15 PM    2792 (0x0AE8)
Copying boot image locally...    TSManager    11/22/2013 7:08:15 PM    2792 (0x0AE8)
Failed to find ADK installation root registry key    TSManager    11/22/2013 7:08:26 PM    2792 (0x0AE8)
Opening image file C:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    11/22/2013 7:08:26 PM    2792 (0x0AE8)
Applying image 1 to volume C:\_SMSTaskSequence\WinPE    TSManager    11/22/2013 7:08:26 PM    2792 (0x0AE8)
Closing image file C:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
Capturing WinPE bootstrap settings    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
==============================[ OSDNetSettings.exe ]===========================    OSDNetSettings    11/22/2013 7:08:28 PM    1468 (0x05BC)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    OSDNetSettings    11/22/2013 7:08:28 PM    1468 (0x05BC)
Captured settings for adapter 1    OSDNetSettings    11/22/2013 7:08:28 PM    1468 (0x05BC)
OSDNetSettings finished: 0x00000000    OSDNetSettings    11/22/2013 7:08:28 PM    1468 (0x05BC)
Process completed with exit code 0    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
Installing boot image to hard drive    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
Backing up existing boot system before trying to set up new boot system    TSManager    11/22/2013 7:08:28 PM    2792 (0x0AE8)
BootLoader::backup: C:\, C:\_SMSTaskSequence\backup    TSManager    11/22/2013 7:08:29 PM    2792 (0x0AE8)
BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Process completed with exit code 0    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence.    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Save the current environment block    TSManager    11/22/2013 7:08:30 PM    2792 (0x0AE8)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence.    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Save the current environment block    TSManager    11/22/2013 7:08:31 PM    2792 (0x0AE8)
Expand a string: %_SMSTSMDataPath%\Logs    TSManager    11/22/2013 7:08:32 PM    2792 (0x0AE8)
<![LOG[LOGGING: Finalize process ID set to 828]LOG]!><time="13:30:51.969+480" date="12-02-2013" component="TSBootShell" context="" type="1" thread="832" file="tslogging.cpp:1495">        1/1/1601 12:00:00 AM    1998216043 (0x771A5B6B)
==============================[ TSBootShell.exe ]==============================    TSBootShell    12/2/2013 1:30:51 PM    832 (0x0340)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    TSBootShell    12/2/2013 1:30:51 PM    832 (0x0340)
Debug shell is enabled    TSBootShell    12/2/2013 1:30:51 PM    832 (0x0340)
Waiting for PNP initialization...    TSBootShell    12/2/2013 1:30:51 PM    840 (0x0348)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    12/2/2013 1:30:51 PM    840 (0x0348)
WinPE boot path: C:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    12/2/2013 1:30:51 PM    840 (0x0348)
Booted from fixed disk    TSBootShell    12/2/2013 1:30:51 PM    840 (0x0348)
Found config path C:\_SMSTaskSequence    TSBootShell    12/2/2013 1:30:52 PM    840 (0x0348)

Specifically the bolded entries above are what is concerning me as possibly causing this "stall."

Has anyone encountered a scenario such as this or can shed anymore light on the errors logged above?  Of possible concern to me is that this started happening in a greater number after configuring and putting in place a second Management Point and Distribution Point.  I'm not saying there's a definitive correlation but the timing of this was worrisome.  The site shows no errors whatsoever with either of the MP's or DP's.

Any help or comments are greatly appreciated!

Thanks

Hi all,

I was hoping someone can shed some additional light and info on an issue we've run into in our Windows 7 migration.  On a recent handful of computers we've noticed that the task sequence will begin to install, but the task sequence does not actually begin.  The symptom of this is in the Software Center the task sequence shows "Installing" but nothing ever happens.

When this happens there is no SMSTS.log file created because the task sequence engine does not seem to initiate.  I found the following errors in the TSAgent.log file on one particular computer that this happened on:

Initializing the Task Sequence...    TSAgent    12/2/2013 7:14:49 AM    1420 (0x058C)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}    TSAgent    12/2/2013 7:14:49 AM    3504 (0x0DB0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}    TSAgent    12/2/2013 7:14:49 AM    3504 (0x0DB0)
UEFI: false    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
SMS Client GUIDGUID:9CEDC2E3-00EE-450E-832C-BB0F2BD7A1AB    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting the client certificate provider to Microsoft Strong Cryptographic Provider.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully set the client certificate provider to Microsoft Strong Cryptographic Provider    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully set the client certificate provider to Microsoft Strong Cryptographic Provider    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype).    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The current advertisement ID is S11200FE    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID of current advertisement is S1100089    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package name of current advertisement is Windows 7 x64 Install and BitLocker Encryption    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID of current advertisement is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The PolicyID of current advertisement is S11200FE-S1100089-6F6BCC28    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The Current Site Code is S11    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The Current Management Point is <Site Server>    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
getting the MP public signing certificates    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
MP public signing cert: 308202E9308201D1A00302010202101FD06A44337313974A6A997A1F8E99DB300D06092A864886F70D01010B05003023311330110603550403130A4954435343434D4D5032310C300A06035504031303534D533020170D3133313131313232313332365A180F32313133313031393232313332365A3023311330110603550403130A4954435343434D4D5032310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100AD1CA948BAAD0FC7AE64055A954A283AD99BFE7FF08B3144A60046E712502857735B0FF5573DC890B95B375698CA2184873B349AF2379C5883EC4686EBCF44096974AFC8573F66151211A7EF7EDD81D28E27DC63ADD9FFA1105E9D22BD7596E48BC4755D3AD22AAC0D8864F86EC8A00F21861609B68B0AF57D7DF36FB67375CBD835A2D699AA2A49C8ABF2EC441F9A83A469127B9C63DADC442439DB9EE21C9993AA95530F78A6FF3237EA696AF598DF6B91C8B215988E131B464A904D8888ED39FD6D1CDB5045DE6EB03B4438DEB0B4B7F977DC2BD7788A7BB2307F48BEA129C2AE8771ED0B3871996F4E9F37FD80948BDFC23D7E406FD40F5B9B98DFB799230203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010B05000382010100A5BF71EFC69D51C2703153B1A8C06653887080AE03BCC2031D36832D03698988D9E19316BEF9618C110F1BE661FA23E93E34BB71C5722B5B94078B4E0BDF5A4106186A899A30F945F59FDE9AB3741C74929D2B34A76021CB80AF14CA22F9CF1114B03DDECF658828AB80B46EEBDE3581B27D37CF65174CCEC87CE89C66D1C6D65918F43493D311CFB039009AE117FF5B027A765D3115F8481979ED18DD738E2D1AA9D749AD7758E652115576D332A005F8E5DAEC4D16CADBF1622B4CB45E38170C4FB682378796EA47FD8B95E88D8B0EA09D3D8D41BBFE83F4BA9BA28BFFBAF0B8CB2580015611D43DC5BFE011590967F079A383B9CF0BDB4CE5C7411BA030A8   TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
MP public signing cert: 308202E3308201CBA003020102021016975DD1F2A8A7B04F44AE9A5855E214300D06092A864886F70D01010B050030203110300E060355040313074954435343434D310C300A06035504031303534D533020170D3133313031323136353835385A180F32313133303931393136353835385A30203110300E060355040313074954435343434D310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100ED2BBAD067A6FEC86F5C574EE1F4FD20DA0E07BA4DBFDBD7BEE2F23672770090EACC121BF2E9BA3FC7C1000C6DA72E4DA9CE38AD853AA7BDD4E89FC05DFD2E0016822AA347E8F0941EA02E1224B4B8055961AC9D9E7D0FBADF45D2171915F7AC0A5D530826BFC4A97D7F3488947ACF2DF5D9A5ED7E04F9D5D09BCBA05FEF5709B06C5E3F7383C91CFDF928BA4AE6CCDB60D7DE00A306103B61755B97AB91430AB461158C633E92F78D203E9BC37DB8480AEEF0FA385C955A603DFE54542E81FE12784530842B0FE8F9ECCEB98AC08EDFADC9C08145B802EA0B763D3E7DCB43AD3AFA16DA8F950A929191118C952FF786464D4FE3802EF43593CB294EA81FB08F0203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010B05000382010100190EF14A96A3A7B33770F65BF4E6A72331865B119CEC1063401C0E15FEC769070349D0401E6C207A46F00DA6A35C8BD22110610716406ECC45221A423E12C3F915D2BBBDD90FDD4E98879ECE28A0F4531E5DE43F5937C0B0A616FE9889D25506669ACF6A08B0A1EAC38367A1501D6109D138B1017AE9ADF04B3B1E61036185035BAB3297E66AE21EB9D3183D7D9B0CDA70281223151737D1161A705C1FD4E73971C796C8695FB7F24838B0765C9B2396129F98BD7EA6756147F784A247410130B2515C6EE8C348C2C556C4C95DA78E4FC0AAA5DA8D68A788826BD0A71D7859BF0BEE7568B667D119F432C11BC790D508D4364DE19294E3205911F49B34F2B549   TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
CRL Checking is Enabled.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Enumerating user affinity    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
User affinity:     TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully retrieved TS launch information.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Current TimeZone saved as 360,0,-60,0,11,0,1,2,0,0,0,0,3,0,2,2,0,0,0,Central Standard Time,Central Daylight Time    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Successfully retrieved Current TimeZone information.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get active request.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Getting Active request details . . .    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The handle for execution request is {3EB98D11-F961-4C7D-93A4-DAB23473992B}    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Saving access handle: {3EB98D11-F961-4C7D-93A4-DAB23473992B}    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this request is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this request is S1100089    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Saving Package ID: S1100089, Program ID:*    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Getting member programs.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
There are 36 member programs for this program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100018 to http://<Site Server>/SMS_DP_SMSPKG$/S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100018 to http://<Site Server>/SMS_DP_SMSPKG$/S1100018,http://<Site Server>/SMS_DP_SMSPKG$/S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS1100018 to http://<Site Server>/SMS_DP_SMSPKG$/S1100018,http://<Site Server>/SMS_DP_SMSPKG$/S1100018    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100065 to http://<Site Server>/SMS_DP_SMSPKG$/S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100065 to http://<Site Server>/SMS_DP_SMSPKG$/S1100065,http://<Site Server>/SMS_DP_SMSPKG$/S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS1100065 to http://<Site Server>/SMS_DP_SMSPKG$/S1100065,http://<Site Server>/SMS_DP_SMSPKG$/S1100065    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110006D to http://<Site Server>/SMS_DP_SMSPKG$/S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110006D to http://<Site Server>/SMS_DP_SMSPKG$/S110006D,http://<Site Server>/SMS_DP_SMSPKG$/S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS110006D to http://<Site Server>/SMS_DP_SMSPKG$/S110006D,http://<Site Server>/SMS_DP_SMSPKG$/S110006D    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is Per-system unattended    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110007C to http://<Site Server>/SMS_DP_SMSPKG$/S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110007C to http://<Site Server>/SMS_DP_SMSPKG$/S110007C,http://<Site Server>/SMS_DP_SMSPKG$/S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS110007C to http://<Site Server>/SMS_DP_SMSPKG$/S110007C,http://<Site Server>/SMS_DP_SMSPKG$/S110007C    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100099 to http://<Site Server>/SMS_DP_SMSPKG$/S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S1100099 to http://<Site Server>/SMS_DP_SMSPKG$/S1100099,http://<Site Server>/SMS_DP_SMSPKG$/S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS1100099 to http://<Site Server>/SMS_DP_SMSPKG$/S1100099,http://<Site Server>/SMS_DP_SMSPKG$/S1100099    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110009A to http://<Site Server>/SMS_DP_SMSPKG$/S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110009A to http://<Site Server>/SMS_DP_SMSPKG$/S110009A,http://<Site Server>/SMS_DP_SMSPKG$/S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS110009A to http://<Site Server>/SMS_DP_SMSPKG$/S110009A,http://<Site Server>/SMS_DP_SMSPKG$/S110009A    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110009B to http://<Site Server>/SMS_DP_SMSPKG$/S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S110009B to http://<Site Server>/SMS_DP_SMSPKG$/S110009B,http://<Site Server>/SMS_DP_SMSPKG$/S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS110009B to http://<Site Server>/SMS_DP_SMSPKG$/S110009B,http://<Site Server>/SMS_DP_SMSPKG$/S110009B    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is MBAM Client Agent 2.0 x64    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000B0 to http://<Site Server>/SMS_DP_SMSPKG$/S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000B0 to http://<Site Server>/SMS_DP_SMSPKG$/S11000B0,http://<Site Server>/SMS_DP_SMSPKG$/S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS11000B0 to http://<Site Server>/SMS_DP_SMSPKG$/S11000B0,http://<Site Server>/SMS_DP_SMSPKG$/S11000B0    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S11000BA    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000BA    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000BA to http://<Site Server>/SMS_DP_SMSPKG$/S11000BA    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000BA    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000BA to http://<Site Server>/SMS_DP_SMSPKG$/S11000BA,http://<Site Server>/SMS_DP_SMSPKG$/S11000BA    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS11000BA to http://<Site Server>/SMS_DP_SMSPKG$/S11000BA,http://<Site Server>/SMS_DP_SMSPKG$/S11000BA    TSAgent    12/2/2013 7:14:50 AM    
The package ID for this member program is S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is Clindesk 2 v1.1.0.18    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000C8 to http://<Site Server>/SMS_DP_SMSPKG$/S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000C8 to http://<Site Server>/SMS_DP_SMSPKG$/S11000C8,http://<Site Server>/SMS_DP_SMSPKG$/S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS11000C8 to http://<Site Server>/SMS_DP_SMSPKG$/S11000C8,http://<Site Server>/SMS_DP_SMSPKG$/S11000C8    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000D5 to http://<Site Server>/SMS_DP_SMSPKG$/S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000D5 to http://<Site Server>/SMS_DP_SMSPKG$/S11000D5,http://<Site Server>/SMS_DP_SMSPKG$/S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS11000D5 to http://<Site Server>/SMS_DP_SMSPKG$/S11000D5,http://<Site Server>/SMS_DP_SMSPKG$/S11000D5    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is *    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Attempting to get locations for this member program.    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000E1 to http://<Site Server>/SMS_DP_SMSPKG$/S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The location for this member program is http://<Site Server>/SMS_DP_SMSPKG$/S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting source for S11000E1 to http://<Site Server>/SMS_DP_SMSPKG$/S11000E1,http://<Site Server>/SMS_DP_SMSPKG$/S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Setting _SMSTSHTTPS11000E1 to http://<Site Server>/SMS_DP_SMSPKG$/S11000E1,http://<Site Server>/SMS_DP_SMSPKG$/S11000E1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_6e47a5de-b426-4246-ba01-f6433a1f97d1    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d32e60-b3a2-448c-a322-96cccc7d5f9e    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d32e60-b3a2-448c-a322-96cccc7d5f9e' with Content Id 'Content_6e47a5de-b426-4246-ba01-f6433a1f97d1'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_9e286aea-80f7-4974-a5ab-a7fc940a2640    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d32e60-b3a2-448c-a322-96cccc7d5f9e    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d32e60-b3a2-448c-a322-96cccc7d5f9e' with Content Id 'Content_9e286aea-80f7-4974-a5ab-a7fc940a2640'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_0cc03acb-0e54-416c-a23e-d19cce402a4f    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d84dad-60db-4fab-85e3-f2c7c82cc9fd    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d84dad-60db-4fab-85e3-f2c7c82cc9fd' with Content Id 'Content_0cc03acb-0e54-416c-a23e-d19cce402a4f'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_3defe9f6-8306-4794-b27a-f3a4e981708c    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d84dad-60db-4fab-85e3-f2c7c82cc9fd    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_06d84dad-60db-4fab-85e3-f2c7c82cc9fd' with Content Id 'Content_3defe9f6-8306-4794-b27a-f3a4e981708c'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_f59aed4d-aa3e-4992-8ef1-9e3d9b973cec    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_0b765060-14c4-40eb-b284-07f77c1f5d49    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_0b765060-14c4-40eb-b284-07f77c1f5d49' with Content Id 'Content_f59aed4d-aa3e-4992-8ef1-9e3d9b973cec'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_b0fc3118-57c4-4f70-9019-f0d021b7a253    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
The program ID for this member program is ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_168a76a3-40f8-43d9-b40f-7485a91bff2d    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)
Found member application 'ScopeId_6031FF47-7EA9-4E27-88D7-11D4D2BA3D21/Application_168a76a3-40f8-43d9-b40f-7485a91bff2d' with Content Id 'Content_b0fc3118-57c4-4f70-9019-f0d021b7a253'. Skipping to store content location information.    TSAgent   12/2/2013 7:14:50 AM    3504 (0x0DB0)
The package ID for this member program is Content_9ca3bd00-4945-4726-848a-fff200d3f79d    TSAgent    12/2/2013 7:14:50 AM    3504 (0x0DB0)

I am running an MDT Task Sequence integrated into CM2012 R2, and I'm deploying Win 8.1.

I'd like to enable Hyper-V on clients that are capable of it, as well as .Net 3.5.  The MDT TS gives me the pretty option of adding a step to Add Programs and Features.  I add the step, and select Win 8.1 as my OS, then select .net 3 and Hyper-V. 

All works peachy, the features do get installed, except that this seems to cause the machine to reboot in an uncontrolled manner by the installation, so the TS fails (it can't find it's files because it never controlled the reboot).  

I've tried moving the step around a bit in the TS as I recall there were issues about when the step can be run by the TS, but can't seem to figure out when or how to use this action and keep my TS from failing after it reboots.  Currently, the step is located in my State Restore section of the MDT Task Sequence, prior to any app installations.  

Does anyone have any guidance on how to do this?  

Thanks!

Using Config Mgr 2012 SP1 CU2 to deploy task sequence to bare metal servers.  I'm using the provided Config Mgr client in the task sequence but the site codes are not being set.  There's no site code at all being set.  When I try and set the SMSSITECODE in the config mgr step under installation properties, I get an error that says "INSTALLATION PROPERTIES CAN NOT INCLUDE SMSSITECODE".

Without using a program, how am I supposed to set the SMS site code?

Hi,

i'm moving OSD from MDT 2012 to SCCM 2012 sp1 cu2. I'm deploying Windows server 2003. I need to create domain user profile during "new computer" deployment. In MDT i use run command line, with additional option "load the user's profile" and profile is created where it should be created - c:\documents and settings\user profile. I use the same "run command line" step in SCCM, specify to run this step with credentials of needed user, but profile is created in c:\documents and setings\<Domain Name>\user profile . Any ideas why?

I'm seeing some issues when using an OU (and child OUs) as a requirement for application deployment during OSD.

The target machine logs the application as "not required" during the Task Sequence, I'm guessing because SCCM hasn't got the OU information for the machine, yet. Is there any way I can trigger population of this data in ConfigMgr during OSD to facilitate this requirement specification.

I have a 'workaround' where I read the OU from ADDS however this won't work for IBCM clients - so I end up either having a working TS and breaking IBCM deployment of the applications, or vice versa.

Thanks,

Chris

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Maybe I am missing something with the capture process.

I created a windows 8 wim customized it, sysprepped (oobe, generalize) and when I deploy using SCCM 2012, my image always comes directly back to the windows welcome screen asking for PC name and local user info. Do I need to avoid the sysprep step?

I am trying to get OSD working with SCCM 12, unfortunately I have never recieved any formal training with SCCM OSD and I never created our imaging with 07.

in 07 we used unknown computer support, specified pc name on boot from media TS and away it went.

Now When I do the same with a TS deployed to collection with direct membership to PC, it applies the image and CM Client, but never joins domain and comes back with this welcome screen.

I appologize in advance, but I am fighting with this trying to keep my head above water.

Hi,

I captured an image of Windows 7 and trying to deploy , at the stage of Applying image 2 from file.wim to volume c:\ , I am getting error with error 0x80070070 , In Apply Operating System Task,   I checked from Image properties. image 2-2 is selected which has OS ,  I am deploying image on Same Model Laptop with same size disk.

Please find blow smsts.log which i copied from client machine during imaging

http://textuploader.com/1snb

Regards
Usman Ghani

Usman Ghani - MCITP Exchange 2010

Greetings,

I'm trying to apply updates to my Windows 7 SP1 x64 Operating System Image.  SCCM 2012 SP1.

From the OfflineServicingMgr.log

Checking if update (20 of 56) with ID 16808244 needs to be applied on the image. 2 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:30.489+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\c39fc94e-b976-41c9-8b8e-01ad700d8be2\windows6.1-kb2676562-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
Applying update with ID 16808244 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.272+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.273+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.273 2013 ISTR0="16808244" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.274+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808244 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.275+420><thread=12784 (0x31F0)>
Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.276+420><thread=12784 (0x31F0)>
STATMSG: ID=7917 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.277 2013 ISTR0="E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe" ISTR1="16808244" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.278+420><thread=12784 (0x31F0)>
Not applying this update binary, it is not supported.   $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.280+420><thread=12784 (0x31F0)>
Checking if update (21 of 56) with ID 16808261 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.327+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\29f0e274-ad1d-4599-bf3d-0c8fa9064e76\windows6.1-kb2660649-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.344+420><thread=12784 (0x31F0)>
Applying update with ID 16808261 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.345+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:42.465 2013 ISTR0="16808261" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.466+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808261 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.468+420><thread=12784 (0x31F0)>
Checking if update (22 of 56) with ID 16808368 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.650+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\96815fb1-35a9-4d82-bf16-f3d257800211\windows6.1-kb2656411-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.644+420><thread=12784 (0x31F0)>
Applying update with ID 16808368 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.647+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.699+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.700+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:48.700 2013 ISTR0="16808368" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.703+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808368 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.704+420><thread=12784 (0x31F0)>
Checking if update (23 of 56) with ID 16808433 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.712+420><thread=12784 (0x31F0)>

I can't seem to figure out why about 10 updates installed, and the rest just bomb out. I did go ahead and exclude all the folders from the antivirus, even though I'm running SCEP.

Thanks

Hello,

i wnat to copy some settings to the current logged user within an application package. The proofing should check if the file is store under %appdata% folder of the users.

I added this as check in Apllication but it failes

I'm trying to run an in-place USMT/OSD process on a client but it's failing to capture the user state, here's the errors in smsts.log:

.

Failed to decrypt state encryption key (0x80070057)

Failed to parse response from Management Point (0x80070057).

ExecuteCaptureRequestMP failed (0x80070057).

ExecuteCaptureRequest failed (0x80070057).

OSDSMPClient finished: 0x00000057

Process completed with exit code 87

Failed to run the action: Request User State Storage.
The parameter is incorrect. (Error: 00000057; Source: Windows)

.

First I look to see if there is a current User State Migration Association - can't see one, but then I look directly in the Table, StateMigrationAssociation, I can see an entry for the computer's resource ID in the SourceClientItemKey. What I also happen to notice is no encryption key exists.

I don't want to manipulate the data in the DB directly, so I try creating a dummy side-by-side association using this computer as the source, nothing changes in the database until I delete the dummy association and the entry is removed. I then run the User State Migration again (as an In-Place again) and everything is working.

.

What's going on?

Have an issue with SCCM 2012 SP1 CU2.  We use OSD which requires computer objects in specific collections that have mandatory assignments associated with them.  What we are running into is if a build fails but it still comes up into Windows and SCCM client communicates, we delete the computer object manually and then re-create it so the advertisement will run the next time we try it.  

However in SCCM 2012 (we've been on it a couple weeks) is giving me problems I didn't experience in 2007.  My process is to power off the physical server that is being built.  Then we delete the object from SCCM.  I update collection membership and verify it's gone.  I look at the All Systems and the object is gone.  I run a MAC address query and I get no results.

I then use the SCCM web service available on CodePlex to re-add the computer object but it fails.  The web service logs shows error was due to the computer name already being in use.  If I try and import the object manually in the console, I get an error that is similar to that.

If I wait a couple hours I can re-add the object.

So where is the object in the mean time if it isn't visible anywhere in the console or queries?  How can I properly delete the object so it's gone immediately so I can re-add it?

Hello,

When staging a machine with standalone media (usb) applications are not installed, when staging via PXE with the same Task Sequence all applications are installed during the staging.

I checked the setting "allow this application to be installed from the install application task sequence action..."

Errors I find in smsts.log are:

<![LOG[spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2237)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="cisdkclass.cpp:2237">
<![LOG[StoreCIFromDisk: Unable to store CI: 0x80004005]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="cisdkclass.cpp:2243">
<![LOG[spAppSDK->StoreCIFromDisk (&PathInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,912)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:912">
<![LOG[StoreCIFromDisk failed]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:912">
<![LOG[StoreAppDocuments failed; 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:948">
<![LOG[TS::Utility::StoreAppDocuments (sAppDocs.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,880)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="installapplication.cpp:880">
<![LOG[StoreAppDocuments failed]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:880">
<![LOG[Step 3 out of 5 complete]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="daprogress.cpp:226">
<![LOG[Install application action failed: 'Adobe Reader XI (11.0.0.3 ) - Français'. Error Code 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:798">
<![LOG[Sending error status message]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="installapplication.cpp:802">
<![LOG[sClientGUID.empty()==false, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5699)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:5699">
<![LOG[The client GUID must be set in an environment variable]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:5699">
<![LOG[Non fatal error 0x80004005 in sending task sequence execution status message to MP]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="2" thread="2644" file="utils.cpp:5811">

Any idea ?

Thanks

Hi,

Have just created a new WIN8.1 x64 enterprise image on a vm and captured it using the capture media.

I have imported it into SCCM 2012 R2 and have created a new deployment task and have sent it out to a test computer.

Once the computer has reimaged, and the task completes, a user logs on and no apps appear at all. not even the default apps like bing, news, weather etc. Just IE, Desktop etc.

In my task sequence, nothing really special happens, other than install image, apply drivers and join domain. I have also made a unattended file to skip through OOBE stuff that happens and to make sure locale is EN-AU. This is set at Apply Operating System.

What am I doing wrong or missing?

I all I want is the default  windows 8.1 apps to appear for each user who logs on.  There is no need to do a copyprofile as i have not made any modifications to the user account during image build.
I did not update the apps before taking the image.

Here is a copy of the unattend.xml file

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="oobeSystem"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><OOBE><HideEULAPage>true</HideEULAPage><HideOEMRegistrationScreen>true</HideOEMRegistrationScreen><HideOnlineAccountScreens>true</HideOnlineAccountScreens><HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE><NetworkLocation>Work</NetworkLocation><ProtectYourPC>1</ProtectYourPC></OOBE><TimeZone>Tasmania Standard Time</TimeZone></component><component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>en-AU</InputLocale><SystemLocale>en-AU</SystemLocale><UILanguage>en-AU</UILanguage><UserLocale>en-AU</UserLocale></component></settings><cpi:offlineImage cpi:source="wim:c:/downloads/windows%208.1%20ent/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

I'm getting an error during the 'Apply Operating System' step of an OSD task sequence.

This same build sequence has been working without error up until this point. It fails only with a certain model of machine, the LENOVO M93P, with 16GB RAM and 500GB SSD.

The error we get is:

Insufficient system resources exist to complete the requested service. (Error: 800705AA; Source: Windows)

There is obviously enough RAM and disk available. 

Any help would be greatly appreciated.

Many thanks.

Good afternoon everyone,

I'm trying to PXE boot with SCCM 2012 for an OSD deployment and I'm getting the following error below, and I've also setup the DHCP server to allow for Options 066 for the IP Address of the SCCM Server and 67 for Bootfile Name  SMSBoot/x86/bootmgfw.efi. Am I doing something wrong with the settings(this is the only way, no IP handlers)?

The error message is PXE-MOF: Exiting Intel Boot Agent. Not Boot Device Available. The forum won't let me post a picture just yet.