Hi,

I upgrade yesterday from Cu2 to CU5. Last evening, I launch an image reference creation but forgot to change the commandline for the client installation.

So this morning, I correct the situation and ran F12. WinPE start but usually, I see only one task sequence, the one for the image reference creation. So after F12, I am seeing all task sequence but NOT the one I need. I did a test as creating a new deployment for my task sequence. Then I ran F12 and ALL task sequence are appearing INCLUDING the one that I need.

All task sequences:

So I selected this one I got:

I did a test on others task sequences and all of them have this behavior.

This is strange, what would provoke that behavior? How solving it?

Empty collection variables, empty computer variables and empty task sequence variables cause a dialog box like that.

So to troubleshoot these things:

1. Empty computer variables: Look at the SCCM computer object and see if there are any variables configured on the object with a blank value.
2. Empty collection variables: Look at the SCCM computer object and see what collections it's a part of. Examine each of those and see if there are any collection variables set to be blank.

Hi,

Everything was fine before going to sleep and this morning the problem is appearing. And now all task sequences have that kind of problem. Almost alltask sequence should not appear as available task sequence.

This is really strange.

I don't understand what you are suggesting.

After upgrading from CU2 to CU5, do I need recreate my WINPE boot disk?

• Edited by FRacine 9 hours 2 minutes ago

Hi,

Everything was fine before going to sleep and this morning the problem is appearing. And now all task sequences have that kind of problem. Almost alltask sequence should not appear as available task sequence.

This is really strange.

I don't understand what you are suggesting.

After upgrading from CU2 to CU5, do I need recreate my WINPE boot disk?

• Edited by FRacine 9 hours 0 minutes ago

Hi,

I just made a test by creating a brand new task sequence with just the required minimum. A MDT task sequence and I just answer the creation's questions. I got the exact same result.

When I created a deployment as required then the task sequences started but fail. I don't worry about the failure but this is strange.

I just made another test. The TS is working fine when required and the problem is appearing when available.

• Edited by FRacine 8 hours 17 minutes ago

Hi,

I just made a test by creating a brand new task sequence with just the required minimum. A MDT task sequence and I just answer the creation's questions. I got the exact same result.

When I created a deployment as required then the task sequences started but fail. I don't worry about the failure but this is strange.

I just made another test. The TS is working fine when required and the problem is appearing when available.

• Edited by FRacine 8 hours 15 minutes ago

Hi,

Everything was fine before going to sleep and this morning the problem is appearing. And now all task sequences have that kind of problem. Almost alltask sequence should not appear as available task sequence.

This is really strange.

I don't understand what you are suggesting.

After upgrading from CU2 to CU5, do I need recreate my WINPE boot disk?

• Edited by FRacine Friday, July 17, 2015 10:46 PM

Hi,

Everything was fine before going to sleep and this morning the problem is appearing. And now all task sequences have that kind of problem. Almost alltask sequence should not appear as available task sequence.

This is really strange.

I don't understand what you are suggesting.

After upgrading from CU2 to CU5, do I need recreate my WINPE boot disk?

• Edited by FRacine Friday, July 17, 2015 10:46 PM

Hi,

I just made a test by creating a brand new task sequence with just the required minimum. A MDT task sequence and I just answer the creation's questions. I got the exact same result.

When I created a deployment as required then the task sequences started but fail. I don't worry about the failure but this is strange.

I just made another test. The TS is working fine when required and the problem is appearing when available.

• Edited by FRacine Friday, July 17, 2015 11:31 PM

Hi,

I just made a test by creating a brand new task sequence with just the required minimum. A MDT task sequence and I just answer the creation's questions. I got the exact same result.

When I created a deployment as required then the task sequences started but fail. I don't worry about the failure but this is strange.

I just made another test. The TS is working fine when required and the problem is appearing when available.

• Edited by FRacine Friday, July 17, 2015 11:31 PM

You second dialog box Edit Task Sequence Variables only shows when there are empty task sequence variables defined. As you mention that you're also seeing task sequences that you would expect, I suspect that your device is simply member of a different collection. At that collection there are probably different task sequence deployed and empty variables defined (properties of the collection).

Hi,

How may I know if there are empty variables?

Check the tab Collection Variables in the properties of the collection and look for the variables shown in the Edit Task Sequence Variables dialog box.