cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Several corrupt <pcname>.XML files

Jump to solution

Over the past few days, we've received calls about Failed to deserialize type... long story short, when we go to export the XML file for the machine, the <algorithim> key is always corrupted.  Where a normal XML will have <algorighim>AES-256-CBC</algorithim> our corrupt XML files all have a bunch of ascii characters in the XML algorithim tag.  It's easy to fix by simply re-typing the correct algorithim between the tags, but when I checked a few random samples, I found about 1/4 of all of our systems have these corrupt XML keys.

EEPC6, latest version released.

Any ideas?

1 Solution

Accepted Solutions
whgibbo
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Several corrupt <pcname>.XML files

Jump to solution

Hi,

This problem is related to 6.0.x machine keys only.   Some changes to EEPC 6.1 were required in order for it to work with ePO 4.6, this involved how the machine key was stored.

Providing you use the new version of EETech supplied with EEPC 6.1, it will deal with this problem.

This problem has been fix in 6.1.1.

Also note that when your clients are upgraded from EEPC 6.0.x to  EEPC 6.1.0, it will automatically send a new machine key and recovery information to ePO.  This is implemented in the 6.1 RTW build.

Sorry for any inconvenience

View solution in original post

3 Replies
whgibbo
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Several corrupt <pcname>.XML files

Jump to solution

Hi,

This problem is related to 6.0.x machine keys only.   Some changes to EEPC 6.1 were required in order for it to work with ePO 4.6, this involved how the machine key was stored.

Providing you use the new version of EETech supplied with EEPC 6.1, it will deal with this problem.

This problem has been fix in 6.1.1.

Also note that when your clients are upgraded from EEPC 6.0.x to  EEPC 6.1.0, it will automatically send a new machine key and recovery information to ePO.  This is implemented in the 6.1 RTW build.

Sorry for any inconvenience

View solution in original post

whgibbo
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 4

Re: Several corrupt <pcname>.XML files

Jump to solution

Re: Several corrupt <pcname>.XML files

Jump to solution

Thank you VERY much for the quick and accurate response!

Rich

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