Bitlocker issues
-
I have been fighting this system for a hot minute now and finally have hit a major roadblock that I have no idea how to get past.
For context:
This is a brand new system set up, I am an L2 for this company, and we are trying to implement fog as our main method of imaging. We have a machine here that is serving as “the master copy”, and when we finally got it to PXE boot properly (whole sleugh of issues there, but have been resolved, we are 90% sure its not causing this issue). Now that we have it PXE booting right, and even registering, fog can attempt to capture it, but we keep getting the following error:
“Found bitlocker signature in partition /dev/sda4 header. Please disable BITLOCKER before capturing an image. (IsBitlockedPartition)
Args Passed: /dev/sda4”I have checked and doublechecked, bitlocker is disabled on the machine in question, is there any way to bypass this issue?
-
@technicaltroll So what is partition #4. Is it was would be the C drive?
If yes, windows some does things a bit problematic in that it will encrypt free/unused space on a drive where bitlocker is not enabled.
From an elevated windows cmd prompt key in
manage-bde -off C: manage-bde -status C:
and confirm that bitlocker has been disabled.
-
@george1421 That seems to have done the trick. Thank you so much! I have been pulling my hair out these past few days over DHCP, fighting with ISP over DHCP, the Master copy machine not PXE booting properly. I am hoping this is my last roadblock in my fog journey.
-
@technicaltroll If you still run into issues with dhcp and your isp, we have options when your dhcp service is managed by a third party and they are unwilling to help. We will just setup dnsmasq on your fog server to send out pxe boot information only bypassing dhcp options 66 and 67. I’m not saying you need to change, only you have options if you need it.
-
@george1421 Our current solution was to isolate the two(technically 3, since the fog server is running in an Ubuntu Virtualbox) to a completely separate domain.
I brought in a spare personal router, hooked the two physical machines up and set the DHCP settings on that. The DHCP problems are no more, for now at least, and whenever necessary, or available, I can always re-bring these two back online after the image capture is done.