To install Iperius ONE massively via GPO , you need to generate the custom MSI package from the dashboard, copy it to a shared network folder and configure a group policy in the Windows domain.
The MSI package already contains the information needed to associate devices with your Iperius ONE environment. After installation, the computers are automatically registered and become visible in the Devices section of the dashboard.
What is the Iperius ONE MSI package for?
The MSI package allows system administrators to distribute the Iperius ONE Agent on multiple computers without having to manually run the normal Setup EXE on each device.
Using Active Directory and Windows Group Policy, you can automate installation on computers belonging to a domain or a specific organizational unit.
This mode is particularly useful for:
- companies with numerous Windows computers;
- MSPs managing multiple endpoints;
- domain administrators;
- centralized and unattended installations;
- standardized deployments on new devices.
What is the difference between the Setup EXE and the MSI package?
| Format |
Recommended use |
Mode |
| Setup EXE |
Installation on one or a few devices. |
Manual installation. |
| MSI package |
Distribution across multiple computers on a network or domain. |
Automated installation via GPO or other deployment systems. |
The Iperius ONE MSI package is customized during generation and contains the essential information for connecting computers to your account.
It is therefore not necessary to create a separate MST transform file to insert the license data.
Important: The MSI package is associated with your
Iperius ONE environment. Keep it in a secure location and do not distribute it outside
your organization or authorized devices.
How to generate the Iperius ONE MSI package
1. Access the Iperius ONE dashboard
Open the Iperius ONE dashboard and log in using your Master Account credentials.
Access the dashboard
Open Iperius ONE to generate the custom MSI package for your environment.
Log in to Iperius ONE
2. Apri “Agent download”
At the top of the dashboard, click the Agent download button .
3. Select the MSI package generation
In the Generate and Download Agent Setup window , select the option:
Also generate MSI package (for mass deployment through GPO)
Then click Generate Agent to create both the Setup EXE and the MSI package.
4. Download the MSI file
Once the generation is complete, download the IperiusONE_Setup.msi file to the computer used to prepare the deployment.
The package already contains the data needed to automatically associate computers with your Iperius ONE environment.
How to prepare the shared folder for the MSI file
1. Create a folder on the server
On the server or file server that is reachable by computers in the domain, create a folder for the installation package.
For example:
C:\MSI
Then copy the file into the folder:
IperiusONE_Setup.msi
Copy the MSI package to the folder that will be shared on the network.
2. Share the folder on the network
Open the folder’s properties and enable network sharing. The computers on which Iperius ONE is to be installed must be able to read the MSI file.
Share the folder and assign the necessary read permissions.
In a test environment, you can assign Read permission to Everyone . In a production environment, it’s best to limit access to the computers or domain groups that should receive the installation.
Caution: If the GPO is assigned to computers,
the domain computer accounts must also have read permissions
on both the share and the NTFS folder.
3. Check the UNC path
The file must be reachable via a full UNC path, for example:
\\Server2019test\msi\IperiusONE_Setup.msi
When configuring the GPO, always use the UNC path. Do not use a local path like C:\MSIor a mapped network drive like Z:\, because it may not be available when the computer starts.
How to create a GPO to install Iperius ONE
1. Open Group Policy Management
On the domain controller, open Server Manager , select Tools , and then select Group Policy Management .
Open the Group Policy Management console from Server Manager.
2. Create a new Group Policy Object
In the console, locate the domain or organizational unit that contains the computers on which you want to install Iperius ONE.
Right-click and select the option to create and link a new Group Policy Object.
Give the GPO an easily recognizable name, for example:
Iperius One Installation
Give your new Group Policy a clear name.
Best practice: Instead of immediately attaching the GPO
to the entire domain, you can initially apply it to a
test OU containing a limited number of computers.
3. Edit the new GPO
Right-click on the newly created GPO and select Edit .
Right-click on the GPO and select “Edit”.
Installation via Computer Configuration
Assignment via Computer Configuration installs Iperius ONE at the computer level and is generally the most suitable method for deploying an RMM Agent on all selected devices.
1. Apri Software installation
In the GPO editor, open the following path:
Computer Configuration > Policies > Software Settings > Software installation
Right-click on Software installation and select:
New > Package
Add a new package from Computer Configuration.
2. Select the MSI file via UNC path
In the selection window, enter the full network path to the MSI package.
For example:
\\Server2019test\msi\IperiusONE_Setup.msi
Select the MSI file from the shared folder using the UNC path.
3. Select Assigned mode
In the Deploy Software window , select Assigned and confirm with OK .
Set the MSI package as “Assigned”.
The package appears in the list of software assigned by the GPO.
Iperius ONE now appears among the software assigned to computers.
With this configuration, the package is normally processed during the startup of the computers affected by the GPO.
Installation via User Configuration
Alternatively, you can assign the package to specific domain users. In this case, the installation is processed during user logon.
Note: It’s not usually necessary to configure the same
package in both Computer Configuration and User Configuration.
Choose the mode that best suits your purpose: assign to computers
or assign to users.
1. Open Software installation in user configuration
In the GPO editor, open:
User Configuration > Policies > Software Settings > Software installation
Right-click on Software installation and select New > Package .
Add the package in the User Configuration section.
2. Select the package and the Assigned mode
Re-enter the UNC path of the MSI file, open the package and select Assigned mode .
3. Enable installation at logon
Right-click the package, select Properties , and open the Deployment tab .
Then activate the option:
Install this application at logon
Enable application installation at user logon.
When is Iperius ONE installed?
The installation time depends on the configuration you choose:
- with Computer Configuration , the installation is processed when the computer starts;
- With User Configuration , the installation is processed during user logon.
Group Policies are periodically updated by domain clients. To speed up application, you can run the following command on the affected computer:
gpupdate /force
Use gpupdate /force to request a policy update immediately.
After updating policies, you may need to restart the computer or log the user off and back on, depending on the assignment type configured.
How to verify that the installation was successful
After restarting your computer or logging in again, first check that Iperius ONE has been installed on your device.
Then log in to the dashboard and open the Devices section . The new computer should automatically appear in the list.
Check that:
- the computer name is present;
- the Agent is installed;
- the device appears online;
- the license status is correct;
- there are no critical errors.
There is no need to manually enter your license information during installation: this information is already integrated into the MSI package generated by the dashboard.
How to distribute the package only to certain computers
To avoid installing Iperius ONE on all devices in the domain, you can link the GPO to a specific organizational unit containing only the affected computers.
You can also use:
- GPO security filtering;
- dedicated computer groups;
- separate organizational units;
- a test OU before general deployment.
Before extending the deployment to the entire infrastructure, it is advisable to test the procedure on a limited number of endpoints.
What to do if the MSI package fails to install
If Iperius ONE is not installed on your computers, perform the following checks:
- verify that the GPO is linked to the correct domain or OU;
- check that the computer belongs to the affected organizational unit;
- verify that the package path is a fully qualified UNC path;
- check share permissions and NTFS permissions;
- make sure your computer can reach the server via the network and the domain’s DNS;
- check that the package is set to Assigned;
- run the command
gpupdate /force;
- restart the computer for an assignment via Computer Configuration;
- perform a new logon for an assignment via User Configuration;
- Check Windows Event Viewer for any Group Policy or Windows Installer errors.
Common errors when deploying via GPO
Use a local path
A path like C:\MSI\IperiusONE_Setup.msiis only valid on the server and does not allow clients to find the package.
Instead, use a UNC path like:
\\NomeServer\Condivisione\IperiusONE_Setup.msi
Use a mapped network drive
Mapped drives may not be available during computer startup, so don’t use paths such as Z:\IperiusONE_Setup.msi.
Do not assign permissions to computer accounts
If you use Computer Configuration, the computer accesses the file before the user logs in. The affected computer accounts must therefore be able to read the package.
Do not restart your device
A package assigned through Computer Configuration is normally installed during startup. Running it gpupdate /forcealone may therefore not complete the installation immediately without a reboot.
Apply the GPO to the entire domain immediately
Before deploying the package to all computers, test it on a separate organizational unit. This way, you can verify permissions, connectivity, and logging in the dashboard.
How to subsequently update the Agent deployed via MSI
When a new version of the Agent is available, you can update it directly from the Iperius ONE dashboard or use a new MSI package.
For a new centralized distribution:
- generate the updated package from the dashboard;
- save it in the shared folder;
- configure the new version in the Group Policy;
- test the deployment on a test group;
- then extend the update to other devices.
Conclusion
The Iperius ONE MSI package allows you to automate the installation of the Agent on computers in a Windows domain.
After generating the file from the dashboard, you need to copy it to a shared folder, using a UNC path, and assign it via a Group Policy.
For a machine-wide installation, generally use Computer Configuration . For a user-specific installation, you can instead configure User Configuration and execution at logon.
Once deployment is complete, the devices are automatically associated with your Iperius ONE environment and can be controlled from the centralized dashboard.
Generate the Iperius ONE MSI package
Log in to the dashboard to create the custom Agent and deploy it to computers in your domain.
Open the dashboard
Frequently Asked Questions about the Iperius ONE MSI package
How do I create the Iperius ONE MSI package?
Access the Iperius ONE dashboard, click on Agent download,
select the Also generate MSI package option, and click Generate Agent.
Once the generation is complete, you can download the IperiusONE_Setup.msi file.
Does the MSI package require an MST file?
No. The MSI package generated by the dashboard already contains the
essential information for associating devices with the
Iperius ONE environment and does not require an additional MST file.
What permissions are needed on the shared folder?
Computers or users affected by the GPO must have
read permissions on both the network share and the
NTFS folder containing the MSI package.
Should I use a UNC path for the MSI file?
Yes. In Group Policy, you must use the full UNC path,
for example, \\ServerName\Share\IperiusONE_Setup.msi. Do not use
a local path or a mapped network drive.
Devo configurare Computer Configuration e User Configuration?
Not necessarily. Use Computer Configuration to install
Iperius ONE at the computer level or User Configuration to
assign it to users. Choose the mode that best suits your environment.
When is Iperius ONE installed via GPO?
With Computer Configuration, installation is normally processed
when the computer starts. With User Configuration, it is processed during
user logon.
Can I force Group Policy to refresh?
Yes. On the affected computer, you can run the gpupdate /force command.
Depending on the assignment type, you may also need to
restart the computer or log in again.
Are devices automatically associated with the license?
Yes. The MSI package contains the information needed to
automatically connect your computer to the Iperius ONE environment. After
installation, the device appears on the dashboard.
Can I use the same MSI on multiple computers?
Yes. The package is designed for mass distribution and can be
used on computers that must be associated with the same
Iperius ONE environment, respecting the seats available in the license.
What should I do if Iperius ONE is not installed?
Check the GPO link, UNC path, folder permissions
, OU membership, and server connectivity
. Then run gpupdate /force and reboot the device.
Do you need assistance?
Contact Iperius technical support for assistance with generating the MSI package or deploying the Agent.
Contact Iperius