A while back, I posted about how to build an installer for NexThink Collector, but my preference is to not do manual packaging if I can avoid it. Instead, my preference is to have AutoPkg handle packaging tasks whenever possible for the following reasons:

1. I can ensure that the packaging task is handled the same way every time.
2. Once I have the correct recipe written for AutoPkg, all I should need to do for future versions of the app is to run the AutoPkg recipe, wait a few minutes and then collect a properly-built installer.

With that in mind, I decided to revisit building an installer for NexThink Collector but this time build AutoPkg recipes which handle the following:

1. Creating an installer package for NexThink Collector
2. Creating an uninstaller for NexThink Collector

I was able to do this, so for those interested, please see below the jump for more details.

I’ve built several AutoPkg recipes for NexThink Collector:

• NexThinkCollector.download: Downloads the latest NexThink Collector installer disk image
• NexThinkCollector.pkg: Builds an installer package for NexThink Collector
• NexThinkCollectorUninstaller.pkg: Builds an uninstaller package for NexThink Collector 
• NexThinkCollector.sign: Signs the installer package produced by the NexThinkCollector.pkg recipe
• NexThinkCollectorUninstaller.sign: Signs the uninstaller package produced by the NexThinkCollectorUninstaller.pkg recipe

All the recipes are available at the following location:

https://github.com/autopkg/rtrouton-recipes/tree/master/NexThinkCollector

The one which needs the most configuration via an AutoPkg override is the following:

• NexThinkCollector.pkg

This is because the details of installing and configuring NexThink are going to vary between shops, because different shops are going to configure different options for NexThink. The various Input variable options will provide hopefully all the possible configuration options needed.

To map between the Input variables and the NexThink command line installation configuration options, please see the table below:

Note: There are two NexThink command line installation configurations that are not directly covered:

• rootca
• key

For the rootca command line installation configuration option, all the documentation I’ve found in the context of installing the NexThink Collector software on macOS is the following:

Graphical installation documentation

• Root CA: Leave this field empty.

Command-line installation

• rootca: Not required.

Since the rootca option doesn’t seem to be required at all and there’s no documentation available on how to configure it for the NexThink Collector software on macOS, I’m leaving it out of the AutoPkg recipe.

For the key command line installation configuration option, this functionality is covered by the following required Input variables:

If both Input variables are filled in, then the postinstall script used by the installer package generated by this AutoPkg recipe will call the key command line installation configuration option and use it to configure the NexThink Collector software with the proper Customer Key information.

To see how this looks in a recipe override of the NexThinkCollector.pkg recipe, let’s create one with the following Input variables set:

• NTSERVERADDRESS: server.nexthink.com
• NTTCPPORT: 443
• NTREMOTEACTIONS: disabled
• NTENGAGE: disable
• NTASSIGNMENT: enable
• NTDATAOVERTCP: enable
• NTCUSTOMERKEYNAME: nexthink-customer-key.txt
• NTCUSTOMERKEYDATA: 

With those variables set, the AutoPkg recipe override should look similar to what’s shown below:

Once configured, the NexThinkCollector.pkg AutoPkg recipe should work with the NexThinkCollector.download recipe to do the following:

• Download the latest NexThink Collector installer disk image
• Wrap the disk image and CustomerKey file inside a separate installer package.
• Use a postinstall script to perform the following actions:

1. Identify the location of the disk image stored inside the installer package.
2. Mount the disk image
3. Identify the location of the csi.app on the mounted disk image.
4. Identify the location of the CustomerKey file stored inside the installer package.
5. Use the csi app’s command line tool to configure and run the NexThink-provided installer package on the mounted disk image, to install the NexThink Collector software.
6. Unmount the disk image.

The other .pkg AutoPkg recipe I wrote is NexThinkCollectorUninstaller.pkg and it is much simpler in terms of operation. It uses the same technique described in my earlier post on how to build a NexThink Collector uninstaller and should not need configuration of any Input variables. The NexThinkCollectorUninstaller.pkg recipe works with the NexThinkCollector.download recipe to do the following:

• Download the latest NexThink Collector installer disk image
• Wrap the disk image inside a separate installer package.
• Use a postinstall script to perform the following actions:

1. Identify the location of the disk image stored inside the installer package.
2. Mount the disk image
3. Use the uninstall script to uninstall the NexThink Collector software.
4. Unmount the disk image.

The AutoPkg recipe override should look similar to what’s shown below: