Importing and exporting policies
The features described in this section are supported on macOS devices.
You can import and export policies from one deployment of Ivanti EPMM to another. Topics in this section include:
This feature is supported when importing or exporting policies or configurations between Ivanti EPMM instances that are running the same version.
Exporting policies or configurations
Exporting policies and configurations help reduce errors when you have multiple instances of Ivanti EPMM. You can export a configuration .json file for an existing policy, modify it, then import it to another policy. The export/import features allow you to do this.
Procedure
- Select Policies & Configs > Policies or Policies & Configs > Configurations. All available policies are listed in the policies table. All available configurations are listed in the configurations table.
- Select a single policy or configuration to export. You can sort, as necessary, to find the one you want to export.
- Select Export to create an export .json file. No application-related information is captured when exporting a policy or configuration.
- Enter an export password and confirm it in the two password fields. This password encrypts sensitive configuration data during export (including passwords and certificates). The same password is required to import the exported data to another Ivanti EPMM server.
- Check Remember password for this session if you want to re-use the password during a session. A session is defined as the length of a single login. The session ends when you log out or when you have been logged out by the system.
- Locate the .json file, open, modify, and save it, as necessary.
Review this file before reusing it as values are not verified before importing them. For instance, If a security policy .json file has a minimum password length of 2000, the imported profile will have a minimum password length of 2000 and, when pushed to devices, it will enforce all the devices to have such a big password. The encrypted hash of the sensitive data is displayed in the .json file, but the sensitive data is not displayed in plain text format in the .json file.
Importing policies or configurations
Importing policies and configurations help reduce errors when you have multiple instances of Ivanti EPMM. You can export a configuration .json file for an existing policy, modify it, then import it to another policy. The export/import features allow you to do this.
Procedure
- Select Policies & Configs > Policies or Policies & Configs > Configurations.
- select Import to locate a saved exported .json file.
- Enter the name of the file or select Browse to locate it.
- Enter the password created when the file was exported. See Enter an export password and confirm it in the two password fields. in Exporting policies or configurations.
- Check Remember password for this session if you want to re-use the password during a session. A session is defined as the length of a single log-in. The session ends when you log out or when you have been logged out by the system.
- Read the warning message and select the I Agree check box.
- Select Import to add the new policy to the policy table. If you import a policy that already exists, you can override the policy or cancel the import. If an exported policy has child object/s (such as app control rules and compliance actions), Ivanti EPMM creates them during import. If the child objects already exist, they are overridden.