US English (US)
GB English (UK)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create ticket
English (US)
US English (US)
GB English (UK)
  • Home
  • Migration Agent

Agent Register initial request failed: Machine not in PSP

Learn how to troubleshoot and fix the Agent Register initial request failed: Machine not in PSP error for smoother operations.

Written by Neil Langston

Updated at September 12th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Getting Started
  • FAQs
  • API Documentation
  • Integrations
  • Migration Agent
  • Directory Synchronisation
  • Remote DC agent
  • Remote Password Sync Agent
  • Install and Configure
  • Support
  • Complex Expressions
+ More

You see the following error(s) on the workstation event viewer or in the failed communications view in the PowerSyncPro server, and you cannot add the workstation to the batch.

Agent Register initial request failed: Machine not in PSP

Failed to complete initial register call: Machine not found

The good news is the workstation has successfully communicated and been able negotiate with the PowerSyncPro server using the PreSharedKey and EndPoint URL, however Migration Agent did not complete the registration fully.

PowerSyncPro only allows known machines to register with the server as an additional security step, so the workstation must be in the AD or Entra. This error is reporting that the device has not been imported into PowerSyncPro server SQL database.

To resolve

  • Check that you have a directory setup for the source environment where the workstation resides.
  • Ensure that devices are selected to import on that directory profile.
  • If it is a new device, the import of the directory may not have been run since the device was created, run the import and ensure the sync schedule is frequent enough for your needs.
  • Once the device is present in the PowerSyncPro database then the Agent should register, and you can review the single object report to locate the computer object within the directory.
  • To check that the agent has registered successfully you can navigate to the agents section on the PowerSyncPro server.
  • If the agent still isn’t appearing navigate to the tray application on the workstation, right click and select “Register Migration Agent”, this will attempt to register the agent.

The agent uses the fibonacci sequence to re-try to register in minutes, 1, 1, 2, 3, 5, 8, 13, 21, 34 etc or until the service is restarted.

If you try and add the device to a batch, and it is missing, then DirSync has not ingested the device yet. Once the device has been imported into PowerSyncPro server, you will also be able to add it into a batch.

error message system failure

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Migration Agent is not starting or registering on a device
  • Prevent Migration Agent uninstall when deployed from Intune
  • Intune Enrollment has not succeeded

Subscribe to Newsletter

Drop your email in the box below to sign up. We promise to keep our updates relevant and useful – and we’ll never share your details.

PowerSyncPro is the ultimate product for easing the pain and frustration during mergers, acquisitions, divestitures, and consolidations.

Terms & Conditions

  • FAQs
  • Privacy Policy
  • Cookies
  • Anti Slavery Notice

PowerSyncPro

  • Case Studies
  • Contact sales
  • Meet the Team
  • EULA

Get Connected

Room 73, Wrest House, Wrest Park, Silsoe, Bedford, England, MK45 4HR
info@powersyncpro.com

Twitter Youtube Linkedin

Knowledge Base Software powered by Helpjuice

Expand