Im running a Lync2013 install in a Task Sequence and and have modified the LyncSetup.msp in OCT with a SETUP_REBOOT Never, but the Task Sequence reboots anyway.

I get this message...

  • Execution is complete for program Lync 2013 15.0.4420.1017 Install. The exit code is 3010, the execution status is SuccessRebootRequired execmgr
  • Execution Request for package C010010E program Lync 2013 15.0.4420.1017 Install state change from Running to ReportStatusAtReboot execmgr
  • The program Lync 2013 15.0.4420.1017 Install for package C010010E and advertisement C01201B0 completed succesfully and it requires a reboot, however reboot is supressed. Removing request. execmgr
  • Program exited expecting reboot, delaying execution of other programs for 60000 ms execmgr

And then it reboots anyway.

The SCCM package program is set to After running: No action required.

I dont have any config.xml file, do I need one anyway?

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

Humm, that could be the Task Seq engine being a knob, since it knows about the 3010 its trying to help you by rebooting.

Is this for imaging a machine, or to deploy Lync via a Task Seq?

Answered 05/15/2013 by: rileyz
Red Belt

  • Its for Lync deployment.
    • Lync deployment as part of a imaging process or you using a Task Seq cos you want too?
      • No Image deployment. Using TS because all the uninstall pakages of OCS and LM etc is already in SCCM, and its more informative for the user since it needs a reboot to complete the installation.
        Sure I can use a script but... if I can do it this way I want to,
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
  • Ahh good shout on the Task Seq, I would of done that as well.

    Humm
    Idea 1) Make a admin install for Lync and merge the MSP into it.
    Idea 2) wrap the MSP into a batch to try and hide the 3010 code from the Task Seq Engine.

    Just did a bit of research, have a look at this. This is a configmgr config problem.
    http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

    http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/6cf0baf8-68c6-4eb2-a1e9-431cb57a3fe0
    • Great thanks!
      Im working with SCCM 2007, I will try hiding it in a batch or script. I will return with the result.
    • I wrapped the MSP in a script, now it works. Thanks alot!
  • Good to hear you got it sorted (:
Please log in to comment
Answer this question or Comment on this question for clarity