I agree. It's getting impossible for our support team to manage the many different versions of EETECH. We have several versions of EEPC/MDE in use including 5.2, 6.2. 7.1.
I'm going through the testing process now to upgrade from EEPC 7.0.0 to MDE 7.1.1 and for grins I tried my original 7.0.0 boot disks on a 7.1.1 encrypted drive and was able to unlock it and remove MDE just fine. Now, I realize McAfee won't agree that this is supported and can't guarantee anything but I do find it odd that the 7.0.0 tools worked on a 7.1.1 system but the 7.1.1 tools don't work on a 7.0.0 system (I'll have to try that out next).
I did finally get a chance to test the MDE 7.1.1 tools on a 7.0.0 install and it also worked. I used the Emergency boot CD, was able to to put in the code of the day, the XML file, load the workspace and decrypt it in memory to verify the key worked as expected. Then I did an emergency boot and it did work. I didn't try to remove EEPC since the Linux boot disc decrypts much slower than the PE DEtech does since it uses generic drivers. I'll be having our boot key team (they do boot keys for other stuff as well like the system deployment boot key) update our PE boot disk with the new 7.1.1 files and then give that a try as well. I know McAfee will not support this but in a pinch, it's at least good to know you can unlock the drive and copy the data if needed.
Unfortunately the software download links in the document are blocked by both Chrome and IE because the SSL certificate for the site is not trusted.
All the links I checked work for me - which one is your computer complaining about?
The files are stored on Dropbox after all - I can't imagine they would have an unnoticed cert problem?
I'm using Chrome on OSX, and it works fine - I am guessing this is a problem between your machine and Dropbox 😞
Maybe try downloading it from another machine / another location?
You can always download from untrusted sites with most browsers, BUT this is very clearly a bad idea. My complaint is that a security company should not be posting executable code on a site with a self-signed certificate (you can see this on the Certification Path tab of the Certificate Manager dialog on the screen shot above).
We spend time training our users NOT to visit sites which are not trusted, and here our security vendor is telling us to download code from such a site..