This message was deleted.

Mount the VHD in Disk Management when the user is logged out. Don't forget to assign it a drive letter and unmount it when finished

Thanks James Question, when using profile containers..is there a reason why there are still a good few files in users upm profile...so office licence activation tokens?

Have you still got other UPM policies applying?

Where id expect them all to be in the profile container..we are taking whole profile through

Are there any still written to the Registry?

Errm sorry what location would I be looking in

HKLM\Software\Policies\Citrix\UserProfileManager I think

Actually found it So we have lots of profiles there yes...which point to the profile container location only for each folder

Any other UPM settings defined? Folder inclusions or exclusions and the like?

Errm yes they do have some inn Citrix components/profile managment/file system/synchronization

Might be an idea to remove those policy settings and see if stuff is still getting written outside of the container then

Ok cool thanks When using profile containers with us taking everything...is there still a need to use exclusions for best practice or just have inclusions and exclusions empty

Take the lot, IMHO

Cool I will test it out and relay back any issues Cheers

It's the old conversation about exclusions, the trade-off between storage utilization and performance. Personally I'd take the lot initially and tune pieces out ONLY if required. Compaction settings should help keep storage down a bit.

Cool thanks It's a new environment I've been put on Wondering why activation tokens are showing for some users and not others with office being activated fine...but I'll get the above looked into firrst

I don't match the VDA and Profile Management version as a rule, although Citrix licensing may want you to. So you mean you have a 1912 VDA and 2203 UPM policies trying to enable containers?

We have 1912 CU 8 VDAs with 1912 Profile management version Look like someone has gone in and put in the 2203( or one of the previous CR releases) ADMX me thinks..thus everyone's profile containers are empty. 1912 PM does not support wildcard for profile whereas someone has enabled that policy with a wildcard for us Citrix docs say 1912 profile container policies are under file system whereas 2203 has its own node We have Profile container with own node so looks like someone has messed it up

Easy way to find out, revert to standard 1912 container settings and see if it works as expected. Sounds plausible though