The only thing I can think of is that you'd used the "uninstall old AV while installing new AV" option in the LDAV push? I've never seen LANDesk Spyware conflict with Symantec, but I have seen LANDesk Antivirus fight with it.
We don't have LDAV installed.
What version of Symantec are you using?
V9.0.2 and V10
There must be more to it.
I had to use extensively versions 8 and 10 of Symantec's AV on my Cores + Lab-machines for duplicating various customer-issues through the whole life-span of 8.7 from release until now, and never had any problems with it. So you'll probably need to nail down on what's causing it a bit better (such as - set up a clean machine that's not installed from your corporate image, but an XP-CD) and install your AV-client on it + LANDesk and let the autofix do its part.
If that DOESN'T break the machine in the manner you describe something else, you have the questionable joy of having a negative synergy of several bits of software somehow managing to break each other.
If you CAN reproduce it with a clean machine, you should first of all check to make sure that the issues doesn't happen with SP5.
If it does, log a case with your regional LANDesk office, and give us details on what you've got set to autofix (potentially, a DB export might be easier) and hopefully we should be able to duplicate it.
LANDesk EMEA Technical Lead.
I had a simular problem.
I created and deployed new Agent configuration files.
Since then Symantec AntiVirus Service starts correctly.
Hope this workaround helps you
in fact it was a timeout, the symantec service didn't start because of the size of the vulscan folder. (appdata\vulscan).
If i clean the folder and run a new scan without antispyware, reboot == ok
sounds like you might want to whitelist that folder in symantec. still seems weird though, mine's <40mb on both test machines.
1 of 1 people found this helpful
We had reported this problem to LANDesk.
This problem was happening on our slower machines.
LANDesk released the patch in SP5.
CR00116342 -- Softmon service is keeping Symantec Antivirus from starting.
thanks, we are patching.
I will let you know.