Azure Virtual Desktop

Hi All!

We have a customer who started to use Azure Virtual Desktop.

If the M-Files upgraded to a new version some user lost the desktop settings for vaults.

But some if they logged in the virtual desktop didn't loose the settings.

If you have any experience about this case, please inform me!

Thank you!

Best regards:

Kornél

Parents
  • Hi Kornél,

    We are in a similar situation and the customer would like to use an Azure File Share for the Shared Client Cache and we are not able to connect to it. The issue we are seeing is, that the M-Files Client Service does not seem to be able to connect to the File Share, see error message below. We are suspecting that the problem is the Local System trying to establish the connection instead of a user account.

    How did you handle this with your client?

    Thanks,
    Thomas




    M-Files Online
    
    The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist.
    The system cannot find the path specified.
    
    ServiceModuleBase.cpp, 1079, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    ServiceModuleBase.cpp, 825, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    ServiceModule.cpp, 274, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    CoApplication.cpp, 148, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    Configuration.cpp, 105, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    Configuration.cpp, 187, The root directory for cached files is invalid. The directory specified in the registry is invalid or the directory does not exist. (0x800407D1)
    Configuration.cpp, 187, The system cannot find the path specified. (0x80070003)
    FileHelper.cpp, 526, The system cannot find the path specified. (0x80070003)
    FileHelper.cpp, 526, The system cannot find the path specified. (0x80070003)
    (M-Files 22.6.11534.5 2022-08-03T13:38:38.443Z)

  • We at M-Files do not have an exact Azure Desktops in use but we do currently utilize a virtualized terminal servers at our "work from anywhere" concept. 

    At these environments, the data is stored with FSLogix to a different storage, from where the server always fetches them. This way the user doesn't acknowledge the session has changed in the background. 

    In our own scenarios, we have not faced the issue described in this topic. 

    FSLogix Overview - FSLogix | Microsoft Docs

  • Thanks for feedback.

    If anyone else is running into a similar issue, we found a workaround for our scenario using Solution 2 described in this article

    Where we use PsExec to launch a PowerShell instance under “NT AUTHORITY\SYSTEM”, when you then mount the Azure File Share in that context, the caching works as intended (at least in our initial tests). 

Reply
  • Thanks for feedback.

    If anyone else is running into a similar issue, we found a workaround for our scenario using Solution 2 described in this article

    Where we use PsExec to launch a PowerShell instance under “NT AUTHORITY\SYSTEM”, when you then mount the Azure File Share in that context, the caching works as intended (at least in our initial tests). 

Children
No Data