We have rebooted several of these servers and this group policy has successfully installed the Manage Engine client on these servers since this group policy is set to install the Manage Engine agent during Startup.

We have also manually installed the Manage Engine client on several other servers. The Manage Engine client can be installed without the server needing to be rebooted to complete the installation.

I am interested in creating a new group policy that I can push out to other servers in a different Organizational Unit that will install the Manage Engine client on these servers without these servers needing to reboot (which as part of the current group policy would cause the Manage Engine client to install during Startup).

This is because we need the Manage Engine client to be installed on the servers in this other Organizational Unit immediately and we can't wait until the scheduled maintenance time in a couple of weeks when these servers will next reboot for the Manage Engine client to be installed.

The current group policy that installs the Manage Engine agent on startup was created using the following PowerShell script. Now what I'm looking for are the steps where I can modify either the existing group policy or the PowerShell script so that the new group policy will push out the Manage Engine agent installation which will install on the target servers in the other Organization Until without these servers needing to be rebooted so that the group policy in its current form will run during startup.

I'm not sure if the best way of doing this will be using a Task that is scheduled to run at a certain time on the target servers or if there is an easier way of doing this by modifying the existing group policy.

What are the steps in modifying this current group policy or PowerShell script to do this?

The current group policy that installs the Manage Engine agent on the target computers is listed in the attached screenshot: