“[Configuration Manager 2007] is a complex product, so if you have 50 machines, you’re not going to install SCCM just to run something like FEP,” he said. The release candidate for Forefront Endpoint Protection 2010 is currently available for download at the Microsoft website. On the Product tabs, check Forefront Endpoint Protection 2010 and click Ok; Verification. ConfigMgrInstallationPath Logs EPSetup.log – Detailed EP Installation status; ConfigMgrInstallationPath Logs Wsyncmgr.log – SUP Synchronization status; You are now ready to manage EndPoint Protection using SCCM.
We have a relatively small organization (~15 users), and have used the ForeFront EndPoint Protection 2010 desktop client without the use of central management, like Configuration Manager.
Now that the System Center 2012 Configuration Manager and Endpoint Protection is rolled together as one installation package, do you have to stand up the Configuration Manager to use the Endpoint Protection desktop client? Or can we still use the desktop client as a standalone anti-virus solution?
sysadmin1138♦2 Answers
You do not need to have SCCM to use forefront. You do however need it if you're planning on doing any reporting on those installed clients (i.e. compliance, tracking, etc.).
TatasTatasNo you can stand them up separately but I believe if you want to know things like agent health you need SCCM.
Download Microsoft Forefront Endpoint Protection
Jim BJim BNot the answer you're looking for? Browse other questions tagged anti-virusdesktopmicrosoft-forefront or ask your own question.
-->Applies to: System Center Configuration Manager (Current Branch)
This procedure configures custom client settings for Endpoint Protection, which you can deploy to collections of devices in your hierarchy.
Important
Only configure the default Endpoint Protection client settings if you're sure that you want them applied to all computers in your hierarchy.
To enable Endpoint Protection and configure custom client settings
In the Configuration Manager console, click Administration.
In the Administration workspace, click Client Settings.
On the Home tab, in the Create group, click Create Custom Client Device Settings.
In the Create Custom Client Device Settings dialog box, provide a name and a description for the group of settings, and then select Endpoint Protection.
Configure the Endpoint Protection client settings that you require. For a full list of Endpoint Protection client settings that you can configure, see the Endpoint Protection section in About client settings.
Important
Install the Endpoint Protection site system role before you configure client settings for Endpoint Protection.
Click OK to close the Create Custom Client Device Settings dialog box. The new client settings are displayed in the Client Settings node of the Administration workspace.
Next, deploy the custom client settings to a collection. Select the custom client settings you want to deploy. In the Home tab, in the Client Settings group, click Deploy.
In the Select Collection dialog box, choose the collection to which you want to deploy the client settings and then click OK. The new deployment is shown in the Deployments tab of the details pane.
Clients are configured with these settings when they next download client policy. For more information, see Initiate policy retrieval for a Configuration Manager client.
Microsoft Forefront Endpoint Protection
How to provision the Endpoint Protection client in a disk image
Install the Endpoint Protection client on a computer that you intend to use as a disk image source for Configuration Manager OS deployment. This computer is typically called the reference computer. After you create the OS image, then use Configuration Manager OS deployment to deploy the image.
Important
Windows 10 and Windows Server 2016 have Windows Defender installed by default. You don't need this procedure on those versions of Windows.
Use the following procedures to help you install and configure the Endpoint Protection client on a reference computer.
Prerequisites
The following list contains the required prerequisites for installing the Endpoint Protection client software on a reference computer.
You must have access to the Endpoint Protection client installation package, scepinstall.exe. Find this package in the Client folder of the Configuration Manager installation folder on the site server.
To deploy the Endpoint Protection client with your organization's required configuration, create and export an antimalware policy. Then specify this policy when you manually install the Endpoint Protection client. For more information, see How to create and deploy antimalware policies.
Note
You can't export the Default Client Antimalware Policy.
If you want to install the Endpoint Protection client with the latest definitions, download them from Windows Defender Security Intelligence.
Note
Starting in Configuration Manager 1802, you don't need to install the Endpoint Protection agent (SCEPInstall) on Windows 10 devices. If it's already installed on Windows 10 devices, Configuration Manager doesn't remove it. Administrators can remove the Endpoint Protection agent on Windows 10 devices that are running at least the 1802 client version. SCEPInstall.exe may still be present in C:Windowsccmsetup on some machines, but new client installations shouldn't download it.
System Center Endpoint Protection
How to install the Endpoint Protection client on the reference computer
Install the Endpoint Protection client locally on the reference computer from a command prompt. First get the installation file scepinstall.exe. For more information, see Install the Endpoint Protection client from a command prompt.
If necessary, also include a preconfigured antimalware policy or with an antimalware policy that you previously exported.
To install the Endpoint Protection client from a command prompt
Copy scepinstall.exe from the Client folder of the Configuration Manager installation folder to the computer on which you want to install the Endpoint Protection client software.
Open a command prompt as an administrator. Change directory to the folder with the installer. Then run
scepinstall.exe, adding any additional command-line properties that you require:Property Description /sRun the installer silently /qExtract the setup files silently /iRun the installer normally /policySpecify an antimalware policy file to configure the client during installation /sqmoptinOpt-in to the Microsoft Customer Experience Improvement Program (CEIP) Follow the on-screen instructions to complete the client installation.
If you downloaded the latest update definition package, copy the package to the client computer, and then double-click the definition package to install it.
Note
After the Endpoint Protection client install completes, the client automatically performs a definition update check. If this update check succeeds, you don't have to manually install the latest definition update package.
Example: install the client with an antimalware policy
scepinstall.exe /policy <full path><policy file>
Verify the Endpoint Protection client installation
After you install the Endpoint Protection client on your reference computer, verify that the client is working correctly.
On the reference computer, open System Center Endpoint Protection from the Windows notification area.
On the Home tab of the System Center Endpoint Protection dialog box, verify that Real-time protection is set to On.
Verify that Up-to-date is displayed for Virus and spyware definitions.
To make sure that your reference computer is ready for imaging, under Scan options, select Full, and then click Scan now.
Prepare the Endpoint Protection client for imaging
Perform the following steps to prepare the Endpoint Protection client for imaging:
On the reference computer, sign in as an administrator.
Download and install PsExec from Windows SysInternals.
Run a command prompt as an administrator, change directory to the folder where you installed PsTools, and then type the following command:
psexec.exe -s -i regedit.exeImportant
Use caution when you run the Registry Editor in this manner. PsExec.exe runs it in the LocalSystem context.
In the Registry Editor, delete the following registry keys:
Important
Delete these registry keys as the last step before imaging the reference computer. The Endpoint Protection client recreates these keys when it starts. If you restart the reference computer, delete the registry keys again.
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft AntimalwareInstallTimeHKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft AntimalwareScanLastScanRunHKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft AntimalwareScanLastScanTypeHKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft AntimalwareScanLastQuickScanIDHKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft AntimalwareScanLastFullScanIDHKEY_LOCAL_MACHINESOFTWAREMicrosoftRemovalToolsMRTGUID
You're now ready to prepare the reference computer for imaging.
Microsoft Forefront Endpoint Protection
When you deploy an OS image that contains the Endpoint Protection client, it automatically reports information to the device's assigned Configuration Manager site. The client downloads and applies any targeted antimalware policy.
See also
Forefront Endpoint Protection 2010 Server
For more information about OS deployment in Configuration Manager, see Manage OS images.