AutoCAD on Citrix VDI

[MarkSanchezSPEC]

We have AutoCAD 2019 setup in a Citrix VDI environment. When our users open AutoCAD and make changes to their AutoCAD workspace, say like opening and docking windows, setting toolbar locations, changing the color of their command line background, etc., these settings persist for the duration of the Citrix session, meaning they can re-enter AutoCAD multiple times and all their UI-related workspace tweaks persist. However, upon logging off of Citrix, then logging back in, their previous workspace settings are returned to the default AutoCAD state when they re-open AutoCAD.

It should be noted that we are not using dedicated virtual machines, but rather, each time someone logs in, they do so on a brand new VM. However, we have setup folder redirection within the virtual environment, such that items like the user’s Desktop is persisted across different Citrix sessions. Why doesn’t AutoCAD behave the same way with regard to the user’s workspace settings? AutoCAD is supposed to be "Citrix Ready". What might we be doing wrong?

[casquatch]

@MarkSanchezSPEC - Late to the party here, but...we have a Citrix VDI setup, but we are using app layering and the user profile is setup as a layer. This means that each time a new VDI is assigned, the same user layer is also assigned. Since this setup doesn't use redirection for profiles, so AutoCAD doesn't blow up.

But I'm curious where you are storing your user CUIX files. Are those in the redirected locations, or are they local to the VDI? I'm assuming VDI, since they are being reset, so it might just be as simple as placing those in another location, either a mapped drive that they always have access to, or somewhere in the redirected profiles.

We also have a XenApp server for AutoCAD. This does use profile redirection for when a user runs the app (some users prefer the app over a VDI). In this case, we are referencing the same CUIX files as within the VDI and things seem to work ok. The main issue that we had in the past was one that you mentioned in another post about the ENU folder needing to be re-created with each new server login. We setup a script to basically check to see if it already existed on another server and if so, copy it's contents from one to the others (run as a login or logoff script, I can't recall).