Deploying FEP manually, then later controlling with SCCM

Answered Deploying FEP manually, then later controlling with SCCM

  • Tuesday, February 05, 2013 10:14 PM
     
     

    We have a scenario where our old AV licenses will be expiring and we'll be eventually going to a SCCM controlled FEP solution.  In the meantime, I'd like to bridge the gap by installing FEP2012 manually (no management) to our clients.  How hard would it be to then, at a later date, to make those clients be under the control of SCCM?  Would it require uninstalling and reinstalling the clients, or can SCCM see the clients and then change the config rather painlessly?

All Replies

  • Wednesday, February 06, 2013 4:28 AM
     
     

    You should be able to do this rather seamlessly. The EP clients would not have to be reinstalled (unless the version of the EP client is different by the time you cut over to SCCM.) Are you going to be controlling the EP policy through Group Policy in the meantime? My only concern would be to make sure that you coordinate the decommissioning of the Group Policy delivered policies with bringing online your SCCM delivered antimalware policies. You wouldn't want to cause any accidental differences or conflicts.


  • Wednesday, February 06, 2013 6:00 PM
     
     
    So, in other words, you're saying that if I deploy via group policy I should disable the policy, wait a bit, and then deploy the SCCM setup?
  • Friday, February 08, 2013 4:03 AM
    Moderator
     
     Answered

    Hi,

    Thank you for the post.

    You may also refer to this guide to deploy FEP: http://technet.microsoft.com/en-us/library/ff823762.aspx

    Regards,


    Nick Gu - MSFT