Configuration file issue with 3.5

[techorders]

Hi everyone,

This morning I tried to update LS to version 3.5, but got stopped by a problem...

are the configuration keys for 3.2 still usable on 3.5? I have my .config file for the LS service with custom values on there keys:

<add key="ListenPort" value="9525" />
<add key="Activescanning" value="0" />
<add key="ConcurrentThreads" value="20" />

I'm not using the default listen port here, because I actually have 2 instances of the service: one of them performs active scanning on my Ad, the other one scans production servers, that are not inside the domain (workgroup mode). This is because I execute the service with a different user name on each case.

When I tried to upgrade with the new version of the service, it looks like the config keys are being ignore and both instances are trying to use the default port (9524), so one of them crashes with this error:

3/11/2009 8:50:24 AM: Failed to listen on prefix 'http://*:9524/' because it conflicts with an existing registration on the machine.
at System.Net.HttpListener.AddAll()
at System.Net.HttpListener.Start()
at LansweeperService.Listen.DoListen()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

So, are these configuration keys still applicable? did their name change on the new version? or am I missing something?


Thanks,
Juan G

[Hemoco]

Use one service, configure active scanning for the AD domain, use alternate credentials and lsclient for the other domain/workgroup.

[techorders]

what would you recommend for my scenario? I basically have 2 separate networks for internal machines that are inside the domain and another network for production servers in workgroup mode. And the LS server stands in the middle.

So I got 2 services running under different user names that scan internal and production networks separately and report back to a single DB. the one for internal network uses active scan, the other one relies on lsclient.

I saw that there's this new feature to tell LS to use a different account when logging into a host, but it looks like I need to add every single machine in there manually...

what would be the best approach?

[Hemoco]

Look for table tsysconfig.

I don't think it will be possible.

[techorders]

so those settings are being stored in database now? can you say on which table is that stored?

would there be any way to have 2 instances of the service running, with independent configuration, as I have it setup now? I know it's kind of a little hack, but it was the best I could do to pass our network configuration between internal and production network at that moment.

[Hemoco]

The configuration keys are no longer needed.
You can configure these options from within lsmanage.exe (configuration/parameters)