For the complete documentation index, see llms.txt. This page is also available as Markdown.
Nightfall Windows Agent Deployment: JumpCloud MDM
Instructions on how to install the Nightfall agent on Microsoft Windows using the JumpCloud MDM.
Prerequisites
Before beginning the install, make sure you have the following:
A JumpCloud Admin / MDM environment ready, and the JumpCloud Agent already configured or in process of being configured for your Windows devices.
The Nightfall Windows Agent (MSI) and associated parameters (API_KEY / COMPANY_ID) as from the Nightfall Endpoint page → Download Packages.
Internal device group or OU targeting plan within JumpCloud (for example: Windows corporate laptops, desktops, etc).
Communication to end-users (if needed) and any documentation of maintenance windows or reboots.
Valid credentials / admin rights on target Windows devices (or ability via MDM / script to install silently).
Connect JumpCloud to Nightfall
Log in to app.nightfall.ai and navigate to Settings > MDM Profile.
Select JumpCloud from the list of supported MDM providers.
Complete the OAuth flow to grant Nightfall read-only access to your JumpCloud device and user directory. This maps JumpCloud user identities to devices in the Nightfall console automatically.
Deploy the Nightfall Agent via JumpCloud
Use JumpCloud’s Commands/Policies feature to deploy the Nightfall Agent silently to the target Windows device group:
In JumpCloud Admin Portal: Device Management → Commands → Commands tab → click + Command (or use Policies if available)
Type: Windows
Check "Windows PowerShell"
Command: Copy/paste in the command shown below.
Replace the File Destination ($msi value) as needed or leave as-is.
Replace the API_KEY and COMPANY_ID with what is in the Nightfall console.
From the Nightfall Endpoint page > click Download Package > copy the API_KEY and COMPANY_ID from the Windows command.
Under Files > click + File > upload the NightfallAgent.msi
Setting the path of the file upload
Copy the File Destination where the MSI would be copied onto the enrolled devices by jumpcloud mdm.
Choose a Device Group
Navigate to the Device Groups tab.
Check the group to use for deployment.
Click "Save".
Click "Run Now".
Post-Installation Verification
After installation, verify that the Nightfall Agent is functioning correctly:
In JumpCloud, Device Management → Devices, check that the device remains active and that there are no policy conflicts or errors.
In the Nightfall Console → Integrations → Manage (macOS or Windows) → confirm the device is in the “Connected” state.
On the Windows machine, check Programs & Features to confirm “Nightfall Agent” appears.
In Services (services.msc), verify the Nightfall service is installed and running.
Confirm that the NightfallUI app is shown on the taskbar and that the Version, Company UUID, and Device ID are correct.
Conduct a simple test of exfiltration detection (per your internal policy) to ensure the agent is monitoring as expected.
Troubleshooting & Best Practices
Ensure that the MSI installation parameters (API_KEY, COMPANY_ID) are correct and correspond to your Nightfall account.
If installation fails silently, re-run the installation with log flags and check the install log file:
If devices have pending reboots or other software installations, consider staging installation to avoid conflicts.
Because you’re installing via JumpCloud, ensure the device’s JumpCloud Agent is up-to-date and reporting properly before deploying Nightfall.
For stealth or minimal-disruption deployment (if desired), schedule installs during off-hours and consider using silent /qn /norestart. The Nightfall Windows guide supports silent installs.
Document versioning of Nightfall Agent: if you need to upgrade later, consider how you’ll script uninstall + reinstall or patch. The MSI guide covers uninstall.
Monitor JumpCloud’s device compliance and policy execution logs to ensure the command executed successfully.