I have a dual boot laptop with a work OS and a 'home' OS on seperate drives within the laptop. Both OS's are Windows 7 64 Bit. Work decided to rollout EE 5.2.2 to my work OS and now my 'Home' unbootable.OS is no longer bootable.
Is there a way of making it so again? I was thinking of doing a repair install, but don't want to do anything that might affect the EE MBR and render my work OS unbootable.
You need to speak with Work. There is possibilty that they might change general machine setting to encrypt one drive but not the other and install boot manager. But based on my eperience that possibility is small. Anyhow, you need to speak to them, at least to decrypt undesired disk and get it removed. Does your Work support configurations like yours? If not and they are uncooperative, you would need to get WinTech, prepare bootable CD and decrypt second disk.
Thanks for that. I have asked the question and they have agreed, somewhat surprisingly, to look into it for me.
As an aside, the second bootable OS hasn't been encrypted, so it is 'just' a case of getting the EE changed boot manager to recognise the other OS, if at all possible. Don't know if it is possible to change/amend an EE modified boot manager without shafting the original encrypted drive.
You could use the boot manager for EEPC, i haven't played with that since I usually see linux dual boots and grub works wonderfully with EEPC.
Using Endpoint Encryption Manager, select your machine. Double click on it (or right click and choose Properties). On the left side scroll down until last item "Boot". Select that. You will see radio box for "Enable boot manager". Check it and "Apply" machine object properties.
Vista and Windows 7 are a totally new kernel and you might have to edit the BCD. If you're not sure how to do that there are tools that can help. Like EasyBCD which you can find at http://www.intowindows.com/download-easybcd-for-windows-7/.
Thanks for that, looks useful.
However I am worried that by changing the BCD it will render the first OS inaccessible as well due to it (the BCD) having been changed by EE and any further changes will cause it to fail.