No, I doubt that will work. However, a "trick" one can use is to try one of
these. (or both, but the ccmsetup one is probably more critical)
On the client, create a system, read-only FILE that just so happens to be
called ccmsetup in %windir%. also create a system, read-only FILE that just
so happens to be called ccm in %windir%
The theory is that even though a client install will be attempted... if the
installation attempt can't create the local ccmsetup folder or ccm
folder--because there are already readonly/system files that just-so-happen to
have those names, the cm client can't install.
Anyway, test it and see.
Now the problem is if/when some techs figure this out and try to prevent the cm
client from installing when you really want it to. Sadly, that's up to you to
monitor your FSP reports for failures and to track if the failures are expected
because of this--or if you've got techs out there trying to keep CM off a box
that shouldn't be excluded like that.
On Tuesday, December 29, 2015 9:08 AM, Chris Barnes
<[email protected]> wrote:
<!--#yiv3274279220 _filtered #yiv3274279220 {font-family:Wingdings;panose-1:5
0 0 0 0 0 0 0 0 0;} _filtered #yiv3274279220 {font-family:"Cambria
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv3274279220
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv3274279220
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv3274279220
#yiv3274279220 p.yiv3274279220MsoNormal, #yiv3274279220
li.yiv3274279220MsoNormal, #yiv3274279220 div.yiv3274279220MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv3274279220 a:link, #yiv3274279220
span.yiv3274279220MsoHyperlink
{color:blue;text-decoration:underline;}#yiv3274279220 a:visited, #yiv3274279220
span.yiv3274279220MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv3274279220 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv3274279220 p.yiv3274279220MsoAcetate, #yiv3274279220
li.yiv3274279220MsoAcetate, #yiv3274279220 div.yiv3274279220MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma",
sans-serif;}#yiv3274279220 p.yiv3274279220msonormal0, #yiv3274279220
li.yiv3274279220msonormal0, #yiv3274279220 div.yiv3274279220msonormal0
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv3274279220 span.yiv3274279220BalloonTextChar
{font-family:"Tahoma", sans-serif;}#yiv3274279220
span.yiv3274279220EmailStyle21 {font-family:"Calibri",
sans-serif;color:#1F497D;}#yiv3274279220 span.yiv3274279220EmailStyle22
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv3274279220
span.yiv3274279220EmailStyle23 {font-family:"Calibri",
sans-serif;color:windowtext;}#yiv3274279220 span.yiv3274279220EmailStyle24
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv3274279220
span.yiv3274279220EmailStyle25 {font-family:"Calibri",
sans-serif;color:#1F497D;}#yiv3274279220 span.yiv3274279220EmailStyle26
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv3274279220
.yiv3274279220MsoChpDefault {font-size:10.0pt;} _filtered #yiv3274279220
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv3274279220 div.yiv3274279220WordSection1
{}-->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/
