You can back up the configuration of a customer account in Nerdio Manager, download it as an export package, and import it into a different Nerdio Manager installation when you add the account there. This lets you move a customer account between installations, for example when an MSP merges with another MSP, when a customer moves to another MSP that uses Nerdio Manager, or when you migrate your installation to a new subscription.
The import re-creates most of the account configuration, so you do not have to set the account up again from scratch. Some configuration must still be completed manually after the import, as described in Complete the configuration after import.
The tasks in this article are performed at the MSP level, in the source installation and in the destination installation.
This feature is in Public Preview as of Nerdio Manager v7.3. The Import & Export tab and the Backup Account and Import Account dialogs show a Public Preview tag. Functionality and scope might change in future releases.
|
Issue/limitation |
Impact |
Mitigation/planned fix |
|---|---|---|
|
Scripted actions are not exported. |
Scripted actions that host pools, desktop images, or auto-scale settings refer to are missing after the import. |
Scripted actions might be the protected intellectual property of the source MSP and therefore aren't exported to avoid infringing the creator's rights. Re-create or re-link the scripted actions in the destination installation. |
|
Credentials and secrets are never exported. |
App registration secrets, Key Vault contents, and passwords are not in the package. |
Enter an app registration secret for the destination environment during the import. |
|
The backup holds the Nerdio Manager configuration and links only. |
Session host VMs, storage account contents, FSLogix profile data, and desktop image objects are not part of the package. User sessions and user data are not included either. |
These stay in the customer's Azure subscription and tenant. Make sure that the destination installation can reach them. |
|
Some configuration is outside the scope of the preview. |
App masking rules, custom RDP settings, capacity extender settings, an account-level copy of the global FSLogix configuration, and desktop image version details and changelogs are not exported. |
Reconfigure these settings after the import. |
|
After the import, auto-scale is disabled and all job schedules are paused. |
This happens even if they were active in the source account. It is by design, so that no automation runs against the environment until you have reviewed it. |
Review, and then re-enable auto-scale and resume the schedules. See the last task in this article. |
The following Nerdio Manager roles allow you to back up and import account configurations:
-
Super Admins can see the Import & Export tab and run the backup and import tasks. The tab is visible only to users who hold the required permission.
Following the Principle of Least Privilege (PoLP), you can define one or more Nerdio Manager custom role(s) with the access level that is required to export and import accounts:
-
Msp.Accounts.ExportImport allows the user to see the Import & Export tab, and to back up, download, and import account configurations.
The backup captures the Nerdio Manager configuration of the account in three areas:
-
Account provisioning settings: the desktop deployment model, the linked subscriptions, resource groups, and networks, the Key Vault and the Automation Account, directory profiles, FSLogix profiles, and backup recovery vaults and policies.
-
AVD and host pool configuration: AVD auto-scale profiles and configurations, host pool properties, and host pool custom tags.
-
Azure resource links and schedules: the Log Analytics workspace link, linked Azure Files shares, linked virtual networks, VPN gateways, and NAT gateways, the auto-scale configuration for servers and Azure Files, and the job schedules for host pools, session hosts, servers, desktop images, backup validation, VPN connections, and NAT gateways.
Note
AVD auto-scale configurations can use global, MSP-level auto-scale profiles. So that auto-scale does not break on import, any global profile that the account uses is included in the backup and is re-created as an account-level profile in the destination installation.
To back up an account configuration:
-
In the source installation, at the MSP level, navigate to Accounts.
-
Locate the customer account that you want to back up, and select Backup.
-
In the Backup Account dialog, confirm the backup.
Result: Nerdio Manager captures the configuration of the account and lists the backup on the Import & Export tab.
To download a backup:
-
On the Import & Export tab, locate the backup.
-
Select Download. The backup package is downloaded as a ZIP file.
-
Store the ZIP file securely, and give it to the administrator of the destination installation.
Important
The package does not contain credentials or secrets, but it does describe the Azure infrastructure links of the account. Treat the file as sensitive.
To import an account configuration:
-
In the destination installation, at the MSP level, navigate to Accounts. Start the account add process, or select Import Account on the Import & Export tab.
-
In the Import Account dialog, upload the backup ZIP file.
-
Enter a valid app registration secret for the destination environment. Secrets are never included in the backup, so you must enter it yourself.
-
Complete the remaining steps of the account add process. At the last step, Nerdio Manager applies the settings from the backup file to the new account.
-
Monitor the provisioning tasks on the Accounts Tasks tab.
The import restores most of the account configuration. Finish setting up the account as follows.
To complete the configuration:
-
Verify the app registration and its secret for the destination environment.
-
Review and re-enable Auto-scale on each host pool, and review the auto-scale configurations for servers and Azure Files.
-
Review the imported job schedules, and resume the ones that you want to run.
-
Re-create or re-link the scripted actions that host pools, desktop images, or auto-scale settings use.
-
Verify the Azure infrastructure links (subscriptions, resource groups, virtual networks, Azure Files shares, Key Vault, Automation Account, and Log Analytics workspace), and grant any permissions or consent that the destination tenant requires.
-
Verify the FSLogix profiles, and reconcile any settings that referred to the global FSLogix configuration of the source installation. Verify the backup recovery vault and policy links, and confirm the protected items.
-
Reconfigure the settings that are outside the scope of the preview: app masking rules, custom RDP settings, the capacity extender, and desktop image details.
-
Add the users, roles, and MSP-level integrations again, because they are configured outside the account backup.
-
Validate the account end to end: confirm the host pool properties and custom tags, run a test user session, and then enable automation.
Contact our Sales team for more information about this feature.
Raise a support ticket about this feature.
Comments (0 comments)