There are a few ways you can deploy this package. I recommend using the Kaspersky Administration Kit and deploying from there.
If your company is more like mine and wants to use AD to deploy the app then there are a few little bugs to get around.
Extract the MSI by running the .exe. You will find it in the %Temp% directory.
License key file (.key) should be placed in the package directory. This will automatically license the product.
Once you put a /qb or /qn switch on the package, it disables the user's ability to see the "Updates" section of the console. To re-enable this I used ORCA and deleted the custom action ImportSetupRegSetProp from the InstallExecuteSequence table.
There are some properties that will help with choosing what features you select. The ones I found were...
ASSELECTED = Anti-Spam
AHSELECTED = Anti-Hacker
NETSELECTED = Mail Anti-Virus
There are more but I did not need them.
Features can also be modified by adding a property called ADLOCALPROP and adding features to that list.
For other settings, create a .cfg file. Install the application manually and configure it as desired. Open the console and click on Settings. Select Service from the menu on the left hand side. You will be able to save your current configuration from there. Name the file Install.cfg (not sure if this name is essential) and put the .cfg file in the package directory.
Questions & Answers related to KELTON Kaspersky Anti-Virus for Windows Workstations
Blogs (0)
Blog posts related to KELTON Kaspersky Anti-Virus for Windows Workstations
Links (0)
Links related to KELTON Kaspersky Anti-Virus for Windows Workstations
Reviews (0)
Reviews related to KELTON Kaspersky Anti-Virus for Windows Workstations
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ