Lansweeper profile on cliens

[airdih]

HI!

Our company uses Lansweeper 3.5.1 Premium in a multiple domain forest and it works great. Our only consirn is that lansweeper creates a local profile (in c:\documents and settings\....). We just had a big virus outbreak in one of the domains. Our antivirus engin detected infected files in these profiles on all computers and it looks like admin credentials (used for lansweeper) were used to spread through the network.

Is there a way to avoid creating these profile folders with cached credentials?

Best regards

[Hemoco]

The biggest problem is when the server is infected (it could be worse if your domain controllers are infected)

Some things that might help preventing this:
-Install some sort of antivirus software on your (non high loaded) servers.
-Install a wsus server to make sure all your clients are always updated.
-Don't let your users work with administrator rights on their machines.

Create Lansweeper reports to verify all of this.

[airdih]

So basicly ther is nothing we can really do about it?

How do other users troubleshoot this? (if any)

It's true that the clients weren't up to date, but that is fixed now. We just don't want to have another incident like that in the future...

[Hemoco]

The profile is created by WMI when you use the remote registry scan.

We have seen this problem before and it was caused by a variant of the sality worm which infected the Lansweeper server.