Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM OSD Task Sequence first Application fails to Install

  • Thread starter Thread starter rhughes
  • Start date Start date
  • Replies Replies 5
  • Views Views 8K

rhughes

Member
Messages
12
Reaction score
1
Points
1
Hello,
I can't seem to find a solution to this problem that I have had for quite some time now and I was wondering if anybody here has come across this? This problem started after updating to build 2107 and that's what we are still running at the moment. We are having a problem with the Install Application step in our OSD task sequence, where the first application will always fail to install. It doesn't matter what application is put first, the first one will always fail. For a long time now, I've had to duplicate the first application, so it would actually install. If an application requires a reboot, after the reboot, the next app in the list will fail to install... always. I can only assume this is related to a service not starting quick enough.

The log file always shows this for the first application or the next application in the list after a required reboot:
Code:
The task sequence execution engine failed to install application VLC Media Player(ScopeId_78FCCC8A-60B6-443E-9F40-4F525FBE127F/Application_829e9174-cd75-467b-ab6b-465f2f3a1ac4) that was specified through TS variable for action (Install Base Applications) 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.

Has anybody else came across this or know of a solution to this problem?

Cheers,
Richard
 
Solution
Hi,

I know this post is old and probably solved. I just want to leave information, maybe for someone in the future, because I spent almost two weeks on this issue. I had the exact same problem as described in this topic. There was no indication in any logs as to what might be causing the problem.

The computer was on a different network than the server, and there was a firewall between them.

SOLUTION:
In my case, the solution was to unblock ports 3268 and 3269 on our Firewall to all Active Directory domain controllers.

After adding a rule to allow this traffic between my networks, the whole task sequence started working flawlessly.
What is the step in the TS before you install any application?.
Hi Prajwal,

Thank you for your prompt response. There are two "Install Application" steps in this task sequence, both install applications based on collection variables. Just before the first "Install Application" step, I have KMS activation for Windows & Office. There is no reboot between the KMS activation and the first "Install Application" step. I then have a restart step before the second "Install Application" step. The first application for both "Install Application" steps, will always fail with the same error. If I duplicate the collection variable so BA01 and BA02 are equal to VLC Media Player, BA01 will always fail but BA02 will install successfully.

Cheers,
Richard
 
I think I may have resolved this (hopefully). I noticed when doing some testing on a VM, I couldn't replicate the problem. The only difference is the boot media being used, with the VM using newly created boot media. I think the USB boot media being used by our technicians, is outdated and the cause of this problem! I have blocked all boot media created prior to August 2022, so I'll see what happens now.
 
Hi,

I know this post is old and probably solved. I just want to leave information, maybe for someone in the future, because I spent almost two weeks on this issue. I had the exact same problem as described in this topic. There was no indication in any logs as to what might be causing the problem.

The computer was on a different network than the server, and there was a firewall between them.

SOLUTION:
In my case, the solution was to unblock ports 3268 and 3269 on our Firewall to all Active Directory domain controllers.

After adding a rule to allow this traffic between my networks, the whole task sequence started working flawlessly.
 
Solution
Hi,

I know this post is old and probably solved. I just want to leave information, maybe for someone in the future, because I spent almost two weeks on this issue. I had the exact same problem as described in this topic. There was no indication in any logs as to what might be causing the problem.

The computer was on a different network than the server, and there was a firewall between them.

SOLUTION:
In my case, the solution was to unblock ports 3268 and 3269 on our Firewall to all Active Directory domain controllers.

After adding a rule to allow this traffic between my networks, the whole task sequence started working flawlessly.
Hi Zbierak,

What was exact your issue? For me I do have the following issue with 24H2 and also less more with 23H2:
it seems that AFTER a restart, the FIRST APPLICATION results in an error.
That first application is randomly in my task seqecuence, but always the first after a restart>

Is that also your experience?
 

Forum statistics

Threads
7,188
Messages
28,061
Members
18,333
Latest member
Sreeja
Back
Top