Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

← Ideas

Continue Installation after dependency requires restart

Around 1706/10...

Available applications (user deployed) stopped completing installation if a dependency required a restart.

Users have to go into software center and initiate the application again to continue the installation. Repeat for every dep that requires a restart.

87 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

11 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    Defiantly a problem and troubled why this has not been addressed. It used to work and not it's broken... break/fix!

  • Nick Aquino commented  ·   ·  Flag as inappropriate

    So, reading here, I find that we'll have a Task Sequence as a deployment type option - this, in theory, may help others here who need to install multiple apps in sequence (Task Sequence), but the app model isn't working for them.

    Seems you can use a Task Sequence as a deployment type in the application model coming soon. This should solve the issue in a workaround-able way:
    https://docs.microsoft.com/en-us/mem/configmgr/apps/get-started/creating-windows-applications#bkmk_tsdt

  • Nick Aquino commented  ·   ·  Flag as inappropriate

    Shocked this is still an issue - just now coming to this need and the packaging team is asking to use task sequences. I would like to keep this in the app model and let the apps take care of the restarts. Please help this out!

  • Nikola Bozov commented  ·   ·  Flag as inappropriate

    Agreed! We currently have in our environment applications which require a "hard reboot" in between the dependency chain. We've also tested the "Application Group" technology which also fails on the restarts as noted in the docs. We don't want to create a TS with "Restart" step for each app which requires a reboot from it's attached dependency. The automatic installation after a hard reboot should be something normal for a dependency chain. The tests were performed on SCCM 2005 TP.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Agreed. When user initiated the install of an application, it should continue after the dependency rebooted. It should not be checking if there is a maintenance window and not continue if there isn't one.

  • Anonymous commented  ·   ·  Flag as inappropriate

    ~Confirmed! This is not limited to user deployed software, happens for Device deployments also and is causing problems where the user call in a say the software failed to install when in fact they just need to click install again which should not be the case.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I seems like CM did not do this in previous versions... this might be a new issue.

Ideas: Software Center

Categories

Feedback and Knowledge Base

(thinking…)