locked
Software Center showing Application Task Sequence as Operating System RRS feed

  • Question

  • I have created a custom task sequence and it includes 2 applications.  The first one uninstalls an app using a batch file and the 2nd TS installs a new version.  The problem is that software center is showing type Operating System so when I click on it to install, it gives a message about installing an operating system and it may delete/format the drive. 

    Is there a setting I need to change so it sees it as an application rather than an OS?  I have other application Task Sequences that show as application rather than Operating System...

    Thanks

    Rick Ray

    Tuesday, February 18, 2014 3:39 PM

Answers

  • Task Sequences were intended to be used for OSD.  Also, they will not partition or reformat unless you specifically have that step in the task sequence.

    I would do this process using SCUP or Application Supercedence. 


    Mike Leach | http://blogs.catapultsystems.com/mleach/default.aspx

    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    Tuesday, February 18, 2014 3:48 PM
  • Hi Rick,

    as TS are designed for os deployment, this is not the way to do this.

    u might try to use dependencies and supersedence rules instead. if you haven't worked with this before, give it a try. the sccm application model is quite powerful.

    regards

    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    Tuesday, February 18, 2014 3:54 PM
  • That's by design. And by design Task Sequences were meant for Operating System Deployment, that's why you also get notified about "Operating System Installation" in the Software Center.

    You should use SCCM Applications with supersedence to accomplish what you are trying to do:

    • Do an application for App 1 (your old app)
    • Do an application for App 2 (your new app)
    • Configure App2 to supersede App1 (uninstall the App1)
    • Deploy App2 to your computers

    This way the App1 will be uninstalled before the App2 is installed.


    • Proposed as answer by Narcoticoo Tuesday, February 18, 2014 6:20 PM
    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    • Edited by Narcoticoo Tuesday, February 18, 2014 6:23 PM
    Tuesday, February 18, 2014 6:20 PM

All replies

  • Task Sequences were intended to be used for OSD.  Also, they will not partition or reformat unless you specifically have that step in the task sequence.

    I would do this process using SCUP or Application Supercedence. 


    Mike Leach | http://blogs.catapultsystems.com/mleach/default.aspx

    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    Tuesday, February 18, 2014 3:48 PM
  • when you create the task sequence are you choosing to create a custom task sequence? 
    Tuesday, February 18, 2014 3:52 PM
  • Hi Rick,

    as TS are designed for os deployment, this is not the way to do this.

    u might try to use dependencies and supersedence rules instead. if you haven't worked with this before, give it a try. the sccm application model is quite powerful.

    regards

    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    Tuesday, February 18, 2014 3:54 PM
  • That's by design. And by design Task Sequences were meant for Operating System Deployment, that's why you also get notified about "Operating System Installation" in the Software Center.

    You should use SCCM Applications with supersedence to accomplish what you are trying to do:

    • Do an application for App 1 (your old app)
    • Do an application for App 2 (your new app)
    • Configure App2 to supersede App1 (uninstall the App1)
    • Deploy App2 to your computers

    This way the App1 will be uninstalled before the App2 is installed.


    • Proposed as answer by Narcoticoo Tuesday, February 18, 2014 6:20 PM
    • Marked as answer by rickray1976 Tuesday, February 18, 2014 6:21 PM
    • Edited by Narcoticoo Tuesday, February 18, 2014 6:23 PM
    Tuesday, February 18, 2014 6:20 PM
  • if you create a custom task sequence and deploy it you do not get notified for OSD.  I agree with NOT using TS for things like applications, but you should be notified for OSD, even with a TS.
    Tuesday, February 18, 2014 6:28 PM