Task Sequence Deployment Type Pre-Release Feature with multiple restarts

Question

I have used a Task Sequence to upgrade VDA clients on machines (as recommended by Citrix) for years now, but decided to try out the Task Sequence Deployment Type of an Application Pre-Release Feature. It provides a few benefits that I hoped to have (uninstall, requirements, dependencies, etc). this all seem to work great, but the Task Sequence kicks of one or more restarts using the TS Type Restart Computer. It is following through on all of the required steps but is doing the app detection after the first reboot.

I tried various options but cannot get it to wait until the Task Sequence is completed to do the app detection. I tried checked/unchecked "Restart Required" in the Task Sequence Properties, as well as OS and no OS requirements.

As a work around I am running a command to force another app detection at the end of the sequence, but would prefer for it to wait so maybe a user could see an installing Status and a returned Installed for reports.

Has anyone seen this issue? Thanks so much for the help!

Answer 1

Thanks for the response. Sorry about the delay I didn’t see the response. I am using a package step in the task sequence with a reboot step depending on the return code. The Task Sequence runs properly however it is causing issues because after the restart the status is showing Failed in Software Center causing the techs to run it again when the Task Sequence is still actually properly being run. The status is evaluated after the restart even though the TS continues and will install completely. The issue is the incorrect early evaluation

Answer 2

Hi, @Allison Lehmann

Thank you for posting in Microsoft Q&A forum.

Are we using an Install Package step instead of an Install Application in the task sequence?

We may use "Task Sequence as an application deployment type" feature with the steps:

1. Create a package that will contains the source for the application you want to install but do not create a program associated to it;
2. Create a Task Sequence that will execute all the actions needed to install your application (Including a step that will use the package previously created);
3. Create an application and chose the Custom deployment setting. When you are at the deployment type creation, select Task Sequence and pick your TS. You can also select a Task Sequence for the un-installation of the application;
4. Deploy the application like any other.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.