Lansweper service restarting?

[ukaussi]

We have been testing Lansweeper Premium for a month or so now and just bought a subscription.

What we have seen in the past few days since increasing the thread scans is what appears to be random restarts of either the Lansweeper service or the website. Yesterday it shows this error 15 times

Here is an example (real server names changed)

Started "lansweeperserver" v5.2.0.17 by NT AUTHORITY\SYSTEM, port 9524, 30 Threads, 18 IP Threads, Premium version SQL Server 10 "sqlserver"

Any ideas?
Are we using too many threads?

[ukaussi]

Will have to check tomorrow as we are on AEST (UT +10)

Anything else we should look for, try, test etc?

We did drop the threads down to 20 / 12 to see if that changed anything so will check logs tomorrow also.

[sukaitsu]

ukaussi wrote:
Will have to check tomorrow as we are on AEST (UT +10)

Anything else we should look for, try, test etc?

We did drop the threads down to 20 / 12 to see if that changed anything so will check logs tomorrow also.

For best performance; separate out the components to Lansweeper by keeping each on a different server:

• SQL Server
  
• Scan Server
  
• Web Server

Lansweeper Website

I'd recommend installation the website using Microsoft IIS if you didn't already. Inside IIS you can manage the Application Pool, which will contain an application called Lansweeper AppPool.

Right Click on Lansweeper AppPool and select Recycling

Check Regular Time Intervals and set it to 1740 (Everything else unchecked)
Next
Only Regular Time Intervals should be checked, then Finish

This is a healthy time period for the AppPool to refresh.

Lansweeper Scan Server

Physical Server (Recommended)

2x Processors (4 cores or more per processor)
8GB or more of Ram
10GB+ Fiber Network Card (Internal Network not WAN)

Computer Threads: 48
IP Threads: 36
Deployment Threads: 12

Physical Server (Adequate)

2x Processors (2 cores or more per processor)
4GB or more of Ram
1GB Ethernet for Public (IP that gets registered in DNS)
1GB Ethernet for Backup

Computer Threads: 36
IP Threads: 32
Deployment Threads: 12

Virtual Server (Recommended)

2 Logical Processors
6GB
1GB Virtual NIC for Public (IP that gets registered in DNS)
1GB Virtual NIC for Backup

Computer Threads: 36
IP Threads: 32
Deployment Threads: 12

[Michael_V · Accepted solution]

The total number of threads should stay below 80 (but it shouldn't crash your service)

Do you see any errors in the eventviewer?