VSE 8.8 not reporting in to ePO 4.5

[Former Member]

We installed VSE 8.8 on three machines yesterday to begin testing it.  The installation went fine.  VSE 8.7 was uninstalled, and VSE 8.8 was successfully installed.  However, these machines now show to be out of compliance because they do not have VirusScan installed.  I'm attaching screenshots.  The VSE8.8.About screenshot shows the About window on one of the test machines.  The VSE8.8.SysDetails screenshot shows the System Details for the same machine in ePO 4.5.  As you can see, VirusScan is not installed, according to ePO.  We have run the Status Monitor and Collect and Send Props multiple times, but they still don't report VSE or Antispyware (both of which are installed.)

Known bug?  What to do to troubleshoot?

[kink80 · Accepted solution]

This was listed as a known issue in the readme.

Compatibility with other products

• Issue

  After successfully upgrading from VirusScan Enterprise 8.7 to VirusScan Enterprise 8.8 the ePolicy Orchestrator 4.5 System Details dialog box does not list VirusScan Enterprise 8.8 in the Installed Products row. (620509)

[Former Member]

I noticed this issue when I was reading the release notes.  I was surprised that there was no workaround listed.  Perhaps we'll have to uninstall 8.7 then install 8.8 in order for ePO to list it as compliant?  That would be a pain.  BTW, some of the Issues say "Workaround: None", some have a workaround listed, and some (like this one) don't say anything.  Can anyone confirm that there is no workaround?

Jay

[Former Member]

Uninstalling VirusScan and reinstalling it doesn't resolve the problem.  We'll have to wait for a fix from McAfee.

[Former Member]

I started testing on two Windows XP Pro SP3 (32-bit) systems.  Both had McAfee Agent 4.5.0.1810 (4.5 Patch 2) and VirusScan 8.7.0.570 (8.7 P4).  On one, I used two separate tasks to uninstall 8.7 and install 8.8, with a reboot in between.  On the other, I just sent a deploy task for 8.8 and let it update from 8.7.  Both finished without errors and are reporting back to ePO properly - correct version, in compliance.  The correct version shows up in the "Installed Products" row when I click on the system in the system tree also.

The "Known Issue" must be with some specific configurations and/or circumstances.  Hopefully tech support can help you figure out what is happening on your systems.

Jay

[Former Member]

My tests were on Windows 7.  Perhaps that's the difference.

[Former Member]

I updated a Win7 32-bit system from VSE 8.7 to 8.8 without uninstalling 8.7, and everything reported back to ePO properly.  It had Agent 4.5.0.1810 (4.5 Patch 2).  I don't have a Win7 64-bit system to test it on.

See McAni's post in this thread for a possible solution.

Jay

[Former Member]

Same issue here, testing on windows 7

Message was edited by: hlager on 1/27/11 10:48:31 PM GMT+01:00

[Former Member]

Hi all,

I have resolved this issue in our ePO console. I was also getting the same issue of installed products not showing up in ePO with our VSE 8.8 Pilot group, and i just took it for granted that this was a known issue as per release notes.

I then realised, that since i had VSE 8.8 in the Evaluation branch, and had not installed the Extension yet under "Software", i could not manage this product (even though a few pilot PCs were running VSE 8.8).

1. With VSE 8.8 still running off the evaluation branch (no need to change the branch to current), i installed only the VSE 8.8 zip and the Help installer.zip extenstions under Menu ->Software->Extensions.

• Make sure you do not install the VirusScanReports8800 (that is a part of VSE880LML zip) extension, as this will replace your VScan8700 reports. This should be installed only when your whole fleet moves to VSE8.8 after pilot testing is complete. Unzip the main VSE880LML.zip, and then individually install extensions VSE880_Client_Help.zip and VirusScan8800.zip into your ePO. Leave the VirusScanReports120.zip as it will replace your Virusscan 8700 reporting.

2. Once the two extensions are installed, you will now be able to view the product in your policy catalog and change any policies as required.

3. Do a wake-up call on your pilot machines running VSE 8.8, and your Products Installed will update properly.

Hope this isn't too confusing, and hoepfully helps someone.

[kink80]

Make sure you do not install the VirusScanReports8800 (that is a part of VSE880LML zip) extension, as this will replace your VScan8700 reports. This should be installed only when your whole fleet moves to VSE8.8 after pilot testing is complete. Unzip the main VSE880LML.zip, and then individually install extensions VSE880_Client_Help.zip and VirusScan8800.zip into your ePO. Leave the VirusScanReports120.zip as it will replace your VirusScan 8700 reporting.

Are you saying that any custom reports you have created in the VirusScan Enterprise section will be deleted or that the VirusScan 8800 reporting will not work with VirusScan 8700 clients? If you meant the latter the new reporting extension should be (is) comaptible with the older versions of VSE otherwise how could you monitor your machine swhile in the "transistion" period. I am also pretty sure that your custom reports will be kept when you check in the new 8800 reports. It may just rename them.