ºÚÁϺ£½Ç91Èë¿Ú

Managed Service Provider (MSP) Admins can save valuable time setting up new organizations by cloning from an existing organization. Double checking policies, re-creating user groups, and manually inputting settings for a new org is not only time consuming, it’s prone to error as well. Save time, and  improve consistency by cloning from an org that you’ve already spent time setting up!

Prerequisites

• You need to have Admin with Billing permissions in order to clone an org.
• You need to be a paying ºÚÁϺ£½Ç91Èë¿Ú customer to access this feature.

Considerations

• While this feature saves admins time, we highly recommend that you review your new org after it’s been cloned to ensure your selections are correct. 

Clone an Organization

To clone an organization:

1. Log into your .
2. Go to the Organizations tab, then click the + Create button. 
3. Select Clone From Existing Organization.
4. On the next page, click on the Select an Organization to Clone dropdown menu to select a source org that you’d like to clone from. 
5. Enter a name for your new Organization in the next field.

Select Organization Settings

To select org settings:

1. Next, under Select Organization Settings, are the copied over settings from the original org. You can click on any of the settings to remove them from being cloned from the original org and customize it once it’s finished being cloned. The following settings are copied over from the original org:
   • For User Portal Settings:
     • Read-Only on the User Portals profile page for all users.
     • Allow all users to enroll their devices through the User Portal, see Enable Users to Install the ºÚÁϺ£½Ç91Èë¿Ú Agent to learn more.
     • User Portal Session Duration (amount of time after which idle User Portal sessions expire.)
   • For Password Recovery Email Settings:
     • Password Recovery Email for all users (allowing users to reset their password with a different email than their org email.)
   • For Administrator Management Settings:
     • SSO with Google on Admin Portal is enabled or disabled.
   • For Password Settings, see Manage Password and Security Settings to learn more.
     • Password Minimum Length
     • Password Complexity
     • Password Originality
     • Password Aging
     • Lockout
   • For UID/GUID Management Settings:
     • A unique User ID assigned by a Unix operating device to each user is enabled or disabled.
   • For Password Configurations:
     • Settings for M365/Entra ID about maintaining users or suspending users during Password Expiration or Account Lockout.
     • Settings for LDAP about disabling users or removing users during Password Expiration or Account Lockout.

Select Device and User Management Options

To select device and user management options:

1. Under Select Device and User Management Settings, are the copied over settings from the original org.You can click on any of the settings to remove them from being cloned from the original org and customize it once it’s finished being cloned. The following settings are copied over from the original org:
   • For Commands:
     • Commands that are applied to the original org, without sensitive, or proprietary information will be copied over.
       • Notes: If the command type is Linux or Darwin and the user is not Root, the command will not be copied (this does not apply to windows commands.)
       • Files uploaded on the command will be ignored. 
   • For Configured Policies and Policy Groups:
     • Policies and Policy Groups that are applied to the original org, without sensitive, or proprietary information will be copied over.
       • Notes: Policy Values with type TEXT, TEXTAREA, FILE, or marked as sensitive are not copied.
       • Policies that have one or more values with type TEXT, TEXTAREA, FILE or are marked as sensitive that are required will not be copied.
   • For User Groups:
     • User Groups are copied over, users are not. 
   • For Device Groups:
     • Device Groups are copied over, devices and any MDM settings are not. 
   • For MFA Configurations (Push, TOTP, WebAuthn):
     • Settings for user authentication will be copied over.
       • Note: DUO configurations will not be cloned.
   • For Conditional Access Policies:
     • Any Conditional Access Policies for how users access their resources will be copied over.
       • Notes: If the conditional access policy applies to a specific app, it will not be copied over.
       • If the conditional access policy has a user group set for inclusion or exclusion and User Groups were not selected for clone, then the conditional access policy will not be copied over.

Customize Organization Configuration

Select Features

To select features:

1. You can customize the features of your new org before it finishes cloning. Under Selecting Features, are the copied over settings for Directory Insights, Remote Assist, and System Insights. You can leave these as is, or you can opt for ºÚÁϺ£½Ç91Èë¿Ú’s default settings, disabling all of these.
2. Click the checkbox next to the feature to enable or disable it.

Select Admins

To select Admins:

1. On the next page is a list of all the Admins that will be copied over from the source org. 
2. If you need to remove any admins, uncheck them before continuing. You can also search for a specific admin. 
3. Once you’ve selected your Admins, click Clone Organization. 
4. Don’t close this window while cloning is in progress or you may encounter a failure.
5. Once your org has been cloned, we highly recommend that you review your new org to ensure your selections are correct.

Manage your Cloned Organization

To manage your cloned org:

1. From your MTP, click on the Organizations tab. Then click Launch on your newly cloned org. 
2. The Admin Portal for your new org will launch and you can manage or edit anything you need to from there. See Settings in the Admin Portal to learn more.