Task sequence fails at enable bitlocker
we are pre-provisioning many computers here (windows 7 and windows 8) and havn't seen this issue yet, what type of hdd's are you using?. I've tried some scripts to check to see if TPM is enabled and TPM is activated which return TRUE for both, however, these don't cater for the ownership. SCCM 2012 R2 on Windows Server 2008 R2. At first i was suspecting missing cpu features, however it might also be larger and slower disks. On working models the disk is already encrypted when maybe 10 % of the wim file is downloaded. It looks like the encryption initially (after the pre provsion step) does not complete fast enough and when the download starts the system does not keep up downloading, applying and encrypting. If i pause the the task sequence before the first reboot the encryption completes and the task sequence completes successfully. We are experiencing this issue also, on a 'high spec' laptop with an SSD. How can I determine if there's a TPM chip on my Lenovo system for BitLocker?. we are pre-provisioning many computers here (windows 7 and windows 8) and havn't seen this issue yet, what type of hdd's are you using?. can you post a smsts.log file from one machine with the problem please. Set command line: OSDBitLocker.exe /enable /wait:True /mode:TPM /pwd:AD. We added the pre-provision as soon as we could and it had been working great up until now. However, after this simple fix I'd say this was only a minor problem but it would sure be nice it is waited until encryption was complete. Other laptops (also Lenovo) running the the same task sequence are succeeding and have been since we started using bitlocker, so I don't think the problem lies there. But this eval device we have been sent, with the same tpm settings always fails and the only real difference i think is the SSD. Pre-Provisioning Bitlocker fails because encryption not fast enough. isn\t the /wait:True command what you guys are trying to do, i.e. add a wait until done via a pause. ? well what errors are you seeing in the enable bitlocker step? have you tried adding a pause command to the ts directly after the pre-provision bitlocker step then open a cmd prompt and issue. It makes no difference though, the Bitlocker pre-provision step succeeds (well i think it does, the TS doesnt bomb out), but fails at the enable bitlocker step. isn\t the /wait:True command what you guys are trying to do, i.e. add a wait until done via a pause. ? Interests: Modern management of devices with Microsoft Intune and System Center Configuration Manager. The Enable Bitlocker step is causing a failure with the exact same errors as in the logs above. It occurs irrespective of whether we tick the "Wait for Bitlocker to complete" box or not?? In our Windows 7 task sequence, I go through the process of enabling the TPM chip on Dell and Lenovo machines which generally works fine, so long as they've not been previously owned. whats the exact failure you are getting? are you doing it similar to the posts below?. please this step before the Apply Operating system step and after the Pre Provision bitlocker step. Home Library Wiki Learn Gallery Downloads Support Forums Blogs.