Configure ActiveEfficiency to support single-site download
By default, Nomad peers share content within the local subnet. Where multiple subnets exist in a location, further WAN efficiency can be achieved using the Nomad Single-Site Download feature. To use the Single-Site Download feature, locations must be defined in the ActiveEfficiency database as groups of adjacent subnets. When a client requires content that is not available on its local subnet, it will check with ActiveEfficiency to see if the content is available from a peer on another subnet in the same location.
Locations can be defined in ActiveEfficiency using scripts. We provide a sample script (
PostADSitesandSubnets.ps1 included in the Nomad installation ZIP available from the 1E Support Portal) to import Active Directory Sites and Subnet definition into ActiveEfficiency. There is an alternative script (
Get-AESitesAndSubnetsFromHINV ) also available from the Support Portal.
Nomad post-installation tasks
You may need to make some post-installation configurations to your environment to ensure that Nomad works effectively. These are two areas that may need attention.
PXE Everywhere stored procedure update
The Peer based PXE feature installs PXE Everywhere. This includes installing PXE Lite Central on the CM server specified during installation. If the specified server is a CAS, you must update the
1E_GetPXEAction stored procedure that is created during the installation to accommodate child primary sites. Download the modified stored procedure from the 1E Support Portal: 1E_GetPXEAction.zip and execute this on the Configuration Manager database on the CAS.
Configuring and Installing the PXE Everywhere components
PXE Everywhere is installed and configured using a task sequence deployment with a customized WinPE boot image. The first step is to create the PXE Everywhere boot image to be used with both the PXE Everywhere installation task sequence and other OS Deployment task sequences. See the following instructions: Create the PXE Boot Image
The PXE Everywhere components along with the newly created boot image are installed using a task sequence. A task sequence is utilized due to the need to access the boot image during the process. See the following instructions: Create the PXE Everywhere installation task sequence.
Enabling Nomad on applications, packages, software updates and task sequences
Nomad must be enabled to act as an alternate download provider on a per-package basis for software distribution, per-task sequence or per-site for applications and software updates.
Create the 1E OEM Toolkit package
The 1E OEM Toolkit Package is utilized during the BIOS to UEFI conversion process – it contains the OEM hardware vendors (Dell, HP and Lenovo) firmware configuration tools and the 1E BIOS to UEFI executables. Refer to Create the 1E OEM Toolkit Package for details on how to create this package using the Create 1E OEM Toolkit Package wizard.
If the Self-service feature was implemented
Install Shopping Receiver on additional Configuration Manager primary sites
The Shopping Receiver component is required on all primary site servers in a Configuration Manager hierarchy. In a multi-site environment that includes a CAS, the Windows Servicing Suite installer does not currently install the Shopping Receiver on the child primary sites. Refer to the following instructions to install the receiver components on each child primary site: Installing the Shopping receiver.
Schedule the ActiveEfficiency Scout to collect data from Configuration Manager
Shopping uses data collected by the ActiveEfficiency Scout and stored in the ActiveEfficiency database. Use the ActiveEfficiency Synchronization Manager to schedule the collection of data from Configuration Manager
Configuring the self-service portal
The self-service portal is the interface that end users will utilize to both request their OS migration as well as additional software and services. The following guides you through the configuration of all of its components:
- Managing Configuration Manager applications – the 1E Windows Servicing Suite Self Service Portal primarily relies on Configuration Manager packages, applications, and task sequences. These can be individually imported following these instructions. A bulk import wizard is also available.
- Configure Self-service Operating System deployment – defines the specific processes for creating the OS deployment and Windows Servicing Assistant applications
- The following are optional steps that can be taken to further control and enhance the capabilities of the Self Service Portal:
- Node Security – by default, any members of the Shopping Administrators Active Directory group that was defined during the setup will have administrative capabilities. If additional access is required to other users or groups, follow the process outlined in this section.
- User and computer categories – this is not required but will allow you to control which applications are available to users (based on Active Directory group membership) or computers (based on Active Directory group or OU membership).
- Managing approvers – by default, if approval for a Shopping application is required, the approvers is the end user's manager that is listed in their Active Directory user object. If other approvers are needed the process for managing them is outlined here.
If the Application Migration feature was implemented
Install Task Sequence Tools on remote / additional SMS Providers
If the Configuration Manager site server defined in the WSS Installer wizard is configured with a remote or multiple SMS Providers, run the Task Sequence Tools installer manually on each remote SMS Provider.
Enable cloud synchronization of the 1E Catalog
The Windows Servicing Suite installer installs the Catalog with cloud synchronization disabled. This can be enabled after installation to ensure the Catalog is kept up to date with all the latest curated software titles etc. (refer to Synchronizing the Catalog for more information).
Schedule synchronization with Configuration Manager
The Application Migration feature is based on the 1E Software Lifecycle Automation (SLA) Platform, which uses inventory data and details of Applications and Packages collected from Configuration Manager. Configure the connector to Configuration Manager to synchronize the data from Configuration Manager to the SLA platform
Configure Application Migration integration in Shopping
If you implemented both Self-service and Application Migration, you will need to ensure Application Migration Integration is configured in the Shopping settings. Refer to Integrating Application Migration with Shopping for details on how to do this.
Configuring Application Migration
The Application Migration process allows you to control which application are reinstalled during the OS migration process. It is driven by a set of rules that must be configured. See the following for instructions on accessing and configuration:
- Accessing Application Migration – the Application Migration node of the SLA Platform is where the migration rules are configured
- Adding a new migration rule to an existing application – guides you through creating new migration rules that are used to control how applications are installed during a deployment task sequence.