Page 1 of 1

FileEncryption on Mac

Posted: 11. May 2017, 13:45
by YeahAustin
Hi all - New to the forum.
Have a Macbookpro 13-inch
Processor i7
16GB memory

I am running virtual box on it successfully and I have got macOS Sierra running successfully on it.
When I connect to company JAMF server and download config all good still.

FileVault then gets turned on automatically by the policy - on physical mac this is fine. Once its encrypted and rebooted I can then go in and turn it off.

However the issue......
With the virtualbox vm - the fileVault turns on then reboots.
After auto reboot I can't boot back into the OS.
I get stuck at still waiting for root devices.

I attach the iso - boot off and go into disk utilities. I see the disk but not mounted, select mount, enter filevault password and it mounts.
Reboot OS then it is unmounted again and wont boot into it.

any ideas?
Is it possible to turn off fileVault on terminal mode when booted off iso?

**I'm new to MacBook also - new job and they want me to be working with them**
*** Hope enough info provided and please let me know what else is needed***

Thanks
Austin.

Re: FileEncryption on Mac

Posted: 11. May 2017, 17:26
by socratis
YeahAustin wrote:With the virtualbox vm
Which VM? You didn't mention anything about a VM so far.
YeahAustin wrote:Is it possible to turn off fileVault on terminal mode when booted off iso?
What???
YeahAustin wrote:Hope enough info provided and please let me know what else is needed
Unfortunately, not at all. You only told me that you have a MBP. That's it. After that you have some problems with FileVault (where?) and that you want to turn it off if you boot from an ISO (what ISO?).
  • What's your host version? Full and complete details please. "OSX" isn't enough, "OSX 10.9.5 build 13f1911" is much better.
  • What's your guest version? Full and complete details please. "Win10" isn't enough, "Win10 1607, build 14393.969" is much better.
  • What's your VirtualBox version? Full and complete details please. "The latest" is not enough, "VirtualBox 5.1.18 r140002" is much better.
For future reference, "current version", "latest version", "previous version" don't (generally speaking) provide accurate information. In a couple of months the "current" will definitely be different. It's better if you use the complete version numbers (including the build numbers) to identify software.

And please try to describe the problem one more time. For example, I have no clue what a "JAMF server" is. Use details as if I was not sitting in front of your computer. Which I'm not.