Skip to main content

Manage Developer Mode

Purpose​

This solution manages Windows Developer Mode across Windows 10 and Windows 11 devices. It lets you define a desired state, run scheduled checks or enforcement, and track the current state on each endpoint.

Use this solution to:

  • Enable Developer Mode where required.
  • Disable Developer Mode where not allowed.
  • Audit the current Developer Mode state without making changes.
  • Compare desired vs current state for validation and compliance reporting.

Associated Content​

Custom Fields​

ContentTypeFunction
cPVAL Desired Developer ModeCustom FieldStores the desired action: None, Check, Enable, or Disable.
cPVAL Current Developer ModeCustom FieldStores the last reported Developer Mode state from the device.

Automation​

ContentTypeFunction
Manage Developer ModeAutomationEnables, disables, or checks Developer Mode based on parameter or custom field value.

Group​

ContentTypeFunction
Manage Developer ModeGroupTargets devices where desired state is Check, Enable, or Disable and excludes None.

Task​

ContentTypeFunction
Manage Developer ModeTaskRuns daily at 11:00 AM on devices in the group to enforce or audit Developer Mode state.

Script Reference​

ContentTypeFunction
Manage-DeveloperModePowerShellCore script logic used by the automation package.

Implementation​

Step 1: Create the Custom Fields​

Step 2: Create the Automation​

Step 3: Create the Group​

Step 4: Create the Task​

Step 5: Validate Results​

FAQs​

Q1. What does this solution do?​

It helps you control and audit Developer Mode on Windows endpoints using a desired-state custom field, a scheduled task, and a reporting group.

Q2. What happens when the desired value is None?​

Devices with None are excluded from scheduled automation targeting. You can still run the automation manually, and manual runs default to Check if no action parameter is provided.

Q3. Which setting takes priority: task parameter or custom field?​

The automation Action parameter takes priority. If no parameter is supplied, the automation uses cPVAL Desired Developer Mode. If neither is set, it defaults to Check.

Q4. My automation suddenly started failing with signature errors. Was the script changed?​

Not always. The NinjaOne automation implementation validates two signatures during execution: its own script signature first, and then the signature of the downloaded script. A failure in either check will stop execution. If changes were made outside the approved process, signature validation can fail.

Q5. Why does script signing matter?​

Signing confirms script integrity and publisher trust at both levels of execution. It helps ensure the NinjaOne automation wrapper and the downloaded script have not been tampered with and are approved for use.

Q6. What should I do if I get a signature validation failure?​

Re-run the automation first to retry a clean download. If the issue continues, verify endpoint security tools are not modifying script files and confirm network access to the content repository. If any update is needed to the NinjaOne automation implementation, route the change through ProVal so the script can be re-signed after the update. Include activity logs and error details when escalating.

Q7. Where can I check the current status for all machines where this solution is enabled?​

Use the Manage Developer Mode group. This is the best place to review all targeted devices in one view.

Check these columns in the group:

Changelog​

2026-06-17​

  • Initial version of the document