Most AVD projects get judged on two things after go-live: are the apps current, and does the environment survive a bad day? Nerdio publishes documentation on both topics for Nerdio Manager. This issue walks through what those pages say. Everything about Nerdio Manager below comes from Nerdio’s own documentation, so treat it as the vendor’s description, not an independent test.
Keeping third-party apps current
According to Nerdio’s guide to Unified Application Management (UAM), UAM is a tool for managing a list of third-party apps and keeping them up to date through deployment policies. It supports Azure, AVD and Intune-enabled environments.
The docs list built-in repositories: Windows Package Manager Community, the Microsoft Store and the iOS Store. You can also add custom repositories for apps those sources do not cover. Windows devices are deployed and updated with WinGet, and other platforms go through the Intune Connector.
The workflow has a clear split between two levels:
MSP level: You find apps in the Unified Catalog and assign them to all accounts or to one account. The docs stress that assigning does not deploy anything.
Account level: You create a deployment policy with a name, targets (included and optionally excluded groups) and the apps and versions to install. Choosing “latest” keeps the newest version installed.
Two limits from the page are worth noting. UAM currently supports per-device deployments only, with per-user planned. And all UAM deployments start through the Intune agent, so they follow its refresh cycle. For devices outside Azure and AVD, the device must be managed by Intune, and a device group is needed when you target a group rather than all devices.
Resilience, component by component
Nerdio’s BCDR guidance for AVD assesses each component on its own and covers three outage types. It says AVD deployments with Nerdio Manager are intrinsically redundant and highly available, but that your recovery targets and budget decide what extra protection you need.
The guidance starts with who recovers what. The AVD service is Microsoft-hosted and fails over on its own during a regional outage. Nerdio Manager is not in the path of a user’s connection, so an outage there does not block sign-in, but without it you would power on session hosts manually in the Azure portal. Active Directory must be reachable or users cannot sign in. In most deployments, session hosts hold no data and can be recreated if the desktop image is available. FSLogix profile storage is the critical data and must be replicated.
Three kinds of bad day
Corruption or local failure. The docs recommend automated configuration backups for Nerdio Manager, multiple domain controllers, versioning images before changes, auto-heal for broken hosts, and restoring damaged profile files from backup.
A single zone or data center failure. Check that your region supports Availability Zones for every product you use, with particular attention to Premium Files. Spread session hosts across zones at deployment, and use Azure Files Premium with ZRS for profiles.
A whole region failure. The recommended pattern is active/passive across two regions. That means a second Nerdio Manager instance in the secondary region, domain controllers there, images cloned after every change, and a decision on session hosts. You can pre-stage powered-off hosts and turn auto-scale on at failover, or provision on demand, which costs less but takes longer to recover. For profiles, the docs state that Azure Files Premium does not support geo-redundant storage, so they point to Azure NetApp Files with cross-region replication.
The architecture view
Nerdio’s AVD disaster recovery architecture article frames the same topic around ownership. Microsoft runs the control plane. The customer owns session hosts, profiles, apps, data and identity. It compares active-active, active-passive and Azure Site Recovery, and lists three ways to handle profiles, including FSLogix Cloud Cache.
Several points are not specific to Nerdio. The article says Microsoft publishes no numeric RTO or RPO for AVD disaster recovery, so you set your own. It says Azure Compute Gallery is regional and does not replicate automatically, so you copy image versions yourself. It advises against using ASR test failover for AVD session hosts, and suggests testing with scheduled starts of secondary hosts and drills with a test user group.
The same article makes performance and savings claims about Nerdio Manager. Those are vendor claims, and I have not verified them.
What to take away
Decide which apps are managed by policy and which stay baked into images, then check repository coverage for your list.
Write down your own RTO and RPO before choosing between pre-staged and on-demand hosts.
Plan profile replication early, because according to Nerdio’s docs Azure Files Premium does not currently support geo-redundant storage.
Rehearse failover and failback. A plan that was never run is a guess.
Listen / Read more
Listen: Azure Virtual Desktop vs Windows 365 with Dieter Kempeneers and Dominiek Verham, which touches on images, profiles and disaster recovery.
Read more: Azure Virtual Desktop - Simply Explained

