I got an idea to use the SCCM Dashboard to present the status from the Forefront Endpoint Protection 2010 . The FEP Dashboard in the SCCM console is based on Collection membership so I opened SQL Management Studio to get the SQL queries for the Collection Membership and use them i the SCCM Dashboard. However
Finally the long awaited update for USMT 4 to support Office 2010 migrations is realeased! This means that finally it will be possible to get the OSD refresh and prelace scenario to work with Office 2010 settings as it works with the other Office versions! For more information see: USMT 4 Update Released to Support Office
When deploying the FEP client during OS Deployment the normal command line used to install the FEP client doesn’t work, the recommendation is to use the following command instead ”Fepinstall.exe /q /s”, see this article for more information http://social.technet.microsoft.com/wiki/contents/articles/how-to-deploy-fep2010-client-via-osd-and-test-deployment.aspx I have deployed the FEP client a couple of times now and I have had some
I have done some FEP installations now and a couple of questions always turn up like how to delegate permissions in the SCCM console for the FEP integration as there isn’t a new security delegation option created for it when installing the plugin for the SCCM Admin Console. I did some research for the different components and
This is a very annoying but really easy to fix feature of two reports in Configuration Manager 2007, the two reports used to report on software registered in Add/Remove Programs on clients: Computers with specific software registered in Add Remove Programs (nr 92) Software registered in Add Remove Programs on a specific computer (nr 93) Shows duplicates
I have installed Forefront Endpoint Protection 2010 a couple of times now and I must say that the system requirements document on Technet has a complete list of pre-req’s, read it before starting the installation. http://technet.microsoft.com/en-us/library/ff823830.aspx The installation it self is really straightforward if all the system requirements are fulfilled. However almost every installation of either the server
A colleague of mine ran into this interesting little problem the other day and I thought I would share the solution here. The setup used is SCCM 2007 Sp2/R2 installed on a Windows 2008 R2 server with package source-files located on a Windows 2003 server share. When distributing packages the following errors where recorded in the distmgr.log
When doing a new installation of System Center Configuration Manager there are a number of hotfixes I always install as I mentioned earlier on my blog. A couple of them includes a client hotfix which needs to be installed on all the client either during OS deployment or another way of deploying the client for
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRejectRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
