Current and Future Clients/Partners are Welcome.
Use the same AD field (CN, not UPN) for both ProfileDisks and Portability settings
I do not know if this is a bug or new feature, but here goes. :)
ProfileUnity uses the truncated part of the UPN as the "username" to build the ProfileDisk.
ProfileUnity THEN uses the CN to build the portability and redirected folders.
This is not consistent and causes errors. When a user in our environment logs in, ProfileUnity uses the truncated part of the UPN as the "username". Our UPNs DO NOT MATCH the CN at all. This leaves the user with 2 folders on the Profile server.
To complicate matters, we use Horizon View with Pods. If a user attaches to a local Pool, 2 different folders are created. If they attach to a remote Pool, only 1 folder is created. Hence the user "looses" his/hers appdata/ProfileDisk.