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.

 

[ChatGPT]

To verify whether software (like the eSET Agent software) has been successfully installed via Group Policy Object (GPO), you can follow these steps:

---

1. Check Software Installation Logs​

GPO-driven software installations are logged in the Event Viewer:

1. Open Event Viewer (Win + R, type eventvwr, hit Enter).
2. Navigate to:
   

    Applications and Services Logs > Microsoft > Windows > GroupPolicy > Operational

3. Look for entries related to the software installation.
   • Successful installations will have Information logs.
   • Any Error logs indicate installation failures.

---

2. Check Installed Programs​

Verify if the software is listed in Programs and Features on the client system:

1. Open Control Panel > Programs and Features.
2. Look for the eSET Agent in the list of installed programs.

---

3. Check Registry Entries​

Group Policy software installations create entries in the registry:

1. Open Registry Editor (Win + R, type regedit, hit Enter).
2. Verify the software entry under:
   

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

   or (for 32-bit applications on 64-bit systems):
   

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

3. Look for a registry key that corresponds to the eSET Agent. This typically includes the software's details like version, installation date, and publisher.

---

4. Check GPO Application Status​

Inspect the GPO responsible for the installation:

1. Open the Group Policy Management Console (gpmc.msc).
2. Navigate to the GPO applied and ensure:
   • The GPO is linked to the correct OU (Organizational Unit).
   • The Software Installation Policy is correctly configured under:
     

      Computer Configuration > Policies > Software Settings > Software Installation

3. Confirm that the deployment status says Assigned or Published.

---

5. Force and Refresh the GPO​

If you're uncertain whether the GPO applied, manually force Group Policy updates:

1. Open Command Prompt as Administrator and run:
   

   cmd gpupdate /force

2. Check for installation results in the logs or programs list afterward.

---

6. Use PowerShell to Verify Installation​

You can also run the following PowerShell command to check if the software appears in the list of installed programs:

Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like "*eSET Agent*" }

This will display details if the software is installed.

---

Troubleshooting Installation Issues​

If the software hasn’t installed:

1. Ensure the GPO is correctly linked to the target OU and that the computers/users are within the scope.
2. Check network connectivity to ensure the client machine can reach the shared path containing the MSI file.
3. Confirm that the account running the installation has sufficient permissions to access the shared installer file.

---

Let Me Know!​

If you're still having trouble or need assistance troubleshooting the logs or setup further, let me know—I'll be happy to help!