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 collected to help customers correlate devices and users, enabling business analysis such as identifying which devices are primarily used or “owned” by specific users. This data may also be used to assist with scoping devices into migration batches or proactively contacting users if a potential migration issue is identified.

The warnings related to profile harvesting that may appear in the Windows Application Event Log before, during, or after a migration are benign and have no impact on migration runbook execution or device state. In many cases, these warnings are generated when a stale Windows user profile exists on the device, such as a profile belonging to a user who has previously logged on but is no longer active.

During profile harvesting, PowerSyncPro retrieves the local user SID and attempts to resolve it against Active Directory for on-premises AD accounts, as well as against its own internal directory tables. For Microsoft Entra ID users, PowerSyncPro performs lookups exclusively against its internal directory tables for the relevant Entra tenant.

When a Remote Directory Sync Agent is used, Active Directory lookups are not performed as part of the profile harvesting process. In this deployment model, PowerSyncPro relies solely on its internal directory data to associate SIDs with users. This is a known and documented limitation of the Remote Directory Sync Agent and does not affect migration execution or device state.