Management Console

[brendangriffin]

Hi,

I am using the Management Console version 2.0 installed on an NT4.0 Server with Service Pack 6a to push out Virus Scan 4.5.1 to Windows 95/98/ME machines.

The software appears to push out okay but once the machines are rebooted they come up with the error message:

"meup.cfg failed its integrity check"

Has anyone experienced this problem before and if so how did you resolve this.

Thanks in advance

Brendan

 

[linney]

See if anything here helps you.

http://groups.google.com/groups?q=m...gtoulgepfh5ba7ldm9ubp701a5h7hu@4ax.com&rnum=1

 

[Guest_imported]

If you are using Management Edition;

A general tip; Get the latest version. I believe version 2.5 is out, which fixes several issues

 

[FatesWebb]

Unable to update machines from the Management Edition console

Any changes made in Management Edition to a target PC's configuration, before it is applied, is reflected in the target PC's MEUP.CFG file. When an apply is started, the PC's Management Agent compares the MEUP.CFG file to its MEUPLAST.CFG file (target PC's current configuration) and tries to carry out the changes.

When a configuration is being applied, the Management Agent writes the results of each operation to the MEUP.CFG file. The last stage of the update process is to recalculate the checksum for the file. If the update process does not complete for any reason (machine crashes, is turned off, etc.) then this checksum will not be calculated. The next time you apply to the machine, MEUP.CFG is renamed to MEUPLAST.CFG (to make room for the new MEUP.CFG file). However, when the update agent starts its run, the (new) MEUPLAST.CFG file will fail its integrity check due to lack of checksum, and the error is generated.

When using a Pull Off or Batch, an extra comparison is done: MEUP.CFG on the target machine to <MACHINENAME>.CFG in the Upgrades folder (shared as MEUPGD$) on the repository machine. The error message, in these cases, will occur also if there is a problem with this repository file.

The problem then is that there is no way to tell which file is at fault. If the console were to perform any action at that point it would run the risk of getting it wrong - possibly with catastrophic results. It does not do anything and the error is displayed.

Deleting the .CFG file(s) on the target machine (running on any of the Windows platforms) fixes the problem because when an apply is done the Management Agent has no MEUPLAST.CFG to compare changes with so it sends all the software and configuration settings specified in MCON for the machine to the machine again (i.e. full install & resultant network traffic) - not just the changes that were made. What is more, not only is there no local comparison but neither is there any comparison with the <MACHINENAME>.CFG in the Upgrades folder (shared as MEUPGD$) on the repository machine.

1) Delete or rename the MEUPLAST.CFG and MEUP.CFG files on the workstation
2) Restart the workstation
3) Apply the configuration again.

 

[brendangriffin]

Thanks for the help I will try this

 

[ESW]

FYI:

Management Edition will be EOL on June 30th 2002.
Start moving to ePO now, because there will be no support available after this date.

 

[Guest_imported]

Where can i find the upgrade of management edition ?
I've the same probleme but the solution to delete 2 files doesn't work.

I must upgrade from 2.0 to 2.5, but this upgrade is not on nai.com web site.

 

[FatesWebb]

you sales rep can get you a copy. FatesWebb

if you do what I suggested it is not my fault...