Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Local Live Update
- Thread starter bookser
- Start date
terrywilson
MIS
Install your clients as managed, specify the parent server to be the one you wish them to recieve updates from etc.
We use 7.51, 7.6 and 8.01 with a couple different versions of LiveUpdate. It was a bear to configure for a rookie like me. The documentation is not detailed enough for me.
Plus it was not made real clear to me that you had to run LiveUpdate for the Admin side of your server and on the client side of your server - using two separate .hst files; luadmin.hst for the Admin side and liveupdt.hst for the client side of the same machine. We use Task Scheduler to run SilntLuA.exe on the server to download the updates and put them in the shared directory for the client to grab using the Scheduled Updates (in the File menu of Norton AV Corporate Ed) to be run on the clients. This way we have the server’s LiveUpdate Admin side going out to the web for the updates for the clients and we have the server’s LiveUpdate client side also going out to the web (at a different time) to get the updates for itself only. The rest of our machines do not go to the internet for antivirus – they use the LAN to go to the LiveUpdate download share directory. We just didn’t want to burn that bandwidth for each machine.
You might want to check the log(s) on the clients that are not running (and possibly server) to see what went wrong. Not always easy to read but can provide some help. Both the below logs exist on server & client. Logs on win2k clients are in c:\Doc & Set\All Users\Application Data\Symantec
-- The sub-dir LiveUpdate contains current Log, Settings and Product Catalog for (up to 10) runs of LiveUpdate
--The sub-dir Norton AntiVirus Corporate Edition\7.5\Logs has 30-day log of client runs. That way you can tell if it ran 4 days ago but not today. Helps to isolate. The log in this dir is for the client side only. There is no 30-day log for the LiveUpdate Admin as far as I know.
I hope this helps.
Plus it was not made real clear to me that you had to run LiveUpdate for the Admin side of your server and on the client side of your server - using two separate .hst files; luadmin.hst for the Admin side and liveupdt.hst for the client side of the same machine. We use Task Scheduler to run SilntLuA.exe on the server to download the updates and put them in the shared directory for the client to grab using the Scheduled Updates (in the File menu of Norton AV Corporate Ed) to be run on the clients. This way we have the server’s LiveUpdate Admin side going out to the web for the updates for the clients and we have the server’s LiveUpdate client side also going out to the web (at a different time) to get the updates for itself only. The rest of our machines do not go to the internet for antivirus – they use the LAN to go to the LiveUpdate download share directory. We just didn’t want to burn that bandwidth for each machine.
You might want to check the log(s) on the clients that are not running (and possibly server) to see what went wrong. Not always easy to read but can provide some help. Both the below logs exist on server & client. Logs on win2k clients are in c:\Doc & Set\All Users\Application Data\Symantec
-- The sub-dir LiveUpdate contains current Log, Settings and Product Catalog for (up to 10) runs of LiveUpdate
--The sub-dir Norton AntiVirus Corporate Edition\7.5\Logs has 30-day log of client runs. That way you can tell if it ran 4 days ago but not today. Helps to isolate. The log in this dir is for the client side only. There is no 30-day log for the LiveUpdate Admin as far as I know.
I hope this helps.
- Status
Similar threads
- Locked
- Question