locked
Configuration Manager 2002 - Task Sequence Deployment Type RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have MEMCM 2002 and recently our packaging team got a package to deploy, which needed dot net Fx 4.8 as pre-req. This pre-req needs a reboot, so we first tried with app dependency and configured 3010 as hard reboot. But after restart, app installation wouldn't continue. So we switched to TS deployment type, which is a pre-release feature in new CM. Install TS had 3 steps -- Install dot net (if not present) and reboot, and then install the main app. But app deployment is failing on machine with below error:

    I created the same app with TS deployment type in another CM environment, it works fine. Also, if I deploy TS directly (not using application model), it works fine in my environment. Any ideas/suggestions? 


    • Edited by Nipun Garg Thursday, August 6, 2020 8:03 AM Image
    Thursday, August 6, 2020 8:01 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thanks for posting in TechNet. We will do more research about this issue, and will let you know if there is any update.


    Best regards,
    Larry

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post.

    Friday, August 7, 2020 2:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,


    Make sure you are creating a custom task sequence and please check the following configuration:

    1. You can only add a non-OS deployment task sequence as a deployment type on an app. High-impact, OS deployment, or OS upgrade task sequences aren't supported.
    2. On the task sequence properties, User Notification tab, don't select the option for a high-impact task sequence.
    3. When you create the application, to add a task sequence deployment type, your user account needs permission to read task sequences. Use one of the following options to configure these permissions:
        Add the app administrator's user account to the built-in Read-Only Analyst role. This role allows them to view all Configuration Manager objects.
        Copy the built-in Application Administrator role to create a custom role. Add the Read permission on the Task Sequence Package object.
    4. You can't yet deploy an app task sequence to a user collection
    5. Don't use the Install Application step in this task sequence. Use the Install Package step to install apps.

    I hope the above information is helpful to you.

    This MECM Forum will be migrating to a new home on Microsoft Q&A<Link>, please refer to this sticky post<Link> for more details.




    Best regards,
    Larry

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post.

    Friday, August 7, 2020 8:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Does the client version match the server version for that site?

    The application model in your first description should work fine, I do this all the time. No requirement to use a TS

    Going back to without the TS break it down a little

    Does each app install when deployed indivually? which part fails?

    Richard Knight | Collection Refresh Manager | Automate detection rules for patch \ msp files | Twitter


    Friday, August 7, 2020 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    All these conditions are fulfilled correctly and as I said, same app is working fine in other CM environment. Thanks!
    Friday, August 7, 2020 11:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, the client version is correct.
    Friday, August 7, 2020 11:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,


    If the software does return a 3010 exit code, the task sequence engine restarts the computer. After the restart, the task sequence automatically continues.
    If you enable the package option Run another program first, and the dependent program already ran on the destination computer, the dependent program runs and the task sequence continues. However, if the dependent program hasn't already run on the destination computer, the task sequence step fails.

    I hope the above information is helpful to you.


    This MECM Forum will be migrating to a new home on Microsoft Q&A<Link>, please refer to this sticky post<Link> for more details.



    Best regards,
    Larry

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post.

    Monday, August 10, 2020 8:13 AM