Punintended Posted July 2, 2013 Report post Posted July 2, 2013 I'm standing up a lab to test MBAM before it goes into production. At the moment we just use AD to store bitlocker recovery keys. I'm a bit confused about how I go about implementing the agent during OSD. A few guides I've found use RTM and don't account for the use of pre-provision bitlocker. I'm hoping someone has implemented this and can share how they built the task sequence. Quote Share this post Link to post Share on other sites More sharing options...
teamfox201 Posted July 2, 2013 Report post Posted July 2, 2013 Have you looked at this link? If so, what exactly is your issue / question? http://technet.microsoft.com/en-US/library/dn145038.aspx Quote Share this post Link to post Share on other sites More sharing options...
Punintended Posted July 2, 2013 Report post Posted July 2, 2013 Thank you. The guide you linked is one I've read among many. With the pre-provision bitlocker step added I don't think I need to mess with importing reg keys and restarting the service. Shouldn't just the act of installing the client allow mbam to take ownership and publish the recovery key? Quote Share this post Link to post Share on other sites More sharing options...
teamfox201 Posted July 2, 2013 Report post Posted July 2, 2013 If you have your MBAM server configured and the MBAM GPO configured (http://technet.microsoft.com/en-us/library/dn186164.aspx) then it should start publishing keys to the MBAM server when you start encrypting or if its already encrypted then it should store the key. Quote Share this post Link to post Share on other sites More sharing options...
Punintended Posted July 2, 2013 Report post Posted July 2, 2013 Great, I think you've confirmed my suspicions. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
