Installing Content Distribution overview

Learn how to install and configure Content Distribution, including required components, installation order, client deployment, and Configuration Manager integration. This overview covers prerequisites, deployment tools, and post-installation tasks to help optimize peer-to-peer software distribution and reduce WAN bandwidth usage across enterprise networks.

Installers

Before installing Content Distribution make sure your infrastructure meets the Requirements.

Content Distribution requires:

  • The Platform.

  • 1E Client with Content Distribution enabled, installed on Windows devices.

  • 1E Client with Content Distribution enabled, installed on Configuration Manager Distribution Points.

For full details, refer to:

Content Distribution Tools

Tool

Description

NomadBranchGui.msi

Installer for a useful troubleshooting tool to monitor Content Distribution activity. It has no dependency on Configuration Manager.

For information about using this tool, refer to Nomad Download Monitor.

NomadBranchTools.msi

Installer for

  • NomadBranch Tools (for OSD) on Configuration Manager site servers.

  • Nomad Branch Admin Extensions on Configuration Manager consoles (previously NomadBranchAdminUIExt.msi).

For information about installing these tools, refer to Installing Content Distribution tools.

Scripts\ExampleSitesAndSubnets.ps1

Sample script that provides two functions to update sites and subnets in the Content Distribution locations table: DeleteAllLocations and AddLocation().

For details of how to use this script, refer to Example Single Site script.

Scripts\PostADSitesandSubnets.ps1

Sample script that scans the Active Directory (AD) environment for all sites and subnets and stores the information in the Content Distribution locations table.

For details of how to use this script, refer to Example Active Directory Single Site script.

The sample PowerShell scripts can be used to populate the Content Distribution database, to support the following Content Distribution features:

1E Client

1E Client installation files are available for download from the 1E Support Portal.

Content Distribution is included with the 1E Client, which also includes Platform and client for Shopping/WSA and WakeUp. Refer to Introducing 1E Client.

Refer to Client Deployment Assistant for information about a wizard that assists Configuration Manager with the deployment of 1E Client and PXE Everywhere, guiding you through common settings for clients and deployments.

Installation Order

We recommend you install Content Distribution in the following order.

  1. Platform:

    If you have purchased a platform license, then you can install and use the Platform for additional features.

  2. Tools for Operating System Deployment (OSD) on Configuration site servers:

    Install branch Tools for OSD on the Configuration Manager primary sites (and extra SMS Providers, if they exist) if Content Distribution's OSD features are required, refer to Installing Content Distribution tools.

    Configuration Manager Console should not be running on the computer when NomadBranchTools is installed/upgraded.

    If you are also implementing PXE Everywhere, you may wish to install PXE Everywhere Central on your site server at this point. Refer to Installing PXE Everywhere Central.

  3. Install Console extensions on Configuration Manager site servers:

    Install branch tools on any computers that have Configuration Management Console installed, refer to Installing Content Distribution tools.

    Configuration Manager Console should not be running on the computer when NomadBranchAdminUIExt is installed/upgraded.

  4. Deploy 1E Client to selected Configuration Manager Distribution Points:

    Install 1E Client (with Content Distribution enabled) on Configuration Manager Distribution Points. Enable Platform features and other settings if required.

    By default, IIS is configured to prevent certain file types from being downloaded. You will need to allow Content Distribution to download all content as it does not use the Configuration Manager workaround to bypass this Microsoft security feature.

    We recommend you read IIS Request Filtering which describes how to update the filtering on all distribution points to enable Content Distribution to function as expected.

    You might also want to configure any virus checkers running on your network to make exceptions for the Content Distribution executables and support files, as described in Antivirus exceptions.

    You can also optionally install PXE Everywhere Responders to selected clients if you have DHCP snooping enabled in your network. Refer to DHCP Snooping.

  5. Deploy 1E Client to selected Configuration Manager clients:

    Install 1E Client (with Content Distribution enabled) on Configuration Manager Distribution Points. Enable platform features and other client settings if required.

    You can also optionally enable PXE Everywhere in the 1E Client..

  6. Post-installation tasks:

    Verify selected clients before deploying the 1E Client to remaining Distribution Points and client devices. Deploy Console extensions to administrator workstations.