Use Firewall settings such as blocking WMI and File and Print Sharing to prevent client push if needed.
Domain admin accounts should never be used for client push, btw. Sent from a mobile device > On Dec 29, 2015, at 9:08 AM, Chris Barnes <[email protected]> > wrote: > > Hey guys – Working with a client on a question of how to block the SCCM agent > installation on a subset of machines. > > It looks like the assumption is that we can’t move them into a different OU, > Client Push account is domain admin (can’t remove rights), and can’t move it > into a network that is not in a boundary. > > I saw that there was a server side reg key you can create to prevent the > installation, however that isn’t going to scale to the number of machines > that we need to work on. > > Will the NO_SMS_ON_DRIVE.SMS file block the install of the client? For > instance, if there is only 1 logical drive, and the NO_SMS_ON_DRIVE.SMS file > exists on the root of that drive, will that prevent the SCCM agent from > installing? > > > > Chris Barnes > > Coretek Services | Enterprise Consultant > ( 248.767.4415 cell > * [email protected] > : http://www.coretekservices.com > >
