ePO-MER is an ePO deployable version of WebMER. The WebMER tool collects the following McAfee product data from your computer so that Technical Support can analyze and resolve the problem.
The information collected includes:
Event logs
File version details
Files
Process details
Registry detail
Contents:
Click to expand the section you want to view:
Click Menu, Software, Master Repository, and then click Check In Package.
When you see the Check In Package wizard, select the package type, and browse to and select the package file MER-FOR-EPO-x.x.x-DEPLOYMENTPKG.zip.
Click Next to display the Package Options page.
In the Branch section, select the branch you want (Current or Evaluation).
In the Options section, select Move the existing package to the Previous branch.
Click Save to check in the package and wait while the package checks in.
You see the new package in the Packages in Master Repository list on the Master Repository tab.
Install the Policy Management package:
Click Configuration, Extensions, and click Install Extension.
When you see the Install Extension dialog box, click Browse, select the extension MER-FOR-EPO-x.x.x-POLICYMANAGEMENT.zip.
Click OK.
Verify that you see the product name in the Extensions list.
Click the ePO-MER Update Package, and click Download.
The MER_FOR_EPO_Update.zip is downloaded.
From ePO, check in the Update package:
Click Menu, Software, Master Repository, and then click Check In Package.
When you see the Check In Package wizard, select the package type, and browse to and select the package file MER_FOR_EPO_Update.zip.
Click Next to display the Package Options page.
In the Branch section, select the branch you want (Current or Evaluation).
In the Options section, select Move the existing package to the Previous branch.
Click Save to check in the package and wait while the package checks in. You see the new package in the Packages in Master Repository list on the Master Repository tab.
Define policies for executing the MER and uploading the output file.
To save the MER file, open the policy and decide on a location.
To configure FTP and Anonymous FTP, enter the URL as either:
ftp://<ftpserver>/<subfolder>
Or
<ftpserver>/<subfolder>, because ftp:// is automatically added to the beginning of the server URL.
NOTES:
Any subfolder must be included in the URL. Because the upload is from the client system, it must have connectivity to the server.
To verify the FTP user name and password configuration, use Verify Credentials.
To configure UNC, enter the server path as either:
\\<server>\<subfolder>
Or
<server>\<subfolder>, because \\ is automatically added to the beginning of the server URL.
NOTES:
Any subfolder must be included in the URL. Because the upload is from the client system, it must have connectivity to the server.
To verify the UNC user name and password configuration, use Verify Credentials. A domain account is needed for UNC and must be in the format of domain\user
Save the policy and apply it to the group or groups where the MER tool is to be deployed.
NOTE: By default, the file is saved on the client in the following location: %AllUsersProfile%\Application Data\McAfee\Supportability\MER for ePO
To complete the following procedure, see the "Deployment Tasks" section in the Product Guide for your ePO version.
From the ePO console, create a Product Deployment client task.
Apply this task to the group or groups to which you want to deploy the MER tool.
After the MER tool package is deployed, create an Update Task to install the Service Pack (MER Update package - MER_FOR_EPO_Update.zip).
Create a client task called Run MER. The client task type is ScanTask (MER for ePO x.x.x).
If you are using Run Client Task Now, set the Stop Task on the Client After: Value to 24 hours.
Select Update MER data to Technical Support, and enter your SR number and email address to automatically upload the data to your SR
After the task has run on the client, the results file is created in the location specified in the policy. The file is uploaded to Technical Support, if the SR is provided
