This can occur when a command is sent to a machine that is turned off or logged out at the time the LiveUpdate command is sent. I believe this is due, in part, to security restrictions in the OS that any application capable of generating a window is not allowed to launch if no one is logged in.
Title: 'LiveUpdate does not properly exit when commanded from the Symantec Administration Console for Macintosh'
Document ID: 2008101511243848
> Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008101511243848
(I have seen it where the LiveUpdate icon is present in the dock and doesn't go away, like you describe.)
If it is common that users turn off or log out of their machines when not working on them, I would recommend sending LiveUpdate schedules rather than sending LiveUpdate commands every day.
Unfortunately you do have to dabble a little in symsched command line stuff, but the good thing is that you can save the command line as a template, then send the command with the schedule as many times as needed.
Title: 'How to remotely schedule LiveUpdate and virus scans on Symantec AntiVirus for Macintosh 10.x clients'
Document ID: 2007393022179698
> Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007393022179698
What happens if you manually launch LiveUpdate on a client machine, and run it for virus definitions? If the defs are themselves corrupted, you'll probably want to obtain the Intelligent Updater to fix 'em. Just get the right one for your processor type.
http://www.symantec.com/business/security_response/definitions/download/detail.jsp?gid=nmc
Hope this helps,
sandra