Please specify your version of LANDesk and level of service pack that you use.
At a guess, this should be fixed with you upgrading your service pack so that you have a contemporary AV engine (the only instance of this sort of thing I had were for somewhat outdated levels of LANDesk agentry).
LANDesk EMEA Technical Lead
By default there is indeed one ScanningProcess per cpu.
Add the following registry key to control this behavior:
32 Bit Systems: HKLM \ Software \ LANDesk \ ManagementSuite \ WinClient \ Antivirus
64-Bit Systems: HKLM \ Software \ Wow6432Node \ LANDesk \ ManagementSuite \ WinClient \ Antivirus
Dword Value: SetAffinity
And then it's basically a bitfield:
Values are 0, 1, 3, 7, 15 ...
So in binary it would have a 1 for each CPU slot.
So try a value of "3" and see how this works for you.
So in binary it would have a 1 for each CPU slot.
Use Default settings: 0 (1 instance per cpu)
1 cpu: 1
2 cpu: 3
3 cpu: 7
4 cpu: 15
5 cpu: 31
6 cpu: 63
7 cpu: 127
8 cpu: 255
We are at 8.8 SP1. I will take a look at the registry suggestion also, thank for such speed replies.
is that a reg_sz or reg_binary key?
OK, that did the trick. That machine now has two scanning processes. Thank you very much.
The registry edit doesn't work. Or at least it didn't work for me. We are running the same version as everyone else, 8.8 SP2. I applied the registry edit to two different machines that had about 10 different scanningprocess.exe and avservice.exe processes running. After I applied the registry edit, the machine behaved fine for about half the day, then additional scanningprocess.exe and avservice.exe started appearing.
I will continue to search this website for additional info, but I wanted to get my experience posted first, in case someone is dealing with this issue as well.
Any help is much appreciated.
This is very likely due to an issue with the local scheduler tasks not getting written properly causing the filters to pass continuously and Pattern File Updates or Scanning tasks running over top of each other when they shouldn't.
When Vulscan.exe or LDAV.EXE run, they check the ldav /scancomputer and ldav /update tasks in the AVBehavior_x.xml file to be sure the tasks on the client are proper or exist. If they are not they are rewritten.
Please install the following patch to resolve this issue:
Wow, thanks for the reply. I am a Landesk newbie, so maybe I can ask a few basic questions? To apply a patch...well, not quite sure how to do that. Is that the agent configuration? Is it a patch for the core server and then that gets pushed out to the clients? Or does it go from peer to peer?
I inherited Landesk admin from the person I replaced (he got promoted) but I have never used Landesk before. I want to go for training but my company is still deciding on that. So I have a ton of basic questions about Landesk.
How do I get a new config from the server to the workstation? Is that done on the client or is that pushed out through the server? How or better yet what is a policy? Is that a config that goes to the clients only when the machine is idle? So the server doesn't push, rather the client makes a request? So if I want to redo our existing configuration, do I create a new agent?
I am going through the Landesk online training info, but any and all help is totally appreciated! Thank you!
To apply a patch, there are several elements. I will cover how to install LANDesk Antivirus patches:
1. Download the .ZIP file and extract it to a directory.
2. Within that directory you will typically see two folders:
The first directory is the server patch, and the directory with the -client extension is for the client.
However, on antivirus patches, the client patch is installed a bit differently than other LANDesk client patches.
3. Inside the Server patch folder (in this case AV-2125388.2-2) run Setup.exe
4. Proceed through the patch installation (this part is self-explanatory)
5. To install the client patch there are a few ways to start the installation:
a. Run an Install/Update LANDesk Antivirus task:
To do this go to the Security and Patch Manager and click the down arrow next to the second icon and select "Install/Update LANDesk Antivirus"
- or -
b. From the client go to the Run line and type "vulscan /installav /showui"
For a full agent configuration, go to your Agent Configuration tool (Under the Configuration group), right-click the Agent configuration you want to send and choose "Schedule". This agent configuration will now appear in your Scheduled Tasks Tool (In the Distribution tools group). You can then-right click that task and "Start Now" or schedule it for a later time.
From the client side, go to the Run line and type "wscfg32 /f". This will bring up a dialog box and you can choose which parts of the agent to install.
If you want to redo your existing configuration you can make changes to the same Agent configuration, or create a new one.
D'oh! I thought this whole time we had SP2 on our installation, but we do not. We don't even have SP1?!?!? I need to upgrade to SP2 before I can apply the new AV settings. I am searching for an article about installing SP2 right now. Is it a drastic change to upgrade to SP2? Will it affect my end-users in anyway? Or will they even know that their machines are being upgraded?
I wanted to add the registry key but I only have HKLM\Software\LANDesk no other sub entries.
My guess is you are using a 64-bit operating system.
In this case, the 32-bit registry keys are located under a section called "Wow6432Node".
So in that case, add to this key:
64-Bit Systems: HKLM \ Software \ Wow6432Node \ LANDesk \ ManagementSuite \ WinClient \ Antivirus\
(And follow the instructions from above)