Hi, I´m looking for any best practise to prevent mistake like advertise a task sequence on wrong collections. I´ve seen that best is never create task sequences as mandatory and really make sure when create the advertisement, but I´m worried about the collection All systems that is to close to the collection All Unknow Computers. Is there any way to block a collection to no accept any task sequence, because I want to prevent this kind of mistake on collections like All Systems and Servers collections, if not is there any problem if i delete the collection All System from my SCCM console? Thanks!!! Rodrigo Daphanis

There are different methods, for example: Put a password on the PXE Service Point (works only with PXE boots) Put a password script on the top of your Task Sequence (works always) In the Properties of your Task Sequence specify that it can only run on a specific OS and select one that your not running in your organization (works only with a running OS, not with PXE/ WinPE) My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

Rename the collections. (I don't like deleting the default collections). Put in a QC/QA process so that it takes two people to make a production change. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi Peter, Do you know any blog or documentation that shows how to put script on a tasksequence. The task sequence password will ask password even for example if some create an advertisement for a wrong collection, I mean if I create a wrong advertisement, and it will show for the user that is a O.S available to run when the user click for run the O.S, it will ask password to run or it will boot the machine into WinPE and inside of WinPE will ask for password? Thanks!!! Rodrigo Daphanis

See for example: http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude