We would need more logs than what is posted. The logs in the agent\logs folder, as well as the install logs from VSE and the agent - should be in windows\temp\mcafeelogs. Preferable would be a mer from the system to view some registry entries and all relevant logs. (mer.mcafee.com - run the mer as administrator and choose vse and the agent as products).
There are several reasons for VSE not showing installed. See KB60593 for one. Are all the McAfee services running in services? Does the agent log show any policy enforcement, property collection, or plugin errors for VSE? That would be in the masvc log.
Sorry, found out that some of the printscreens were just black. Grabbed the last 5 minutes from the user before going home to get more logs. Found some remains in the temp-folder of this notebook fo the McAfee Agent AAC Host. I assume the cleanup-job shoudl get rid of this.
Downloaded the actual mer.exe and will run it tomorrow morning.
thanks for your advise
Checked KB60593: Plugin Flag for both 32/64: value is 0x00000000 (0)
compared to another w7-notebook all services are running
masvc.log is in notebook_2.zip
2017-11-30 15:00:00.417 macompatsvc(6224.7180) plugin.Error: Failed to open the plugin = C:\Program Files (x86)\McAfee\VirusScan Enterprise\VsPlugin.dll 5
2017-11-30 15:00:00.418 macompatsvc(6224.7180) plugin.Error: Failed to initialize the plugin for product id = VIRUSCAN8800 and plugin path = C:\Program Files (x86)\McAfee\VirusScan Enterprise\VsPlugin.dll.
2017-11-30 15:00:00.418 macompatsvc(6224.7180) compatbase.Error: Manageability client initialization failed for the application VIRUSCAN8800, error = 2003.
2017-11-30 15:00:00.418 macompatsvc(6224.7180) cmasvc.Error: Manageability client initialize/start failed for the application VIRUSCAN8800.
The mer will tell us a little more, but it is clear there are issues with the VSE plugin. You might want to try removing VSE, reboot, then reinstall and reboot again after install to see if that resolves before running the mer.
Installed VSE P9 an connected to ePo-console successfully. The Auto-Update-Task installed P10, the VSE P10 and the actual agent 220.127.116.11 show up in the ePo-console now.
The Dat-File is on 1111.0000, but should take up from the repository in the next hour. Now the user ist logged-on and we will see, how it progresses. Actually I took a second MER before i handed the computer back to the user.
NB512745_1.tgz 14.4 MB
after more than 24h, the notebook doesn't update to the newer dat-file, still on 1111.0000. The update from the epo-server failed, as well as the AutoUpdate from the client virusScan-Console.Still getting the same error: "Errro occured while getting point product callback component interface". In the client-console telling update successful tuesday, 5 of dec 2017 at 1pm:08:17.
compared the registry-content from a similar notebook and found out the following entries missing but can't tell the reason why at the moment
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\MCDATREP1000]
"Plugin Path"="C:\\Program Files (x86)\\Common Files\\McAfee\\DATReputation\\mgmtplugin\\datrepmp.dll"
"Product Name"="McAfee DAT Reputation"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\VIRUSCAN8800]
from the mer, it looks like you are running into issues with our processes being injected by 3rd party dll's and vse/agent processes are being blocked. Here is a screenshot of all the instances of this occurring in the system event log.
To resolve this, attached is a tool that will detect and add to the McAfee trust, any dll's that are injecting and causing this issue (refer to KB74176 for more info). Please remove VSE and the agent, reboot, run this tool, then reinstall the products and see if that resolves. Run the setup file.
McAfee_SysPrep_18.104.22.168.zip 1.9 MB