well the first thing to check is what your smsts.log file tells you when you do any bitlocker specific steps, so what does it tell you ? attach it here if you wish
On Wed, Sep 25, 2013 at 3:59 PM, Linkey, Mike <[email protected]>wrote: > We check the bois before we start and it is already enabled. From there > whatever is in the task sequence by default and the MBAM 2.0 client take > care of the rest. That is how we have done it with the normal laptops with > Windows 7. If we put the Windows 7 image on these, it works like a champ. > So it is just something with the Windows 8 TS. Just can’t seem to find > that needle in the hay stack at this point.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Niall Brady > *Sent:* Wednesday, September 25, 2013 8:52 AM > *To:* [email protected] > *Subject:* Re: [MDT-OSD] HP Revolve 810 and Bitlocker during OSD**** > > ** ** > > aer you enabling the tpm as part of your task sequence ? are you using any > vendor specific tools to do this ?**** > > ** ** > > On Wed, Sep 25, 2013 at 3:45 PM, Linkey, Mike <[email protected]> > wrote:**** > > We have just got some HP Revolve 810 Tablets/laptops. We have our Windows > 8 image setup and working to some extent. We can install the operating > system with it just fine. When we enable the bitlocker stuff, Bitlocker > will not work. We can’t enable it or anything. We also are installing the > MBAM 2.0 client. That install works fine, but again it will not start > encrypting the drive. So thinking there was some incompatibility, we > decide to just use the Windows 8 DVD to install the OS as a test and it > worked as advertised. We can enable Bitlocker no problem. So I have been > scratching my head now trying to figure out what is different. What would > keep Bitlocker from working? It almost seems like the TPM chip can’t be > detected after using the OSD image, but it does work with just using the > DVD to install.**** > > **** > > Anyone have experience with these that can give us some pointers? Not > sure where to go with it at this point.**** > > **** > > Mike L.**** > > ** ** >
