Thanks for the reply, ill have to try this out on Monday but as I sit here on the bus I got to thinking... could the refresh scenario be causing it?
If the the drive was encrypted previously then I think it would cause the same situation specially if through the deployment I'm am change the encryption to aes 256 and not staying with the default 128 Sent from my BlackBerry 10 smartphone on the Rogers network. From: Niall Brady Sent: Friday, February 6, 2015 16:58 To: [email protected] Reply To: [email protected] Subject: Re: [MDT-OSD] Bitlocker suspended for Surface Pro 3s after mdt deployment click on http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/ scroll down to.... CM12 in a Lab - Why is my Surface Pro 3 not BitLockered after OSD via System Center 2012 R2 Configuration Manager ?<http://www.niallbrady.com/2014/09/18/why-is-my-surface-pro-3-not-bitlockered-after-osd-via-system-center-2012-r2-configuration-manager/> On Fri, Feb 6, 2015 at 9:39 PM, Bain.John <[email protected]<mailto:[email protected]>> wrote: Maybe this is a simple fix, but when I image a surface pro 3 using MDT 2013 the deployment is successful but Bitlocker is in left in a suspended mode. Any idea why this is happening ? If I click on the “resume protection” Bitlocker enables properly. Weird John
