cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Former Member
Not applicable
Report Inappropriate Content
Message 1 of 6

Safeboot to Endpoint Encryption

Jump to solution

I've just done a test run of upgrading our Safeboot (5.1) server to Endpoint 5.2, it looks like the upgrade went ok, and my test client machine seems happy to reconnect, updated a few files, etc, .

One thing I'm confused about is that it still seems to identify itself as "Safeboot", I was expecting to see some evidence of the rebranding. Particularly on the client, it doesn't mention Mcafee or Endpoint anywhere, it just looks like the same old Safeboot, including the pre-Windows Safeboot login screen, it still says safeboot.

Is this normal?

What's the dilly?

thanks in advance

PS. is there some way I can check the client version number installed on my workstation?

1 Solution

Accepted Solutions
Former Member
Not applicable
Report Inappropriate Content
Message 3 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

If you installed EEPC on server and deployed client file set properly....

Pre-boot is changed after next sync and reboot.

Also, system tray icon and window got changed and now says McAfee....

View solution in original post

5 Replies
Former Member
Not applicable
Report Inappropriate Content
Message 2 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

Hi jackmulder,

I've moved this thread to the Endpoint Encryption v5 community. Hopefully someone can help you soon!

Former Member
Not applicable
Report Inappropriate Content
Message 3 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

If you installed EEPC on server and deployed client file set properly....

Pre-boot is changed after next sync and reboot.

Also, system tray icon and window got changed and now says McAfee....

View solution in original post

Former Member
Not applicable
Report Inappropriate Content
Message 4 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

To check client version:

1. Look at sbclientlog.txt - at boot time the client version is stamped in. Note: After upgrade, it will report the old version until it's rebooted.

2. In the Status window, click the Modules button. You'll see the specific version for each file.

Former Member
Not applicable
Report Inappropriate Content
Message 5 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

When you upgraded the files to 5.2,  did you change Themes?   If you left the theme the same, then your PBA screen won't look any different.  If you updated the theme,  there is a definite difference...

Former Member
Not applicable
Report Inappropriate Content
Message 6 of 6

Re: Safeboot to Endpoint Encryption

Jump to solution

thanks everyone

the problem was that I hadn't changed my filesets from DE51 to EEPC52

everything seems to be ok now

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community