N-central Troubleshooting
Client agent deployment to Microsoft Entra ID using Microsoft Intune
Last Modified
Friday, May 9, 2025
Description
- Trying to deploy agents to an environment that uses Microsoft Entra ID/Intune
- NOTE: Cloud based domain, no probe possible
- Possible to deploy software via Intune via app deployment, but it fails installation with command line used.
Environment
- N-able N-central
Solution
- Deploying with Intune is possible with the following steps:
- Extract the MSI from the installer.
- Create an intunewin package using the intune package converter "InTuneWinAppUtil.exe" (found on github):
- Upload the package to Intune.
- Use the following command:
- msiexec /i "windowsagent.msi" /q CUSTOMERID="123" CUSTOMERNAME="Name of client" SERVERPROTOCOL="https" SERVERADDRESS="Address of Server" SERVERPORT="443"
REGISTRATION_TOKEN=<registration token> is also necessary if using N-able N-central 2020.1 or higher.
To extract Windows Agent MSI installer:
Start the Windows Agent installer. Allow the installer to extract the Windows Agent MSI file as part of the normal Windows Agent install process.
The Installer will create the following path to store the Windows Agent MSI file in
C:\Users\*User Name*\AppData\Local\Temp\{D4D230B6-D5EB-4C78-8156-FEED25BF7DF5} <
. This folder will be the variable and will be different for each extraction.
The file location may be different for newer versions:
Go in the most recently modified folder in C:\Windows\Downloaded Installations
and that is where the MSI is. Or under C:\Users\{LOGON NAME}\AppData\Local\Temp
open a file called MSI*****.LOG (the most recent one) and this will have the following info in it pointing you to the MSI location
The Windows Agent.MSI file is now available for use where deemed necessary.
We however do not fully support this install method and would suggest the original install method using the Windows Agent executable where possible.
Article Number: 107985