Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Chadddada

  • Rank
  1. I seem to be getting a fairly common generic error but with possibly with a slight difference then some of the other problems/answers I have seen. Generally it looks like this is a DNS issue but I am not sure in my case. Let me 1st describe my infrastructure and what I am trying to accomplish. We use PKI on the main MPs/DPs. I have another DP that I will use for OSD content that won’t use PKI. I am 1st attempting to use boot media, vs PXE, to image a computer. I have distributed the content to the DP, created a boot media USB and everything looks good there as far as I can tell. My b
  2. I just stood up a SCDPM 2012 SP1 server and I am having an issue pushing an agent. I suspect that it is a firewall issue in the datacenter, between different subnets, but I am trying to verify that. I have been using a helpful guide that I found http://blogs.technet.com/b/dpm/archive/2012/02/06/data-protection-manager-agent-network-troubleshooting.aspx . I seem to be OK going from the DPM server to the computer I want to protect, but there seems to be an error communicating back. Should I have a successful WBEMTEST going from the protected server to the DPM server? That part fails. I pre
  3. Figured out what our problem was, but trying to replicate the issue. We took the EP settings out of default and moved them to their own client setting policy. That client setting was applying to the collection but for some reason wasn't taking. We re-linked it and it seems to be working now <buggy?>.
  4. Giving this a bump as I am seeing / having this issue as well. Any thoughts out there on this?
  5. EP is installed, version is higher than expected installer version 4.1.522.0 Has anyone see that in the EndpointProtectionAgent.log on a system they have been trying to push the SCCM client to before? We have a number of servers that haven't reported back to SCCM that their Endpoint Protection is being managed. Looking at the log noted above has that error. A snipped from the log: A few of these systems were previously manged under a dev SCCM 2012 SP1 install, and some under FEP 2010. Now we are deploying from a new SCCM site that we have setup to these servers.
  6. It looks like this might be a version of EP for sharepoint that is being left behind...
  7. I should see "Microsoft Forefront Server Protection" disappear after SCEP installs, right? After AV is being managed by SCCM?
  8. Yes, I have the client settings configured to remove previously installed AV. Looking at one of the managed servers now, I see 'Microsoft Forefront Server Protection' listed under programs as well as 'System Center 2012 Endpoint Protection'.
  9. Hello, I have been installing Config manager clients on servers I want to manage. These servers already had Forefront 2010 installed and being managed by the FEP server. When I log into a server I see that FEP 2010 is still listed under programs as well as the ConfigManger stuff. Is the FEP 2010 supposed to be manually removed or is this supposed to be automatically overwritten / uninstalled when I elect to use SCEP? Please let me know if you need more information.
  • Create New...