‎08-31-2009 04:13 PM
‎10-13-2009 09:22 PM
‎10-13-2009 02:51 AM
‎10-12-2009 07:05 AM
‎10-12-2009 10:29 AM
AdmJLovejoy wrote:
As a follow up to the post found at...
http://www.lansweeper.com/forum/yaf_postst2227_New-configuration.aspx
After introducing two or more "Lansweeper Service" servers, into a segregated environment, it appears that there are no options to a assign a specific "Lansweeper Service" (LS2, LS3, etc.) server to only target specific clients in relation to a specific Domain, or a specific Active Directory Site. Although the current scan model works well for small fully routed networks, this is not ideal for large complex geographically disperse segregated WAN/VLAN networks.
Having the ability to configure a "Lansweeper Service" server to target scans on a AD Site by AD Site basis would be a preference.
My question is, will this be a consideration to truly scale the product? If not, how will the issue described above be addressed?
‎08-31-2009 06:07 PM
‎08-31-2009 05:30 PM
‎08-31-2009 05:55 PM
pentel wrote:
Hi,
A possible solution for this that seems to work fine for me when I did some tests was to simply take a backup of your current database for safety reasons, and install Lansweeper without the Database service on another server. Just make sure to point to the first Lansweeper installation's computer and you should have 2 Lansweeper applications using the same database. Simply go to the configuration console of the second one and remove active scanning.
If anything bad comes up you should have a fresh database backup which contains all the information.
Hopefully that helps or at least points in the right direction since I only did it in test mode.
‎08-31-2009 04:27 PM
‎08-31-2009 04:40 PM
Lansweeper wrote:
Now it's possible but a bit tricky if you use active scanning.
Lansweeper wrote:
Next version wil support this so you can have multiple configurations all pointing to the same database.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now