This article will explain what problems are encountered when you want to run Nomadesk in a Remote Desktop Services setup, and how to resolve them.
Nomadesk will work out of the box on Windows server operating systems.
However, when you want to use the Windows server with Remote Desktop Services to allow users to remotely connect to it, there are some problems you might encounter:
- The data is synchronised to the local hard drive of the Windows server, causing a lot of duplicate data and network traffic.
- If the RDS server is configured to remove local application data at every logout, the user will have to import, and re-sync their data in every session, causing a bad user experience, data that is not immediately accessible, and unnecessary network traffic. It also render 'TheftGuard' unusable, as you will have a new 'computer' entry for every session.
The Nomadesk software can be configured (using registry keys/group policies) to avoid these problems. The solutions:
The client can be configured to import the Vaults through the WebDAV protocol, instead of synchronising everything to the local filesystem.
To do this, create the following registry key
Create an entry (of type REG_SZ or REG_MULTI_SZ): With name "WebDAV"
with value(s): Wildcard e.g. (*, or vaulLabel , ....). If you then want to import a vault you still see the message "import as synchronized vault", but it will be a WebDAV connection.
- Changing configuration location:
By default, Nomadesk stores it's configuration in 2 places: %LOCALAPPDATA% and %APPDATA%. On many RDS servers, the Nomades config in %LOCALAPPDATA% is removed whenever a user logs out. To prevent this, create the following registry entry (of type REG_SZ):
with as value a user-specific path value that is not automatically removed, example: %APPDATA%\NomadeskConfig