Instant Task Deployment Fails with “Invalid Authentication Passcode” - OS Deployment

Instant Task Deployment Fails with “Invalid Authentication Passcode” - OS Deployment

WarningProblem Description:
A client encountered a deployment failure when using an Instant Task to deploy an OS image over the network.
The error displayed: Invalid authentication passcode.


Notes

Observations:

  • The authentication passcode has been verified as correct.

  • Valid username and password credentials are used.

  • The same OS image deploys successfully when using a Standalone Task, confirming that the image itself is not corrupted or misconfigured.


Alert

Impact:

  • Deployment fails for machines using Instant Task with misaligned Remote Office boot media.


Info
Root Cause:
  • The issue occurs due to a mismatch between:

    1. The Remote Office of the boot media used to start the target machine

    2. The Remote Office assigned to the Instant Task

  • OS images are created in a specific Remote Office and may be replicated to others.

  • Only the image-created Remote Office and its replicated Remote Offices are valid for the Instant Task.

  • Booting the target machine using media from a different Remote Office than the task-assigned Remote Office triggers the authentication error.


Idea

Solution:

  1. Verify Remote Office Alignment

    • Ensure the Remote Office of the boot media matches the Remote Office assigned to the Instant Task.

  2. Confirm Booted Remote Office on Target Machine

    • Verify the Remote Office displayed in the top-right corner of the deployment screen matches the task’s assigned Remote Office.


Resolution / Expected Outcome:

  • Once the boot media Remote Office and the task Remote Office are aligned, the “Invalid authentication passcode” error is resolved.

  • The OS deployment via Instant Task completes successfully.



    • Related Articles

    • Restricting Browser Screenshots: Edge Web Capture Configuration

      Purpose To disable the built-in Web Capture (Screenshot) feature in Microsoft Edge via Registry configuration, ensuring users cannot capture screen content through the browser UI. Prerequisites Administrative Privileges: Required to modify ...