Peter33

Hi, make sure that all used Images, Driver packages and Software Packages, which are being used in your Task Sequence, are available on your local Distribution Point. Otherwise the Task Sequence will not start.

Have you created a transform file for the msi? oh wait .. just by the way http://www.windows-noob.com/forums/index.php?/topic/2502-deploying-symantec-endpoint-protection-with-task-sequence/

Hi, unfortunately this happens pretty often when injecting modules or new drivers to pxe wim's. This also may happen after deleting a pxe wim. Remove the folder "c:\windows\temp\pxeootfiles" and try to start the wds service. Don't worry, the folder will be recreated. In case this fails remove the pxe image from the smspxeimages$ share an restart the wds service. Seems like you can edit the pxe wim's just a few times before they get messed up. I started to delete and recreate the pxe wim's from the cratch to avoid this behavior. Good luck

Hi, if the task sequence is installing a software, just query for the ProductID in AddRemovePrograms, for several Products chain it with "and". You are still limited by the software inventory schedule though, which will give you a delay of several days. Peter

Hi, there is no need for deleting the obsolete objects manually. Just edit your collection query and add the "System Ressource\Obsolete" property with a value of 0. This should do the trick. Edit: Also check your collection update schedules. The standard setting is 1 day when creating a new collection which will cause a huge delay. Peter