Deploying nvm-windows noinstall package with Microsoft Intune for standard users

[DeltaFourCoding]

Deploying nvm-windows No-Install Package with Microsoft Intune for Standard Users

Overview

I wanted to share an Intune deployment approach for nvm-windows using the nvm-noinstall.zip package.

The goal is to install NVM for Windows at the machine level so standard users can install and switch Node.js versions without needing local administrator rights.

This deployment method:

• Installs NVM to C:\Node\NVM
• Sets NVM_HOME and NVM_SYMLINK as machine environment variables
• Adds the required NVM paths to the system PATH
• Configures settings.txt
• Grants standard users the necessary permissions under the NVM install path
• Avoids pre-creating C:\Node\nodejs, allowing NVM to manage it as the active Node.js symlink path
• Creates an NVMVersion.txt marker file for reliable Intune detection
• Backs up the existing NVM folder during upgrades

---

Download

I've attached the deployment toolkit used for this implementation.

NVM-Windows-Intune-Toolkit.zip

Contents include:

• Install script
• Uninstall script
• Detection script

The NVM binaries are not included.

Download the desired nvm-noinstall.zip release from the official NVM Windows release page and place the extracted nvm-noinstall folder alongside the scripts before packaging.

Folder Structure

Before packaging, place the scripts and extracted no-install package in the same source folder.

Source
├── nvm-noinstall
│   ├── nvm.exe
│   ├── settings.txt
│   ├── install.cmd
│   ├── elevate.cmd
│   └── other nvm-noinstall files
├── Install_NVM_NodeJS.ps1
├── Uninstall_NVM_NodeJS.ps1
└── Detection_NVM_NodeJS.ps1

---

Preparation

1. Download the Desired Release

Download the desired nvm-noinstall.zip release from the project releases page.

2. Extract the Package

Extract the contents into a folder named:

nvm-noinstall

3. Place the Scripts

Place the following scripts beside the nvm-noinstall folder:

• Install_NVM_NodeJS.ps1
• Uninstall_NVM_NodeJS.ps1
• Detection_NVM_NodeJS.ps1

4. Update Company Name

In all three scripts, update:

$CompanyName = "Your Company Name"

5. Update Version Variables

In the Install and Detection scripts, update the version value to match the NVM release being packaged:

$NvmPackageVersion = "1.2.2"

$ExpectedNvmVersion = "1.2.2"

---

Packaging with IntuneWinAppUtil

Use the Microsoft Win32 Content Prep Tool to package the application.

Example:

.\IntuneWinAppUtil.exe `
    -c "C:\Packages\NodeJS\NVM\V1.2.2\Source" `
    -s "Install_NVM_NodeJS.ps1" `
    -o "C:\Packages\NodeJS\NVM\V1.2.2\Output"

This will create the .intunewin package for upload into Intune.

---

Intune Configuration

Install Command

powershell.exe -ExecutionPolicy Bypass -File .\Install_NVM_NodeJS.ps1

Uninstall Command

powershell.exe -ExecutionPolicy Bypass -File .\Uninstall_NVM_NodeJS.ps1

Install Behavior

System

Detection Method

Use a custom PowerShell detection script:

Detection_NVM_NodeJS.ps1

Recommended settings:

Setting	Value
Run script as 32-bit process on 64-bit clients	No
Enforce script signature check	No

---

Upgrade Process

When a new NVM version is released:

1. Download the new nvm-noinstall.zip
2. Replace the contents of the existing nvm-noinstall folder
3. Update the version variables in the Install and Detection scripts
4. Repackage using IntuneWinAppUtil
5. Upload the new package to Intune
6. Deploy as an update or supersedence relationship

No script modifications beyond the version number should normally be required.

---

Backup and Rollback

Before copying new NVM files, the install script creates a backup of the existing NVM folder.

Example:

C:\Node\NVM.Backup_20260623_081500

This provides a simple rollback path if issues are encountered after upgrading.

---

Handling Existing nodejs Folders

Older deployments may have created:

C:\Node\nodejs

as a physical folder.

Newer NVM versions expect to manage this location themselves.

During installation:

• Empty folders are automatically removed.
• Non-empty folders are automatically moved to a timestamped backup.
• Existing symlinks or junctions are preserved.

This prevents the common error:

activation error: NVM_SYMLINK is set to a physical file/directory

---

Standard User Usage

After deployment, users can manage Node.js versions without requiring administrator rights.

Examples:

nvm install latest

nvm install 24.16.0

nvm list

nvm use 24.16.0

node -v

npm -v

---

Why Use the No-Install Version?

For managed enterprise environments, the no-install package offers several advantages:

• Fully controlled deployment through Intune
• Consistent installation location
• No interactive installer required
• Easier upgrades through Win32 app supersedence
• Standard users can manage Node.js versions after deployment
• Works well in environments where local administrator rights are restricted

Hopefully this helps anyone looking to deploy NVM at scale through Microsoft Intune while still allowing developers flexibility in managing Node.js versions.

[coreybutler]

We have a build option with an official Intune installer coming in v2.

[DeltaFourCoding]

That is good to hear. Feel free to take from my script if you want to to help build it out. Always want to see the community grow.

[coreybutler]

Update: September 2026

Version 2 certified builds ship with a code-signed MSI and Intune files. There is a guide for Deploying with Microsoft Intune and Deploying with Active Directory. The governance add-on also provides ADMX/ADML and additional deployment scripts.