Search the Community

Hello all, I was wondering if anyone knew a way to automatically sync the SCEP definition to SCCM without needing to reboot. For instance, the SCCM console shows me that my server has the endpoint definition of 1.215.422.0 but after checking locally I have 1.215.565.0. This inaccurate result is throwing off my reports. If I reboot the server in question then SCCM shows the correct version. Is there another way to get this to sync without a reboot?

Hi guys, I wondered if someone here can provide clarity regarding update sources for the SCEP client as I've hit a brick wall this side of the wire! We have implemented the EPP role, configured AMW policies and deployed, setup ADR and tested and up until recently had no issues with SCEP or AMW update functionality. The SCEP clients are now failing to update their definitions. The updates sources, and order, are: 1. SCCM 2. Microsoft Update Clients fail to update and provide the following error: CODE: 0x8024402c MESSAGE: System Center Endpoint Protection couldn't install the definition updates because the proxy server or target server names can't be resolved. Having removed Microsoft Update from the Update Sources (as I believe there's no route to it), clients update their policies and now receive their updated definitions. When I examine the MPxxxxxx.log in ProgramData\Microsoft\Microsoft Antimalware\Support, it shows that the definitions were updated via MMPC. This causes a quandary because it isn't in the sources list. I think my question is relatively straight forward... Are the definitions being updated from SCCM but incorrectly reported as MMPC or is there a default position within SCEP 2012 whereby it checks the MMPC regardless of what the configuration is set at? Thanks, Ian.

I've been reading the somewhat complete documentation on SCCM 2012, but I'm having a difficult time understanding the definition for: Package - Application - Deployment Packages - I think I have somewhat of an idea for "package" - a group of files that do not have an installation/setup routine (hence you can't run a setup.exe). Application, from what I gather, is a group of files that do have an installation/setup route (hence you can run a setup.exe/msi). Deployment package - I'm not even going to attempt it. Do applications become a package, or a deployment package, at any given time?