Software Deployment Recipes (Microsoft)

The Software Deployment Recipes (Microsoft) section provides a curated collection of practical guides and step-by-step instructions for efficiently deploying software and applications in Microsoft environments. Discover proven techniques and best practices for automating software deployments, managing configurations, and optimizing compatibility on Windows devices. Whether you're a system administrator or an IT professional, these recipes offer valuable insights to streamline your software deployment processes, enhance productivity, and ensure a seamless experience across your Microsoft devices.

7zip (Windows MSI)

Description

Example recipe for deploying 7zip with new MSI parameters in FileWave 15.2.0.

Ingredients

Be sure to review 7zip FAQs to use the proper install path. FileWave will force a silent install when using MSI installers.

Directions

  1. Download the 7zip MSI installer from 7zip: Download

  2. Upload MSI installer by creating New Desktop Fileset and choose MSI / PKG to create
  3. Highlight the newly created MSI Fileset, and select Properties
  4. Scroll down to the Custom MSI install options
  5. Enter in the desired path for 7zip7zipMSI.pngExample here is installing to C:\Program Files\7-Zip
  6. Click OK to save

Always test deployment for both successful installation and uninstallations. If you were assigning via Self Service Kiosk, and then end users decides to uninstall, want to be sure it does uninstall successfully.

Assign to Devices

Once testing has been completed and is successful, assign your Fileset to your devices. By way of either a 'Deployment' or 'Association' within FileWave, assign the Fileset to your devices.

Related Content

Adobe Creative Cloud (Windows EXE)

Description

In today's digital age, visual content plays a pivotal role in branding, marketing, and communication strategies for enterprises. Adobe Creative Cloud offers a robust suite of tools tailored for creative professionals, and its enterprise version brings forth additional functionalities to manage and streamline the creative workflow.

FileWave can help you in deploying and managing these Adobe Creative Cloud applications.

Ingredients

Directions

  1. Accessing the Admin Console:
    • To initiate the deployment process, administrators must log in to the Adobe Admin Console using their authorized credentials. The admin console provides a range of management options, including user provisioning, license management, and application deployment.
  2. Navigate to Packages AdobeConsoleWindows.png
  3. Creating Deployment Packages
    • Choose the proper platform, next to the search product bar; select Windows for Windows deployment
    • Within the admin console, administrators can create customized deployment packages for Adobe Creative Cloud applications. These packages include specific software, settings, and configurations tailored to the organization's needs.
    • Select Packages to customize managed installers or Pre-generated packages for pre-built installer ready for deploymentCustomizedManagedDeployments.png
  4. Selecting Applications
    • The admin can choose which Adobe applications to include in the deployment package based on the roles and responsibilities of different users within the organization. This flexibility ensures that each user has access to the tools they require for their tasks.
  5. Distributing Deployment Packages
    • Once the deployment package is configured, administrators can distribute it to users or groups within the organization. This can be achieved by downloading the installer created, then upload into FileWave Central via the New Desktop Fileset > Empty Fileset.
  6. Upload into FileWave Central using the New Desktop Fileset > Empty Fileset.
  7. Assign to a Windows device
  8. Update Model

Please Note: Adobe Creative Cloud Packager may be customized with settings for application updates directly from Adobe and custom install directory for Windows and macOS.

Adobe may need to setup and installed with the trigger of the EXE. Below are the steps to locate the Setup.EXE file within the Adobe Creative Cloud installer for Windows and be sure the EXE is executed during deployment.

  1. Open FileWave Admin and navigate to your uploaded Adobe Creative Cloud installer.
  2. Double-click on the new Fileset to open the "Fileset Contents".
  3. Uncheck "Hide unused folders" if enabled.
  4. Navigate to through to find the Adobe Creative Cloud Setup.EXE file
  5. Select the EXE and click "Get Info" from the menubar.
  6. Navigate to the "Executable" tab.
  7. Check the "Execute once when activated" box and the "Non-interactive (background)" box. Then click the "Wait for executable to finish" and set it to 15 minutes.
  8. Click the "[+]" button to add any Launch Arguments to the EXE's installation. 
    Syntax:
setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]

[ADOBEINSTALLDIR] is the installation directory where apps are to be installed on the client machine.
[INSTALLLANGUAGE] is the locale in which the apps are to be installed.

Syntax example:
setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=en_US
  9. Click "Apply" to save your changes and Close the "Get Info" window.
  10. Close the "Fileset Contents" window.
  11. You should now see your EXE Fileset in the "Filesets" view.
    * The Fileset will be labeled as "Modified" indicating the it has not yet been saved.
  12. "Update Model" if you'd like to save the changes.

Setup.EXE_options

As always, test deploy the Fileset to a few devices before mass deployment.

Related Content

Adobe Air (Windows EXE)

Description

Need to deploy Adobe Air onto your Windows machines? Here is what you need to know to make that fileset.

Ingredients

Directions

  1. Download the most recent Adobe AIR Installer from http://get.adobe.com/air/

  2. Extract and import the AdobeAIR-Installer.fileset.zip into FileWave Admin and open it. This fileset contains a script that calls the Adobe AIR Installer.
    Starting the installation this way enables it to succeed even if no user is logged on at the target system.

    start "" C:\Windows\temp\AdobeAIRInstaller.exe -silent

  3. Import the "Adobe AIR Installer" into the C:\Windows\temp folder

  4. Adjust the "Adobe AIR Installer.exe" verification settings to "Ignore at verify" using the "apply to enclosed" button as depicted below

    RecipeAdobeAirWIN-verification.png

  5. Close the fileset and associate it to a test client

CrowdStrike Falcon Protection (Windows EXE)

Description

Needing to deploy to Crowdstrike Falcon antivirus to your Windows fleet? FileWave has you covered.

CrowdStrike's flagship product is called Falcon, which is a cloud-native platform that combines next-generation antivirus, endpoint detection and response (EDR), threat intelligence, and proactive threat hunting. Falcon aims to provide real-time visibility into endpoint activity, rapid threat detection, and automated response to security incidents.

Ingredients

Directions

Deploying the Crowdstrike Falcon to your devices

CrowdStrike deployment for Windows devices has one Fileset. This Fileset includes an EXE with launch arguments to be customized with your CrowdStrike license code.

The Fileset included with the EXE installer is the latest version of CrowdStrike. If you have an EXE installer provided by CrowdStrike, you may replace with your own EXE installer version.

CrowdStrike Windows Installation.fileset.zip

WindowsCrowdStrike.png

Customizing the Installation EXE

Editing the Fileset EXE

 

  1. Highlight the CrowdStrike Windows Installation Fileset
  2. Double-Click to open the Fileset Contents
  3. Highlight and select the .exe file.
  4. Click on 'Get Info'
 WindowsCrowdStrike1.png

Enter in your CrowdStrike License code

 

  1. Select the tab 'Executable.'
  2. Under the tab 'Launch Arguments' highlight CID=
  3. Enter in your CrowdStrike License code.
  4. Click the Apply to save your changes to the Launch Arguments
  5. Close the Get Info Window to save your changes.
 WindowsCrowdStrike2.png

Please Note: Launch Argument NO_START=1 is intended if the desired outcome if you want CrowdStrike to start after the first reboot post-install. If not, remove NO_START=1 from the Launch Argument list.

Creating a Fileset Group

Keeping your Filesets organized is good practice, especially if there are multiple Filesets for software deployment or organziation based on specific platform of deployment.

You may create a New Fileset Group, label it CrowdStrike Falcon (Windows 2023), and move the Fileset you created into this Group. Then associate the Fileset Group labeled CrowdStrike Flacon (Windows 2023) to your devices versus individual Filesets.

When ready, associate the Fileset Group labeled CrowdStrike Falcon (Windows 2023) to a few devices as a test. This is to verify and confirm that the software is installed properly based on your license code configured.

For best practice, always test a few devices before mass deployment.

Related Content

Firefox Configuration Recipe (Windows)

Description

After installing Firefox, some configuration may be desirable, examples may include:

Firefox Documentation
The details of the Fileset are based upon: Firefox Configuration
This is known to work with version 60, upwards. It may work with earlier versions, but testing on placement of files may vary with earlier versions. 

Ingredients

Directions

// Any comment. You must start the file with a comment!
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
// Any comment. You must start the file with a comment!
 
// Disable updater
lockPref("app.update.enabled", false);
lockPref("app.update.auto", false);
lockPref("app.update.mode", 0);
lockPref("app.update.service.enabled", false);
 
// Set Homepage and stop Mozilla startup pages
lockPref("browser.startup.firstrunSkipsHomepage", false);
pref("browser.startup.homepage","http://www.filewave.com");
lockPref("browser.startup.homepage_override.mstone", "ignore");
 
// Disable Privacy telemetry
lockPref("datareporting.policy.firstRunURL",);
lockPref("datareporting.healthreport.service.enabled", false);
lockPref("datareporting.healthreport.uploadEnabled", false);
lockPref("datareporting.policy.dataSubmissionEnabled", false);
lockPref("toolkit.telemetry.unified", false);

Preference Overview

Preference types can include: pref, defaultPref, lockPref, amongst others.  Details can be found at: https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig

pref

This is used to set a preference that can be overridden by the user, but on next launch of the application it will revert back to the setting within the configuration file

lockPref

A lockPref cannot be overridden by the user

defaultPref

This is used to set a preference that can be overridden by the user.  The user's setting will persist until the user resets them, at which point the defaultPref will be used on next launch of the application

Preference Names
Navigating to 'about:config' in the Firefox URL bar will list all possible preference names and their values and types.

Association

When associating, to ensure the configuration is installed with the Application, consider creating a Fileset Group:

Associating the 'Firefox' Fileset Group will ensure both the Application and Configuration are associated to devices.  

When there is an update to Firefox, replace the version in the Fileset Group with the latest version after testing.

To ensure users may not circumvent management by changing the locale, enable 'BlockAboutConfig' (already set as TRUE in the template file)

Related Content

Google Chrome Extension Management (Windows)

Description

Chrome Extensions, like ClassSpaces, can be managed via FileWave on multiple device types.

If the Chrome browser is already managed using Google Admin Console, then all management may be applied to devices via the Google Admin Console.  It is though possible to apply the management of Chrome to macOS and Windows devices via FileWave also.

Ingredients

↓ Windows

Windows

The provided download is a basic example of a PowerShell Activation Script within a Fileset to apply ClassSpaces and block the user from other extensions.  Drag and drop the Fileset into the Admin Console, associate to test devices and deploy once tested.

The script will create the necessary registry settings.

Contents of Script:

if ( -Not (Test-Path -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\*") ) {
 
    New-Item -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\" -Name "*" -Force
    New-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\*\' -Name "installation_mode" -Value "blocked"
 
    New-Item -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\" -Name "obeophmpnnhboefjagnpbllfbbaeodnn" -Force
    New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\obeophmpnnhboefjagnpbllfbbaeodnn\" -Name "comment" -Value "ClassSpaces"
    New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\obeophmpnnhboefjagnpbllfbbaeodnn\" -Name "installation_mode" -Value "force_installed"
    New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\obeophmpnnhboefjagnpbllfbbaeodnn\" -Name "update_url" -Value "https://clients2.google.com/service/update2/crx"
     
}

If there is already other extension management in place, the 'if' block may bypass the installation of the Extensions.  If Extensions are already being managed, alter the conditions of the script appropriately.

Notes

As part of the example, an additional key has been added to block all other extensions.  Remove or edit as desired

If Chrome is already open, the settings will not be applied until after the browser has been restarted

Related Content

Installing SOLIDWORKS (Windows EXE)

What

Need to deploy and install SolidWorks on Windows clients? Not a problem – FileWave has you covered. We need a few components from SolidWorks and some scripting tips to get deployment-ready.

Required components:

When/Why

We will need to download and install the SolidWorks Administrative Image Creator on your Windows machine with FileWave Admin installed. This is to create the SolidWorks image that can be used for deployment and installation. You may review the SolidWorks documentation for further details on setting up and configuring here: Creating an Administrative Image.

This “image” you created will be downloaded and placed onto the Windows machine under the default file path:

 C:\SOLIDWORKS Admin\SOLIDWORKS 2022 SP2.0

Once completed, it will be ready to be uploaded into FIleWave Admin.

How

The SolidWorks image containing the contents of the installation will need to be uploaded into a Fileset. Below is a Fileset template with an included Powershell script to install SolidWorks and remove the shortcut links from the Users Desktop. More information on Script Best Practices and Windows Software.

SolidWorks Template Fileset
FileWave Download.png

 

 

 

 

The final version of the Fileset should be around 23Gb in size (with included SolidWorks image).

image.png

Here is the PowerShell script used in this Fileset.

#############################################################################
#SolidWorks Installation
#############################################################################

If ( [IntPtr]::Size * 8 -ne 64 )
{
    C:\Windows\SysNative\WindowsPowerShell\v1.0\PowerShell.exe -File $MyInvocation.MyCommand.Path
}
Else
{
# Hide Wizard
$regPath = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks'
New-Item $regPath -ErrorAction SilentlyContinue | Out-Null
Set-ItemProperty -Path $regPath -Name UnattendedAccessWizardShown -Value 1 -Type DWord -ErrorAction SilentlyContinue | Out-Null
}

# Install MSI
$options = '/i', '/qb',  '/s', '/v', '/qn', "C:\SOLIDWORKS Admin\SOLIDWORKS 2022 SP2.0\startswinstall.exe"

echo "Installing with options: $options"

Start-Process -FilePath "C:\SOLIDWORKS Admin\SOLIDWORKS 2022 SP2.0\startswinstall.exe" -ArgumentList $options -NoNewWindow -Wait -PassThru

# Remove Desktop Icon
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS 2022.lnk� -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\eDrawings 2022 x64 Edition.lnk" -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS Composer 2022.lnk" -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS Composer Player 2022.lnk" -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS Electrical.lnk" -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS Manage 2022.lnk" -ErrorAction SilentlyContinue
Remove-Item -Path "C:\Users\Public\Desktop\SOLIDWORKS Visualize 2022.lnk" -ErrorAction SilentlyContinue
 
#############################################################################
#End
#############################################################################

Java (Windows EXE)

Description

This recipe shows you the steps you need to follow to make a Java Fileset for Windows.

Ingredients

Directions

  1. Download the offline EXE update from: Oracle Download Page

  2. Create an empty Fileset and drag the Java install EXE to an appropriate location, e.g. ProgramData > fwEXE

  3. Select the EXE and choose Get Info > Executable

  4. Set to 'Execute once when activated'

  5. Add the below Launch Argument to silently instal and remove older installed versions

    "/s REMOVEOUTOFDATEJRES=1"

  6. TestJavaGetinfo.png

Digging Deeper 

Oracle's Configuration Documentation

Applicable to online and offline installers only (.exe files and wrappers). Enables uninstallation of existing out-of-date JREs during JRE install.

REMOVEOUTOFDATEJRES

For example, running jre1.8.0_60.exe /s REMOVEOUTOFDATEJRES=1 will remove all JREs below the security baseline.

JREs above the security baseline will not be uninstalled.

Details of baseline may be observed from Oracle's release notes:
https://www.oracle.com/technetwork/java/javase/8all-relnotes-2226344.html

Legacy Installers
Although recommendation is to always use the latest version, legacy versions are available from Oracle's archive

Microsoft Defender Recipe (Win)

Description

Example recipe for deploying Microsoft Defender.

Ingredients

On Windows devices this is relatively straight forward.  Just a couple of items required:

Downloads:

See below directions for deployment before associating with devices.

Microsoft Defender deployment script is available through the M365 Defender portal; details in the Microsoft Deployment KB:

image.png

The 'WindowsDefenderATPLocalOnboardingScript.bat' is built by Microsoft with the appropriate licence code embedded into the script, such that the download is personal to the logged in account, when downloading.

It can be seen in the script from the line commencing as below:

REG add "HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection" /v OnboardingInfo /t REG_SZ /f /d "{\"body\":\"{\\\"previousOrgIds\\\":[],\\\"orgId\\\":\\\"


Directions

Download the example Fileset and import into FileWave

Script: WindowsDefenderATPLocalOnboardingScript.bat

Edit the text of the provided 'WindowsDefenderATPLocalOnboardingScript.bat' file within the Fileset and paste in a copy of the script contents downloaded from Microsoft:

image.png

image.png

Assign to Devices

By way of either a 'Deployment' or 'Association' within FileWave, assign the Fileset to one or more test devices and once happy expand this to more devices.

Office 2019 / Office 365 (Windows)

Description

Need to deploy Microsoft Office 2019 or Office 365 onto your Windows machines? We've got you covered! 

Note the Fileset below is based from the Microsoft Article listed here: https://docs.microsoft.com/en-us/deployoffice/office2019/deploy

Ingredients

This Fileset utilizes scripts to install and uninstall Office. After the Fileset is deployed and activated it can take a few minutes for the Office installation to be completed. When the Office Fileset is removed from the device (by removing the association in FileWave) a script will start that will uninstall Office from the clients.

For Office 365 just substitute Office 365 in place of Office 2019 where it's mentioned below

Directions

These directions assume you are creating an Office2019 folder on your local C:\ drive and you name the XML NewConfiguration. If you change the folder location, folder name, or XML name make sure you modify the steps below with your modifications.

C:\Office2019\setup.exe /download C:\Office2019\NewConfiguration.xml 

This is assuming you ran the deployment tool to a folder in the C:\ drive called Office2019 and you also added the xml to the same folder from earlier steps.  This command will download from Microsoft a folder called "Office" with configuration files that you will need to install Office on your clients


SentinelOne (Windows EXE)

Description

SentinelOne is a cybersecurity company that specializes in endpoint security and threat intelligence. They provide a platform for autonomous endpoint protection that uses AI and machine learning to prevent, detect, and respond to a wide range of security threats, including malware, ransomware, and other cyberattacks.

This recipe will guide you on configuring and deploying to your Windows devices.

Ingredients

Directions

  1. Download the EXE installer from SentinelOne

  2. Upload the EXE installer into FileWave Central to a Fileset you will use to deploy it

  3. Highlight the Fileset and double click to open Fileset Contents
  4. Highlight the EXE file
  5. Click on Get Info

    newScreenshot 2025-02-13 at 11.28.07 AM.png

  6. Select the Executable tab
  7. Check 'Execute once when activated'
  8. Choose radio button 'Non-interactive (background)'
  9. Check 'Wait for executable to finish' select 15 Minutes
  10. Under the Launch Arguments tab click on the + icon
  11. Enter in and replace "your_token_registration" with your actual token  
    -t your_token_registration
  12. Click on the + icon to create new Argument.
  13. Enter in  
    -q
  14. Click 'Apply' to save the fileset

    newScreenshot 2025-02-13 at 11.28.35 AM.png

Notes

Note: You need to use the -q parameter so that the install will be silent and, you must also use the -t parameter and enter your token because SentinelOne needs a token and as a silent install there will be no way to enter the token at install time.

Related Content

Upgrading or Repairing the Visual C++ Redistributable on Windows (Windows script)

Description

This article describes how to use the attached FileWave Fileset to install or update the Microsoft Visual C++ Redistributable (VC++). The provided Fileset ensures that the appropriate version of VC++ is installed based on the processor architecture (AMD64, ARM64, or x86) of the device. The script included in the Fileset automatically downloads the correct VC++ installer from Microsoft, installs it, and then performs cleanup.

Ingredients

Windows VC++ v17
FileWave Download.png

Directions

  1. Import the Fileset:

    • Download the Fileset from the link above.

    • Import the Fileset into the FileWave Admin console.

  2. Review the Script in the Fileset:

    • The Fileset contains the following PowerShell script that determines the system architecture, downloads the appropriate version of VC++, installs it, and cleans up the temporary files.

      echo $env:PROCESSOR_ARCHITECTURE

# Determine processor architecture
$Architecture = $env:PROCESSOR_ARCHITECTURE
if ($Architecture -eq 'AMD64') {
    $InstallerUrl = 'https://aka.ms/vs/17/release/vc_redist.x64.exe'
} elseif ($Architecture -eq 'ARM64') {
    $InstallerUrl = 'https://aka.ms/vs/17/release/vc_redist.arm64.exe'
} else {
    $InstallerUrl = 'https://aka.ms/vs/17/release/vc_redist.x86.exe'
}

echo $InstallerUrl

# Download installer
$InstallerPath = "$env:TEMP\vc_redist.exe"
Invoke-WebRequest -Uri $InstallerUrl -OutFile $InstallerPath

# Install Visual C++ redistributable
Start-Process -FilePath $InstallerPath -ArgumentList '/install', '/passive', '/norestart' -Wait

# Clean up
Remove-Item -Path $InstallerPath

  3. Associate the Fileset:

    • Assign the Fileset to the relevant Windows devices where VC++ needs to be installed or updated.

Notes

Related Content