If you do have multiple licenses, one for each site, you can request a cloud relay key for each installation and simply use the correct relay key with the correct LsAgent installations. If you are using the relay, you can choose which scanning server is used to fetch the data from our cloud server.
If you have a multi-scanserver installation, and you are using a direct connection (so no relay server) you can choose which scanserver is tried first, and if there are any other scanservers that should be checked afterwards if the first scanserver connection fails. Since there is no way to split asset permissions based on site, there is also no need for multiple LsAgent keys per installation, since all assets are in the same database anyway. Because of this and until we have a better way of splitting asset management permissions, only 1. This way you can find out which devices utilize manufacturer support and also which license key can potentially be re-used on other machines. However, I've added your topic to the list of people requesting the feature. Lansweeper allows for 1 production installation per license. When scanning Windows systems, Lansweeper automatically scans the serial number which is used to determine whether the machine is using an OEM license key or not. This particular feature is already on our list of thing to do in the future.
The Lansweeper data will always be stored in one database, meaning that even if you have multiple scanning servers, they will all send data to the same database, and people can view all the assets in that single database. Just to avoid confusion, in order to isolate assets in the way you described, you'll need multiple licenses (one for each site).
0 kommentar(er)
