task sequence failed to install application
he task sequence failed to install application Mozilla Firefox (en-US)(ScopeId_DF37C18A-3DCC-4C3E-87B7-BCF6704DB3F9/Application_b2c11445-6b22-4a02-96d4-69bbafcc7d92) for action (Install Applications) in the group () with exit code 617. The operating system
reported error 617: You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used.
regards
Lashkham
December 23rd, 2013 10:21am
This is definitely a new one on me. Is the task sequence for OSD or just multiple app installs? Have any other app install steps worked before it gets to this step or is this the first app?
December 23rd, 2013 10:07pm
Could you post AppEnforce, AppDiscovery and AppEval logfiles?
February 22nd, 2014 11:50am
Lashkam, have you resolved this? I am experiencing the same issue. Using the MDT database to install role-based apps, and the error only happens on random machines. No applications get installed and no log files are moved. This is on SCCM 20
March 21st, 2014 11:34am
Has the password on your Network Access Account expired?
March 21st, 2014 11:48am
Hey MadLuka, this is a clients site and I thought of that but the service account was set to never expire or change. Plus I figured it would be more frequent. This issue only occurs on a handful of machines. The only thing I can think of is that they are
running the TS as a new computer to remove 3rd party encryption and move to bitlocker. Maybe an issue with the computer account itself, thoughts?
March 21st, 2014 11:52am
No applications get installed and no log files are moved. This is on SCCM 20
March 21st, 2014 11:59am
You haven't said yet if this issue applies to all apps or just the firefox app?
March 21st, 2014 12:03pm
Has the customer implemented any crazy permissions on OU's that would affect the ability of the system to amend it's own computer account? For new computers, check the OU permissions. Does the DomainJoin account you are using have the necessary
delegated permissions (there are a handful) to perform the required operations on existing computer accounts wherever they may be?
March 21st, 2014 12:06pm
All good questions. I will double-check with the client if:
- They created a new OU for bitlocker and the domainjoin account has proper permissions
- If Firefox is a part of the install
- If there an appenforce.log
I will update as soon as they respond, thanks for the help guys.
March 21st, 2014 12:10pm
Ok, here is an update:
- DomianJoin account is still valid and working. Permissions are the same on the OU.
- Firefox is not part of the installs
- There is no appenforce.log, as a matter of fact, there are quite a few logs missing.
I will be remoting into the machines over the weekend. I will keep the forum updated if I find a solution.
March 21st, 2014 5:23pm
I came across this error during my SCCM 2012 R2 CU1 build this morning. Not sure if this helps or not but my problem was that the domain join was trying to join to a non existent OU in my AD. The OU had been removed from AD and relevant settings in Config Manager had
not been updated / removed.
Reviewing the setupact.log provided relevant information.
Cheers
Damon
July 7th, 2014 10:56pm
Lashkam, did you ever solve this problem? We have this issue on SCCM 2012 R2 CU1.
Regards Anders
September 23rd, 2014 11:24am
Did anyone find a solution to this problem?
I have the same problem in my build and capture TS.
Installation of the Office Application in my TS exits with this error code :-(
March 30th, 2015 5:32am