I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE

Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)

Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)

More detailed smsts.log below:

During the reimaging of computers and after SCCM agent installation task, the SCCM object in the console appears with a new ResourceID and SCCM agent ID, but most other attributes (DDR time, primary users, HW/SW inventory) seem to be getting merged from the old object (before it was reimaged). Are there any settings in SCCM to block that from happening? One way we can get around this is by deleting the computer object in AD prior to reimaging (or of course deleting the SCCM object) but I was wondering if there are any settings that control that.

Hi,

We are experiencing a really strange problem with our OSD which is hard to pin down. Our setup is SCCM 2012 R2 with 4 PXE enabled DP's (VMWare VMs) across 2 data centers and on seperate hosts and we are delivering Windows 7 (32 and 64) with recaptured WIM files. Ouor deployments work fine for around a week and then they suddenly start experiencing a reboot look and blue screening at the first boot into the full OS.

This occurs on multiple different physical machines and we inject driver packages for different builds with WMI filters on motherboard as is common. The really weird part is that this will work for days then stop working. The only workaround we have is to recapture the WIM file (we have a build and capture task sequence for this) and then it works again, even though the content and drivers are exactly the same from the same B+C task sequence. Even the windows updates are the same with no new ones. It doesn't seem to be the drivers themselves but rather the process of DISM injecting them offline in windows PE which appears to break the registry. The last thing we see before blue screen is "Updating registry" in windows 7 boot.

These are the things we have tried are...

 - Recapturing the WIM (works for around a week but not a fixed period)
 - Host the WIM on a physical DP (to rule out VMWare) with only the WIM and a single driver package. Again this worked fine for a week or so.
 - Built several different physical machines. All fine but when this stops, it stops for all of them
 - If we remove all drivers but the LAN driver it can work but our testing has ruled out a specific bad driver as we have used different models of machine and if it was, then it would never work.
 - We have set the TFTP block size to default of 1024 (we had it higher as 8192) to rule out the boot image being corrupted on download. It made no difference other than being a lot slower.
 - Compared MD5 hashes for the WIM to rule out corruption.
 - Removed and redistributed the WIM and drivers to different DP's (that it had never been on before)

The DISM.log on a failed device shows entries like

 CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]

Any advice would be greatly appreciated. This question on Dell's forum sounds very similar.

What we are really struggling with is why would the same WIM, with the same driver package, from the same distribution point, to the same physical machine, work every day for a week the permanently break? Aaargh!

Thanks everyone,

Shaun

Hey all, I've got a brand new SCCM 2012 installation and I can't get it working.  I installed a long list of pre-reqs, did the install, and created a new task sequence media job to capture a system's image.  I updated my DHCP scope settings and turned off my old WDS server.  Now I get a timeout when the system tries to PXE boot, at the TFTP stage.

So I downloaded a TFTP client and, sure enough, I can't connect to my distribution point (which is also my sccm server (stand-alone install)), over ftp.  I presume that's the problem, but googling how to enable tftp on SCCM has gotten me no-where.  

Can you smart people help?

Thanks,

Joe

I want to use thin image to deploy win7.

So do I need to built a reference Image, or I can use install.wim from Windows 7 media directly?

I saw someone suggest built a reference Image fist. so what different between  builting a reference Image or using install.wim from Win7 media?

http://1drv.ms/1jWJ5a3

Problem with capturing image. Logs included.

Also after deploying letters are swapped. System is on D drive, and data on C drive.

Any idea ?

I have all my client machines to look for Windows update automatically from the internet. After I configured my SCCM 2012 to have EndPoint 2012 Protection and all clients to sync to the SCCM server for new definitions. Now all client machines are checking for Windows updates on my SCCM server as well.

1. How can I have my client machines to still check for Windows update from the internet WHILE synching AV definition from SCCM server?

THANK YOU FOR ANY HELP.

Hello,

When using the "Create Task Sequence Wizard" no images are displayed to be select an Image Package on the "Install Operating System" page. Is there a work around or hotfix?

Skydrive link to image: sdrv dot ms/13hZgIo

System: Win 2012 & SQL 2012

SCCM 2012 SP1 and CU1

Thank you.

From my main SCCM R2 server, I went to add an additional server with multiple roles. 

I can't tell if it's working properly, however. 

For example, the Distribution Point role. I've set it as PXE boot, and our Cisco admin has setup an IP helper accordingly, but when I go to boot a client to PXE, it gets an error "Windows failed to start". 

File: \Tmp\x86x64{13902C6F-DD5F-4467-88C9-1BAC44DF8287}.bcd

status: 0xc0000098

Info: The windows boot configuration data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. 

From Boot Images on the main SCCM server, I had pushed them to the distribution point. Or so I thought? I mean, the "In Progress" tab says the distribution point server name I'm trying to push it to under the "Device" column. Then Description reads "Distribution Manager Successfully processed package "Boot Image (x64)" (package ID = STL00005)". 

But it's been sitting like that for over an hour...

WDS role is also installed on the DP I'm trying to PXE boot from. 
Should I disable WDS and then what do I do in SCCM to get it to PXE boot and make sure the boot file for SCCM is on there? 

I'm able to deploy an OS perfectly with OSD task sequences with the image I'm using.  However when I attempt to inject the updates using the "Schedule Updates" method, I get the following error.  Failed to mount the image on the system.

I opened SCCM console from the primary site itself just in case, I also retried with elevating permissions on the console.

OfflineServicingMgr.log

from within your task sequence, after the OS has been installed how can you turn off your firewall?  I've noticed that when I lay down our generic Windows 7 OS via a TS the firewall is on and we want them off.

Problem appeared immediately after upgrading from SCCM 2012 SP1 -> R2. There are also a few other posts about this, but their proposed solutions don't appear to solve the problem.

Problem: Some applications do not install successfully via OSD Task Sequence. However, it does not appear to be specific to any one application. If i rearrange the applications, a different Install Application task will fail.

I'm confident this is not a boundary group issue, as other applications deployed in the OSD task sequence are succeeding, and are deployed/distributed in an identical manner. 

Interesting entries from SMSTS.log ...

<![LOG[Installing application 'AppSense Client Communications Agent 8 FR5 32bit']LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="1" thread file="installapplication.cpp:863"><![LOG[MP list missing in WMI, sending message to location service to retrieve MP list and retrying.]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="2" thread file="installapplication.cpp:1051"><![LOG[Waiting for installation job to complete..]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="1" thread file="installapplication.cpp:1179"><![LOG[Execution status received: 24 (Application download failed )]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="1" thread file="installapplication.cpp:1316"><![LOG[App install failed.]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="3" thread file="installapplication.cpp:1396"><![LOG[Install application action failed: 'AppSense Client Communications Agent 8 FR5 32bit'. Error Code 0x80004005]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="3" thread file="installapplication.cpp:879"><![LOG[Install application action cannot continue. ContinueOnErrorFlag is set to false.]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="3" thread file="installapplication.cpp:898"><![LOG[hrInstallation, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,899)]LOG]!><time date="03-25-2014" component="InstallApplication" context="" type="0" thread file="installapplication.cpp:899">

No unique errors/failures noted in CAS.log, CIDownloader.log, ContentTransferManager.log or DataTransferService.log. 

What IS interesting is on a box that has failed, the client doesn't ever grab any policies from the server. On a system that works, I can see in \\dts-lab-ws05\c$\Windows\ccmsetup\Logs\ccmsetup.log that after the client is installed in the task sequence, if the machine is 'working' i'll see additional entries in ccmsetup.log indicating that ccmsetup.exe has been run again. Here is my example...

<![LOG[Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Deleted file C:\WINDOWS\ccmsetup\vcredist_x86.exe.download]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Deleted file C:\WINDOWS\ccmsetup\Silverlight.exe.download]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Deleted file C:\WINDOWS\ccmsetup\SCEPInstall.exe.download]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Deleted file C:\WINDOWS\ccmsetup\client.msi.download]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Deleted file C:\WINDOWS\ccmsetup\configmgr2012ac-r2-kb2910552-i386.msp.download]LOG]!><time="16:15:56.925+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:9493"><![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="16:15:56.940+420" date="03-25-2014" component="ccmsetup" context="" type="0" thread="2100" file="wintask.cpp:634"><![LOG[CcmSetup is exiting with return code 0]LOG]!><time="16:15:56.940+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="2100" file="ccmsetup.cpp:10875">
<![LOG[==========[ ccmsetup started in process 2668 ]==========]LOG]!><time="17:00:25.734+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="ccmsetup.cpp:9437"><![LOG[Running on platform X86]LOG]!><time="17:00:25.734+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="util.cpp:1837"><![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="17:00:25.734+420" date="03-25-2014" component="ccmsetup" context="" type="0" thread="3428" file="ccmsetup.cpp:9281"><![LOG[Launch from folder C:\Windows\ccmcache\2i\]LOG]!><time="17:00:25.734+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="ccmsetup.cpp:721"><![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="17:00:25.734+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="ccmsetup.cpp:727"><![LOG[Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18]LOG]!><time="17:00:25.812+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="util.cpp:1919"><![LOG[Ccmsetup command line: "C:\Windows\ccmcache\2i\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:6]LOG]!><time="17:00:25.812+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="ccmsetup.cpp:3590"><![LOG[Loaded command line: "C:\Windows\ccmcache\2i\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:6]LOG]!><time="17:00:25.812+420" date="03-25-2014" component="ccmsetup" context="" type="1" thread="3428" file="ccmsetup.cpp:3767"><![LOG[SslState value: 224]LOG]!><time="17:00:25.812+420" date="03-25-2014" component="ccmsetup" context="" type="0" thread="3428" file="ccmsetup.cpp:4425"><![LOG[Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=PEN))']LOG]!><time="17:00:25.843+420" date="03-25-2014" component="ccmsetup" context="" type="0" thread="3428" file="lsad.cpp:656"><![LOG[OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert> yes i removed the cert </SiteSigningCert></SecurityConfiguration><RootSiteCode>SWP</RootSiteCode><CCM> <CommandLine>SMSSITECODE=AUTO FSP=CMPRI-00-0</CommandLine> </CCM><FSP> <FSPServer>CMPRI-00-0.domain.tld</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="domain.tld" /><Forest Value="domain.tld" /></ClientOperationalSettings>']LOG]!><time="17:00:26.030+420" date="03-25-2014" component="ccmsetup" context="" type="0" thread="3428" file="lsadcache.cpp:236">

But on a machine where the client is installed and the task sequence has failed, it never does this, nor does it download any of the client policies.

My deployments were dead slow, so as per THIS I've installed KB2910552. The problem I'm reporting was there before and after applying the KB, but it sure did speed up my deployments.

Then I found this gem in KB2854009 for SP1 CU2.

• A task sequence that has multiple "Install Application" steps may fail. For more information, click the following article number to go to the article in the Microsoft Knowledge Base:2837395 The "Install Application" task sequence fails in System Center 2012 Configuration Manager SP1

Too bad it applies to SP1. It would be nice to know if it was rolled into R2.

So, does anyone else have a similar problem or an idea of where I should look?

Thanks,

I want to use auto apply drivers. So I just import drivers to "Drivers", but I don't create any driver package. Then I want to update drivers to DP, but I don't know how to do

According to the above method, can I auto apply drivers?   or I need to create driver package(even I don't want to apply driver package), and then update driver package to DP?

I have a SCCM 2012 SP1 CU4 environment and I updated my Windows 7 Enterprise x64 image install.wim with all security patches using Offline Servicing..a nice feature...works perfectly.

But when using this new updated image in my Task Sequence I noticed that still 150+ patches are installed during the Install Updates phase in my task sequence. More then 130 of them are already added using Offline Servicing so why are they added again ???

What is going wrong here....what am i missing....

Due to different country, the same series of computers have different model (over 30), but the drivers are same.

I want to apply driver package;

SELECT * FROM Win32_ComputerSystem WHERE Model ="ABC" OR Model="DEF" OR Model="GHI"    is work

SELECT * FROM Win32_ComputerSystem WHERE Model IN ('ABC','DEF','GHI')       is failure

I think SQL IN is more clear, why doesn't it work?

Dr. Chuck

Jan Hoedt

At one site builds seems to regularly fail to install some/all of the applications. A reboot of the site's DP/MP seems to help

smsts.log

NotifyProgress received: 16 (Application failed to evaluate ) InstallApplication 31/03/2014 11:19:51 3488 (0x0DA0)
GetAppMgmtSDKInterface successful InstallApplication 31/03/2014 11:19:51 3488 (0x0DA0)
CAppMgmtSDK::GetEvaluationState ScopeId_8CE4CACC-8D03-4A83-9457-17F578AB3E0A/RequiredApplication_fab9df5e-5f3b-45e8-843c-a4ad95db57c1 DCMAgent 31/03/2014 11:19:51 3488 (0x0DA0)
Passed in version 12 for ScopeId_8CE4CACC-8D03-4A83-9457-17F578AB3E0A/RequiredApplication_fab9df5e-5f3b-45e8-843c-a4ad95db57c1 DCMAgent 31/03/2014 11:19:51 3488 (0x0DA0)
spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState, 1), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2088) DCMAgent 31/03/2014 11:19:51 3488 (0x0DA0)
CAppMgmtSDK::GetEvaluationState - ScopeId_8CE4CACC-8D03-4A83-9457-17F578AB3E0A/RequiredApplication_fab9df5e-5f3b-45e8-843c-a4ad95db57c1.12 Not found in CI state store. Marking CIs state as EvaluationFailed DCMAgent 31/03/2014 11:19:51 3488 (0x0DA0)
Waiting for job status notification... InstallApplication 31/03/2014 11:24:51 3456 (0x0D80)
Retrying: 1 attempt InstallApplication 31/03/2014 11:24:51 3456 (0x0D80)
Waiting for job status notification... InstallApplication 31/03/2014 11:29:51 3456 (0x0D80)
Retrying: 2 attempt InstallApplication 31/03/2014 11:29:51 3456 (0x0D80)
Waiting for job status notification... InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
Retrying: 3 attempt InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
nRetryVal != 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1170) InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
Exhausted retry attempts. Giving up.  InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
WaitforJobCompletion(spAppMgmtSDK, m_guidPolicyEvalJobID, ulPolicyEvalTimeout, nPolicyEvalRetryAttempts), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,992) InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
Step 2 out of 4 complete InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)
Install application action failed: 'Adobe Reader XI'. Error Code 0x80004005 InstallApplication 31/03/2014 11:34:51 3456 (0x0D80)

The build works perfectly at the site I'm at every time. I don't know whether its a DNS issue or failing to resolve the MP correctly ?. There are three sites/Domains with no trust relationship between them. I don't see any further information in appenforce.log - would I expect to when part of Task Sequence ?

Ian Burnell, London (UK)

So this seems to have existed since we first started using SCCM 2012 i think, initially SP1, then upgraded to R2 with same.

Devices of any type, once the OSD TS has completed, the full HW inventory does not run.  I haven't had a chance to fully test for how long yet, but certainly today's test shows a machine that has been on (not in standby at any point) for 15 hours, and still no HW inventory (blank in Resource Explorer).

Checking the InventoryAgent.log shows that only 17 items have been processed at the point of client install/policy processing.  Here is the end of that log:

Collection: 17/18 inventory data items successfully inventoried.	InventoryAgent	31/03/2014 14:23:03	212 (0x00D4)
Inventory: Collection Task completed in 2.106 seconds	InventoryAgent	31/03/2014 14:23:03	212 (0x00D4)
Inventory: 1 Collection Task(s) failed.	InventoryAgent	31/03/2014 14:23:03	212 (0x00D4)
Inventory: Temp report = C:\WINDOWS\CCM\Inventory\Temp\108cd8b0-9945-4fc3-b2c9-8065d523858f.xml	InventoryAgent	31/03/2014 14:23:03	212 (0x00D4)
Inventory: Starting reporting task.	InventoryAgent	31/03/2014 14:23:03	4780 (0x12AC)
Reporting: 18 report entries created.	InventoryAgent	31/03/2014 14:23:04	4780 (0x12AC)
Inventory: Reporting Task completed in 0.951 seconds	InventoryAgent	31/03/2014 14:23:04	4780 (0x12AC)
Failed to load logging configuration for 'CcmExec' (87d00275)	InventoryAgent	31/03/2014 14:23:05	4780 (0x12AC)
Inventory: Successfully sent report. Destination:mp:MP_DdrEndpoint, ID: {C71920AC-7530-4E48-817E-A3C2A4981C21}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted	InventoryAgent	31/03/2014 14:23:05	4780 (0x12AC)
Inventory: Cycle completed in 5.475 seconds	InventoryAgent	31/03/2014 14:23:05	4780 (0x12AC)
Inventory: Action completed.	InventoryAgent	31/03/2014 14:23:05	4780 (0x12AC)
Inventory: ************************ End of message processing. ************************	InventoryAgent	31/03/2014 14:23:05	4780 (0x12AC)

Is this a fault with SCCM?  Has anyone else experienced the same behaviour?  I have created a FinaltTasks.bat that is used via SMSTSPostActionvariable, which should trigger a full HW scan, but this doesnt seem to be run after the TS has finished for some reason, so that workaround is not working.

If I manually trigger a full HW scan (either using the above script or via control panel applet) it runs immediately, with not issues.

Can anyone help here?

Thanks.

Windows 7 64bit task sequence with HP 6570b.

SCCM 2012 Sp1

They hang just after the sccm client installation.
I verified we have the AD group ConfigMgr Remote Control Users

Our 32bit image seems to work fine.

From the smstslog

Waiting for CcmExec service to be fully operational TSManager 1/17/2013 3:36:50 PM 2988 (0x0BAC)
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)
Failed to create an instance of COM progress UI object. Error code 0x80070015 TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)