<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Endpoint-Protection on Anything About IT</title><link>https://www.verboon.info/tags/endpoint-protection/</link><description>Recent content in Endpoint-Protection on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 Mar 2013 14:48:33 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/endpoint-protection/index.xml" rel="self" type="application/rss+xml"/><item><title>How to install System Center 2012 Endpoint Protection on a standalone client</title><link>https://www.verboon.info/2013/03/how-to-install-system-center-2012-endpoint-protection-on-a-standalone-client/</link><pubDate>Sun, 24 Mar 2013 14:48:33 +0000</pubDate><guid>https://www.verboon.info/2013/03/how-to-install-system-center-2012-endpoint-protection-on-a-standalone-client/</guid><description>&lt;p&gt;Suppose you have a need to deploy System Center 2012 Endpoint Protection to a number of clients that later run in standalone mode, meaning that they are not joined to a domain, can’t be managed by SCCM and operate in a network that is not connected to your corporate network.&lt;/p&gt;
&lt;p&gt;The installation source &lt;strong&gt;scepinstall.exe&lt;/strong&gt; for the System Center Endpoint Protection agent is stored within the SCCM 2012 client installation folder on the SCCM 2012 SP1 server under C:\Program Files\Microsoft Configuration Manager\Client. Within that same directory we also find the endpoint protection default policy settings stored as &lt;strong&gt;ep_defaultpolicy.xml&lt;/strong&gt;, but we won’t use this , as we are going to prepare our own policy that meets our requirements for a standalone unmanaged client.&lt;/p&gt;</description></item></channel></rss>