Yes, that's what I'm shooting for. I'll try the application method. I have EP in my applications, but the detection rule is for the registry value HKLM\ SOFTWARE\Microsoft\Microsoft Security Client. The computer in question has this value, even though the client is not installed. If I add a file system detection rule, will that force the install if both detection rules aren't met?
From: [email protected] [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Friday, January 17, 2014 10:29 AM To: [email protected] Subject: [mssms] RE: More help with Endpoint Protection compliance needed Are you trying to setup an ADR to deploy the Endpoint Client on machines that are non-compliant? What about using an application to deploy the EP client to your non-compliant collection. I've used this in the past SCEPINSTALL.EXE /S to deploy Endpoint silently. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Friday, January 17, 2014 1:07 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] More help with Endpoint Protection compliance needed I got my compliance settings working. I have a machine that had its EP install get corrupted, and my rule detects it and places the system into a non-compliant collection. I have an ADR that is set to target this collection. This ADR is identical to the one that initially distributes EP to new SCCM clients. Although the system is there, EP is not getting deployed to it. What am I missing? [cid:[email protected]] Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]>
<<inline: image001.png>>
