Acer Desktop Acer Veriton S6620G BIOS setting chaning when installing Windows Bitlocker/TPM/UEFI?

wardh

Hi,

I am having some strange issues with and Acer Desktop. (Acer Veriton S6620G)

 

We are using bitlocker and TPM doing various Operating Systems Installs of SCCM using via UEFI and non UEFI and USB.
(SCCM 2012 SP1, MDT 2012). The OS I am installing is WIndows 7 x64 in an Active Directory domain.

 

So please bear with me I don't have the exact or precise synario - so I am looking for
some general guidence. However what seems to be happening depending on the state of the
disk (if there is some on the "C" drive or not the BIOS boot device will change).

 

So lets say the disk is blank and I have the primary boot device set to [HardDiskT-500DM00...]
(This is short for the Hard Drive type ST500DM002-1BD142)

all is well.

 

Once the system completes the OSD build / or I think fails half way through and
puts something on the disk. The stage changes so instead of say [Hard Disk].

I think this alsohappens if choose to build a non-uefi system.

 

In the BIOS i cannot select the Hard Disk by its model
number any more (HardDiskT-500DM00...) I can only see [Hard Disk].

 

So when I say UEFI or non-UEFI I am refering to pressing F12 and then chosing the USB device to boot
from like "Imation" - this will start a non-UEFI build.  Alternativly if I select "UEFI:Imation" this
will do a UEFI build. (Imation being the brand of USB key).

 

BTW: I currently have the bios  not set to write protected.

 

In our task sequence btw we have one format step if UEFI and another if it is not.

 

 

 

Ok so here are my questions:

 

1. Is this behaviour normal TPM/Bitlocker should the BIOS be chaning around like this if I am
not manually changing it myself. Like does the OS go down TPM chip starts and changes the settings.

 

2. For bitlocker/TPM to work do they require UEFI or can they happily work with standard BIOS mode.

 

3. I have also noticed a boot device called [EFI Device] is this something special that only get activated
by TPM etc?

 

Just a note to add I am not expecting people here to be SCCM experts. I am just providing this a

a full detail of what I am doing. They key I am trying to find out is why the BIOS settings would

be chaging if (I am not chaning them myself). In short is the normal behaviour?

 

So there you have it I might be asking some *newbee* questions but I have never seen a behaviour before
like this using OSD - which is why I am thinking the ball game changes with TPM/Bitlocker/Uefi

 

Thanks,

 

Ward.

Blayn-Acer

I am looking into the issue you are describing and it would be helpful if you can provide your serial number. If possible, please send me a private message with your serial number. This will help me understand exactly what hardware shipped in your product.