Forum Discussion
Intermitent issues writing files to Local_Username redirection.xml
accounts2021 Hi, unfortunately I haven't I hit a brick wall of support from vendor as Sage do not support VDI environments, however that appears to be more of an issue with using "ClickOnce" installers as thats a limitation of that and until that changes.
What I haven't tested mostly due to time, is mounting the FSLogix accounts in Azure Files rather than direct on a fileserver in azure.
With another WVD deployment I ran into performance issues/limitations of locating them on a fileserver then the bottleneck of access becomes the singulare fileserver, whereas if they were in Azure Files it is far higher and the bottleneck becomes the higher spec'd WVD that is trying to connect to it.
I have another project to deploy and will be using this method instead hopefully with better results.
StevenR we think we have found a solution, it seems the problem is related to the UAC virtualization. If you disable the UAC virtualization and restart the host it seems to work.
- Has this been a run the fix once and it has worked so far, I will give it a try as WVD is the better solution long term for this customer as long as sage 200 work 🙂
It does seem to be working, however we did not disable UAC V on the entire server.
We did not install our sage200 client using the click once installer, but instead have a single installation location for all users. This meant that in theory we only need to create a "Sage200Desktop.exe.manifest" file and set the correct "requestedExecutionLevel", but found that Sage had already generated one but renamed it to "Sage200desktop.manifest.manifest" (this is from memory so it might be named something else). We simply renamed this file and restarted the WVD host, its worked ever since.
We are are not sure why Sage had chosen to rename the manifest file, but so far we have not noticed any unexpected behavior.
