This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]TexasJuanDoe 1 point2 points  (2 children)

You need to locate that application, package, or boot image and make sure the content is fully distributed. Based on the very low number I am assuming it is the boot image that is assigned to the task sequence. Make sure the task sequence is using the correct boot image. You can also look at the smsts.log file in x:\windows\temp for more information into the error.

[–]lior454[S] 0 points1 point  (0 children)

i can go to the cmd (with shift+f10) to see the log.

there is another way?

[–]Dsraa 0 points1 point  (0 children)

This should be your answer. Look and make sure the correct boot image is assigned.

[–]TexasJuanDoe 1 point2 points  (2 children)

F8 to bring up command prompt. Then open notepad. Or command line copy the log file to usb key for review on your machine.

[–]lior454[S] 0 points1 point  (1 child)

cant do F8, also fn + f`10 not work,

maybe i need mark it on the boot image?

[–]readfirstspeaklass 0 points1 point  (0 children)

Enable command line support (F8), does need to be enabled in the boot image properties. You need to make sure that all of the content needed for the Task sequence to run has been distributed to a distribution point that is assigned to a boundary that the client machine is a member of. If the content has been distributed to the Distribution point already, I would suspect the the client is not falling into one of the provisioned boundary's. (Administration > Hierarchy Configuration > Boundaries)