OSD task sequence fails to install application on workgroup computers

Environment:
Windows Server 2008 R2 Standard, SP1
SCCM 2012 R2
Issue:
OSD TS fails to install applications from local DP on Windows 8.1 x86 workgroup computers. Same applications install fine from OSD/TS on domain computers. A standard push installs fine when deployed outside of OSD/TS to workgroup, or domain computer.
- “SMSMP=managementpoint.domain.com” is included in ‘Setup Windows and ConfigMgr’ installation poperties
- “Allow clients to connect anonymously” enable on DP system role, HTTP client communication
- Network Access Account is configured and authentication is confirmed
- Have confirmed no overlapping boundaries
- IIS anonomys and Windows authentication is enabled for SMS_DP_SMSPKG$, anon authentication creds set to "Specific user: IUSR"
After OSD deployment to workgroup computer completes -
AppEnforce.log is missing
smsts.log
App install failed.
Setting TSEnv variable '_TSAppInstallStatus'='Error'
Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/Application_486d99ca-817a-4600-889e-50f8e4f91592'=''
Completed installation job.
Step 3 out of 3 complete
Install application action failed: 'Microsoft_Office_Professional_2013_v15.0.4420.1017_CA-copy'. Error Code 0x80004005
CITaskMgr.log
State transition to (Failure), Error(0x87d00222) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_f7f47522-3654-43b0-95ef-55198d957bdf.8..Install.ContentDownload)
Initiating task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15 (Microsoft_Office_Professional_2013_v15.0.4420.1017_CA_x86_P_PW) for target: , consumer: {634F5894-5AB1-4D48-83F7-603E94FE1F3F}
Initiating content download : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
State transition to (InProgress), Param(0) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
State transition to (InProgress), Param(0) : CTaskConsumer(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15.{CC8A099F-8EC4-4484-9191-53FFC1775D18})
Successfully initiated contents download request {5237AC77-651A-4723-AF91-78A1C0497DBD} : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15 for target: , consumer {634F5894-5AB1-4D48-83F7-603E94FE1F3F}
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/Application_486d99ca-817a-4600-889e-50f8e4f91592.22 for target: , consumer {502180D3-CA3B-4657-AD32-D43F952A6576}
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/RequiredApplication_486d99ca-817a-4600-889e-50f8e4f91592.22 for target: , consumer {1A485BC4-DD0C-4659-B034-8D7F9B436B3A}
State transition to (Failure), Error(0x87d00222) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
ContentTransferManager.log
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} (corresponding DTS job {901A1D57-D363-45FE-A4F4-8509F5556D53}) started download from 'http://HOUMGMT49.APACHECORP.COM/SMS_DP_SMSPKG$/Content_ed232f49-224b-48cc-9c01-0ff31bae851e.1' for full content download.
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM encountered error processing reply from DTS. Code 0x87d00215
Cancelled CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E}
Two workarounds below (Not acceptable solutions)
*I can add a pause script after Setup Windows and ConfigMgr sequence, wait 5-10 minutes and the applications will install. I assume this is because the CM client has time to fully provision.
* I can add the anon ‘IUSR’ account to the local administrators group on the DP and all applications install (without the pause script mentioned above). I can reproduce the issue repeatedly by removing and adding the anon account.
Any help with this would be greatly appreciated…
Also, I come from a CM 2007 background and somewhat new to CM 2012. Should WebDAV and/or URL Authorization be installed and configured on the DP? According to MS tech support “No”. However, I’ve seen several SCCM 2012 guides on the web that say it should
be installed.
Regards
David K. Harrison

Locationservices.log, CIDownloader.log, CIagent.log, DataTransferService.log also need to be checked. We need to find out what credential the Client trys to use when it downloads content from DP.
Juke Chou
TechNet Community Support

Similar Messages

OSD Task Sequence fails to install SCCM client

Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windows

Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
can mount the Image and check those settings.
RunOnce Key Reference :
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
can be beneficial to other community members reading the thread.

OSD Task sequences failed in application installation step.

Hello,
I am deploying win 7 with installing app-v client application(by package), I applied this Task sequences on some of devices sometimes it worked and installed app-v client application but in some cases
Task sequences failed to installed app-v client steps.
Please provide reason for this and how to resolve this.

Certain pre-requisites need to be installed for the App-V client to successfully install.
Take a look here http://sccmentor.wordpress.com/2013/05/21/deploy-the-app-v-5-0-client-with-sccm-2012/
Note that KB2533623 has been superseeded if you are pushing out any Windows Updates as part of your OSD.
http://sccmentor.wordpress.com/2013/07/30/kb2533623-superseded-by-kb2758857/
Have these pre-reqs been applied in the Task Sequence prior to the App-V client install? If not add them in and try the push again.
Cheers
Paul | sccmentor.wordpress.com

OSD Task Sequence Fails with Error 0x80091007

Hello Everyone,
I have a bit of a weird hash mismatch problem. The issue is only occuring on one laptop. The laptop was imaged successfully, new out of the box. Computer started "acting craptacular" according to the tech, so he tried to reimage it,
assuming one of the applications he put on the computer while setting it up for the user may have messed it up.
From that point forward, the computer couldn't image anymore. I can image the same model, TS, and even other models without issue. The error logs are pointing to a hash value mismatch on the OS WIM.
Here are the log files - I wish there was a way to make them cleaner. I ran some hardware tests with IBM's PCDoctor, and it came back clean. I'm starting to run out of ideas.
Thanks in advance!
Log: (SMSTS.LOG)
Download done setting progress bar to 100 ApplyOperatingSystem 5/14/2010 4:09:31 PM 840 (0x0348)
Hash could not be matched for the downloded content. Original ContentHash = A6170DC8CFC5A443636828F093C45377B5FE2A62, Downloaded ContentHash = 7DEBC67B90C2326031EF8727238176C92A02006C ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2901) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3000) ApplyOperatingSystem 5/14/2010
4:09:53 PM 840 (0x0348)
DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3128) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3029) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
TS::Utility::ResolveSource( this->packageID, this->packagePath, TS::Utility::ResolveSourceFlags::PersistContents ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1255) ApplyOperatingSystem 5/14/2010 4:09:53
PM 840 (0x0348)
resolvePkgSource(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1299) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
Installation of image 1 in package RH1000DD failed to complete..
The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
installer.install(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1373) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RH1000DD ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
The user tries to release a source directory C:\_SMSTaskSequence\Packages\RH1000DD that is either already released or we have not connected to it ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,360) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840
(0x0348)
Process completed with exit code 2148077575 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
!--------------------------------------------------------------------------------------------! TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Failed to run the action: XP SP3 - Multi-HAL.
The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Send a task execution status message SMS_TSExecution_ActionFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
MP server rh1-sccm.ritehite.com and port 80. SSL=false. CRL=false. TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Site code: RH1 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Client machine name: R842AEYa TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Client Identity: GUID:428CFC8B-1BE1-4E11-B2C4-21E31EA71572 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Advertisement ID: RH1200C2 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Package ID: RH1000DF TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending StatusMessage TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Formatted header: TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>56d444c9-6bf0-4ed2-86a9-5f199c90924c</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T21:09:53Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="4246"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
CLibSMSMessageWinHttpTransport::Send: URL: sccmserver.x.com:80 CCM_POST /ccm_system/request TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
The request has succeeded. 200 OK TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Set a global environment variable _SMSTSLastActionRetCode=-2146889721 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Clear local default environment TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Let the parent group (Apply Operating System) decides whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Let the parent group (Install Operating System) decide whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Failed to run the last action: XP SP3 - Multi-HAL. Execution of task sequence failed.
The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Hi Guys,
My WIM is currently sitting at 1.8 GB, so I'm not sure it is the 4 GB bug you were referring to.
I haven't tried a re-import/update DP yet mainly because the problem is occuring on only
one computer at this moment. In fact, I have deployed several computers already with the same DP, same WIM and even the same model of computer. That makes me think it isn't an issue with the WIM as
much as it is an issue with the computer itself.
Can you guys think of anything on the computer that would cause the failure?
Thanks again,
Sean

SCCM 2012 OSD Task Sequence Fails "An error occurred while retrieving policy for this computer"

We have SCCM 2012 R2. I amm trying to start OSD task sequence from bootable media.
Hyper-v client gets DHCP ip and starts MDT bootable media, but could not find policy.
From F8 I can ping SCCM/DP/MP server.
What could be the cause?

Yes, this DHCP client is in the same subnet as other working clients.
smsts.log from client
Request was successful. TSPxe
21.03.2014 14:14:14 324 (0x0144)
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1970)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
reply has no message header marker TSPxe
21.03.2014 14:14:14 324 (0x0144)
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Failed to get client identity (80004005)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1113)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
failed to request for client
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Exiting TSMediaWizardControl::GetPolicy. TSPxe
21.03.2014 14:14:14 324 (0x0144)

PXE OSD Task Sequence fails to run on new laptop

We are trying to run a working PXE OSD task sequence on a new HP laptop. It's a Elitebook 840 G2. We've downloaded the provided driver package & created a new driver package in SCCM. We inserted the driver into the boot image &
updated the DPs. When we PXE boot the laptop it flashes the splash screen & reboots. Other laptops & desktops boot properly. This looks like a driver issue but we wanted to run it past the forum to see if anyone had any other suggestions.
The SMSTS log file is copied below.
LOGGING: Finalize process ID set to 728
TSBootShell
4/23/2015 4:20:40 PM
732 (0x02DC)
==============================[ TSBootShell.exe ]==============================
TSBootShell 4/23/2015 4:20:40 PM
732 (0x02DC)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
TSBootShell 4/23/2015 4:20:40 PM
732 (0x02DC)
Debug shell is enabled TSBootShell
4/23/2015 4:20:40 PM 732 (0x02DC)
Waiting for PNP initialization... TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
RAM Disk Boot Path: NET(0)\SMSIMAGES\ALN00001\BOOT.ALN00001.WIM
TSBootShell 4/23/2015 4:20:40 PM
736 (0x02E0)
Booted from network (PXE) TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
Network(PXE) path: X:\sms\data\ TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
Found config path X:\sms\data\ TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
Booting from removable media, not restoring bootloaders on hard drive
TSBootShell 4/23/2015 4:20:40 PM
736 (0x02E0)
X:\sms\data\WinPE does not exist. TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
X:\_SmsTsWinPE\WinPE does not exist. TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
Executing command line: wpeinit.exe -winpe TSBootShell
4/23/2015 4:20:40 PM 736 (0x02E0)
Executing command line: X:\WINDOWS\system32\cmd.exe /k
TSBootShell 4/23/2015 4:20:40 PM
732 (0x02DC)
The command completed successfully. TSBootShell
4/23/2015 4:20:40 PM 732 (0x02DC)
Successfully launched command shell. TSBootShell
4/23/2015 4:20:40 PM 732 (0x02DC)
Executing command line: X:\WINDOWS\system32\cmd.exe /k
TSBootShell 4/23/2015 4:20:41 PM
732 (0x02DC)
The command completed successfully. TSBootShell
4/23/2015 4:20:41 PM 732 (0x02DC)
Successfully launched command shell. TSBootShell
4/23/2015 4:20:41 PM 732 (0x02DC)
Executing command line: X:\WINDOWS\system32\cmd.exe /k
TSBootShell 4/23/2015 4:20:41 PM
732 (0x02DC)
The command completed successfully. TSBootShell
4/23/2015 4:20:41 PM 732 (0x02DC)
Successfully launched command shell. TSBootShell
4/23/2015 4:20:41 PM 732 (0x02DC)
The command completed successfully. TSBootShell
4/23/2015 4:20:43 PM 736 (0x02E0)
Starting DNS client service. TSBootShell
4/23/2015 4:20:43 PM 736 (0x02E0)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\
TSBootShell 4/23/2015 4:20:44 PM
736 (0x02E0)
The command completed successfully. TSBootShell
4/23/2015 4:20:44 PM 736 (0x02E0)
==============================[ TSMBootStrap.exe ]==============================
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
Current OS version is 6.2.9200.0 TSMBootstrap
4/23/2015 4:20:44 PM 1124 (0x0464)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
PXE Boot with Root = X:\ TSMBootstrap
4/23/2015 4:20:44 PM 1124 (0x0464)
Executing from PXE in WinPE TSMBootstrap
4/23/2015 4:20:44 PM 1124 (0x0464)
Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll
TSMBootstrap 4/23/2015 4:20:44 PM
1124 (0x0464)
TsPxe.dll loaded TSPxe
4/23/2015 4:20:44 PM 1124 (0x0464)
Device has PXE booted TSPxe
4/23/2015 4:20:44 PM 1124 (0x0464)
Variable Path: \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var
TSPxe 4/23/2015 4:20:44 PM
1124 (0x0464)
Succesfully added firewall rule for Tftp TSPxe
4/23/2015 4:20:44 PM 1124 (0x0464)
Executing: X:\sms\bin\i386\smstftp.exe -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
TSPxe 4/23/2015 4:20:44 PM
1124 (0x0464)
Command line for extension .exe is "%1" %*
TSPxe 4/23/2015 4:20:44 PM
1124 (0x0464)
Set command line: "X:\sms\bin\i386\smstftp.exe" -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
TSPxe 4/23/2015 4:20:44 PM
1124 (0x0464)
Executing command line: "X:\sms\bin\i386\smstftp.exe" -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
TSPxe 4/23/2015 4:20:44 PM
1124 (0x0464)
Process completed with exit code 1 TSPxe
4/23/2015 4:21:31 PM 1124 (0x0464)
Succesfully removed firewall rule for Tftp TSPxe
4/23/2015 4:21:31 PM 1124 (0x0464)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
Failed to download pxe variable file. Code(0x00000001)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
PxeGetPxeData failed with 0x80004005
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1459)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2667)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
Exiting with return code 0x80004005 TSPxe
4/23/2015 4:21:31 PM 1124 (0x0464)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)
TSPxe 4/23/2015 4:21:31 PM
1124 (0x0464)
Execution complete. TSBootShell
4/23/2015 4:21:31 PM 736 (0x02E0)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
GetTsRegValue() is unsuccessful. 0x80070002.
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
End program: TSBootShell
4/23/2015 4:21:31 PM 736 (0x02E0)
Finalizing logging from process 728 TSBootShell
4/23/2015 4:21:31 PM 736 (0x02E0)
Finalizing logs to root of first available drive
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)
LOGGING: Setting log directory to "D:\SMSTSLog".
TSBootShell 4/23/2015 4:21:31 PM
736 (0x02E0)

Press F8 in order to get a cmd window and see if the client got an IP address.
Torsten Meringer |
There's no IP Address when trying to the command prompt. It doesn't even show a MAC Address.

OSD Task Sequence fails with "There are no task sequences available for this computer"

Let me preface this by saying that I have read at least 100 forum posts with people having similar issues. However, none of the solutions in those
posts have worked for me.
The Problem: SCCM 2012 R2 will not image unknown computers.
The task sequence gives the error "There are no task sequences available for this computer." As soon as that error occurs, SCCM places an Unknown entry into the All Systems collection. I have been imaging unknown computers, without fail, for
4 months and no environmental changes have been made. NOTE: I am using USB media, not PXE.
What I've Tried:
Checked for duplicate SMSBIOS GUIDS in the console, none.
Checked for duplicate MAC Addresses in the console, none.
Checked for expired certificates, none.
Recreated Boot Media, twice.
Deleted the Unknown entry and retried, SCCM just recreates the Unknown entry.
Deleted all of my task sequence deployments, and then redeployed them each to All Systems (Only Boot Media and PXE) and to Unknown Systems (Only Boot Media and PXE)
I have also ran the following in the SQL Server Management Studio;
SELECT
* FROM
ResPolicyMap WHERE
machineid = 0 and
PADBID IN
(SELECT
PADBID FROM PolicyAssignment
WHERE BodyHash
IS NULL)
No result
Select
* From
vMacAddresses Where
MacAddresses = '00:00:00:00:00:00'
This displays an entry for every time that I have tried to image the unknown machine attached to the MAC Address with a different ItemKey and SMS_Unique_Identifier for each entry.
Added the machine manually using Import Computer Information, immediately recognized the Task Sequences that I have advertised to the All Systems collection.
Any and all assistance is welcome, I am going on the third straight day of dead ends. Below I have tried my best to post the entire SMSTS Log;

LOGGING: Finalize process ID set to 744
==============================[ TSBootShell.exe ]==============================
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Debug shell is enabled
Waiting for PNP initialization...
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM
WinPE boot path: C:\SOURCES\BOOT.WIM
Booted from removable device
Found config path C:\
Booting from removable media, not restoring bootloaders on hard drive
C:\WinPE does not exist.
C:\_SmsTsWinPE\WinPE does not exist.
Executing command line: wpeinit.exe -winpe
The command completed successfully.
Starting DNS client service.
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
The command completed successfully.
==============================[ TSMBootStrap.exe ]==============================
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'
Current OS version is 6.2.9200.0
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH
Failed to open PXE registry key. Not a PXE boot.
Media Root = C:\
WinPE boot type: 'Ramdisk:SourceIdentified'
Failed to find the source drive where WinPE was booted from
Executing from Media in WinPE
Verifying Media Layout.
MediaType = BootMedia
PasswordRequired = false
Found network adapter "Intel(R) Ethernet Connection I217-LM" with IP Address XXX.XX.XXX.XXX.
Running Wizard in Interactive mode
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Activating Welcome Page.
Loading bitmap
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Spawned thread 1008 to download policy.
Entering TSMediaWizardControl::GetPolicy.
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}
Setting LogMaxSize to 1000000
Setting LogMaxHistory to 1
Setting LogLevel to 0
Setting LogEnabled to 1
Setting LogDebug to 1
UEFI: false
Loading variables from the Task Sequencing Removable Media.
Loading Media Variables from "C:\sms\data\variables.dat"
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Setting SMSTSMP TS environment variable
Setting _SMSMediaGuid TS environment variable
Setting _SMSTSBootMediaPackageID TS environment variable
Setting _SMSTSBootMediaSourceVersion TS environment variable
Setting _SMSTSBrandingTitle TS environment variable
Setting _SMSTSCertSelection TS environment variable
Setting _SMSTSCertStoreName TS environment variable
Setting _SMSTSDiskLabel1 TS environment variable
Setting _SMSTSHTTPPort TS environment variable
Setting _SMSTSHTTPSPort TS environment variable
Setting _SMSTSIISSSLState TS environment variable
Setting _SMSTSMediaCreatedOnCAS TS environment variable
Setting _SMSTSMediaPFX TS environment variable
Setting _SMSTSMediaSetID TS environment variable
Setting _SMSTSMediaType TS environment variable
Setting _SMSTSPublicRootKey TS environment variable
Setting _SMSTSRootCACerts TS environment variable
Setting _SMSTSSiteCode TS environment variable
Setting _SMSTSSiteSigningCertificate TS environment variable
Setting _SMSTSStandAloneMedia TS environment variable
Setting _SMSTSSupportUnknownMachines TS environment variable
Setting _SMSTSTimezone TS environment variable
Setting _SMSTSUseFirstCert TS environment variable
Setting _SMSTSx64UnknownMachineGUID TS environment variable
Setting _SMSTSx86UnknownMachineGUID TS environment variable
Root CA Public Certs=
Missing root CA environment variable from variables file
Support Unknown Machines: 1
Custom hook from X:\\TSConfig.INI is
No hook is found to be executed before downloading policy
Authenticator from the environment is empty.
Need to create Authenticator Info using PFX
Initialized CStringStream object with string: 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A;2014-07-16T18:15:39Z.
Set media certificate in transport
Set authenticator in transport
CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXX.XXXXXX.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA
Request was successful.
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider
Default CSP Type is 24
New settings:
site=XXX,XXX, MP=http://XXXX.XXXX.com, ports: http=80,https=443
certificates are received from MP.
Unknown machine GUIDs: 774b17a2-6eeb-44bc-9c94-ce9081f5fe4c 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
MP specific X86 unknown machine GUID is received at run time
MP specific X64 unknown machine GUID is received at run time
Getting MP time information
Set authenticator in transport
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 406, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Current time: 2014-07-16 18:15:39.787 TZ:Pacific Standard Time Bias:0480
Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0
Adjusting the system time: -14400.551 seconds
Time zone info set to: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
New time: 2014-07-16 14:15:39.235
Current time: 2014-07-16 14:15:39.231 TZ: Bias:0300
Downloading policy from http://XXXX.XXXX.com.
Initializing HTTP transport.
Setting URL = http://XXXX.XXXX.com.
Setting Ports = 80,443.
Setting CRL = false.
Setting Server Certificates.
Set authenticator in transport
Setting Media Certificate.
Preparing Client Identity Request.
Setting transport.
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Setting site code = XXX.
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.
Setting SMBIOS GUID = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Adding MAC Address XX:XX:XX:XX:XX:XX.
Executing Client Identity Request.
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 415, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Client GUID = , Netbios name = , State = Known
Using unknown machine GUID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE
Hash computed from CSP: Microsoft Enhanced RSA and AES Cryptographic Provider, AlgID: 32772, HashSize: 20
Computed HardwareID=2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Hardware ID: 2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Preparing the Client DDR Message
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Sending the Client DDR message.
Sending Report
<Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:26717327-194f-4cd6-90ba-309998c058f2</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory
Data</ReportContent><ReportType>Full</ReportType><Date>20140716141539.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryAc
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
Submitted new client identity: GUID:26717327-194f-4cd6-90ba-309998c058f2
Preparing Policy Assignment Request.
Setting transport.
Setting site code = XXX.
Setting client ID = 74f16942-dd75-437f-8c4b-2a5de4d0e5e5.
Setting site signing Certificate.
Setting SiteSigningCertificateContext
Executing Policy Assignment Request.
Sending RequestAssignments
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 274, uncompressed size 662.
Request client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Response client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Retrieving Policy Assignments:
Successfully read 0 policy assignments.
Retrieving collection variable policy.
Found 0 collection variables.
Retrieving machine variable policy.
Found 0 machine variables.
Setting collection variables in the task sequencing environment.
Setting machine variables in the task sequencing environment.
Exiting TSMediaWizardControl::GetPolicy.
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.
Skipping Confirmation Page.
Skipping Task Sequence Selection Page.
Skipping Variables Selection Page.
Skipping Resolve Progress Page.
Activating Finish Page.
Loading bitmap
Executing command line: X:\windows\system32\cmd.exe /k
The command completed successfully.
Successfully launched command shell.

OSD Task sequence failing

Ive done a build and capture in Sccm and now im trying to test to do a test deploy however im getting these errors in smsts.log
http://i615.photobucket.com/albums/tt232/regan1985/wqewqewq.jpg
This is my task sequence
http://i615.photobucket.com/albums/tt232/regan1985/12356.jpg
Thanks in advance

Try to remove the "Apply Data Image 1" step from your TS.
The 1-1 partition is used for boot files and recovery info, and is created by default. The second (2-2)
partition is the one used for the Windows 7 installation.
Benoit Lecours | Blog: System Center Dudes

OSD task sequence fails when 2 or more network cables attached

I run SCCM 2012 R2, and am starting to build an image for Server 2012 R2
The server I'm testing has 2 network ports. If I connect only 1 network cable, the image process completes without issue. But I noticed when I cable both, and launch the build, it will fail before even starting with the following:
RequestMPLocation failed; 0x80004005
GetMPLocations failed; 0x80004005
QueryMPLocator: no valid MP locations are received
With both cables connected, I drop to a cmd prompt and ipconfig, both have valid IP addresses, are identified correctly, and I can ping the MP server and get to any other network locations.
The simple work around is to just plug in one cable to do server images, but we have servers delivered to remote sites that a 3rd party racks and cables, so to have them "just cable one", then the rest later (or get the network guy to disable ports
temporarily) so we can image it is kinda hokey.
Anyone seen this before? thanks in advance for any input
Tony

Those network cards are probably receiving ip addresses in different subnets. Could it be that you've configured boundaries, but didn't include one of these subnets/ranges?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Install Software Updates fails (timeouts) during OSD Task Sequence

Hi
As one of the lasts steps in our OSD Task Sequence we have an "Install Software Update" step where "Mandatory Software Updates" is choosen. It worked a week ago, but now the step fails with error code 0x800705B4
(This operation returned because the timeout period expired.)
When examining the WindowsUpdate.log I see an error followed by several minutes without log activity:
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:999
1632 4e4
COMAPI - Updates found = 260
2014-02-18 10:39:13:999
1632 4e4
COMAPI ---------
2014-02-18 10:39:13:999
1632 4e4
COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]
2014-02-18 10:39:13:999
1632 4e4
COMAPI -------------
2014-02-18 10:39:18:835
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 11:08:12:225
416 4dc
AU AU received policy change subscription event
2014-02-18 11:08:12:334
416 4dc
AU AU Options changed from policy.
2014-02-18 11:08:12:334
416 4dc
AU Successfully wrote event for AU health state:0
2014-02-18 11:08:12:334
416 4dc
AU ########### AU: Policy change processed ###########
When examining the WUAHadler.log - again there is no log activity during the Software Update step.
Its a WSUS Update Source type ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}), adding it.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Existing WUA Managed server was already set (http://<servername>:8530), skipping Group Policy registration.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Added Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Scan results will include all superseded updates.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching of updates using WUAgent started.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching completed. WUAHandler
18-02-2014 10:39:13 1108 (0x0454)
Successfully completed scan. WUAHandler
18-02-2014 10:39:15 2016 (0x07E0)
Removed Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 11:06:25
1160 (0x0488)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
for bundles WUAHandler
18-02-2014 11:09:25 2232 (0x08B8)
The Software Update Step started at 10:27 and the timeout came at 11:05.
Any ideas why the step times out? Or which logs I should look at?
Regards,
FC

PolicyEvaluator.log:
No errors. The last event is:
Received notification that Local policy has changed.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:11
1692 (0x069C)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095123.565000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 1768;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:23 1768 (0x06E8)
Forcing settings update for local policy change.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:23
2900 (0x0B54)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:33
2900 (0x0B54)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095144.641000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 2900;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:44 2900 (0x0B54)
UpdatesHandler.log:
No errors. A couple of lines:
Successfully initiated scan. UpdatesHandler
19-02-2014 10:54:10 1768 (0x06E8)
Updates scan completion received, result = 0x0.
UpdatesHandler 19-02-2014 10:55:23
3572 (0x0DF4)
UpdatesStore.log
No errors. Just quering updates, and the last line:
Querying update status completed successfully.
UpdatesStore 19-02-2014 10:56:27
3300 (0x0CE4)
In the smsts.log I found an interesting thing:
Successfully initiated RefreshUpdates operation
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
Waiting for RefreshUpdates complete notification from Updates Deployment Agent
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
Timedout waiting for updates refresh complete notification
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
It times out after exactly 30 minutes. Does 2012 have the same "feature" as 2007? (http://support.microsoft.com/kb/2009754/da)
Still the last event in windowsupdate.log is:
2014-02-19 10:55:37:251
324 dd0
Report CWERReporter finishing event handling. (00000000)
Regards,
FC

Service Pack for Proliant installing successfully but returning failure in OSD task sequence

Building bare metal servers with SCCM 2012 SP1 CU2 OSD and running into an issue with HPs where they attempt to install the Service Pack for Proliant 2013.02.0. I am using a package with a program. Here is the program command line:
Hpsum.exe /use_latest /allow_non_bundle_components /current_credential /silent
The application installs successfully but there is a distinct delay and then errors thrown that fails the TS. Setting 'continue on error' is a work around but not what I want to have in the production environment. How can I get around this issue?
This is the same exact package and program that ran perfectly fine in SCCM 2007, but we are seeing this as a new issue since the migration to SCCM 2012.
I'd like to solve this issue as well as get rid of the "Waiting for job status notification....InstallSoftware"
Any suggestions?
SMSTS.LOG
Invoking Execution Manager to install software InstallSoftware
12/3/2013 9:59:49 AM 1568 (0x0620)
Installing software for PackageID='WCD002D2' ProgramID='Silent install' AdvertID='WC120008' has started, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Waiting for installation job to complete.. InstallSoftware
12/3/2013 9:59:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:20 AM 1568 (0x0620)
Launching command shell. OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Windows station: WinSta0 OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Desk"Apple-tab-span" style="white-space:pre;"> OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
executing command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
executed command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:50 AM 1568 (0x0620)
CompleteExecution received InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
CompleteExecution processed InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
Received job completion notification from Execution Manager
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation completed with exit code 0x80070001
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation failed with error (0x80070001)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'=''
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
GetExecRequestMgrInterface successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Releasing job request, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Releasing of Job Request successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
CompleteJob successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
reference count 1 for the source D:\_SMSTaskSequence\Packages\WCD002D2 before releasing
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Released the resolved source D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
pInstall->Install(sPackageID, sProgramName), HRESULT=80070001 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Install Software failed, hr=0x80070001 InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Process completed with exit code 2147942401
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the action: HP Server Pack for ProLiant 2013.02.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
MP server http://MP_server.company.com. Ports 80,443. CRL=false.
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Setting authenticator TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set authenticator in transport TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Sending StatusMessage TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting message signatures. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting the authenticator. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
CLibSMSMessageWinHttpTransport::Send: URL: MP_server.company.com:80 CCM_POST /ccm_system/request
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Request was succesful. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionRetCode=-2147024895
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Clear local default environment TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Let the parent group (System Management Install) decides whether to continue execution
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
The execution of the group (System Management Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the last action: HP Server Pack for ProLiant 2013.02. Execution of task sequence failed.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)

Hello Guys!
HP ProLiant Support Pack / Service Pack uses different Exit Codes, due to that this software support other operating systems than Windows. Therefore HP has standardized to use other Exit Codes, which Windows Detect as failures.
HPSum Exit Codes:
ExitCode 1 = "Installation Successful"
ExitCode 2 = "Installation Successful, but a reboot is required"
ExitCode 3 = "Installation was canceled, or no components were updated"
EcitCode 9009 = "Installation did not complete. Check the path and make sure that the Installation exists at the specified location"
HP recommends to use following Batch File to workaround this issue for SCCM:
=======================START_BatchFile=============================
:Init
@Echo Off
Cls
:Main
Echo HP Proliant Service Pack Setup
Echo Source : %~dp0
Echo ===============================================================================
Echo Installing the HP Proliant Service Pack Setup
Echo Command: "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
"%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
:CheckForErrors
Echo HP Proliant Service Pack Stauts:
If "%errorlevel%"=="0" (
     Echo *******************************************************************************
Echo                            INSTALLATION FAILED!
Echo *******************************************************************************
exit 1
If "%errorlevel%"=="1" (
     Echo Installation Successful!
     exit 0
If "%errorlevel%"=="2" (
     Echo Installation Successful, but a reboot is required.
     exit 3010
If "%errorlevel%"=="3" (
     Echo Installation was canceled, or no components were updated
     exit 0
If "%errorlevel%"=="9009" (
     Echo Installation did not complete. Check the path and make sure that the
Echo Installation exists at the specified location:
Echo Path: %~dp0
Exit 1
:End
Echo An unknown status code was returned from the PSP.
Echo This status code is [%errorlevel%]. This will be treated as a success,
Echo but please check the installation to make sure it completedly properly!
Exit 0
=======================STOP_BatchFile=============================
God Luck!
Best Regards Anders Horgen

UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhet

your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Non-Deployed Applications in OSD Task Sequence Are Deployed To Collection Members where OSD TS is deployed

Hello,
I have a situation where an application (which is not deployed) that is part of an OSD Task Sequence is being deployed to computers that are in the same collection my TS for OSD is deployed.
For OSD I have created an application to check the BIOS version and upgrade the BIOS if there is a newer one available. The application has numerous deployment types (13) due to various hardware models and the requirement to go to several intermediary BIOS
versions to reach the current newest version. There are dependencies configured to handle these incremental bumps.
The OSD TS is deployed to a collection that contains all windows desktop class operating systems. What I have seen happen once is that one users workstation somehow discovered and installed the BIOS Upgrade package and their BIOS was upgraded on their workstation.
I've checked the logs on several other machines and this same application has been run as well.
The application is configured "Allow this application to be installed from the Install Applications
task sequence action without being deployed" which allows it to be ran from a TS even though it is not deployed.
I have verified the application is not deployed. I have verified there are no superceedence rules configured. As I stated, there are dependencies, but all dependencies are within this one application.
What I do not understand is, how can an application that is not
deployed and is only referenced in an Operating System Deployment Task Sequence able to be ran outside the task sequence?
This is/has occurred with computers imaged with cm2012 and with computers imaged with cm2007 who have now been migrated to cm2012.
I'm fairly sure that it is due to the task sequence and where it is advertised. Computers that are not in this collection do not show the application being applied in the AppEnforce.log. If it is the TS that is causing this, how can something that is designed
to be a "sequence of tasks", allow something to occur out of that sequence?
Current environment is CM2012R2.
Any thoughts to what might be happening?
Thanks

Hello,
After working with Microsoft Support, we were able to resolve the issue.
Turns out there was something (old policies) "stuck" in the SCCM database that was causing this to be advertised outside the task sequence and not visible on the console. While they didn't call this "a bug" since it has happens with CM2007 as well, it definitely
was not normal behavior. Still not sure how that could happen as I'm 99.99% sure I never deployed this to any collection, but that's what they said.
It took several hours of support rooting through the database to figure out what was going on but after some SQL magic it was fixed. Sorry I don't have more specifics regarding the fix. MS basically said "If it happens again you can do this this and this
in the db and voila its fixed". Since I'm likely to cause more damage (messing with the database) then good if it were to happen again I'd contact them.
Anyway, this odd behavior has spooked me and I've reverted back to deploying the TS to the unknown computer collection. As much as it disappoints me to take a step back and cause more work for the guys doing the imaging, the extra safety this grants (if
something like this or worse were to happen) I think is better than an OSD task sequence gone wild.
Thanks,
Mark

Nvidia (Quadro K2000) Driver isn't installed during OSD (Task Sequence succeeded) - HP Z620

Hi everyone,
I have added a driverset (HP Z620) in SCCM for the first time using our internal procedure (Importing Drivers to SCCM, Create Driver package with specific category, apply driver package in TS using WMI to query for the model).
The Task Sequence succeeded, but the NVIDIA K2000 Graphics driver isn't installed (only HD Graphics 4000 driver).
Looking at the drivers in the Driver Package, this should normally apply since the driver is compatible with this specific GPU.
At the forums, I can see that some people have created a seperate package for the GPU driver installation using command line switches.. But looking at the environment at the customer, we have never done this and in the past, we have succesfully installed
the driver for this GPU before.
PS: The driver for the GPU in my new driver package (HP Z620) isn't the same as for previous models (HP Z220, Z230, Z600).
Could you please advise me what to do? Should I have added something in the driver sources before importing the driver to SCCM?
Thanks in advance!
Kind regards

Hi
I m installing Nvidia (Quadro K2000) Driver during OSD (Task Sequence succeeded) - HP Z420
Remove the Graphics driver for NVIDIA from the current driver database
Added below task in the existing task sequence as invidual installation based on the Condition (WMI query)
Command Line
HP_Z420_Graphics_x64\Win64_332_50\setup.exe -s -k -clean -noeula
This will install the desired driver and related configurable components
WMI Query
select * from win32_ComputerSystem where manufacturer like '%hewlett%' and model like '%z420%'
Currently I m looking out for the Errors codes needed to add to this task . Success codes 3010 and 0 already added

Creative Cloud: "Build" MSI Hangs During SCCM OSD Task Sequence Installation

I wanted to share problem and solution I found when deploying Creative Cloud Packager-created packages/application using SCCM 2012 R2. I encountered this problem packaging this as both a Package and as an Application in SCCM.
When installing the software through SCCM Software Center onto a client, Software Center would close right as the installation of the "Build" folder MSI completed. This is abnormal behavior.
When installing the application as part of an OSD Task Sequence, the software would get installed (as shown by logs) but SCCM would hang forever at the "Installing Application" step.
I tried all sorts of different settings in SCCM and with the MSIEXEC command line and eventually traced it to the Reboot Manager functionality in MSIEXEC that will close and attempt to restart processes using files that the installer needs. Reboot Manager clobbered part of SCCM and in the Task Sequence, the connection between SCCM and the installer was broken.
The solution is to pass the property "MSIRESTARTMANAGERCONTROL=Disable" along the command line when calling MSIEXEC on the Build folder MSI file. This setting disabled Restart Manager so it didn't mess up SCCM. Once I did this, my Software Center installs and OSD Task Sequences ran as intended.
For reference, I used the REBOOT=ReallySuppress property for reboots and let SCCM determine what to do with reboots based on the return code. My testing was done with Windows 8.1 Enterprise x64.

Like said, did you configure my proposal: "Configuration Manager client will force a mandatory device
restart" ? After you've configured that, update your deployment type manually and remove the old revisions of the application and try running the TS again. I'm guessing you're a little bit too fast on your doings so the ConfigMgr doesn't play a long very
nicely...
The TS stops because of your Hard Reboot (exit code 1641), I've seen this before and I configured my application so that ConfigMgr client will force device restart and that fixed my problem. Although, also my application is the last one in the TS, but still,
the TS continues after the reboot.
Btw. have you tried changing your command line to:
msiexec.exe /i cd-ord.msi TRANSFORMS=sv-se.mst MVLICENSE_KEY=xxxxxxxxxxxxxxxxx /L*V "%temp%\cdord.log" /qn
/norestart

OSD task sequence fails to install application on workgroup computers

Similar Messages

Maybe you are looking for