BUG: Nested Task Sequences do not update references to packages correctly
In CM Admin Console > Task Sequences when using nested TS the parent TS does not update package references correctly until sub-TS is re-added to the main.
If you are still seeing issues with this nested task sequences, please send a frown through the console or contact support to get further assistance.
33 commentsComments are closed
Kim Rinderknecht commented
I also can see the same or a similar behavior after applying the recommended 1802 hotfix. But instead of getting errors on all child-ts steps while running the partent-ts, now in most cases only the steps that were changed will fail.
Then Solution was the same as bevore we applied the hotfix. Just copy the child-ts and change the run-ts step in the parent-ts.
Hope the nex update will fix that :)
I'm having similar to Brian T.
Whats interesting is that for me if i have multiple Parent TS's calling to the same Child/nested TS, only the first Parent TS that i had called to the Child TS's will update the references, any others after that will not update whether i copy the one that is updating or create new Parent TS's from scratch.
Brian T. commented
Still seeing the same behavior in the reference list of parent task sequences. Modifications made in the child task sequence are not being reflected in the parent task sequence reference list. This is post 1802 hotfix. Anyone else still experiencing this issue?
Boris K. commented
This is a major issue. Happening in 1710 with the latest hotfixes.
I have the same issue as Mike Plichta, is this related? I'm in 1802 but have not updated the ADK tools to the very latest.
Also experiencing in 1802- I hope there is a hot fix soon.
Michael Gerressen commented
Same problem here running 1802. With this bug in place, nested TS is useless.
Same issue here we are running 1802
Mike McGee commented
Same issue here running 1710. Was hoping that this may've been resolved in 1802. I've had the same realization as Emil as to how to resolve the issue. Hopefully a fix is in the pipe.
Mike Plichta commented
The parent TS keeps telling me that a package dependency is missing when booting from 1709 PXE. The referenced package ID is the child TS itself but there is no way to distribute the child TS. All the references for both main and child TS are 100% and distributed to all DP's. I can copy/paste the tasks from the child TS to the main one and they work fine.
I did check the box for using a neighboring DP but a TS should come from the main MP directly, no?
It might need to go back to beta.
Getting the same issue here running 1802.
Emil Bogopolskiy commented
I have the same issue. I placed all enterprise applications that need to be installed during OSD into the child TS and after updating that child TS with the new application, parent TS is not getting updated. The only way to update parent TS is to re-add the same child TS to the parent TS. Only then all parent TS references are getting updated with reflected changes on applications (from the child TS).
Mike Marable commented
It appears that the package references for the nested sequence are embedded into the parent sequence at the "Run Task Sequence" step. These references are not updated should the nested child sequence be updated.