WMS public cloud version local repository needed?

Thanks for your answer, but what does it mean condors

So what is the advantage of using WMS pro public cloud version in terms of saving costs, when  there is still a local repository on a windows server needed. How about home office places? Do I have to setup the ThinOS client inhouse and send it then to the employee’s home office place? How about upgrade ThinOS version? Is a home office place then using the local repository at the company place.

Are there any documentation besides the admin7deployment guide to get in-depth knowledge of the concept.

Roman

So this means that the “local” repository could also be on a Server in the cloud somewhere and not necessarily on the LAN where the clients are?

we have an ousourced data center (IaaS, PaaS) in which all servers are. Our employees have thin clients (ThinOS) and access VDIs in the data center via Citrix. In other words, there are no servers in the LAN of the employees (location). Currently I have a WDM installation on a server in the data center. I would like to eliminate this server (costs). My consideration now is that I run the WMS version in the public cloud (low cost, outsourced maintenance) with the required remote repository on a cheap rented server in the cloud (not in the outsourced data center). So I can keep the maintenance costs low. Therefore I would like to know, if the WMS_Repo must be local (LAN of coworker) or if it can be also remote (not in the LAN coworker), assuming good InterNet speed.

Hope not to bother you too much