LKBDE11221: EPO Server basierte Installation von VirusScan 8.5


This article has not been checked!

LKB | Created: 02/04/2020 | Version: 0 | Language: DE | Rating: 0 | Outdated: False | Marked for deletion: False

Author: Wim Peeters - Keskon GmbH & Co. KG


Symptom

VirusScan 8.5 Installation scheitert - Fehlermeldung im EPO Agent 3.55

Cause

EPO Agent Version < 3.62

Solution

1. Installiere EPO Server 3.6x
2. Konfiguriere den Server entsprechend der Dokumentation
3. EPO Agent 3.6x mit Spracherweiterung ("Language Pack") und Reporting ("Reporting Files") herunterladen
4. EPO Agent 3.6x in das Repository einchecken
5. EPO Agent 3.6x Language Pack in das Repository einchecken
6. EPO Agent Reporting File in das Repository einchecken
7. VirusScan 8.5 herunterladen
8. VirusScan 8.5 in das Repository einchecken
9. Richtlinien ("Policy Settings") für EPO Agent einstellen (Sprache wird vom Betriebssystem übernommen)
10. Richtlinien ("Policy Settings") für VirusScan 8.5 einstellen (Spracheinstellung ist in der GUI Policy)
11. Deployment Task: EPO Agent und VS 8.5 in einer Task konfigurieren
12. Neue Update-Task für Dat, Engine, EPO Agent und VS8.5 in einer Task
13. Neue Repository Update Task
14. Dies funktioniert alles nicht mit EPO Agent < 3.6x

Anmerkung: VS8.5 ist nicht mehr für Windows Server 2008 geeignet!

About the Author

Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux in different European countries and different European languages. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform where he is one of the most important contributors and the main developer.

Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!