NMM - Install, Manage, and Optimize

Carl Long

May 06, 2024 21:20

Applies to: Nerdio Manager for MSP (NMM)

Disclaimer : Nerdio Manager for MSP is an automation and management solution. NMM Partners are responsible for understanding, and managing Microsoft Identity Services and Azure Resources. For Identity and Azure support, please contact your Distributor or Microsoft directly.

Other Articles in this Series

Microsoft Azure Resources and NMM Prerequisites
Step 1 - Install, Manage and Optimize NMM (You are here)
Step 2 - Adding Accounts in NMM
Step 3 - Managing Accounts in NMM
Step 4 - Tips, Tricks and Customizations

Installing, Managing and Optimizing NMM

This document will guide you through the process of installing, managing and optimizing Nerdio Manager for MSP. By following this guide, you are registering an Enterprise Application in your own Azure tenant, in a subscription that you select and into a new Resource Group. Once the install is completed, you’ll gain access to a URL and be able to login to Nerdio Manager for MSP web application.

This guide contains Nerdio Help Desk articles (KB's) and videos that further explore them.

Prerequisites
Install Nerdio Manager for MSP
Managing and Customizing NMM
- Update NMM
- Users and Roles in NMM
- Remove NMM
- Modify NMM URL (Azure App Service)
- Reboot NMM (Azure App Service)
- NMM Costs (Azure App Service)
Optimizing NMM
- Obtain Azure App Logs
- Harden Azure App Services
- Harden Azure SQL Services
- Reviewing Logs in NMM

Prerequisites for Installing NMM

You must be logged into Microsoft Entra ID as a Global Administrator before starting the deployment process via the Azure Marketplace.
You need to have an Azure subscription that is accessible to your Entra ID user with owner role. The subscription must be able to deploy Azure SQL, Web Application, Key Vault, Application Insights and Automation account in your selected region.
You must have a virtual network and subnet available to deploy AVD session host VMs. You will be prompted to select this virtual network and subnet during the installation process.
You must have Windows Active Directory or Microsoft Entra Domain Services deployment accessible from the virtual network where AVD session host VMs will be deployed. The custom default DNS server setting specified on the virtual network subnet must be pointing at a DNS server that is AD-aware.
Windows Active Directory must be synchronized with Microsoft Entra ID.
You need an Active Directory user account with rights to join and un-join VMs from domain. This user account must be able to create computer objects in at least one OU in AD domain and be able to disable these computer objects.