Please provide your feedback in this short Flings' survey.

Forklift for Workspace ONE UEM

version 3.0.2 — September 07, 2021

Contributors 3
View All
Comments 26
View All

Release Date: January 14, 2019

Summary

The Forklift for Workspace ONE UEM Fling allows migration of Workspace ONE UEM Resources between different Workspace One UEM environments. Rapid deployment of resources bundled as a "Deployment Template". Lastly the creation of a Continuous Delivery Pipeline for resources.

Forklift for Workspace ONE UEM (Workspace ONE UEM Workload Migration Tool) includes the following primary features:

  • Migrations for Applications, Profiles, Sensors, Scripts and Windows 10 Baselines
  • Continuous Delivery pipelines as a turnkey CD solution to Create/Update and promote resources from Dev to Test to Production with a button click
  • Deployment Templates as exportable/importable resource containers for rapid resource deployment in a UEM environment.

Forklift is distributed as a series of linked containers for deployment simplicity. Included in the release are 2 container images, helper scripts for running the containers and a Docker Compose file to keep the containers linked correctly.

Requirements
  • Docker for Desktop
  • macOS Version 10.14+ or Windows 10 Professional or Enterprise 64 bit
  • 1+ Workspace One UEM environments
  • Admin Api credentials for the two environments
  • Admin Api permissions in the two environments

Network connectivity between the two environments

Instructions
Installation and Setup Installation

Platform specific installers are included in the download. The installer will setup the docker images, create folder mounts for the containers and stage useful scripts.

Note: The Installer can be run if Docker is not installed. It will fail on the final initialization step. If this happens follow the instructions in the Manual Installation Instructions. If the installer fails during the last install script. Then attempt to run the script manually from the install folder. It's located in <InstallDir>

Manual Installation Instructions
  1. Ensure Docker for Desktop is installed and the Docker daemon is running. The install script performs a check for the Docker daemon.
  2. Run the Installer to stage the container images and install scripts in the following folders:
    • macOS - /Applications/Forklift
    • Windows 10 - C:\Program Files\Forklift
  3. Navigate to the scripts folder
    • macOS - /Applications/Forklift/scripts
    • Windows 10 - C:\Program Files\Forklift\scripts
  4. In the scripts folder, run install.sh (macOS) or install.ps1 (Windows 10)
  5. The install script will load the container images so that docker compose can start the containers in the correct configuration.
  6. Starting Forklift
    1. First time launch
      • In scripts/operational, run startup.sh (macOS) or startup.ps1 (Windows 10). This will run docker compose up against the docker-compose.yml file located in the scripts folder.
      • Note: The startup script is written to one with relative paths and expects docker-compose.yml to be in the parent folder.
    2. Subsequent launch
    3. There are two options for subesquent launches.

      • Use the same startup script from the First Time Launch instructions
      • In Docker for Desktop, click the start button for the container cluster.
    Shutting Down Forklift

    There are two options for shutting down Forklift.

    • In Docker for Desktop, click the stop button for the container cluster.
      • Note: This option allows for restarting the app in Docker for Desktop as mentioned above.
    • In scripts/operational, run shutdown.ps1 (Windows 10) or shutdown.sh (macOS)
      • Note: This option will shut down the container cluster, remove the virtual network and lastly remove the containers as well. If this option is used, then startup.sh/startup.ps1 must be used for the next app launch
Video
Changelog

Version 3.0.2

  •  Fixed Baseline migration issue

Version 3.0.1

Improvements

  •  Improved error handling and messaging

Bug Fixes

  • Fixed app migration issue for File Exists Criteria
  • Fixed baseline migration issue from additional policies
  • Fixed baseline migration issue when Group UUID is undefined
  • Fixed Pipeline rollback showing on first step.

Known Issues

  • Some Windows 10 scripts do not migrate
  • Baselines with custom firewall settings will not migrate
  • The configured environment in a Pipeline Step does not show in the UI
  • The comparison for Pipeline steps does not compare the correct data

Version 3.0.0

Improvements

  • Added Support for more than one environment
  • Added MST and Icon Support to Windows 10 App Migrations
  • Added support for applications larger than 2 GB
  • Added Sensor and Script support
  • Added Continuous Delivery Pipelines

Bug Fixes

  • Fixed Baseline migration issue where values were not migrating correctly
  • Fixed App migration issue where file modified date was defaulting to default values
  • Fixed missing location group id for profile migrations

Same Version

  • Changed Fling name from Workspace One UEM Workload Migration Tool to Forklift for Workspace ONE UEM

Version 2.1.0

  • Fixed app upload issues for Workspace One UEM 1910+
  • Fixed profile search issue for Workspace One UEM 1910+
  • Added profile update support
  • Added template folder structure creation
  • Updated Mac app to support notarization for Catalina

Version 2.0.1

  • Fixed Baseline Migration issue
  • Fixed Profile Errors not displaying in the UI

Version 2.0.0

  • Baseline Migration Support
  • MacOS application
  • UI refactoring to make bulk migrations easier
  • Added support for script detection with Win32 applications

Version 1.0.1

Fixed issue with expired credentials.