Address the issues regarding the compatibility between FDE and other products.
Below are the common compatibility problems that you may encounter with FDE:
After installing FDE and re-imaging a machine using a Ghost Corporate Edition 8 DVD, the machine fails to boot.
This issue occurs because the cloning feature of Ghost 8 leaves FDE on the machine, thus rendering it useless.
To resolve the issue, image the disk without cloning or using a command such as fdisk to ensure that the drive is completely erased before applying the image.
Symantec is aware of the issue and has assigned it as case number 310-818-321. Below is the workaround provided by Symantec:
- Open Symantec Anti-Virus.
- Click Configure, and then click File System Auto-Protect.
- Click Advanced.
- Under the Startup option, select Symantec Anti-virus Start.
- Click OK and click Exit.
- Reboot the system.
Contact Symantec support for further details.
HBSS and FDE can be installed in any order.
No additional steps are required if HBSS is installed prior to FDE deployment. FDE can be installed successfully with or without Symantec or McAfee anti-virus.
However, if you installed FDE first, you must add a command to the HBSS installation script that stops Endpoint Encryption MobileSentinel Windows Service. To stop the MobileSentinel Windows Service, use a Net Stop Service command, which can be scripted. Note that if it is stopped this way, MobileSentinel automatically restarts upon the next reboot of the machine.
Below are the sample commands that can be used in scripts to stop and start the MobileSentinel Windows services. Administrative privileges are required to run these commands.
- Net Stop MobileSentinel
- Net Start MobileSentinel
You may also physically access each machine, suspend the MobileSentinel Windows Service, and then deploy HBSS. No issues are recorded using this approach.