1231 How to fix premature upggrade to OS X 10.10.1 Yosemite on SecureDoc version that has no support for that OS X version

Prev Next

How to fix premature upggrade to OS X 10.10.1 Yosemite on SecureDoc version that has no support for that OS X version

Issue:

Prematurely upgrading OS X to an unsupported version (10.10.1) on a SecureDoc Client version that has no support for that level of OS X can yield problems

IMPORTANT: As a general recommendation, where enterprise customers are using SecureDoc for FileVault 2 to protect their machines, it is vital to educate end users to first validate that the version of SecureDoc they are running can support the version of Mac OS X they wish to install before they proceed to upgrade the Operating System.

Scenario:

One customer had a device running Apple OS X 10.8.5, with SecureDoc for FileVault 2 V2 6.2SR2 currently installed.

Contrary to recommended process, he attempted to upgrade Apple OS X to 10.10.1 Yosemite before upgrading the existing V6.2SR2 version of the SecureDoc client to a version that will support OS X Yosemite. (NOTE: Support for Yosemite became available in SD V6.5).

Following the attempt to upgrade Mac OS X to 10.10.1 Yosemite, error messages were displayed because the existing V6.2SR2 of the SecureDoc client does not support OS X 10.10.1

The user then upgraded the version of SecureDoc for FileVault 2 running on that computer to V6.5 GA release build number 241, and then re-installed Mac OS X Yosemite 10.10.1 again to ensure that the Mac OS upgrade completed successfully.

However, after rebooting the Mac device, it now showed an error message:

“SecureDoc for FileVault2: Unable to determine drive protection status”

Solution:

If such an event re-occurs, to correct this:

1 - Open “Terminal” and type in the following command:

sudo rm/Library/Preferences/loginwindow.plist , then press enter

2 -Type in the password , and press enter

The terminal screen will show:

rm:/Library/Preferences/loginwindow.plist: No such file or directory

3 - Lastly, reboot the Mac computer

NOTE:

This scenario has been noticed to occur when upgrading from V6.2SR2 to V6.5, and there is no such issue when upgrading from V6.4SR1 to V6.5.