Good Morning All - Today I am starting the OSD Deployment Rollout for my company and I'm trying to make it as easy as possible for all techs. I have 4 different site specific OSD TSs that I've already advertised to "All Unknown Computers." More often than new computers, though, they reimage computers which have already been on the domain. For that purpose, I have also advertised the same 4 OSD TSs to a Collection which they may move individual computers into to receive the advertisement. I have also created 4 different boot medias (each different DPs) to use. We are not currently using PXE. What I'd prefer to do is cut having to move existing computers to a collection from the equasion entirely. Is there a way to accomplish this? I know it sounds really risky, but is there a way to perhaps advertise the same 4 TSs to All Systems - BUT - make it to where a boot disk is needed to run the operation - that it would not just automatically start to reimage All Systems? What do you think? Thanks! Ben K.

Hello, If you advertise a TS to All Systems and you don't set it to Mandatory then you shouldn't have an issue. But anyone would be able to reimage his machine. I did this when I've started using SCCM as well and it worked well for me, but most of my users don't know where Add/Remove Programs is, starting applications from the network is beyond them.

Making the Task Sequence non-mandatory is the first thing but if you mean can you limit people’s ability to initiate an OSD Task Sequence from WinPE only, then one option is to set that the “Task Sequence can run only on the specified client platforms” and then choose an Operating System that you are sure you don’t use (e.g. x64 Windows XP Professional SP1; as I am guessing this is not a common OS at your company). Clients will reject the Task Sequence advertisement so will not be available in Windows but if you pxe-boot or boot from WinPE boot media (e.g. CD/USB) the OSD Task Sequence will be available (as the platform requirements are not relevant once in WinPE).

Thanks Guys - Interesting... So I can set it for XP x64 (yes, don't have a clue who would use that anywhere), but boot media would still be able to grabit? ThanksBen K.

OK - Just tried to advertise a TS to a Collection, but don't see where I can make it OS specific. The only way i can really think of where that is an option is when making a Program for a Package. Where do I do it? - Thanks!Ben K.

to hide the task sequence from RAP, right click on your task sequence, choose Properties click on the Advanced tab Select an operating system from the list which is NOT in use in your organisation *eg: Windows Vista X64, or Windows 2000* click Apply, My step by step SCCM Guides I'm on Twitter > ncbrady

Hi, Ben: I'm in a similar environment to yours and have technicians that need to have access to build computers, but they have no business getting into SCCM. I opted for this approcate: 1. Build Collections for various OS deployments such as OSD\Winxp and OSD\Win7 2. Advertised the build sequence to each of the coresponding Collections 3. Created a simple web service that has the ability to delete a computer, import a computer, assign a computer variable, and add a computer to a collection. 4. Built a front end to the web service. It walks through different "build templates" and allows someone to assign a computer to a collection without really knowing that is what they were doing. 5. Published the program to only people who should have rights to build the workstations and servers. I know you said that you didn't want to deal with moving computers to collections, but to me, thats the safest way. I'm too scard to advertise anything to "all systems", so I looked for a different approach. It takes about 5-10 seconds for the program/web service to import the computer and make a collection rule (that includes deleting the computer account if it already exists), so it's not too time consuming. It also gave me the opportunity to put variables into my sequence for each app and give the person building the machine a way to customize the build on the fly. It works rather nice and would be the way I would recommend doing it.