You can deploy multiple instances of the vRealize Log Insight Windows agent on target computers in a Windows domain.

For more information about why you need to reboot the client machine twice, see http://support.microsoft.com/kb/305293.

Prerequisites

Procedure

  1. Log in to the domain controller as an administrator or a user with administrative privileges.
  2. Create a distribution point and copy the vRealize Log Insight Windows agent .msi file to the distribution point.
  3. Open the Group Policy Management Console and create a Group Policy Object to deploy the vRealize Log Insight Windows agent .msi file.
  4. Edit the Group Policy Object for software deployment and assign a package.
  5. (Optional) If you generated an .mst file before deployment, select the .mst configuration file on the Modifications tab of the GPO Properties window. and use the Advanced method to edit a Group Policy Object to deploy the .msi package.
  6. (Optional) Upgrade the vRealize Log Insight Windows agent.
    1. Copy the upgrade .msi file to the distribution point.
    2. Click the Upgrade tab on the Group Policy Object Properties window.
    3. Add the initially installed version of the .msi file in the Packages that this package will upgrade section.
  7. Deploy the vRealize Log Insight Windows agent to specific security groups that include the domain users.
  8. Close all Group Policy Management Console and Group Policy Management Editor windows on the domain controller and restart the client machines.
    If Fast Login Optimization is enabled, reboot the client machines twice.
  9. Verify that vRealize Log Insight Windows agent is installed on the client machines as a local service.
    If you configured SERVICEACCOUNT and SERVICEPASSWORD parameters for using an .mst file to deploy multiple instances of vRealize Log Insight Windows agent, verify that vRealize Log Insight Windows agent is installed on the client machines under the user account that you specified.

What to do next

If the multiple instances of vRealize Log Insight Windows agent is not successful, see Mass Deployment of the Log Insight Windows Agent is Not Successful.