Prior upgrade to 4.1 question, and a bug question.

[vargaboti]

Hi. We need to know, if upgrading the Lansweeper server (Premium) to last version 4.1, and we cannot update all clients (LSclient.exe) ver. 4.0.1.4 to the new ver. 4.1.0.3. What will be the result? Will affect functionality (database, web interface,…)?

Other question is that we noticed in ver. 4.0.0.42 / Dashboard reports, that operation systems having latest updates SP1 available for short time(at Microsoft), and applied to these system are misreported as not latest ones. Is this a bug, or it is solved in ver.4.1?
OS: Not latest Service Pack Win2008 R2 (1)
OS: Not latest Service Pack Windows 7 (1)
Thank you for your support.

[Hemoco]

Please contact us by e-mail for this problem

[vargaboti]

Lansweeper wrote:
Please contact us by e-mail for this problem

Email has been sent with subject from this topic.

[Hemoco]

vargaboti wrote:
Email has been sent with subject from this topic.

Can you mail it again to lansweeper@hemoco.com please.

[vargaboti]

1)We made the upgrade. At first we got the following errors. After upgrade the service doesent start automaticly on server reporting conflict
2)WebUI Is reporting still old version,checking the Lansweeper.DB[tsysASServers], found that probably sql script did not update to the new version
Servername/Computerscanned/activescanning/Version/Listenport/ConcurrentThreads
Myserver/598/1/ 4.0.0.42/9524/20

3)WebUI/Scanning configuration/Configuration tool Redirecting to error page, error page content in the attachedAppErr.txt
4) Using the same name on network for domain and workgroup, because in many other application building the same NetBIOS name for computers it is a must, we could not define workgroup . Also attached image with the error, “Violation of Primary….”
Please advice for further steps.

[Hemoco]

1)We made the upgrade. At first we got the following errors. After upgrade the service doesent start automaticly on server reporting conflict

Which is the exact error?

2)WebUI Is reporting still old version

This is because the service isn't started

3)WebUI/Scanning configuration/Configuration tool Redirecting to error page, error page content in the attachedAppErr.txt

can you set debug to true in the web.config file please, this should give a better error.

4) Using the same name on network for domain and workgroup, because in many other application building the same NetBIOS name for computers it is a must, we could not define workgroup . Also attached image with the error, “Violation of Primary….”

this is currently not possible, domain is a unique field.

[vargaboti]

vargaboti wrote:

1)We made the upgrade. At first we got the following errors. After upgrade the service doesent start automaticly on server reporting conflict

Which is the exact error?

C:\Program Files\Lansweeper\Install.log
02.02.2011 16:13:06: Stopping service
02/02/2011 16:30:10: 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()

2)WebUI Is reporting still old version

This is because the service isn't started

After server restart service was started mannualy. So C:\Program Files\Lansweeper\Service\Lansweeperservice.exe is running. This is the only one installed as Service

3)WebUI/Scanning configuration/Configuration tool Redirecting to error page, error page content in the attachedAppErr.txt

can you set debug to true in the web.config file please, this should give a better error.

Shure:attached file with debug information

4) Using the same name on network for domain and workgroup, because in many other application building the same NetBIOS name for computers it is a must, we could not define workgroup . Also attached image with the error, “Violation of Primary….”

this is currently not possible, domain is a unique field.

It would be good, anyhow at least in wish list to be inclouded.

[vargaboti]

First thanks for the quick reply.
1) OK it’s good because we had some issues before, upgrading from 3.x to first ver4, and we was afraid to not happen anything wrong.
2) “Can you explain some more please. Is the computer rescanned after the service pack was applied?”
We use LSclient in Group-policy, so each time that system is restarted or user log in, system is rescanned, we use also scheduled scan, so the answer is : Yes since they were updated to SP1 they were scanned many times.

[Hemoco]

vargaboti wrote:

We use LSclient in Group-policy, so each time that system is restarted or user log in, system is rescanned, we use also scheduled scan, so the answer is : Yes since they were updated to SP1 they were scanned many times.

What is the waittime for OS?
This defines the scanning of the operating system.
You can check the lastdate scanned for this item on the bottom of the action page.

[vargaboti]

Lansweeper wrote:

vargaboti wrote:

We use LSclient in Group-policy, so each time that system is restarted or user log in, system is rescanned, we use also scheduled scan, so the answer is : Yes since they were updated to SP1 they were scanned many times.

What is the wait time for OS?
This defines the scanning of the operating system.
You can check the last date scanned for this item on the bottom of the action page.

Item wait time OS=3
I have triggered scan before begin the post to forum and followed up the results.
Os 3 02/02/2011 10:39:16 1,00
Also now, as it can be seen here:
Os 3 02/02/2011 15:24:39 1,00

Windows Server 2008 R2 / CSDVersion: Service Pack 1 Date: 24.01.2011 02:00:49 Dashboard compliance OS: Not latest Service Pack Win2008 R2
Windows 7 Professional / CSDVersion: Service Pack 1 Date: 24.01.2011 16:43:43 Dashboard compliance OS: Not latest Service Pack Windows 7