Jump to content


jeffpoling

Established Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jeffpoling

  • Rank
    Member
  1. Tay, Thanks. I made that adjustment to our policy and will see if that makes a difference. I don't know why the clients would be seen as offline, but it is definitely a possibility as a cause for the extra scans. Thanks again, Jeff
  2. Thanks. I generated the CAB file and poured over the log files. I can clearly see the "Extra" scan kicking off, but there is absolutely no explanation as to why, I am sure I must be missing something or perhaps encountered a bug. As for the state of the systems during the actual scheduled scan, they were all on and available. The client GUI showed that the last scan completed successfully and the "extra" scan kicked off any way. Thanks again, Jeff
  3. Ok. I verified in the EndpointProtectionAgent.log file that the correct antimalware policy is applying to the machines. I also looked at the MPLog*.log in C:\ProgramData\Microsoft\Microsoft Antimalware\Support. One thing that stands out in that log is a statement about "Run lost scheduled job" Here is a snip of that log: **************************END RTP Perf Log************************* Signature updated on ?Wed ?Oct ?24 ?2012 03:14:31 Product Version: 3.0.8410.0 Service Version: 3.0.8410.0 Engine Version: 1.1.8904.0 AS Signature Version: 1.139.410.0 AV Signature Version:
  4. We are piloting System Center Endpoint Protection 2012 in our environment. On several of the pilot PCs, a scheduled scan runs per our antimalware policy; however, two days later, another full scan kicks off and runs through the day. Our policy is configured for a full scan to happen on Sundays at Midnight. Has anyone experienced this? How do I troubleshoot why the scan is initiating outside of the parameters in the policy? Thanks, Jeff
  5. For the last several days, past USMT migration data is not being cleaned up from the state migration point. Looking at the SMP log, I found this: CheckAndDeleteSMPStores failed with error code (80070003) A quick search revealed this to be a problem in COnfigMgr 2007, but I can't find anything related to 2012. Has anyone seen this? Any ideas on what to do? Thanks, Jeff
  6. We had an issue with our StateMigrationPoint today that caused one machine to have an issue with the USMT capture and restore process. The error returned on the PC was: The task sequence execution engine failed executing the action (Release State Store) in the group (USMT Capture) with the error code 16389 Action output: anced RSA and AES Cryptographic Provider (Prototype). Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic
  7. Yes, I exported the certificate on the SCCM server and imported it on the workstation where I am running the report. Are you familiar with using the certificates MMC? A quick summary: To export the certificate on the SCCM server: 1. Open MMC on the SCCM server 2. Add the certificates snap-in for the local computer 3. Browse to the personal node 4. Find the machine certificate for the sccm server 5. Right click and choose export. No need to export the private key 6. Step through the wizard, saving the cert in CER format 7. Copy the exported certificate to your work station.
  8. In my case it was related to SSL certificates. Our SCCM deployment is using a self-signed cert. So, I had to export it and import it to the trusted root certificate authority node on my PC where I am running the report.
  9. I am running into this as well. Did you resolve it? Thanks, Jeff
  10. I ended up combining the images into a single WIM file. Doing so worked around the issue. Thanks, Jeff
  11. I have a task sequence that includes two operating system images. Variables are used to determine which image gets applied. I need to create task sequence media for this task sequence; however, it is failing when it stages the second operating system image: Staging OS Image Package SAL00017 CreateTsMedia 7/2/2012 3:58:18 PM 584 (0x0248) Media Remaining Space before executing state is 33667 Mb CreateTsMedia 7/2/2012 3:58:18 PM 584 (0x0248) File splitting is required because file size exceeds max file size. CreateTsMedia 7/2/2012 3:58:18 PM 584 (0x0248) Total file size is 8905 MB, ma
×
×
  • Create New...