temporarly disable SCCM clients
If we have a collection of 70 systems and don't want them get advertisements or any windows updates ect. from SCCM. Would simply blocking them be the best way to prevent and SCCM communicator until we are ready for them to communicate again and then simply unblock them?
August 24th, 2011 3:58pm

Just don't advertise the update package on that collection.Zulqarnain Ali | MCTS, MCSA | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2011 4:08pm

Put them in a 1 min long maint windows and make sure you use maint windows for everything. Also exclude members of that collection from all other collections using a subselect query. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
August 24th, 2011 4:28pm

Create a GPO and stop the SMS Agent Host Service, that way the client is not working.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2011 4:47pm

While Kents suggestion will definately work I feel like that's just putting a band-aid on a gaping wound. If configured properly you should never have any concerns what-so-ever that a client will run a package that you do not intend for it to run. If that's not something you can accomplish you need to bring in a consultant or someone with more experience. SCCM is very powerful. The last thing you want to do is accidently send out an OSD package to all computers in the company or something horrible like that. With proper collections, maintenance windows, properly configured advertisements etc this should never be a concern. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
August 25th, 2011 1:40pm

While Kents suggestion will definately work I feel like that's just putting a band-aid on a gaping wound. If configured properly you should never have any concerns what-so-ever that a client will run a package that you do not intend for it to run. If that's not something you can accomplish you need to bring in a consultant or someone with more experience. SCCM is very powerful. The last thing you want to do is accidently send out an OSD package to all computers in the company or something horrible like that. With proper collections, maintenance windows, properly configured advertisements etc this should never be a concern. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/| +1 I agree with you.Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2011 2:23pm

Hi, You don't need to block or disable your client for just don't let them receive any software or updates. Propery software distribution / software update / OSD settings are needed and keep this collection out of any of the target collection and make this collection exculded in all your distribtion's target collection. Thanks
August 31st, 2011 5:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics