Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Third-party AV still installed after deploying agent using GPO in OfficeScan (OSCE)

    • Updated:
    • 23 May 2017
    • Product/Version:
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • Windows 10
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2008 Datacenter
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Server R2
    • Windows 2012 Standard
    • Windows 2012 Standard R2
    • Windows 2012 Web Server Edition
    • Windows 2016
    • Windows 2016 Server Datacenter
    • Windows 2016 Server Standard
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary

Your third-party antivirus (AV) software is still installed even after deploying the OSCE agent via Group Policy Object (GPO). All other installation methods are working successfully.

Details
Public

Automatic uninstallation of third-party AV software through GPO deployment is supported when the deployment method used is "Published" and it requires users to take action. Refer to the following KB article for more information: Deploying the OfficeScan (OSCE) client using Group Policy Object (GPO).

However, uninstalling third-party AV fails if "Computer Configuration" and "Assigned" are selected even before the user successfully logs into the system; the MSI package is already installing in the background. Because of this, the OSCE agent MSI installation process fails to uninstall the third-party AV because it checks specific UIs that are not present since the user is still logged into the system.

As a workaround, you can use different installation methods using Trend Micro Vulnerability Scanner (TMVS), Software Deployment (i.e. SCCM)  software, login script, etc.

Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy; Uninstall
Solution Id:
1117245
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.