I have almost the same exact problem today.
I've just upgraded my server to endpoint manager 220.127.116.11 and build version 5701, it all looks fine, I went to System/File Groups and updated all files, and then I got my test client to synchronise, it of course found a whole heap of new files, and successfully downloaded them. I rebooted and expected the client to now be on 18.104.22.168 but it seems stuck on 5.1.3 (like yours).
I tried removing safeboot from the client completely, rebooting, creating a new set of install files, installing those, rebooted, and still 5.1.3
So I too feel like I'm missing something very obvious, where can I get the 522 client install files?
From what I've read, the EE Manager and Client are now seperate in order to allow different release schedules. I would imagine that's why the latest version of EE Manager is still only bundled with 5.1.3 maybe ?
Hopefully someone will be able to point use both in the right direction then !!
ok I think this may be helpful.
Like you I was expecting my DE51... file sets to change to DE52... (or be available in addition).
I think DE has become EEPC in the new system.
So I simply deselected all of the DE51s for my test machine, and then selecting the equivalent ones in EEPC. then got my client to synchronise, and reboot. It now shows my system at 5.1.9 instead of 5.1.3
Can anyone confirm if DE has become EEPC?
1 of 1 people found this helpful
When you upgrade MEE to a new version this is what you need to do:
1.) Go to the System Tab and expand "Endpoint Encryption File Groups." You will see all the filesets available to your clients at that time. Now right click the "Endpoint Encryption File Groups" and select "Update File Groups."
2.) Scroll down the list and select only the filesets you need or want.... you dont need to download everything in that list and clutter up your DB. Be sure to get the new client file sets for sure.
3.) Once the update is finished you will now see the new client file set for the new version listed under "Endpoint Encryption File Groups"
now the important part.
4.) Go to your machine groups. Right click a machine group or an individual machine and go to properties --> Files and unselect the already checked client file set for the old version and then select the new versions client files. If you make this change at the Machine Group level be sure to right click the group again after the change has been made and select "Reset all to group configuration" and then UNCHECK "Exlude File Groups." This will make the new changes to the group effective on all the machines inside that group.
Now the next time those clients in that group sync, they will get the new updated version of MEE installed.
thanks for the reply
however i think you are one step behind us, what we're asking is - why do we not see DE52 in the list of available file groups? (after running the update as you've suggested).
And what i suggested is that maybe DE has become EEPC in the new system?
can you confirm this?
1 of 1 people found this helpful
Yes it has.
In version 5.2.3 at least anyways. Mine is showing up as EEPC52:
cool, so my only issue now is that my EEPC client files are only 5.1.9 and not 5.2.x
I'll have to try and download the new pack.
also is EEFF an integral part of the new system? or optional? what functionality does it add exactly?
When I update the file groups I get a small box telling me it's searching for updates but, when that box disappears, I don't see anyEEPC52 in the list (or any EEPC files for that matter).
Now, I don't know if this irrelevant but, under the SYSTEM tab, the File Group appears as "SafeBoot File Groups" not "Endpoint Encryption File Groups". I was using Safeboot 5.01 but did a straight upgrade to EEM 5.2.3. The main window titles shows as "McAfee Endpoint Encryption Manager” and the about box shows "McAfee Endpoint Encryption Manager v5, 2, 3, 5" so it would appear I'm using the latest version.
I have no clue why I get no file group updates after choosing the update option!
Thanks for all your help up to this point by the way; you've answered my question as to how I get new File Groups into EEM. Now I just gotta work out why it's broke!!
EEFF is for File and Folder encryption. You can encrypt network drives, certain folders on your HDD like the My Documents folder or a lot more stuff too.
You can use EEFF to lock down removable media and encrypt anything that gets dropped onto a flash drive. You should read up on the EEFF Admin Guide to get a good idea of its capabilities.
The thing is this. EEPC protects your HDD against unauthorized access. But once you unlock the HDD by authenticating at preboot none of your files are encrypted. You can send them out via email, copy them to thumb drives, take them home, sell them to strangers etc. EEFF helps to protect your files once your users are logged in to their desktops.