UPM is installed (standalone or as part of Citrix Virtual Delivery Agent).
Installation completes successfully without errors.
UPM policies are configured and applied.
However, user profiles are not managed by UPM during logon/logoff
Local profiles are created instead

Policy Verification

UPM policies are confirmed to be applied by verifying the following registry locations:

HKEY_LOCAL_MACHINE\Software\Policies\Citrix\UserProfileManagerHDX
HKEY_LOCAL_MACHINE\Software\WOW6432Node\Policies\Citrix\User\UserProfileManagerHDX
HKEY_LOCAL_MACHINE\Software\Policies\Citrix\<session ID>\User\UserProfileManagerHDX
HKEY_LOCAL_MACHINE\Software\WOW6432Node\Policies\Citrix\<session ID>\User\UserProfileManagerHDX

On affected machines, the following registry entries are missing:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\UserProfileMan

And UserProfileMan is not present in:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logon
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logoff

Expected Configuration

The following entries should exist:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\UserProfileMan
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logon
Value: SessionEnv,UserProfileMan,Profiles,Dot3svc,Wlansvc,GPClient,TermSrv,AUInstallAgent,*
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logoff
Value: *,TermSrv,GPClient,Profiles,UserProfileMan,SessionEnv,Wlansvc,Dot3svc

During installation, UserProfileManager.exe is responsible for registering UPM with Winlogon by performing RegQueryValue and RegSetValue operations on:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logon
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Configurations\Default\Logoff
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\UserProfileMan

In this scenario, Process Monitor trace took during installation confirms there are no attempts at all to access or modify these registry paths during installation.

This indicates:

The UPM installer is functioning correctly
However, the code path responsible for Winlogon registration is not executed

This behavior is caused by an incorrect process execution context, where required privileges are not properly inherited.

Specifically, intermediate installation processes run at Medium integrity level instead of High, which prevents the required registration logic from executing.

Install UPM using an explicitly elevated SYSTEM context:

psexec -i -s msiexec /i <actual path>\profilemgt_x64.msi
or
psexec64 -i -s msiexec /i <actual path>l\profilemgt_x64.msi

After installation, you need to verify
1.The required registry keys are created by confirming that UserProfileMan is present in Logon/Logoff values as mentioned above.
2.Perform a user logon test

If the registry entries are present, UPM will process user profiles correctly.

If the registry are not set, it indicates additional OS-level restrictions (e.g., UAC, security policies, or hardening settings) preventing correct execution. In that case, further investigation is required by your Windows/OS team.

Citrix Profile Management does not process user profiles during user logon and logoff.
Instead, a local user profile is created on the system.