Is the endpoint protection cluster-aware?
Hi,
I have HYPER-V cluster nodes. I have also SCCM 2012. I want to deploy EP 2012 via SCCM 2012. is the endpoint protection support windows cluster (especially Hyper-V clsuter)?
Thank you.
When you have operating system installed whether it is Windows Client or Windows Server and whether it is in physical machine or in virtual machine , you need to have Anti-Malware install on top of it.
Anti-Virus is not like any other applications, the statement applies for other applications but Anti-Malware is essential for the system. Just imagine you don't have Anti-Virus on your host and then one of someone accidently install a malware and it will
hit all other virtual machines and if host machine not operate , then its virtual PCs won't operate.
Similar Messages
-
I added a number of folders and files in the excluded files and locations and after that I am unable to access the Antimalware Policies it gives the following error( I am new at sccm):
Unhandled exception occurred in your application. If you click continue the application will ignore this error and attempt to continue. I you click quit the application will close immediately
Object reference not set to an instance of an oblect
With the following details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryPropertySingleItem.get_BooleanValue()
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.Utilities.CreateSCIResultObject(IResultObject antimalwareResultObject)
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.Utilities.LoadDefaultSettingObjects(ConnectionManagerBase connectionManager, Dictionary`2& defaultSettingObjects, DialogType dialogType)
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.HomePageControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SccmPageControlDialog.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18051 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Microsoft.ConfigurationManagement
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.exe
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18022 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18045 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
Microsoft.EnterpriseManagement.UI.ConsoleFramework
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.ConsoleFramework.DLL
Microsoft.ConfigurationManagement.ManagementProvider
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.ManagementProvider.DLL
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.EnterpriseManagement.UI.Foundation
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.Foundation.DLL
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.ServiceModel.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18045 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Web/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll
System.ServiceModel
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18056 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18016 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
AdminUI.SmsTraceListener
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SmsTraceListener.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.EnterpriseManagement.UI.ConsoleFramework.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.ConsoleFramework.resources.DLL
Microsoft.EnterpriseManagement.UI.RibbonConsole
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonConsole.DLL
RibbonControlsLibrary
Assembly Version: 3.5.41019.1
Win32 Version: 3.5.41019.1
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/RibbonControlsLibrary.DLL
PresentationFramework.AeroLite
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.AeroLite/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.AeroLite.dll
Microsoft.EnterpriseManagement.UI.RibbonLayout
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonLayout.DLL
Microsoft.Windows.Shell
Assembly Version: 3.5.41019.1
Win32 Version: 3.5.41019.1
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.Windows.Shell.DLL
Microsoft.VirtualManager.UI.ViewModel.Core
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.VirtualManager.UI.ViewModel.Core.DLL
Microsoft.EnterpriseManagement.UI.Controls
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.Controls.DLL
Microsoft.EnterpriseManagement.UI.RibbonData
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonData.DLL
AdminUI.HelpSystem
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.HelpSystem.DLL
AdminUI.UIResources
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.UIResources.DLL
AdminUI.PersonalFolders
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.PersonalFolders.DLL
AdminUI.ConsoleGlobalSearchView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleGlobalSearchView.DLL
PresentationFramework.Classic
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Classic/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Classic.dll
Microsoft.EnterpriseManagement.UI.Controls.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.Controls.resources.DLL
WindowsFormsIntegration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_4.0.0.0__31bf3856ad364e35/WindowsFormsIntegration.dll
PresentationFramework-SystemXml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemXml/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemXml.dll
PresentationFramework.Aero
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero.dll
PresentationFramework-SystemCore
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemCore/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemCore.dll
UIAutomationProvider
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll
AdminUI.Controls
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Controls.DLL
AdminUI.Common
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Common.DLL
Microsoft.EnterpriseManagement.UI.WpfViews
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.WpfViews.DLL
Microsoft.EnterpriseManagement.UI.ViewFramework
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.ViewFramework.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
AdminUI.WqlQueryEngine
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.WqlQueryEngine.DLL
AdminUI.WqlInitializer
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.WqlInitializer.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.CollectionMenuActions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.CollectionMenuActions.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.OSImage
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.OSImage.DLL
AdminUI.AssetIntelligence
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AssetIntelligence.DLL
AdminUI.SoftwareMeteringRule
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SoftwareMeteringRule.DLL
AdminUI.DcmProperties
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DcmProperties.DLL
AdminUI.UsmPolicy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.UsmPolicy.DLL
AdminUI.ClientAgentSettings
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientAgentSettings.DLL
AdminUI.FirewallPolicy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.FirewallPolicy.DLL
AdminUI.LegacySWD
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.LegacySWD.DLL
AdminUI.ConditionalDeliveryRule
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConditionalDeliveryRule.DLL
AdminUI.VirtualEnvironment
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.VirtualEnvironment.DLL
AdminUI.SideloadKeys
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SideloadKeys.DLL
AdminUI.SoftwareUpdateProperties
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SoftwareUpdateProperties.DLL
AdminUI.Driver
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Driver.DLL
AdminUI.DriverPackage
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DriverPackage.DLL
AdminUI.Subscriptions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Subscriptions.DLL
AdminUI.Queries
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Queries.DLL
AdminUI.SrsReporting
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SrsReporting.DLL
AdminUI.SiteHierarchyVisualization
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteHierarchyVisualization.DLL
AdminUI.SystemStatus
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SystemStatus.DLL
AdminUI.ClientOperation
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientOperation.DLL
AdminUI.ClientHealth
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientHealth.DLL
AdminUI.ContentMonitoring
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ContentMonitoring.DLL
AdminUI.AntiMalware
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AntiMalware.DLL
AdminUI.CloudServiceRoles
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.CloudServiceRoles.DLL
AdminUI.SiteHierarchy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteHierarchy.DLL
AdminUI.SiteBoundaries
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteBoundaries.DLL
AdminUI.ExchangeConnector
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ExchangeConnector.DLL
AdminUI.Addresses
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Addresses.DLL
AdminUI.ActiveDirectory
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ActiveDirectory.DLL
AdminUI.AzureServices
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AzureServices.DLL
AdminUI.RbacUser
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacUser.DLL
AdminUI.RbacRole
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacRole.DLL
AdminUI.RbacCategory
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacCategory.DLL
AdminUI.Package
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Package.DLL
AdminUI.Certificate
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Certificate.DLL
AdminUI.SiteSystems
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteSystems.DLL
AdminUI.HomePageView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.HomePageView.DLL
Microsoft.EnterpriseManagement.UI.WpfViews.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.WpfViews.resources.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.ViewCommon
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ViewCommon.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.AICustomizeCatalog
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AICustomizeCatalog.DLL
AdminUI.AISoftwareProducts
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AISoftwareProducts.DLL
AdminUI.ConsoleView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleView.DLL
AdminUI.External.Controls
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.External.Controls.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
PresentationFramework-SystemData
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemData/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemData.dll
Microsoft.ConfigurationManagement.DialogFramework
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.DialogFramework.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.DialogFoundation
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DialogFoundation.DLL
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
AdminUI.DetailPanel
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DetailPanel.DLL
AdminUI.FeaturesUtilities
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.FeaturesUtilities.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.ConnectionAccount
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConnectionAccount.DLL
System.Runtime.Caching
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll
AdminUI.ConsoleRootActions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleRootActions.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
When I go and check the Endpoint Protection properties it gives me the following Error:
The SMS Provider reported and error
With the following Details:
ConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "ERROR ON Property Convert";
ErrorCode = 0;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspsitesettingitem.h";
Line = 377;
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_SCI_ClientComp WHERE FileType=2 AND SiteCode='CCM' AND ItemName='Antimalware Agent' AND ItemType='Client Component'";
ProviderName = "WinMgmt";
StatusCode = 2147749917;
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
The SMS Provider reported an error.
Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.EndpointProtectionSpynetControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()
System.Management.ManagementException
Unexpected error
Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.EndpointProtectionSpynetControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()Hi,
If you only add one file into the excluded files and locations, does this error still appear?
Could you reproduce this error on another system?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Automatic Install of Endpoint Protection fails on windows 8.1 clients with SCCM 2012 R2
Running SCCM 2012 R2 and deploying CM clients and Endpoint Protection via software updates. CM client and EP install fine on Windows 7 clients. CM client installs fine but endpoint protection fails on Windows 8.1 clients with the following from the
endpoint protection agent log:
<![LOG[Create Process Command line: "C:\Windows\ccmsetup\SCEPInstall.exe" /s /q /policy "C:\Windows\CCM\EPAMPolicy.xml".]LOG]!><time="12:22:02.560+240" date="08-13-2014" component="EndpointProtectionAgent"
context="" type="1" thread="4260" file="epagentutil.cpp:607">
<![LOG[Detail error message is : [EppSetupResult]
HRESULT=0x80070643
Description=Cannot complete the System Center Endpoint Protection installation. An error has prevented the System Center Endpoint Protection setup wizard from completing successfully. Please restart your computer and try again. Error code:0x80070643. Fatal
error during installation.
So on the win8.1 client I run the above command line manually in a command window and receive Access is denied. Then I run the same command in an elevated command window and EP installs fine. Does this have something to do with why the automatic
EP client install fails with the 0x80070643 error code? If so, what is the fix?Hi,
Try uninstalling any other security software.
For more information, please review the link below:
I‘m getting an error code from my Microsoft security software
http://www.microsoft.com/security/portal/mmpc/help/errorcodes.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
We upgraded SCCM SP1 to CU5. We got one primary site, on which we had no problems with running the CU setup. After the upgrade we pushed the new administrator console and client.
SP1 CU5 - console update -> Updated on all administrator users (50 computers)
SP1 CU5- x64 and x86 client update -> Updated on pilot group (50 computers)
No problems so far.
We are having troubles updating the Endpoint Protection Client version. This was V4.1.522.0 before the upgrade. When we enroll a new computer, it receives the new V4.5.216.0, which is the last version.
But we can't update our older clients. We try to deploy the software update (Update for Forefront Endpoint Protection 2010 Client - 4.5.216.0 (KB2952678)) but it doesn't install. After 20 minutes, if I look in the Deployment logs, it says the installation
was successfull; but it isn't, it's still the old version.
Strange thing is, we can upgrade to an inbetween version (Update for Forefront Endpoint Protection 2010 Client - 4.3.215.0 (KB2864366)). Which installs on a test client.
If I look to the cache files of the new EP Client update, and use the UpdateInstall.exe manually, the update does install. Then I see in the logfile EndpointProtectionAgent.log it still refers to the version 4.1.522.0.
EP 4.5.216.0 is installed, version is higher than expected installer version 4.1.522.0. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
Re-apply EP AM policy. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
Apply AM Policy. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
Applied the C:\Windows\CCM\EPAMPolicy.xml with ConfigSecurityPolicy.exe successfully. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
Save new policy state 1 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
State 1 and ErrorCode 0 and ErrorMsg and PolicyName Antimalware Policy and GroupResolveResultHash D277339FA77A9017801399D96266BAD42DE74F38 is NOT changed. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
Skip sending state message due to same state message already exists. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
Firewall provider is installed. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
Installed firewall provider meet the requirements. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
This is the WindowsUpdate.log when I try to push the new EP client.
2015-01-14 11:24:13:651 7416 1c44 Handler :::::::::
2015-01-14 11:24:13:651 7416 1c44 Handler : Updates to install = 1
2015-01-14 11:24:21:716 7416 1c44 Handler : WARNING: Command line install completed. Return code = 0x8004ff25, Result = Failed, Reboot required = false
2015-01-14 11:24:21:716 7416 1c44 Handler : WARNING: Exit code = 0x8024200B
2015-01-14 11:24:21:716 7416 1c44 Handler :::::::::
2015-01-14 11:24:21:716 7416 1c44 Handler :: END :: Handler: Command Line Install
2015-01-14 11:24:21:732 7416 1c44 Handler :::::::::::::
2015-01-14 11:24:21:794 1096 c18 Agent *********
2015-01-14 11:24:21:794 1096 edc AU Can not perform non-interactive scan if AU is interactive-only
2015-01-14 11:24:21:794 1096 c18 Agent ** END ** Agent: Installing updates [CallerId = CcmExec]
2015-01-14 11:24:21:794 1096 c18 Agent *************
2015-01-14 11:24:21:794 2296 fac COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = CcmExec]
2015-01-14 11:24:21:794 2296 fac COMAPI - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
2015-01-14 11:24:21:794 2296 fac COMAPI - Reboot required = No
2015-01-14 11:24:21:794 2296 fac COMAPI - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
2015-01-14 11:24:21:794 2296 fac COMAPI ---------
2015-01-14 11:24:21:794 2296 fac COMAPI -- END -- COMAPI: Install [ClientId = CcmExec]
2015-01-14 11:24:21:794 2296 fac COMAPI -------------
2015-01-14 11:24:21:794 1096 1620 AU Can not perform non-interactive scan if AU is interactive-only
2015-01-14 11:24:26:739 1096 1424 Report REPORT EVENT: {ED287668-4BEF-46FD-BB57-CA17680E5D3B} 2015-01-14 11:24:21:732+0100 1 182 101 {A90C3005-7B59-4268-8B11-12D9BE5C8EA0} 201 80070643 CcmExec Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Update for System Center Endpoint Protection 2012 Client - 4.5.216.0 (KB2952678).
2015-01-14 11:24:27:207 1096 1424 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2015-01-14 11:24:27:207 1096 1424 Report WER Report sent: 7.5.7601.17514 0x80070643 A90C3005-7B59-4268-8B11-12D9BE5C8EA0 Install 101 Managed
2015-01-14 11:24:27:207 1096 1424 Report CWERReporter finishing event handling. (00000000)
Thanks in advance!Hello,
According to
kb2952678:
To apply this update, you must have one of the following installed:
System Center 2012 R2 Configuration Manager Cumulative Update 4 for System Center 2012
Configuration Manager Service Pack
Service Pack 2 for System Center Configuration Manager 2007 and Update Rollup 1 for
Forefront Endpoint Protection 2010
Do you have Update Rollup 1 for Forefront Endpoint Protection 2010?
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
Report to show Endpoint Protection last time updated?
Hello,
I am trying to create a report to show the Endpoint Protection version and the last time it updated. I found this page of different views but non of them include last update:
http://technet.microsoft.com/en-us/library/dn581986.aspx
Does anyone know a way of doing this or is it not possible?
ThanksFor Custom End Point Report, You can check below link
http://blogs.technet.com/b/configmgrteam/archive/2012/03/28/building-custom-endpoint-protection-reports-in-system-center-2012-configuration-manager.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali -
What is correct method to deploy cluster aware technology using HA VMs?
Dear all,
I recently had experience creating Hyper-V Server 2012 cluster. This allows for deploying a highly available virtual machine. That's fine. The business machine (virtual machine) becomes highly available. This includes an existing VM enabled to be highly
available or a new VM installed into cluster from scratch.
On the other hand; we have cluster aware applications (SQL Server, SCVMM etc.) which are installed in clustered OS (Windows 2008 R2 Enterprise edition which has failover clustering service) .
Just for clearing concept; what is correct way of deploying a cluster aware technology (SQL Server, SCVMM) in the scenario where the underlying OS; running in VM(s) can be made highly available.
Method 1:
Create simple non clustered VM, install cluster aware application (SQL Server e.g.). Make this VM highly available using Hyper-V cluster. (This seems to be clustering the VM running cluster aware application, not the cluster ware application; which
requires clustering.)
Method 2:
Create HA-enabled VM onto Hyper-V Servers cluster; install cluster aware application within this HA-enabled VM. (This again; the underlying OS/VM is clustered first, the cluster aware application (SQL server or others) how would it leverage
the cluster?)
Please shed light on what is correct method. In both cases it seems the VM running the cluster aware application; is made highly available; meaning leveraging clustering. What about clustering the application
itself? The objective is to be able to not only make the VM highly available; but also deploy clustered SQL Server or other cluster aware technology using such HA VM.
Regards,
Shahzad.Dear all,
I recently had experience creating Hyper-V Server 2012 cluster. This allows for deploying a highly available virtual machine. That's fine. The business machine (virtual machine) becomes highly available. This includes an existing VM enabled to be highly
available or a new VM installed into cluster from scratch.
On the other hand; we have cluster aware applications (SQL Server, SCVMM etc.) which are installed in clustered OS (Windows 2008 R2 Enterprise edition which has failover clustering service) .
Just for clearing concept; what is correct way of deploying a cluster aware technology (SQL Server, SCVMM) in the scenario where the underlying OS; running in VM(s) can be made highly available.
Method 1:
Create simple non clustered VM, install cluster aware application (SQL Server e.g.). Make this VM highly available using Hyper-V cluster. (This seems to be clustering the VM running cluster aware application, not the cluster ware application; which
requires clustering.)
Method 2:
Create HA-enabled VM onto Hyper-V Servers cluster; install cluster aware application within this HA-enabled VM. (This again; the underlying OS/VM is clustered first, the cluster aware application (SQL server or others) how would it leverage
the cluster?)
Please shed light on what is correct method. In both cases it seems the VM running the cluster aware application; is made highly available; meaning leveraging clustering. What about clustering the application
itself? The objective is to be able to not only make the VM highly available; but also deploy clustered SQL Server or other cluster aware technology using such HA VM.
Regards,
Shahzad.
With SQL Server both M1 and M2 are by far the best solutions. See guest VM cluster is non-optimal as SQL Server works better with own clustering features (AlwaysOn, see link below). And HA would make VM re-boot on another physical host so there would be
both downtime and potential data loss. Run SQL Server in a pair of VMs on a different physical hosts, configue AlwaysOn (use failover SMB share as a witness) and you'll be fine. See:
Overview of AlwaysOn Availability Groups (SQL Server)
http://technet.microsoft.com/en-us/library/ff877884.aspx
How to Build SQL Server
2012 AlwaysOn Hyper-V Virtual Machines
http://social.technet.microsoft.com/wiki/contents/articles/6198.how-to-build-sql-server-2012-alwayson-hyper-v-virtual-machines-for-demos-emu-build.aspx
SQL Server 2012 AlwaysOn High Availability and Disaster Recovery Design Patterns
http://blogs.msdn.com/b/sqlcat/archive/2013/11/20/sql-server-2012-alwayson-high-availability-and-disaster-recovery-design-patterns.aspx
Also the best place to ask about SQL Server High Availability is dedicated MSFT group here:
SQL Disaster Recovery Forum
http://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqldisasterrecoveryHope
this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts. -
SCCM 2012 Endpoint Protection initial update not downloaded
Hi,
I'm new to SCCM 2012. I recently started deploying the Endpoint Protection to all of clients (Windos 7 and XP Pro).
I've noticed that some clients have not been updating their initial definitions after the Endpoint Protection Software is installed.
Since they are not updating their detonation the client remains unprotected with the status icon in red.
The odd thing is that some of our computers do the initial update just fine while others are effected.
Also if I click update manually then the update goes through no issue, but with 100+ clients not updated its not something I want to do manually.
The clients are set to receive auto updates via a auto deployment rule.
Also the antimalware policy is set to do updates as well in this order:
Config Mgr
WSUS
Microsoft Malware Protection Center
Microsoft Update
Has anyone seen this before?
If I need to upload any specific logs just let me know.
Many ThanksDo you have Software update configured (and working) thru ConfigMgr or using a standalone WSUS?
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals -
Steps to install Forefront Endpoint Protection 2010?
I've been searching on how to install Forefront Endpoint Protection 2010 on a Windows Server 2012 R2 Server. I can't seem to find anything about this. Can someone tell me the steps I need to take. I installed SQL 2012, then SCCM
2012, but when I launch the Forefront 2010 installer its saying it can't find SCCM 2007. I take it its not supported in Forefront 2010? Anyways, if there are instructions on how to install the Endpoint Protection and Exchange Online protection I'd appreciate
it.
FernandoHi,
In SCCM 2012 Endpoint Protection 2012 is integrated so you cannot install FEP 2010 in it. Add the Site System role called "Endpoint Protection" on your Primary site server, CAS if you use a CAS and then you are good to go.
the steps are described here:
http://blogs.technet.com/b/anilm/archive/2012/02/19/how-to-enable-configuration-manager-2012-endpoint-protection.aspx
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Pre-Install Endpoint Protection
Good morning.
We have a large number of Windows 8.1 Tablets used by our students. At the end of each course the Tablets are removed form Intune, Re-Imaged and rejoined back to Intune.
The only thing that's causes us a headache is the amount of time it takes to download the Endpoint Protection.
Is it possible to pre-install Endpoint Protection, then when re-joining Intune it just pulls down the latest definitions.
The image we use is updated, Windows and software updates etc, prior to being deployed to the Tablets.
TIA
Mick
PS. Just been thinking, Windows 8.1 Defender looks exactly like Endpoint Protection, so is Intune just using Defender, renaming it and updating it. If so I could just update Defender to the latest definitions .
Would that work!!!!!PS. Just been thinking, Windows 8.1 Defender looks exactly like Endpoint Protection, so is Intune just using Defender, renaming it and updating it. If so I could just update Defender to the latest definitions .
Would that work!!!!!
No. That wouldn't work. The Endpoint Protection client is required and is not the same as Windows Defender.
As for the length of time it tales to enrol, install EP and download the updates, that can be a pain. When I'm doing this I make sure that the devices are using WiFI rather than mobile networks to speed up the process. Then the process really doesn't
take long at all. Other than that there is nothing much that can be done.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
Endpoint Protection Client not running run scheduled scan
Hi,
We are running SCCM 2012 R2 CU1 on our site system and clients, having upgraded from SCCM 2012 sp1 12 months ago.
A few of our clients will not run a scheduled scan, even though it displays the Scan date and time in the client properties.
Someome did create a new EP policy and pointed the clients at it, but that didn't fix this problem.
The AV engine and AV definitions are upto date and the real time monitor is running.
In the SCCM console, Active Clients at Risk, the client has Endpoint Protection Enabled showing as Disabled, nothing in the Endpoint Protection Engine Version, nothing for Last Full Scan Start Time, Endpoint Protection Pending Full Scan - No.
The MPLog-xxxx-xxx.log shows:
Signature updated on 02-11-2015 05:57:13
Product Version: 4.7.205.0
Service Version: 4.7.205.0
Engine Version: 1.1.11302.0
AS Signature Version: 1.191.4588.0
AV Signature Version: 1.191.4588.0
2015-02-11T05:57:15.492Z IWscAVStatus::UpdateStatus() succceeded writing instance with state (1) and up-to-date state(1)
2015-02-11T05:57:15.492Z IWscASStatus::UpdateStatus() succceeded writing instance with state (1) and up-to-date state(1)
2015-02-11T05:57:40.982Z Process scan (postsignatureupdatescan) started.
2015-02-11T05:57:50.420Z Process scan (postsignatureupdatescan) completed.
2015-02-11T06:06:47.173Z AutoPurgeWorker triggered with dwWork=0x3
2015-02-11T06:06:47.173Z Product supports installmode: 0
2015-02-11T06:06:47.173Z Task(Scan -ScheduleJob -RestrictPrivileges) is scheduled to run in 604800000(ms) from now with period 21957080(ms)
2015-02-11T06:06:47.173Z Task(SignatureUpdate -ScheduleJob -RestrictPrivileges) is scheduled to run in 28800000(ms) from now with period 28800000(ms)
2015-02-11T06:06:47.173Z Task(Scan -ScheduleJob -RestrictPrivileges -ScanType 2) is scheduled to run in 86400000(ms) from now with period 70114864(ms)
2015-02-11T06:06:47.844Z Detection State: Finished(0) Failed(0) CriticalFailed(0) Additional Actions(0)
The EndpointProtectionAgent.log shows:
Endpoint is triggered by message. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
File C:\WINDOWS\ccmsetup\SCEPInstall.exe version is 4.5.216.0. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
EP version 4.7.205.0 is already installed. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
EP 4.7.205.0 is installed, version is higher than expected installer version 4.5.216.0. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
Re-apply EP AM policy. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
Apply AM Policy. EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/02/2015 12:12:00 2692 (0x0A84)
Applied the C:\WINDOWS\CCM\EPAMPolicy.xml with ConfigSecurityPolicy.exe successfully. EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
Save new policy state 1 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
State 1 and ErrorCode 0 and ErrorMsg and PolicyName Default Client Antimalware Policy
SCEP Standard Desktop EP Policy and GroupResolveResultHash 5E75089B490B85DD66BBA85BC91E15A5EA853B9C is NOT changed. EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
Firewall provider is installed. EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
Installed firewall provider meet the requirements. EndpointProtectionAgent 11/02/2015 12:12:01 2692 (0x0A84)
Could anyone provide any pointers on why the scheduled scan wont work?
JazHi,
Please verify if any GPO applied and overwrite the setting, you can check registry key:
http://blogs.technet.com/b/mspfe/archive/2013/11/13/system-center-configuration-manager-2012-scep-policy-behavior.aspx
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
ISE and Microsoft System Center Endpoint Protection AV Posture Issues
We are deploying an Enterprise ISE Infrastructure. The Customer has adopted Microsoft System Center Endpoint Protection ver 4.x as its approved AV. NAC Agent detects the AV. It however has issues detecting the Definition Files.
See Log File below:
7721: XXXX-JOSE-W54: Aug 22 2014 11:03:00.624 UTC: %NACAGENT-6-OPSWAT_PROD_ENG: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: ID: MicrosoftAS - Product Engine Version, Result: rcInternalError
7722: XXXX-JOSE-W54: Aug 22 2014 11:03:00.624 UTC: %NACAGENT-6-OPSWAT_DAT_FILE_VER: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: ID: MicrosoftAS - Product File Version, Result: rcInternalError
7723: XXXX-JOSE-W54: Aug 22 2014 11:03:00.624 UTC: %NACAGENT-6-OPSWAT_DAT_FILE_SIG: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: ID: MicrosoftAS - Product Data File Sig, Result: rcNotSupported
7724: XXXX-JOSE-W54: Aug 22 2014 11:03:00.624 UTC: %NACAGENT-6-OPSWAT_DAT_FILE_TIME: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: ID: MicrosoftAS - Product Data File Time, Result: rcInternalError
7725: XXX-JOSE-W54: Aug 22 2014 11:03:00.624 UTC: %NACAGENT-6-OPSWAT_DEBUG: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: OPSWAT AV/AS Retrieval Time(sec) Info for MicrosoftAS: total=0.0000, pid=0.0000, vendor=0.0000, desc=0.0000, vsn=0.0000, type=0.0000, engineVsn=0.0000, dataFileVsn=0.0000, sig=0.0000, dataFileTime=0.0000
7726: XXXX-JOSE-W54: Aug 22 2014 11:03:00.640 UTC: %NACAGENT-6-OPSWAT_DAT_FILE_SIG: %[sev=info][prodtype=AV/AS][func=OpswatChecks::GetAllAVInfo]: ID: MicrosoftAV - Product Data File Sig, Result: rcNotImplemented"
NAC Agent version is 4.9.4.3 and CM version 3.6.9186.2Hi,
Yes you can install the Endpoint Protection Client in the image, the process for doing this is described here:
http://technet.microsoft.com/en-us/library/dn236350.aspx You can configure it manually to use Windows Update as the source for definition updates before the imaging as well then you should
be good to go.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Collection Alerting for Endpoint Protection and Client Status
both for the Client Status alerts and for the Endpoint Protection alerts I have set these up on one collection each,
the thing is if you go to the Client Status node under monitoring, by default the collection 'All desktop and server clients' is selected, while this one doesn't even have the alert configured
same goes for endpoint protection, where by default the collection 'All client Systems' is selected ...
what is the purpose of configuring a specific collection for the alerting, if you have to select this every time you look at the monitoring?
try to explain that to customers..The purpose of configuring alerts for different Collections is that you can have e-mails send to different Groups. When you create subscriptions you can select the different alerts and configure them to mailed to different Groups.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals -
Endpoint Protection Managed Workstations: Antimalware policy application failed
Hello,
When looking at the Endpoint statistics I have the line for systems failing to apply policy. An easy fix to this is to delete the registry.pol file. I would like to make a collection that automates this task for me. Basically if it reports back failure,
it gets added to a collection, an advertisement runs on it to fix it and redeploy the policy.
The only thing I need to know is the query behind the "Endpoint Protection Managed Workstations: Antimalware policy application failed" so I can make a collection for it. Does anyone happen to know it?
ThanksClient logs:
Client 1:
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
Failed to apply policy with error 0x80004005, retry number : 1 after 60 second. EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
Failed to apply policy with error 0x80004005, retry number : 2 after 60 second. EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
Failed to apply policy with error 0x80004005, retry number : 3 after 60 second. EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
Failed to apply policy with error 0x80004005, retry number : 4 after 60 second. EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
Failed to apply policy with error 0x80004005, retry number : 5 after 60 second. EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:32:00 PM 2056 (0x0808)
Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
State 2 and ErrorCode -2147467259 and ErrorMsg Failed to open the local machine Group Policy and PolicyName Antimalware Policy and GroupResolveResultHash 23496E87C22E7CA5048254CC04CCF582A084C108 is NOT changed. EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
Client 2:
Apply AM Policy. EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
Failed to generate AM policy XML with error code 0x8000ffff EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
start to send State Message with topic type = 2002, state id = 2, error code = 0x8000ffff, and message = <Instance><AppliedAmPolicies/></Instance>
EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
Start to send state message. EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
Send state message successfully EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Firewall provider is installed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Installed firewall provider meet the requirements. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Endpoint is triggered by WMI notification. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
File C:\Windows\ccmsetup\SCEPInstall.exe version is 4.3.215.0. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
EP version 4.3.215.0 is already installed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Expected Version 4.3.215.0 is exactly same with installed version 4.3.215.0. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Handle EP AM policy. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Apply AM Policy. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Failed to generate AM policy XML with error code 0x8000ffff EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
State 2 and ErrorCode -2147418113 and ErrorMsg Failed to load WMI instances. and PolicyName Antimalware Policy and GroupResolveResultHash 2B22C160D3BC8DC4BECF08D4F632D4756D4C9622 is NOT changed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
Client 3:
Apply AM Policy. EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
Failed to apply policy with error 0x80004005, retry number : 1 after 60 second. EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
Failed to apply policy with error 0x80004005, retry number : 2 after 60 second. EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
Failed to apply policy with error 0x80004005, retry number : 3 after 60 second. EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:29:00 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:29:01 PM 1768 (0x06E8)
Failed to apply policy with error 0x80004005, retry number : 4 after 60 second. EndpointProtectionAgent 11/3/2014 12:29:01 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
Failed to apply policy with error 0x80004005, retry number : 5 after 60 second. EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
State 2 and ErrorCode -2147467259 and ErrorMsg Failed to open the local machine Group Policy and PolicyName Antimalware Policy and GroupResolveResultHash 23496E87C22E7CA5048254CC04CCF582A084C108 is NOT changed. EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
I have 12 systems total having issues with Policy right now. -
Overview of SCCM and Endpoint Protection...
I'm very new to the whole SCCM environment and I'm having the damnedest time finding just basic information concerning SCCM and it's separate modules. I have three basic questions that I hope someone here can answer before I move forward with anything to
do with SCCM:
1. My main need at this time is to deploy the Endpoint Protection portion to all of the machines in our Domain. Does EP require the Configuration Manager to get the central administration I'm looking for?
2. Can modules be added to SCCM any time? For example, if I were able to just get the Endpoint Protection installed now, could I add the rest of the suite later?
3. Where can I find installation instructions for SCCM, Configuration Manager and Endpoint Protection?
Thanks
Brian Brehart Network Administrator SurePayroll, Inc.1. Yes, to manage Endpoint Protection, you need ConfigMgr.
2. ConfigMgr has many different roles (but not separate modules) which can be implemented later like Application Management and Operating System Deployment.
3. You can find detailed step-by-step guides that are meant to help a person learn the product.
http://gerryhampsoncm.blogspot.com/2013/02/sccm-2012-sp1-step-by-step-guide.html
http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/
However, these guides are not prescriptive for the real world, just learning. ConfigMgr is arguably one of the most powerful and complex tools that Microsoft sells. Consider engaging an experienced consultant to architect and implement it, and/or
take an in person training course.
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer. -
Endpoint Protection Role fails after SCCM 2012 SP1 upgrade 0x8004ff84
We have been in the process upgrading our SCCM RTM to SP1 in order to get to R2 in the end. After upgrading the PRimary Site server to SP1 it seems the Endpoint protection update did not succeed. I removed the role and after that tried it to install again,
results below.
EPSetup.log
I<09/26/14 14:24:25> Installing the SMSEP
<09/26/14 14:24:25> Passed OS version check.
<09/26/14 14:24:25> File E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe version is 4.4.304.0.
<09/26/14 14:24:25> EP version 2.2.903.0 is already installed.
<09/26/14 14:24:25> EP 2.2.903.0 is installed, version is lower than expected installer version 4.4.304.0.
<09/26/14 14:24:25> Invoking process "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml"
<09/26/14 14:24:25> CreateProcess: E:\BO\Microsoft Configuration Manager, "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml"
<09/26/14 14:25:00> CreateProcess: -2147156092
<09/26/14 14:25:01> SCEPInstall.exe returns 0x8004ff84
<09/26/14 14:25:01> SMSEP could not be installed. The return code was -2147156092
<09/26/14 14:25:02> ~RoleSetup().
When I manually try to run the SCEPInstall.exe setup asks for certain msi files it cannot find. Anyone seen this behaviour before? I'm not able to find information on this one.It seems the uninstallation of the current SCEP client fails. It uses the new SCEPinstall.exe version to do the uninstall which fails. I copied the old version from another computer and used that to do the uninstall manually scepinstall.exe /u
It asks a few times for a location to find the msi files used to do the uninstallation. You have to point at a temporary map created at the drive root location. The Uninstall succeeds.
Now the Endpoint Protection role can be added again and will also succeed.
Maybe you are looking for
-
Hi everybody! I reinstalled the windows on my T60 and didn't have any problem with my Intel PRO Wireless 3945ABG adaptor. After one day it stopped working. The small green light for it doesn't turn on anymore, even if a press fn+F5. I tried to reinst
-
dear all: 1, the user's requirement is below: the project have a budget. When exceed budget, system auto send a message to the relevant person in charge (such as: project managers, financial, WBS responsible person, etc.) FYI: workflow can't meet th
-
Hi, I have this message on almsot all sites ( sites of videos or cam): To view this page ensure that Adobe Flash Player version 11.1.0 or greater is installed. I have the last version 11 8 800 94. I have try to uninstall and reinstall but its change
-
CacheGetDNForName: NWDSReadObjectInfo returned -601
Hi, I did install 2 radius servers. 1 server is good. and the other server is so bad. what's '-601'...???? help me...!!! [2004-12-04 00:33:56 AM] CopyCache: [2004-12-04 00:33:59 AM] CopyCache: [2004-12-04 00:34:02 AM] 5) [(ip) 123.456.789.000:16384],
-
Installation from ZIP or native package??
Hi guys, i have installed DSEE 6.3 from ZIP package for Solaris 9 Sparc and all the components are working fine... But i came to know that the "directoryserver" command is not present under /usr/bin... The unix guys feel that maybe the Native package