deploying F-Secure Computer Security on MacOS , does not take license key from filename

gmork123

Hi,

When installing F-Secure_PSB1_Mac_Installer\[XXXX-XXXX-XXXX-XXXX-XXX\].mpkg it does not take the license key from the filename.

Is there a way to add this license? It would like to do a silent/unattended install via munki

Thanks, Wessel

JamesC

Hi Wessel

We're currently working on it. Silent install and subscription activation using package name are already available in CP for Mac for many years. In the next release there will be more options and features.

So, first, in order to make embedded into the package name code to work, it should look like F-Secure_PSB_Mac_Installer[XXXX-XXXX-XXXX-XXXX-XXXX].pkg,

Notice there are no slashes before brackets. This feature did not change, you just had the package name wrong

Silent installation

macOS supports silent installation of product packages from the Terminal or through ssh that does not require user interaction:

sudo installer -pkg /path/to/pkg -target /

Check man installer for more details and options.

Subscription activation

In become operational, Computer Protection for Mac should be activated with subscription key. There are two options how this could be done automatically without user interaction:

1. Embed subscription key into the product package name. Product will be activated during installation process. In order to do that, either select subscription key while downloading product installation package from the PSB portal or change product package manually so it looks like this: F-Secure_PSB_Mac_Installer[XXXX-XXXX-XXXX-XXXX-XXXX].pkg
2. Activate after installation using activator tool, distributed with F-Secure Computer Protection for Mac. To activate subscription, use activator tool as follows: /usr/local/f-secure/bin/activator --subscription-key "<subscription key>"

Common PSB client distribution scenarios and how to customize Computer Protection for Mac

• Through ssh:
  • Copy Computer Protection for Mac package to the target machine using scp or any other preferred way.
  • Execute installer on the target machine using ssh, check Silent installation section of this guide.
  • Execute activator with desired configuration parameters on the target machine using ssh.
• Through MDM or other software distribution solution (e.g. Munki) with manual activation and configuration:
  • Import Computer Protection for Mac package into your MDM or other software distribution solution (check your solution documentation on how to do this). This will allow to install Computer Protection for Mac on Macs in your organization. Notice that they still require activating and are not yet connected to the PSB portal.
  • Execute activator with desired configuration parameters on target machines using ssh.
  • Create and import into your software distribution software a custom macOS software package with activator call using pkgbuild utility shipped with macOS (see Creating macOS software package code listing below).
  • Create as many activation packages as you need and assign them to specific devices or device groups, whatever your software distribution solution supports.
  • Original Computer Protection for Mac product package stays intact and keeps its designated signature.
  • In order to macOS to validate your custom package, it needs to be signed and notarized. On how to do that refer to Signing and notarizing software on macOS in this guide.
• Through MDM or other software distribution solution (e.g. Munki), activation and configuration done using custom package:
  • Import Computer Protection for Mac package into your MDM or other software distribution solution (check your solution documentation on how to do this). This will allow to install Computer Protection for Mac on Macs in your organization. Notice that they still require activating and are not yet connected to the PSB portal.
• Through MDM or other software distribution solution (e.g. Munki), using one package for both product installation and activation:
  • Create special product package based on Computer Protection for Mac product package. Use prepare-installer.sh script available below in this guide as is (see Using prepare-installer.sh code listing below), or use it as an inspiration to create your own better fitting your needs.
  • In order to macOS to validate your custom package, it needs to be signed and notarized. On how to do that refer to Signing and notarizing software on macOS in this guide.

marcus8M

jamesch, thanks for information. Silent installation helped in my case. Some people say that it can malware or something like that. For example, virus safe finder - do you think it can affect such behavior? This article ( https://macsecurity.net/view/124-remove-safe-finder-virus-from-mac-in-safari-chrome-and-firefox ) helps to remove this type of malware. Now I'm just curious how "deep" this type of virus can go in your system.