Elscorpio Posted June 11, 2014 Report post Posted June 11, 2014 Hi I run SCCM 2012 SP1 - which of these options must you select (see attached screenshot) to hide the OS deployment task sequence inside the SCCM client ? I have experienced that in one instance that OS deployment task sequence were visible inside the SCCM client and my user by accident started to reinstall her computer although I selected the media and PXE option in the attached screenshot. I cant select media and pxe(hide), as it makes it impossible when booting from network to select the correct assigned task sequence. What to do - has this been fixed in SCCM 2012 R2? Quote Share this post Link to post Share on other sites More sharing options...
wilbywilson Posted June 11, 2014 Report post Posted June 11, 2014 If you go to your Task Sequence, right-click and go to its Properties. Then go to the "Advanced" tab. At the bottom, there is an option to "Run on any platform", or you can choose to "Run only on the specified client platforms." Choose something strange like "Vista" (or anything that does NOT exist in your environment.) Then it should never show up on your clients as an option... Quote Share this post Link to post Share on other sites More sharing options...
wilbywilson Posted June 11, 2014 Report post Posted June 11, 2014 I wanted to ask a follow up on this topic, because this seems to unfortunately be a common issue. I've read numerous accounts in these forums about end users accidentally installing an O/S through the Software Center, without understanding what they are doing. Is there a bug in SCCM, where the Task Sequence shows in Software Center, even if you've set it for "Only Media and PXE?" In my case, I've made that "Only Media and PXE" setting, made sure it was only "Available" (not required), plus I changed it to run only on Vista x32 (which we don't have.) And I'm advertising it to the "All Unknown Computers" collection. I haven't seen the advertisement in any of my client's Software Centers, but I'm curious how it's happening in other environments. Are people not configuring it properly? Bug in SCCM? Quote Share this post Link to post Share on other sites More sharing options...