Integrating SCCM 2012 SP1 Endpoint Protection Manager with SIEM

Team,
Does anyone know how to expose the central SCCM antimalware reporting data to external sources? I would like to take all centrally collated security events and load the data into Arcsight express, e.g. client malware detection events. Are all
client security events logged in a file on the SCCM server before being copied to the SQL database? Or do I have to read a SQL table to get this information? Any help greatly appreciated.
Cheers
Rod

Hi,
You will have to read that from the ConfigMgr database views, start by having a look a the SCCM_EXT.vex_EP_AntimalwareInfectionStatus view.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Similar Messages

Using the pre-configured SCCM 2012 SP1 endpoint protection templates for Exchange 2010?

I am looking to update the exclusions for SCCM Endpoint Protect clients performing server AV protection on Exchange 2010 nodes.
Within SC there are a number of pre-defined templates, including ones for Exchange 2007 / 2010. However when I analyse these they do not appear to list all the exclusions that the Exchange product team define on TechNet -
http://technet.microsoft.com/en-us/library/bb332342(v=exchg.141).aspx
So do I;
1 - Use the template as it has been verified by Microsoft for using with Exchange 2010 and it covers all I need to exclude?
2 - Edit the template, adding in the additional exclusions as defined by the Exchange product team?
Would whichever logic I use apply to other templates, such as SQL, SharePoint, etc as well?
Thank you
Alan

As I cut and pasted the xml file I noticed the following comment that I had missed before..........
        
        
        
Still going with adding the full recommended list from TechNet though

SCCM 2012 SP1 CU4 ccmsetup runs with SMS Agent Host on the "Service" mmc after upgrading the client to CU4.

Dear Brothers,
I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:
Scenario:
1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.
2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.
Issue:
After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host"
at the Service MMC. Which I believed this is very unusual behavior.
The Client however it seems properly installed and working please see below details:
Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.
1. How can I resolved this issue?
2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?
3. Or this is a normal behavior for the scenario?
Advance thanks for your future replies, my brothers in technology.

Dear Brother,
2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed
the issue .
CCMsetup.log
==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
Ccmsetup command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628
(0x15FC)
MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
2. Checks the desktop client version and gets the installation direcotry.
3. Stops remote control and other desktop components.
4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
Action: InstallFiles.
ErrorMessages:
Internal Error 2902. ixfAssemblyCopy
7/1/2014 7:15:33 PM 5628 (0x15FC)
A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)
Regards,

SCCM 2012 SP1 - Vendors or Publishers with multiple spellings or formatting

Hey all,
When trying to do reports by Vendor for example, how can we deal with the fact, for example, that the employees at Adobe are not applying the company name incorrectly.
When I go to the All Software Companies report I find that there is
Adobe Systems Incorporated
Adobe
Adobe System Incorporated
Adobe Systems
Adobe Systems Inc
Adobe Systems Inc.
Adobe Systems Incorporaetd [Realy, it is spelled incorrectly]
Adobe Systems Incorporated
Adobe Systems Incorporated.
Adobe Systems, Inc
Adobe Systems, Inc.
Adobe Systems, Incorporated
Adobe Sytems Inc. [Another mispelling]
Adobe Sytems Incorporated [Another misspelling]
Heck, even Microsoft has this issue.
And ever duplicates that may or may not be there.
How has anybody been dealing with this? It's annoying to have to deal with this when trying to do any sort of drilling down through various canned reports.
I was thinking about creating a little process that goes through the registry in attempts to find the typographically incorrect names and if found replace with with something more commonplace.
Thanks for the discussion on this issue.

Hey Jason,
Got to say, I looked over the link and it took me a while to finally grasp the scope of where that "Set Names" was it. I tend to leave anything that says "Default" in some areas of System Center alone; mostly because there may not be
an option available to reset back to default. I would have hoped that when I made a client policy, as suggested in the documentation that all settings would be carried over to it, much like creating a group policy. Is it normal to edit the Client Default Settings?
As the documentation says "You can also configure custom client settings, which override the default client settings when you assign these to collections. For information about how to configure client settings, see
How to Configure Client Settings in Configuration Manager." I guess somebody in the user interface department missed that bit about overriding default client settings with custom
settings because custom settings do not have all the settings; such as Set Names. And hey, I found a post
http://social.technet.microsoft.com/Forums/en-US/41285bd4-e5b2-4a75-94ce-02669e5df592/sccm-2012-how-i-can-reset-default-client-settings-policy-?forum=configmanagerdeployment" So it would appear that there is no way to reset to default settings should
something get way out of hand.
Why inventory EXEs? I thought about that and wanted to know what EXEs are on a computer, from what I understand about software inventory, and perhaps this is from my scripting days. I saw lots of people, in the past, ask how they can use VBS or WMI
for example to do software inventory, the usual stock answer is something like "wmic product"; which only returns products installed by an MSI source, while non-MSIs usually end up in the registry in either Install or Uninstall area, or both
as well as MSIs ending up there. Perhaps I don't need to inventory EXEs, but it's there, and I would like to know what computers potentially have an EXE on them that I might want to look for. For example there are plenty of applications that install
without an install method; they just simply get themselves copied by the user or some hack of an installer. I don't go trolling through the reports, but there is an occasion where I may want to see if a computer has an EXE, and if I'm lucky the path
to the EXE is also captured so that's a bonus, right? I could potentially use that information to find an EXE that is in a user's AppData folder, for example. Right? A virus, or a bit of spyware that the AV product may not know about.
For example; here's a script that claims to inventory software -
http://gallery.technet.microsoft.com/scriptcenter/Software-Inventory-of-f66b5bdc
- The Win32_Product
WMI class represents products as they are installed by Windows Installer. A product generally correlates to one installation package. (from
http://msdn.microsoft.com/en-us/library/aa394378(v=vs.85).aspx).
What about products not installed via the Windows Installer? Pointless. Is that what SCCM does as well? Or does it look in the registry combining both Win32_Product and what is in the Uninstall/Install registry hive? Working with a school district I've installed
a lot of software that doesn't use the Windows Installer.
I did find these posts interesting -
http://social.technet.microsoft.com/Forums/en-US/23c875b4-0e1e-406d-b28f-ee082a20bbf2/default-software-inventory-not-collecting-any-data-from-client?forum=configmanagergeneral
It was interesting in that I was having a similar issue where nothing was showing up until I added scan the exes, but maybe that's a coincidence.
And finally -
http://technet.microsoft.com/en-us/library/gg682067.aspx#BKMK_SoftInventoryDeviceSettings
Taking note of the option to inventory file types within Microsoft's own documentation. A useless feature? Hmm. And why not? Take a look at this -
https://www.grc.com/oo/program.htm. You will notice that it says there is nothing to install, just run it. Okay, so what there applications follow the just download and run, no need to install it. Sure GRC is
a security site, but if some user thought it might be good to have it, and they ran it, and started having issues with something that doesn't do traditional installing then we as IT don't have a real clue as to what is really on a user's system.
You'll have to forgive me, but if Microsoft created a feature, why not use it? It's like the age old debate as to - Should I keep my computer on, or should I turn it off. Should I deploy images via SCCM using multicast or not.

SCCM 2012 R2 - Endpoint Protection is greyed out

Somehow the Endpoint Protection menu is greyed out for me. It was setup and we use it to do a quick scan on user's machine when needed. All of the sudden, it's being greyed out. Does anyone knows how to fix this problem?

Hi,
Have you seen this thread?
Right click on a server endpoint greyed out
http://social.technet.microsoft.com/Forums/en-US/efe34496-8cf2-4fe7-9074-83221bf8bf9e/right-click-on-a-server-endpoint-greyed-out?forum=configmanagersecurity
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.

Backup Sharepoint 2013 SP1 Farm with SQL 2014 RTM "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
Igor

This is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to convert Unmanaged SCEP clients to Managed in SCCM 2012 SP1

We recently started installing SCEP clients from the .exe and a preconfigured .xml file to client machines in a domain setting. This was done from a USB drive, going from machine to machine, with a .bat file.
This was a stop-gap until we were able to install and configure SCCM 2012 SP1.
PCs that already had the SCEP client (prior to SCCM coming into production) are showing up as unmanaged. PCs that have had SCCM install SCEP all are listed as managed.
I've searched, but have yet to find a definitive answer as to how get the manually installed SCEP clients to register as managed in SCCM.
AD Domain with WIN 2008 R2 DC, SQL 2012 Standard, SCCM 2012 SP1

Also, make sure the Endpoint Protection Point is installed properly on SCCM and the Client Setting for SCEP is enabled.
Juke Chou
TechNet Community Support

Management Point fails after installing SCCM 2012 SP1

I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
1. Newly built Windows Server 2012 box
2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
[19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
[19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
[19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
[19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result.
Would really appreciate some help if anyone's fixed this issue

I'm still struggling, I've uninstalled MP
<04/16/14 08:06:59> SMSMP Setup Started....
<04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
<04/16/14 08:06:59> Deinstalling the SMSMP
<04/16/14 08:06:59> No versions of SMSMP are installed. Returning Success.
<04/16/14 08:06:59> ~RoleSetup().
Ran the command, Invoke-Command {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
Checked Namespace Instances to ensure '= ccm' is not longer there.
Rebooted Server and re-installed MP but it still fails
<04/16/14 08:37:26> ====================================================================
<04/16/14 08:37:26> SMSMP Setup Started....
<04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
<04/16/14 08:37:26> Installing Pre Reqs for SMSMP
<04/16/14 08:37:26> ======== Installing Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP
<04/16/14 08:37:26> Pre Req MSXML60 found.
<04/16/14 08:37:26> No versions of MSXML60 are installed. Would install new MSXML60.
<04/16/14 08:37:26> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
<04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
<04/16/14 08:37:26> Pre Req SqlNativeClient found.
<04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
<04/16/14 08:37:26> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Installing the SMSMP
<04/16/14 08:37:26> Passed OS version check.
<04/16/14 08:37:26> IIS Service is installed.
<04/16/14 08:37:26> No versions of SMSMP are installed. Installing new SMSMP.
<04/16/14 08:37:26> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE
SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04/16/14 08:37:26> mp.msi exited with return code: 1603
<04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
<04/16/14 08:37:26> ~RoleSetup().
On checking I don't seem to have anything in IIS, no default web site.
I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
Any assistance would be greatly appreciated.
Thanks

Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

Hi,
I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily.
I just installed Office 2013 on this system and have activated it as necessary. The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM. I have other systems with
Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
What can I check to try and determine what the problem is?
Thanks in advance,
Nick

Yes, the 8.1 system is a member of collection where the update deployment is targeted.
Are there any specific logs I should check in the client? If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

How to configure SNMP on all managed client using SCCM 2012 SP1

hi ,
do you know How to configure SNMP on all managed client using SCCM 2012 SP1?

As a side note, I made an interesting discovery last week: the SNMP Service is deprecated in Windows Server 2012. Why would you want to use SNMP on an actual Windows OS though? There are far better ways available to monitor Windows. I'm sure that lines
up with why they deprecated it.
Jason | http://blog.configmgrftw.com

Backup Sharepoint 2013 Farm with SQL 2012 "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 Farm with SQL 2012 "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find confirmation anywhere.
Regards,
John

Per this thread
http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup, no it does not look like this is supported.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

DP Job queue manager not working- SCCM 2012 SP1

I am getting below error when trying to open DP job queue manager in sccm 2012 SP1
Please find the details information
see the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException:
Invalid query
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at DPJobMgr.Form1.SummaryRefresh_Click_real(Object sender, EventArgs e)
   at DPJobMgr.Form1.SummaryRefresh_Click(Object sender, EventArgs e)
   at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.TabControl.WmSelChange()
   at System.Windows.Forms.TabControl.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.1008 (RTMGDR.030319-1000)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
DPJobMgr
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/DPJobMgr.exe
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1002 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1001 built by: RTMGDR
    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.1001 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
Microsoft.ConfigurationManagement.ManagementProvider
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/Microsoft.ConfigurationManagement.ManagementProvider.DLL
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Data.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1015
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Data.Linq.dll
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    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.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/AdminUI.WqlQueryEngine.DLL
System.Configuration
    Assembly Version: 4.0.0.0
   Win32 Version: 4.0.30319.1015 (RTMGDR.030319-1000)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1015 built by: RTMGDR
    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.237 (RTMGDR.030319-2300)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.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.

Hi,
That is as expected, the new tools require Configuration Manager 2012 R2 to work. From the download page of Configuration Manager 2012 R2 toolkit.
"Note: Items with an * are new in the R2 Toolkit and require Microsoft System Center 2012 R2 Configuration Manager for full functionality.
Server Based Tools
* DP Job Manager - A tool that helps troubleshoot and manage ongoing content distribution jobs to Configuration Manager distribution points.
* Collection Evaluation Viewer - A tool that assists in troubleshooting collection evaluation related issues by viewing collection evaluation details.
* Content Library Explorer - A tool that assists in troubleshooting issues with and viewing the contents of the content library"
So you need to upgrade to R2 before you can use the new tools.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Will SCOM 2012 R2 co-exist with SCCM 2012 SP1

Hi. Sorry if the answer is obvious, but I need to ask...
Will SCOM 2012 R2 coexist with SCCM 2012 SP1?
We currently have SCOM 2007 R2 installed and we'd like to upgrade.
We installed SCCM 2012 close to 2 years ago and upgraded to SP1 last summer.
We had SCOM 2007 R2 integrated with SCVMM 2008 R2, but have upgraded to SCVMM 2012 SP1 recently - so there is nothing setup between SCOM and SCVMM.
There is currently nothing setup between SCOM and SCCM.
We're a single forest, single domain shop. Ideally, we'd like or System Center products to "work together", thus the question about the 2012 SP1 and R2 mix.
Thanks for any input. I appreciate your time and expertize. Joe.

Hi,
I concur with Alexey, a side note SCCM and SCOM do not use the same SQL Server.
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.

[Forum FAQ] Management Point fails after installing SCCM 2012 SP1

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

SCCM 2012 SP1 is Running on SQL Server 2012 with NO CU

I am working in an org that has SCCM 2012 SP1, it is and always has been running on SQL Server 2012 RTM, with NO CU installed it seems (judging by the file versions 11.0.2100.60, which are not the same as as documented here http://support.microsoft.com/kb/2703275).
sigh..........
So before I upgrade to R2 I will ensure I installed SP2 and CU3 onto SQL Server.
However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum and what damage may have been done as a result of this configuration?
Are there any actions that can be performed as remediation or health check?
Can anyone speculate?

However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum
Because the Microsoft product group decided it that way. All supported SQL versions are listed here:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig
Damage? Hard (impossible) to tell. You would have seen errors in various components if there were problems.
Torsten Meringer | http://www.mssccmfaq.de

Integrating SCCM 2012 SP1 Endpoint Protection Manager with SIEM

Similar Messages

Maybe you are looking for