
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2014 02:06 PM
Hi, we'd like to get our License Management going and Lansweeper does a nice job so far.
However, it seems that LsPush has it's own list of "known Product Key Locations"(?) and therefore cannot extract keys that where added in the Lansweeper Server Backend. (Via Configuration -> Product Keys)
Three Questions:
a) Can LsPush extract more / less Keys than the standard (uncustomized) Lansweeper installation?
b) is there a way to get the custom Keys with LsPush?
c) If not... I assume LsClient would work better with that issue than LsPush, right?
However, it seems that LsPush has it's own list of "known Product Key Locations"(?) and therefore cannot extract keys that where added in the Lansweeper Server Backend. (Via Configuration -> Product Keys)
Three Questions:
a) Can LsPush extract more / less Keys than the standard (uncustomized) Lansweeper installation?
b) is there a way to get the custom Keys with LsPush?
c) If not... I assume LsClient would work better with that issue than LsPush, right?
Labels:
- Labels:
-
Archive
5 REPLIES 5

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2014 05:44 PM



Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2014 09:19 PM
FYI: we edited our previous response as it was only partially correct.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2014 03:23 PM
- LsPush scans the same built-in product keys as the Lansweeper service.
- Scanning custom product keys with LsPush will work if you use direct server connection. Without direct server connection, LsPush will only scan the built-in keys. It can't know what your product key configuration is and there is currently no option for storing these settings offline.
- If you're connecting to your Lansweeper server anyway, it would be better to use LsPush instead of LsClient. Both will retrieve the keys and LsPush is immune to most scanning errors.
If you know of additional registry locations that store product keys, please forward them to support@lansweeper.com so we can add them as standard scans to our next release.
- Scanning custom product keys with LsPush will work if you use direct server connection. Without direct server connection, LsPush will only scan the built-in keys. It can't know what your product key configuration is and there is currently no option for storing these settings offline.
- If you're connecting to your Lansweeper server anyway, it would be better to use LsPush instead of LsClient. Both will retrieve the keys and LsPush is immune to most scanning errors.
If you know of additional registry locations that store product keys, please forward them to support@lansweeper.com so we can add them as standard scans to our next release.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2014 04:36 PM
Thank you for the updated answer! Very helpful and good to know that is works with Server connectivity.
Will those standard scans also be included in a "new" LSPush.exe?

Lansweeper wrote:
If you know of additional registry locations that store product keys, please forward them to support@lansweeper.com so we can add them as standard scans to our next release.
Will those standard scans also be included in a "new" LSPush.exe?


Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2014 05:29 PM
Steven | MAGIX wrote:
Will those standard scans also be included in a "new" LSPush.exe?![]()
Yep, we'll create an updated LsPush executable as well.
