Profile Configuration Issues?

Hello Profile Community:

We’ve been having some challenges with Profile, and wondering if any one else in this community is going through similar challenges.

First, let me share a little bit about our environment:  We use Azure Virtual Desktops.  At the moment,  we have 15 hosts (8 vCPUS, 64GBs RAM, SSD for C:) with up to 12 user sessions per host. Users could get connected to any random host – so their personal data is stored in User Profile Containers with FS Logix. There are about 150 users at this time of year – more so during tax season.  At any point in time, of the 12 users on a box, I would estimate about four or so are using Profile at the same.

We update a master image with new OS patches and application versions weekly, and all the hosts are re-imaged from this master image every weekend.

One significant observation we’ve made is that Profile creates a directory for each user in the following path:

C:\ProgramData\Intuit\AutoUpdateClient\{DOMAIN}\{USERNAME}.

This directory is about 250 MB’s per user.

Please note that this path is stored in the C:\ Drive – and not the User Profile Container (C:\Users\{Username})

That path doesn’t exist at the beginning of the week because the user has never logged into this “brand new” box…

This, I believe, has three impacts on us:

The first one is disk space consumption. I can easily accommodate 20 users, but when more than 20 users log into the individual host over the course of the week, I run into disk problems at the end of the week. Remember – the user gets a random box at the start of the day.

The second issue here—and this is speculation on my part —is that I suspect the license info is stored in that directory. As a result, the first time a user connects to a host, they end up having to enter a license key instead of remembering it week after week.

The third is probably our most challenging issue – I believe when each user launches Profile for the first time and we create that directory, we do a lot of WMI queries – so many in fact,  that WMI runs away on the box.  I have seen WMI use up 75% of my CPU after a single user launches Profile - interrupting every user on that box, and in certain circumstances, I’ve even had to do hard-reboot the box to get it working again.

I was hoping for a mechanism to store that file in the User Profile Container rather than Program Data.  I think that addresses the disk space issue because it’s in each users container; it addresses the license issue since the directory persists week over week; and it addresses the CPU usage, since it doesn’t have to create that directory over and over.

Anyone have the same kind of issues? Any advice you can provide?