The following table provides a quick checklist for upgrading Nomad.

Main StepStep Outline
  • Upgrade ActiveEfficiency
  • Backup any customizations made to ActiveEfficiency as these will be overwritten during the upgrade
  • Upgrade ActiveEfficiency Server (by installing the new MSI – and specifying the Configuration Manager database details for the Nomad Sync option).
  • Re-apply any backed up customizations
  • Prepare 1E Client installation files
  • Use the 1E Client Deployment Assistant (CDA) wizard to create applications, collections, deployments and packages for the 1E Client in Configuration Manager. The Nomad client is now part of the 1E Client, and you must enable the Nomad client module of the 1E Client during installation. The 1E Client 5.1 documentation also explains how to deploy the 1E Client with the Nomad client module enabled.
    • Before running the CDA wizard, review AppImport.xml. Subject to the settings required in your organisation, make changes to the file as appropriate.
    • If the settings available in the wizard or AppImport.xml do not cover those that need to be configured within your organisation, customize the automatically generated MST as decribed in the 1E Client Deployment Assistant (CDA) documentation.
  • (Re)Distribute the 1E Client application and package contents to all DPs.
  • Upgrade Nomad on the Primary Site server
  • Extract the Nomad 7.0 ZIP file onto the server
  • Upgrade NomadBranchTools
  • Upgrade NomadBranchAdminUIExt
  • Upgrade Nomad client by installing 1E Client
  • Upgrade Nomad on the Distribution Point server(s)
  • Upgrade the 1E Client with Nomad enabled on all of the Distribution Point servers (before upgrading clients).
  • Upgrade Nomad on test client(s)
  • Create a test collection and deploy the 1E Client application or package to one computer – to test successful deployment.
  • Upgrade Nomad on all clients
  • Create a new deployment or use application supersedence to upgrade client computers.
  • Update/Create Compliance Baseline
  • (Optional) Update an existing Compliance Baseline, or use the new Nomad Baseline Wizard to create a new Compliance Baseline/configuration items by importing your 1E Client 5.1 MSI/MST. If you are updating an existing baseline, review specific Nomad 7.0 settings (such as BLOCKSIZE=131072) making sure you only deploy this to Nomad 7.0 clients.
  • Update 1E PXE Boot Image(s)
  • Update your 1E PXE Boot Image(s) by right-clicking the Boot Image and selecting “Update Distribution Points” - this will recreate the Boot Image and automatically inject the updated Nomad binary files into the Boot Image.
  • Create a new deployment of your specific Task Sequence to pre-stage the Boot Image onto PXE Everywhere clients.  Ensure you select the Rerun behaviour to “Always rerun program” and the Deployment Option of “Download all content locally before starting the task sequence”.
Nomad will only download the block differences (ie: deltas), so your clients won’t be downloading the entire Boot Image all over again.
  • Update OSD Task Sequences (with new Nomad package) and Pre-Cache new Nomad package
  • If you already have OSD Task Sequences, then you’ll need to update the Stage Nomad Package or Stage 1E Client Package step to point towards the new Nomad client installation package.
  • The new 1E Client installation package will need pre-caching to remote clients, usually already setup by the Nomad Pre-Cache Wizard.  In the background, the content from the old 1E Client installation package to the new 1E Client installation package will automatically be cached onto clients after updating your OSD Task Sequences, but this can take up to 24 hours.  You can speed this up by manually initiating the Nomad Sync (C:\Program Files (x86)\1E\ActiveEfficiency\Service\ServiceHost.exe -NomadSyncAll on the AE server), and then perform the NomadBranch.exe -precache command on remote clients.