Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, May 29, 2012 7:15 AM
We have a task sequence that fails to install software and updates with an error liek this: Operation System Error 615: The password you provided was too short for the computers password policy. Please provide a longer password.
With all software installations I always tick the continue on failure. Consequently in a task sequence you see the entire list of installation requirements fail with this error. This includes Applications, Packages and Software Updates. Without any amendment, the next time it is run, it runs successfully. Add to this the issue that the task sequence no longer displays the progress bar after rebooting into windows (x64) and it all points to the OSD process being a bit flaky.
By the way, we are installing Win7 x64 (No x86 anymore) over PXE.
So any pointers with this would be very gratefully received.
Anthony Sheehy - MCP, MCITP
All replies (31)
Tuesday, June 12, 2012 9:54 AM ✅Answered
This stopped happening after we used a newly captured image captured with the same MDT package.
Anthony Sheehy - MCP, MCITP
Tuesday, May 29, 2012 8:55 AM
can you post the exact failure message from your SMSTS.log file or even better, post that log file somewhere we can examine
Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
Tuesday, May 29, 2012 1:30 PM
In addition to providing the smsts.log, is this an OSD task Sequence?
Have you reviewed group policy to examine the password policy?
Are granular policies in place in group policy that may be somehow getting in the way?
Have you reviewed the Windows Event logs on the system to see if there are any other Windows related error messages?
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Tuesday, May 29, 2012 6:31 PM
Here is the status message sent to Configuration Manager:
The task sequence execution engine failed executing the action (Freefall Sensor) in the group (Install) with the error code 2278559764
Action output: 7"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)
0, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)
Entering ReleaseSource() for C:\SMSTaskSequence\Packages\WGS00137
reference count 1 for the source C:\SMSTaskSequence\Packages\WGS00137 before releasing
Delete source directory C:\SMSTaskSequence\Packages\WGS00137
Released the resolved source C:\SMSTaskSequence\Packages\WGS00137
pInstall->Install(sPackageID, sProgramName), HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Failed to invoke Execution Manager to Install Software for PackageID='WGS00137' ProgramID='Silent Installation' AdvertID='WES20013' hr=0x87d01014
InstallSoftware failed, hr=0x87d01014
Install Software failed, hr=0x87d01014. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
And here's the group policy that is applied to that OU:
Enforce password history |
0 passwords remembered |
Maximum password age |
0 days |
Minimum password age |
0 days |
Minimum password length |
0 characters |
Password must meet complexity requirements |
Disabled |
Of course, the password complexity issue is a non-starter: How come SCCM 2007 task sequences did not have the same problem? Why does the Task Sequence work sometimes and not others. All passwords I provide to Configuration Manager all conform to complexity rules anyway.
The relevant SMSTS.log portion is below:
<![LOG[Variable name: _SMSSWDProgramName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsswd.exe /pkg:WGS00137 /install /basevar: /continueOnError:]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 90]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Applications]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_382fdd99-2228-452d-a6f0-63e543ce628d /basevar: /continueOnError:True]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 91]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Language Packs]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_9df3ec9a-e691-4106-b274-46c4c6c319b9,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_42e28566-b339-4773-92cf-05b8e748d996,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_305b4a34-0b5a-46fe-82dd-c57a5897e063,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_379afca3-f48e-486b-8848-296223481edd,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_502bf2db-e1c8-42ac-a499-61320d661cc3,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_455a6de9-fe98-47ed-8dab-e860dd4681ed,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_1707c97e-b4bb-4827-9117-02e79435213e,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_a17f2337-ad2e-42cb-9813-c9e167a85050 /basevar: /continueOnError:True]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 92]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[Processed all elements]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:333">
<![LOG[Adding end group instruction at 93]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:402">
<![LOG[The next instruction after group will be at 94]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:408">
<![LOG[
Parsing step node: Opt In to CEIP and WER]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
Anthony Sheehy - MCP, MCITP
Tuesday, May 29, 2012 6:41 PM
I'd suggest putting another system with an OS already installed and run a GPRESULT /V to see what policies are really being enforced. Password policies are generally only applied at the domain level.
Tuesday, May 29, 2012 7:00 PM
Same questions: What makes that different from 2007 task sequences? All passwords provided to configuration manager meet password complexity anyway?
Anthony Sheehy - MCP, MCITP
Tuesday, May 29, 2012 7:37 PM
Have you reviewed the Windows Event logs for any corresponding events?
Does this only happen for this single application installation?
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Wednesday, May 30, 2012 7:43 AM
A: Good point, will double check that when I get in first thing tomorrow
B: It happens with all application installations, all package installations, and with the 'Install Updates' task item. It didn't happen when I ran a command line using a package as the source. Everything else runs, including setting Bitlocker, without complaining at all.
Anthony Sheehy - MCP, MCITP
Thursday, May 31, 2012 8:55 AM
I've reviewed the Windows event logs and there is nothing (no really - absolutely nothing) that relates to these failures. It is as if they were never executed in the first place.
Anthony Sheehy - MCP, MCITP
Wednesday, June 6, 2012 2:42 PM
Managed to grab the SMSTS logs before they were moved and compressed. This is the sum of it:
<![LOG[Received job completion notification from DCM Agent]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="1" thread="2848" file="installapplication.cpp:1166">
<![LOG[GetAppMgmtSDKInterface successful]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="0" thread="2848" file="installapplication.cpp:160">
<![LOG[Policy Evaluation failed, hr=0x87d00267]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="3" thread="2848" file="installapplication.cpp:1187">
<![LOG[Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2'='']LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="1" thread="2848" file="installapplication.cpp:63">
<![LOG[EvaluationJob complete]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="1" thread="2848" file="installapplication.cpp:1206">
<![LOG[m_hResult, HRESULT=87d00267 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,993)]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="0" thread="2848" file="installapplication.cpp:993">
<![LOG[Step 2 out of 3 complete]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="0" thread="2848" file="daprogress.cpp:226">
<![LOG[Install application action failed: '.Net redistributable'. Error Code 0x87d00267]LOG]!><time="14:51:54.877-60" date="06-06-2012" component="InstallApplication" context="" type="3" thread="2848" file="installapplication.cpp:788">
Anthony Sheehy - MCP, MCITP
Tuesday, June 12, 2012 8:12 PM | 1 vote
Sounds like something was embedded in the image? Areyou joining your reference system to the domain? If so, bad joo-joos there.
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Wednesday, June 13, 2012 8:29 AM
No Jason, I've read the fandangled manual. All reference PCs are non-domain, password free, etc, etc. I've also seen other issues resolved by taking a new reference image with the new MDT, so I can't explain it, as I don't have all the facts, I just know that new image = problem solved... The old image worked fine in 2007.
Anthony Sheehy - MCP, MCITP
Wednesday, June 13, 2012 2:16 PM
Just trying to see what would've caused this as I've never specifically seen it happen before but it may help someone in the future.
So, this was the same image you used in 2007?
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Friday, June 15, 2012 7:32 AM
Correct. This was the image we used in SCCM 2007 using MDT 2010. It worked fine then. The image was migrated across during the initial migration process.
Anthony Sheehy - MCP, MCITP
Sunday, June 17, 2012 1:10 AM
Sounds like an account/password combination was embedded somewhere in your original image that does not conform to your new policies.
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Thursday, December 6, 2012 2:09 PM
Wow, I came up with this problem after I did offline servicing to my .wim image file. Not all, but some of applications fails with this error. I hadn´t this problem before and there wasn´t any change to any passwords or policies.
Wednesday, January 9, 2013 12:21 AM
After doing 2 things, this issue was fixed for me:
- Updated 'Apply Windows Settings' TS step with a password for the local admin account (previously this was blank)
- Did 'Update Content' on the application deployment type that was failing
My Microsoft Core Infrastructure & Systems Management blog - blog.danovich.com.au
Wednesday, January 9, 2013 7:34 AM
We've been using complex passwords in that field since SCCM 2007. Nice thought though.
Anthony Sheehy - MCP, MCITP
Friday, February 22, 2013 11:29 PM
Have any luck identifying a root cause? I had this problem show up today. yesterday the OSD ran just fine. Using an older image I captured last week. WE made some changes to our captured image, and so we captured new images. And the problem showed up with all the apps. I've got all my apps deploying via the same Install Apps step in the TS (6 apps are included in that step things like flash. shockwave, etc). All 6 apps fail just like yours. The TS runs that step, you can see it install the apps when it runs, though they are quick. Nothing in event viewer.
Packages are installing just peachy keen thank you.
So, I thought it was my image. I changed my TS back to using the old image, and voila, it doesn't work on THAT image anymore. SOMETHING changed in the last 24-36 hours.. but I've got no idea what. Any ideas would be welcome. :)
Wednesday, May 15, 2013 11:49 AM
Hi guys,
Even I faced similar issue after migrating packages and TS from SCCM 2007 to SCCM 2012.
1.Symantec install fails on Windows 2003. See the error below.
The task sequence failed to install application Symantec Endpoint Protection 11 Server x86(ScopeId_8C926A80-576F-466A-826B-XXXXXE1442D5941BE/Application_c55063ca-XXXX8aa4-447b-a46c-bf5869a8c4fe) for action in the group () with exit code 615. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
In the above given example the issue was resolved. I think after the packages are migrated, SCCM stores user id and blank\some password internally somewhere. This happend for only few applcations.
I did the following to solve this:
Under Software Library, Go to Application Management -> Applications -> <Your application >.
Select Deployment types tab, right click the Install program and click on Update Content. This solved the issue. Strange :)
Thursday, August 29, 2013 12:27 PM
Same issue here. No guaranteed solution yet.
- SCCM 2012 SP1.
- Deploying W7 x64.
- Complex password set during TS.
- DP's updated.
- Occurs with different captured images.
- Sometimes 1 application fails with error 615 on some machines.
- As far as I know it never occured on the capture TS.
Thursday, November 21, 2013 12:18 PM
Does anyone have more success with this issue atm?
We also have the same problem: The task sequence execution engine failed to install application <Name and id of app> that was specified through TS variable for action (Install Application) in the group () with exit code 16389. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
Very random failures on different task sequences. Now testing with updating the content of the different deployment types. A lot of OSD are installing the application succesfully though.
We are running SCCM SP1 with cu2. MDT Task Sequences. The CU2 patch is installed with ConfigMgr Client with the PATCH parameter. New reference image is being used for 2 weeks now.
Thursday, November 21, 2013 12:47 PM
Strangely enough our problem was solved when we combined our 'install applications' tasks in the TS.
We had one 'Install Applications' per application directly after eachother for cosmetic reasons. The problem described stopped when we combined these in a single 'Install Applications' step.
Did not try to reproduce it by splitting them up again, but it feels like this solved our problems.
Good luck, hope this helps for others too!
Dave
Thursday, November 21, 2013 2:52 PM
Thanks you for your reply.
We only have one Install Application step because we use the dynamic variable list to install applications.
I will try to switch to two Install Application steps because we have more than 9 applications to install.
Our AppDiscovery logging for the app that is failting every TS:
+++ Did not detect app deployment type Microsoft App-V Client 4.6 SP2 - Script Installer (Native)(ScopeId_49A5C9EF-5655-4DD0-B686-247188338CBC/DeploymentType_896e5251-a7e3-4e30-9b37-9d8c41f23693, revision 17) for system. AppDiscovery 21-11-2013 13:58:36 2464 (0x09A0)
ActionType - Install will use Content Id: Content_4f4afc80-fb83-4cc8-8de7-16ada00e023d + Content Version: 1 for AppDT "Microsoft App-V Client 4.6 SP2 - Script Installer (Native)" [ScopeId_49A5C9EF-5655-4DD0-B686-247188338CBC/DeploymentType_896e5251-a7e3-4e30-9b37-9d8c41f23693], Revision - 17 AppDiscovery 21-11-2013 13:58:37 2464 (0x09A0)
ActionType - Install will use Content Id: Content_4f4afc80-fb83-4cc8-8de7-16ada00e023d + Content Version: 1 for AppDT "Microsoft App-V Client 4.6 SP2 - Script Installer (Native)" [ScopeId_49A5C9EF-5655-4DD0-B686-247188338CBC/DeploymentType_896e5251-a7e3-4e30-9b37-9d8c41f23693], Revision - 17 AppDiscovery 21-11-2013 13:58:37 2464 (0x09A0)
This App is missing in the AppEnforce.log!
Applicatons with Deployment types based on script seem to give problems on occasional base in our case.
Thursday, November 21, 2013 8:16 PM
We have stopped using Applications to install and reverted to using packages. This has worked for us. However, I did come across this tiny far out of the way option in the Client Agent settings -> "Use a managed service to install applications." Un-ticking this box has solved a lot of our application deployment problems.
Anthony Sheehy - MCP, MCITP
Thursday, November 21, 2013 8:28 PM
"Use a managed service to install applications."
That option is for third-party integration and control of app deployment. Having it checked will completely break app deployment (without a third-party in the picture that knows how to initiate app install on the client side); i.e., don't check this box with or without OSD issues.
Jason | http://blog.configmgrftw.com
Thursday, November 21, 2013 8:38 PM
Agreed. Maybe I should have been clearer in saying that while that box was ticked (for the life of my I cannot think how it came to be set) we were getting errors in application deployment similar to that seen in the task sequences. Hence, why I mentioned it. Mind you, that was now some time ago. My mind could be a bit misty about it.
Anthony Sheehy - MCP, MCITP
Monday, November 25, 2013 9:26 AM
After switching from applications installed with the variable to "install folowing" I have constant error on another app:
The task sequence failed to install application Adobe Acrobat X Pro(ScopeId_49A5C9EF-5655-4DD0-B686-247188338CBC/Application_6ac4c2c3-e0cf-4dab-93d8-955aaf76d5eb) for action (Install Application - Phase 2 (Laptop)) in the group () with exit code 16389.
This is not the password policy error anymore but a different error, same exit code.
Edit: Full error is back again "The task sequence failed to install application Adobe Acrobat X Pro(ScopeId_49A5C9EF-5655-4DD0-B686-247188338CBC/Application_6ac4c2c3-e0cf-4dab-93d8-955aaf76d5eb) for action (Install Application - Phase 2 (Laptop)) in the group () with exit code 16389. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password."
Next steps for us are to update content of the deployment type of the adobe app and after that remove de CU2 patch from ConfigMgr Client installation.
Edit: Now it looks like the error is more specific aboud download problems in the smsts.log: "Execution status received: 24 (Application download failed )"
Found a thread with similar error descriptions: 3de9c8bc-28b0-4701-91e7-1909c78692bf/osd-task-sequence-applications-fail-to-install
Wednesday, December 4, 2013 11:55 AM
Now I have the same error message when deploying Win7 x64 with OSD to some older models. Password, images and all the apps are the same for every machine, new hardware works 100%, older hardware works 0%. Only differency is, that older hardware uses Auto Apply Drivers to gather any driver from the catalog, new hardware is modelled more carefylly with using Driver Packages.
Monday, June 9, 2014 7:30 PM
Hi
DID any of you guys ever pinpoint this problem?
We have it in ONE OSD TS out of 10? and they're all copied from one original and just modified with regards to what domain they join the PC to.
No matter what one or more of the installed applications through the dynamic variable list, fails during the OSD TS.
Wednesday, October 28, 2015 9:30 AM
Adding comment to the Detection Method of Application might help, because it then changes the Content ID