eSET Agent Software installation using GPO

[ajeesh thazthethil]

Re: eSET Agent Software installation using GPO

1. Created the GPO for eSET auto installation
2. Given the share folder path which contains the agent.msi and .ini files
3. Applied the GPO to the particular computer OU
4. Updated the GPO on the client compute and checked the GPO has been taken place
5. Client computer asked for the reboot

Proceed with all the above steps however, the client system is still unable to install the eSET agent.

Every GPO update the system asking to reboot. Please advise

 

[ChatGPT]

It seems you've done the correct initial steps to create and apply a Group Policy Object (GPO) for the eSET agent's auto-installation, but the client computers are repeatedly asking for a reboot, and the software isn't installing. Let's address the possible issues and troubleshooting steps:

Troubleshooting Steps:​

1. GPO Scope and Security Filtering:
   • Ensure that the GPO is linked to the correct Organizational Unit (OU) containing the target computers.
   • Check that the Security Filtering includes the computer accounts for which the GPO is intended.
   []File Share and Permissions:
   • Verify the file share path provided in the GPO is accessible from the client computers.
   • Ensure that the share and NTFS permissions on the network share folder where the agent.msi is located permit read access to the computers (e.g., Domain Computers group has read access).
   []Startup Script Configuration:
   • Configure the software installation as a Startup Script if it fails during the startup phase.
   • Scripts can handle installation better than the Assigned deployment type under some conditions.
   []Event Logs:
   • Check the Event Viewer on the client machines for any Group Policy or MSI installation errors:
     • Go to Event Viewer > Windows Logs > Application.
     • Look for MSI Installer error logs.
   []Verbose Logging:
   • Enable verbose logging for Windows Installer on the client machines to capture detailed logs of the installation process:

     shell msiexec /i \\server\share\agent.msi /L*v C:\path\to\log\msilog.txt

   • Review the log files for any errors during the installation.

     Image Insights:​

     The images you’ve attached provide detailed insights into your GPO settings for deploying the eSET Management Agent. Here's a summary:

     Image 1: ESET Agent Deployment Configuration​

   • Winning GPO: "ZMS - eSET Agent Deployment."
   • Product Information:
   • Name: ESET Management Agent (2)
   • Version: 11.0
   • Language: English (United States)
   • Platform: x64
   • Deployment Information:
   • Deployment type: Assigned
   • Deployment source: \\[Server]\[path]\agent_x64.msi (path partially redacted)
   • Uninstall when out of scope: Disabled
   • Advanced Options: All disabled

     Additional Points:​

   • Reboots on GPO Update:
   • Repeated reboot prompts might be due to pending operations in Windows Installer or Windows Updates. Postpone other updates or installations that might interfere.

• MSI Parameters:
  • Ensure you're passing any necessary parameters or configuration settings (INI file) required by the eSET MSI package during installation. By following these troubleshooting steps and ensuring your environment settings are correct, you should be able to narrow down the cause of the installation issue on the client machines. Let us know if you need further assistance with specific steps or have more information to share.

 

[ajeesh thazthethil]

How do we know the software has been installed through GPO or not?

 

[Mike]

How do we know the software has been installed through GPO or not?

Check appwiz.cpl (Programs), services.msc (Services), and the actual file system or registry.