SOLVED OSD Task Sequence - The operating system reported error 615

[Andrejs]

Hello team!

Today got OSD TS error, while reinstalling laptop (computer account was presented in both AD and SCCM (version 2103).

Error:
The task sequence failed to install application Google Chrome v. 92.0.4515.107 (x64)(ScopeId_B895B697-43BD-4C31-A436-BFEBF400699C/Application_c40d1ca2-a25b-4a9e-961e-718c45622748) for action (Install Application Google Chrome v. 92.0.4515.107) 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 fact computer was installed, just this app was missing, which I later installed manually via Software Center)

Please kindly assist, how to fix this problem.

 

[Prajwal Desai]

Are you deploying Chrome as application or package ?.

 

[Andrejs]

Are you deploying Chrome as application or package ?.

As a Package (MSI)

 

[nautilus2104]

Im seeing the same error as of today.. chrome packaged as an application..
Will try and investigate whats going on

 

[JohnT1971]

I am getting the 615 error suddenly (the past few days) for the Office 365 installs on our OSD builds. Not sure what is going on. We end up installing via Software Center after the build completes.

 

[mortis316uk]

Seeing this as well, OSD builds and TS installs. No pattern to what works and what doesn't within the app install step. First noticed on Monday 13th Sep. If anyone can help it would be appreciated.

 

[MdKnightR]

This sounds very much like an issue that I'm having. It just randomly omits applications that should be installed during the OSD task sequence. https://forums.prajwaldesai.com/threads/os-deployment-task-sequence-problem.4485/

 

[mortis316uk]

We recently updated to 2107 and upgraded to .net 4.8 in advance of this. The error seems to have appeared around this time - has anyone else upgraded to .net 4.8 before the issues appeared?

 

[MdKnightR]

We recently updated to 2107 and upgraded to .net 4.8 in advance of this. The error seems to have appeared around this time - has anyone else upgraded to .net 4.8 before the issues appeared?

I upgraded Config Manager to 2107 on Sept 3rd. We have .Net 4.8 installed, but I don't know when it was installed. I can only assume that it was installed prior to the upgrade.

 

[dannnyb_kcgm]

Having the same issue. Office 365 has given me this error in my TS.
The task sequence failed to install application Office 365 Inc All x64(ScopeId_8FF8CF4F-A517-42A8-8298-009CB7C43FF0/Application_b3ed98c7-af10-4336-832e-33d4e47e6938) for action (Install Office 365 x64 - No Access) 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.
We upgraded to 2107 last week.

 

[Marek Belan]

Same here. Random app in TS failed with 615....

 

[dannnyb_kcgm]

I just redistributed the content and it seems to work fine now. Fingers crossed.

 

[MdKnightR]

This worked for me....

I found this thread for the same issue on version 2006. Apparently it cropped up again in 2107.

TS application install fail after 2006 upgrade - Microsoft Q&A

Applications installed in task sequence are failing after upgrade to version 2006. Policy Evaluation failed, hr=0x87d00267 Install application action failed: 'Bomgar Jump Client'. Error Code 0x87d00267 Anyone else seeing this behavior?

docs.microsoft.com

The Readers' Digest version - you have to add an administrator comment to each deployment type then update content on each. It doesn't matter how long it is (for example, "SCCM2107Fix"). There was also mention of the issue affecting applications that have operating system requirements. Incidentally, every one of mine that weren't getting installed had these requirements, so I cleared them out for good measure.

Now my primary OSD task sequence works great! However, I still had an issue with a new task sequence that I put together prior to the ConfigMgr 2107 update. It was made for imaging Surface Go devices with LTSC. For their purpose, the users only need access to email, so I had created a deployment of Outlook 2019 only. The little trick mentioned above did not work for it, so I had to go and create a brand new application using the SCCM's built-in Office Customization Tool. Now it installs with the OSD task sequence as expected.

 

[Marek Belan]

This worked for me....

I found this thread for the same issue on version 2006. Apparently it cropped up again in 2107.

TS application install fail after 2006 upgrade - Microsoft Q&A

Applications installed in task sequence are failing after upgrade to version 2006. Policy Evaluation failed, hr=0x87d00267 Install application action failed: 'Bomgar Jump Client'. Error Code 0x87d00267 Anyone else seeing this behavior?

docs.microsoft.com

The Readers' Digest version - you have to add an administrator comment to each deployment type then update content on each. It doesn't matter how long it is (for example, "SCCM2107Fix"). There was also mention of the issue affecting applications that have operating system requirements. Incidentally, every one of mine that weren't getting installed had these requirements, so I cleared them out for good measure.

Now my primary OSD task sequence works great! However, I still had an issue with a new task sequence that I put together prior to the ConfigMgr 2107 update. It was made for imaging Surface Go devices with LTSC. For their purpose, the users only need access to email, so I had created a deployment of Outlook 2019 only. The little trick mentioned above did not work for it, so I had to go and create a brand new application using the SCCM's built-in Office Customization Tool. Now it installs with the OSD task sequence as expected.

this is workaround confirmed