Symantec Endpoint Encryption
-
I have a question. We have a few computers left that are still encrypted with SEP. This is a product we are getting rid of, thank goodness, however while implementing Fog we ran into an issue. We have a computer that was encrypted with SEP, however when we went to deploy the image it couldn’t see the drive to mount it. We have others of the same model that work, so I know its not anything like that. I would have assumed it would just have mounted the drive and overwrote it, however my tech is telling me it just failed out as it couldn’t find the mount point. My current solution for him is to wipe the drive then image it, however it looks to me like there should be another way. Any thoughts or ideas would be greatly appreciated.
-
There’s no reason that wiping the drive would magically make the disk available for use. This sounds, too me, to be an issue with how the disk is being presented to the machine.
There are three commonly used methods of presenting the HDD.
- AHCI (Advance Host Controller Interface) – Typical
- IDE (Integrated Drive Electronics) – Less common now, but usually still functional.
- RAID (Redundant Array of Independent Disks) – Usually I see this set as the default for DELL machines, but this also is “strange” to FOS and often a cause of not seeing the disk.
I doubt wiping the drive would make the disk presenting to FOS.
-
@Jethrov said in Symantec Endpoint Encryption:
I would have assumed it would just have mounted the drive and overwrote it, however my tech is telling me it just failed out as it couldn’t find the mount point.
Please do me a favor an let your tech take a picture of the actual error on screen. It’s a lot more helpful than trying to guess what was going wrong.
-
Ok, the plot thickens… We have imaged the same model laptop, and changed the drive just and see. In addition, I changed the drive from AHCI to IDE and it made no change. I was thinking the same suggestion as Sebastian posted above, so the pic of the error is attached.
-
I got it figured out. As I was staring at the error message, it occurred to me I was blaming the computer and not really giving thought to the server itself. Anyway, upon digging I found the .mntcheck file was missing from it was supposed to be, so a couple of touch commands later and we are off an running.
Thanks for the help.
