If UPN is being used and it differs from the existing domain name, password synchronization will fail. UPN support requested for differing domain names.
Support has worked directly with Product Management and has determined this feature will not be included at this time. Please subscribe to this article for any updates. To be added to this Feature Request, please contact support who will track specific customer requests therein.
Reproduced the behavior on SEE 11 with the following steps:
1. Added to an existing user named user1 (domain: SEE) an UPN which is firstname.lastname@example.org. 2. On an endpoint encrypted with SEE 11, verified the current list of registered users. The user1 user is present on the registered users list. 3. Logged off as user1 from the endpoint and logged in as email@example.com with the same password as user1. The login completed successfully. 4. Registered firstname.lastname@example.org with the following command:
5. Verified and confirmed that the user was properly added to the disk. Rebooted the machine twice and verified login to BootGuard both as user1 and email@example.com. SSO works for both users. 6. When logged in as firstname.lastname@example.org, change the password to newuser1pass via Ctrl+Alt+Del. Logged off from Windows and logged in again with the new password, confirmed it is working. 7. Reboot the machine and attempt to log in to BootGuard as email@example.com using the newuser1pass password. This does not work. The old password - user1pass - works fine, however SSO is not functioning properly as Windows passphrase is different now. 8. Reboot the machine again and attempt to log in to BootGuard as user1 using the newuser1pass password. Successfully login with SSO directly to Windows.
Imported Document ID: TECH226600
Subscribing will provide email updates when this Article is updated. Login is required.