On Thu, Aug 13, 2020 at 4:09 PM Stefan Bogdan Cimpeanu <[email protected]> wrote:
> Hello Mike, > > Appreciate the fast answer. > > In our setup we have multiple guacamole servers, which are grouped > geographically due to legal reasons, especially around this mapped drive > feature. > For group A, we use a shared folder A, where users get their own subfolder > with their guacamole user name, for group B a different shared folder B, > and so on. > > This behaviour is only for one fo the groups, although all groups are > being deployed identically. > Here’s a short (and terribly cropped) sample of the behaviour > https://www.youtube.com/watch?v=0QnYCBL-cAk&feature=youtu.be. This is not > VM specific, as all VM’s going to this particular guacamole group, > experience this behaviour. We’re using Azure storage for the shared folders. > Well ... I'm not sure what might be happening there, but it is not possible for Guacamole (which manages the drive receiving the file) to affect whether Windows believes its own local file exists. I suggest investigating further to try to identify a difference between the Windows machine/group that is working vs. the Windows machine/group that is not. I do not believe this behavior is related to Guacamole in any way, as the error you're seeing relates to a resource that is entirely outside Guacamole's scope of control. - Mike
