Hi, my name is Nick

and I have implemeted SafeGuard Easy on the network for our laptops.
SGE installas like any other application on a mchine and then it reboots automatcally.
After reboot is done it encrypts entire hard drive, and changes the MBR. It also adds a pre-boot authentication so if that PC is lost or stolen you can't go to boot device list and BIOS settings without proper user ID and pswd.
Anyway, I have MSI on the network which is properly configued.
I created Group Policy and eveything works fine, but only IBM R5x series laptops been having issues.
Blue screen and reinstall by initilizing the Window Installer trying to repair / reinstall that same SGE.
It is not Group Policy or the batch file because I scripted it that way if it is installed to go to end.
I found a possible fix tha tneeds to have some registy changes on the insallation MSI package.
BUT I'm affraid if I change that original MSI on the network, that all of my client machines will try to reinstall / repair tehm self which would be a disaster.
In other words, will the laptops notice that the original MSI was changed and will they then try to reinstall / fix tehat application ?

Any help wpould be greatly appreciated.
Nick [:o]

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Nick.

I managed an implementation of SafeGuard easy via group policy here as well last December. We use IBM's as well, though only the S5X, T4x, and X4x series. None of those have had any problems.

To answer your question, no, modifying your source MSI will not affect your clients unless you mandate a repair via policy.

Several thoughts for you:

- Do your R5x machines have any kind of modification to the GINA? We've found that the SGE GINA doesn't play well with others.

- What is being referenced when you get the blue screens? We recently purchased 50 high end dells, and we're seeing random bluescreens referencing an SGE file (I'll have to look up which one)

- IMPORTANT - This one's big. We've found that trying to remove the SGE installation by using the 'uninstall when falls out of scope' option DOES NOT WORK. What happens is your machine tries to run the uninstall, but because you need to enter SGE credentials in the uninstaller before it can be removed, you end up permanently ruining your machine. It will boot & sit at the 'Removing Managed software' screen indeffinately. And because your drive is still encrypted, your left with no way to access the data on the drive.

Thus we unchecked the 'remove when falls out of scope' option, so Group policy cannot try to uninstall the software. I'd HIGHLY recommend doing this, since group policy assigned apps requently uninstall and reinstall (ie if you remove a machine from the domain.

Let me know if you have any other questions, I've worked with this product quite a bit.
Answered 11/02/2006 by: Bladerun
Green Belt

Please log in to comment