Skip to content

Deployment via SCCM

Microsoft Configuration Manager (MCM) commonly referred to by its old name Microsoft System Center Configuration Manager (SCCM) is a way to support the mass deployment of SenseOn. This guide outlines the suggested steps for using SCCM to deploy the SenseOn endpoint agent.

⚠ Note: SCCM requires that the files to be installed are accessible over the network, for this reason SCCM is not preferred.

Install steps

  1. Create a shared location on your network which will be accessed by the computers you are deploying to.
    1. Copy the SenseOn MSI file to the shared location.
    2. Copy the SenseOn install key to the shared location.
    3. Copy and save the following PowerShell deployment script to the shared location. Be sure to fill in the path values. 
      #Set paths
$folderpath = "PATH\TO\SHARED\LOCATION"
$keyfile = "SENSEON_KEYFILE_NAME.txt"
$msifile = "SENSEON_MSI_NAME.msi"
$temp = "C:\Windows\Temp"
$keyfilepath = Join-Path -Path $folderpath -ChildPath $keyfile
$msifilepath = Join-Path -Path $folderpath -ChildPath $msifile

#Copy SenseOn key file and run MSI installer 
Copy-Item -Path $keyfilepath -Destination $temp -Force 
Start-Process -FilePath "msiexec.exe" -ArgumentList "/i $msifilepath /qn" -Wait -NoNewWindow
  2. In the Configuration Manager or SCCM go to the Software Library > Application Management.
  3. Right click Packages and choose Create Package.
  4. For the first page under Package fill in the following details:
    1. Name: Specify a name for the package: SenseOn Endpoint.
    2. Description: Specify a description for this package with a maximum of 128 characters.
    3. Manufacturer (optional): Specify a manufacturer name to help you identify the package in the Configuration Manager console. This name can be a maximum of 32 characters.
    4. Language (optional): Specify the language version of the package with a maximum of 32 characters.
    5. Version (optional): Specify a version number for the package with a maximum of 32 characters.
    6. This package contains source files: This setting indicates whether the package requires source files to be present on client devices. By default, this check box is cleared and Configuration Manager does not use distribution points for the package. When this check box is selected, distribution points are used.
    7. Source folder: choose Browse to open the Set Source Folder dialog box and then specify the source as the shared location created in step 1.

  5. Click next for Standard program type and enter the following information:

    1. Name: Specify a name for the deployment i.e. SenseOn
    2. Command Line: powershell.exe -ExecutionPolicy Bypass -File script_name.ps1

    Where script_name is the name of the SenseOn PowerShell deployment script

If you wish to modify the MSI options used in this script see the below reference Reference: MSI command line options

Set the following options:

  • Program can run: Only when a user is logged on
  • Run mode: Run with administrative rights
  • Drive mode: Runs with UNC name
  • Run and Start-up fields are optional
  • On the Requirements section, create a requirement rule that the package runs only on supported Windows platforms.
  • Optional settings:
  • Run another program first, Estimated disk space and Maximum allowed run time (minutes).
  • Complete the wizard to finish creating the package. The package is now ready to be deployed to your computers.

Reference: Microsoft documentation on how to install packages in SCCM

If using distribution points, distribute the package by right-clicking it and selecting Distribute Content. Complete the Distribute Content Wizard by navigating through the pages and adding distribution points.

Deploy the package by selecting it and clicking Deploy. Complete the deployment wizard, selecting the desired device collections to deploy to and deployment scheduling options.

Uninstall steps

If using the PowerShell deployment script:

  • Navigate to the package under Software Library > Application Management.
  • Navigate to the Programs tab.
  • Right click and view Properties.
  • Edit the command run to uninstall the package: msiexec.exe /quiet /x absolute\path\to\MSI
  • Apply changes and redeploy

Otherwise:

  • Open the deployment type name Properties dialog box for the SenseOn endpoint agent deployment.
  • On the Programs tab, specify the command line to uninstall the application in the uninstall program field.
  • The following command is required for the uninstall of the endpoint agent: msiexec.exe /quiet /x absolute path of the MSI
  • Apply the changes, then select the deployment action Uninstall on the Deployment Settings page of the Deploy Software Wizard.

💡 Note: Note. When you select a deployment action of Uninstall, the deployment purpose is automatically configured as Required.

Reference: Microsoft documentation on uninstall steps using SCCM