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.
conrad.murray@powersyncpro.com
Article
Last Month
TL-DR Edge and Chrome browser saved passwords are not migrated. Bookmarks are preserved. You need to manually export them pre-migration and re-import them. Options: Export / Import passwords Use a password vault like LastPass or 1Password EXCEPT… If your use case is migrating from Hybrid Entra joined (or AD Joined) to Entra Joined “aka go Cloud nat
There may be times where you need or want a complete uninstall of PowerSyncPro Migration Agent. The following script will achieve this for you. You can use this script stand-alone, or incorporate it into your software deployment tools and also Intune as a Platform Script under Scripts and remediations. It will: Check for the presence of PowerSyncP
Occasionally after a migration Office applications might not sign in properly. This can present in not being able to create a new Outlook profile or not being able to correctly sign-in to Word at the accounts screen. This is usually due to conflicted Office licensing and Identity. Try following the steps in this article: Reset activation state for
Recently at a client we saw this error when the workstation was trying to register. (TLDR: invalid Pre Shared Key “PSK”) Category: Agent API EventId: 0 HttpMethod: POST Uri: https://powersyncpro.contoso.com/Agent/register {OriginalFormat}: HTTP {HttpMethod} {Uri} A transient HTTP error occurred while contacting PSP server: Error code: InternalServe
PowerSyncPro has the ability to restore deleted objects from the target AD Recycle Bin if they were ever created or matched by PowerSyncPro. They might have been deleted manually in the target by accident, or got marked out of scope in the source through a config change, or the objects themselves were moved to an out of scope OU, or had an attribut
You may see this error (No connection could be made because the target machine actively refused it. (login.microsoftonline.com:443)) when trying to add an an Entra ID Directory to your PowerSyncPro Server configuration: You would see this screenshot when saving your directory: and in the C:\PowerSyncProLogs directory in the file that is PSP-YYYYMMD
You are trying to generate the Bulk Enrollment Token in your tenant to support Entra join of your devices: But when you click “Generate” nothing happens, or you are taking to the Microsoft authentication page but after Sign in, you are returned with a blank browser screen: This will happen if the URL you have started your configuration from in
PowerSyncPro Migration Agent Known Issues and Limitations Version : This document is relevant to PowerSyncPro Workstation Migration Agent version 3.1x Known Issues and Limitations Admin Fallback Account Password The password complexity that you use here must match any policy requirements on the device, otherwise you will see an event log error lik
There could be a situation pre-cutover of a tenant where you will be taking over the domains, but you need to match the users in advance. The users may have been created in the target with the *.onmicrosoft.com value as the right part. So you could have a user like: SOURCE DisplayName: Conrad Murray mail conrad.murray@tailspintoys.com UserPrincip
If post migration you need to add a user to be a local admin to an Entra Joined device you can log in as a local Admin yourself. From an elevated command prompt you can run: net localgroup admnistrators "AzureAD\[EntraIduserPrincipalName]" /add e.g.net localgroup administrators "AzureAD\donald.duck@contoso.t2t.dev" /add When you look in the Loc
Once an Agent is installed and registered the agent will collect User Profile information and report it back to the PSP Console. PowerSyncPro harvests user profile information on the device solely for the purpose of writing this data back to the PSP database, where it is displayed in the PSP Console under User Profile Reports. This information is c
Bulk Enrollment Token for directory is about to expire If you see a message like this: Warning Bulk Enrollment Token for directory M365 Fabrikam is about to expire Bulk Enrollment Token for directory M365 Contoso is about to expire Then you need to go to your Directory configuration and open in “Edit mode” At the bottom of this dialog screen you
Important Note This was fixed in PowerSyncPro v3.2. If you are running version 3.2 or later, this is no longer required. If you are using Intune to push out the PowerSyncPro Migration Agent, then there is a possibility it could be uninstalled / removed during the execution of the migration agent part way through, and your migration will fail to c
Migration Agent Logs If you are having issues with your Windows 10/11 Workstation migrations and you raise a support ticket you will almost certainly be asked to provide the logs either from the PSP Server and/or the Application Event Logs from the device itself. Additionally, you maybe be asked to send screenshot of your Runbooks and Batches. If y
Why is the account BPRT set as the OWNER of the newly migrated Workstation in Entra? Update Feb 2026 We have seen more recently that for Entra Joined devices when you try to enrol in InTune they are successfully updating the owner of the workstation with the logged in user if licensed. However, Microsoft documentation is not reflective of this yet
Intune Enrol Entra Joined devices The PowerSyncPro Runbook option “Enroll Devices to Intune”, when selected, will check if the device is enrolled to Intune. The Migration Agent will report to the local Windows workstation Application event log success or fail, and the logs will be sent up to the PowerSyncPro server. If the Migration Agent sees that
When the PowerSyncPro Windows Workstation Migration Agent finishes and users log in to their workstation for the 1st time, there is one final step that must run under the User Context and this is the re-permission of AppX packages. AppX packages are things like the Company Portal, Quick Assist, Sticky Notes, Calculator, Spotify, Netflix, Weather and
Server Sizing The recommended size for the PowerSyncPro Server depends on the number of Migration Agents reporting to it, as well as the number of objects being synchronised. Up to 1,000 Agents and 100,000 Objects 2 vCPU 16 GB RAM Additional 100 GB data drive SQL Express can be used Over 1,000 Agents and 100,000 objects 4 vCPU 32 GB RAM Additional 2
If you are running PowerSyncPro Server in WORKGROUP or will install PowerSyncPro under a local account or you just want to run the PowerSyncPro Service using a local account then you will need to add that account to SQL and make it DBOwner of the 'PowerSyncProDB' database, or may even want to make it a SQL SA. If you create a local account called ps