Creating BigFix Fixlets with the Software Distribution Wizard

Step 1: Open the SWD in the Console

Under "All Content", go into Dashboards, Software Distribution, and then Manage Software Distribution.  You can then start to manage the software distribution packages.

• You can use the search box to look for existing packages.  You can only search on the package name.
• This will give you all the packages people have created.  I can only assume that they were made public when people created them.
• You can modify an existing package or create a new one.

Step 2: Create or Edit a Package

The package is the container from which fixlets are built, so you must either create one or modify an existing one before you can have SWD create your fixlet.  

If you modify an existing package...

You can search for a package by vendor, product, or version number in the search box.  Unfortunately, you cannot search by creator or owner to filter only your own packages.  Therefore, it's important that you scroll through the list to find your existing package.  Do not attempt to use or modify packages belonging to others.  I do not know what will happen.

When you select an existing package, you will have the ability to manage the existing files (meaning you can add or remove them) or manage the tasks associated with the package.  The tasks are the fixlets that have been created using SWD.

If you want to use updated versions of the files included in the package, it's generally simpler to modify your package and add the newer files (while removing the old ones). You will then have to create new tasks that use the new files.

If you're creating a new package...

Click the "New Package" button and fill in the form that pops up.

I recommend leaving the access setting on "Private" unless you have a good reason for making the package shared.  Click "Confirm" when you are done.

Step 3: Add files

The files you want to add are usually going to be the executables used to install software.  For Windows, they can be .EXE or .MSI files.  For Macs, they can be .DMG files.  You might also be able to add other types of files if the installer needs them.

You can also add multiple installers.  For example, you could add a Windows installer and a Mac installer, and then make separate fixlets for each from the same package.  After you select your file, click "Add to Package".

You must wait for the file upload to complete before closing the "Add Files" window.  The window will close on its own when the uploads finishes.  You'll see the uploaded file in your "Manage Files" list.

Step 4: Add tasks

Click "Manage Tasks", then "Add Task".  Select the installer file that you want to have included.  Usually, you will only need to include one installer in each task.

Next you'll want to review the installation commands.  Typically these are just the name of the executable you included.  There are other options available, but I have never used them.  Make sure the task is set to run as the System User, and click "Next".

Next, create the task.  You can probably leave the "Do not use any additional applicability conditions" button selected.  That is an opportunity to add relevance language, but you can also do that later by editing the fixlet itself.

Then go ahead and create the fixlet.  You can change the name to something a little more meaningful.  Also make sure you change the "Create in Site" value to "Pharmacy".  It likes to default to your personal operator site, but you want to create fixlets in the Pharmacy site so that other Pharmacy BigFix operators can use them.  If you forget, you can always create a copy from your operator site into the Pharmacy site.  Click "OK" to save it.

Additional Things to Know

• You can edit/delete the package or any file/task within it by clicking the appropriate form controls.
• Deleting a task from a package will also delete its corresponding fixlet, and vice versa.
• It's not always necessary to create a package for different installers.  For example, you could create a package that contains installer files for Windows and Mac, and then from there create separate tasks/fixlets for each.  Just select the correct file to include with the task.
• In most cases, the relevance generated for the task/fixlet is sufficient.  If you need to fine tune it, I recommend doing so in the fixlet after it has been created.
• It may take a few minutes for the fixlet to appear in the Pharmacy site.