On this page:

Document Purpose and Conventions

This document has the following aims:

  • To provide instructions to delegates to enable completion of the practical training labs
  • Where relevant, provide guidance which can be used during real world implementations

The following conventions are used to highlight important information.

Warning
Hot Tip
Best practice
Discussion point
Indicates the virtual machine that should be used for the exercise or task.

Lab Information

The lab environment consists of the following computers:

Computer

Role

Subnet

AD Site

1ETRNDC

Domain controller for the 1ETRN.LOCAL domain. The ConfigMgr package source folder is located on this server.

10.0.0.0/24

Datacenter

1ETRNCM

ConfigMgr server with a local SQL instance. All ConfigMgr roles are installed in this server.

10.0.0.0/24

Datacenter

1ETRNAP

Application server that will host the ActiveEfficiency server and database. SQL is installed locally.

10.0.0.0/24

Datacenter

1ETRNW71

Windows 7 client computer

10.0.1.0/24

RemoteOffice

1ETRNW72

Windows 7 client computer

10.0.2.0/24

RemoteOffice

1ETRNW73

Windows 7 client computer

10.0.1.0/24

RemoteOffice

1ETRNW101

Windows 10 client computer

10.0.1.0/24

RemoteOffice

1ETRNW102

Windows 10 client computer

10.0.2.0/24

RemoteOffice


The password for all accounts used in the lab environment is: Passw0rd

Ignore any patching popups on our servers. We have deliberately left them unpatched to show patching via Patch Success and/or Nomad

Unless otherwise indicated, logon to the lab VMs using the following accounts

System

Account

1ETRNDC

1ETRN\Administrator

1ETRNAP

1ETRN\AppInstaller

1ETRNCM

1ETRN\SCCMAdmin

1ETRNW71

1ETRN\User

1ETRNW72

1ETRN\User

1ETRNW73

1ETRN\User

1ETRNW101

1ETRN\User

Troubleshooting Nomad Content Delivery

This mini lab will guide you through the steps to troubleshoot software installation failure when using System Center Configuration Manager and Nomad for content delivery.  This lab focuses on five scenarios where software installation failed.  The steps walk you through stepping through the logs to determine exactly what failed and shows how to resolve the failure.  This lab is not meant to be an exhaustive listing of possible failures but is designed to give you a framework to build on when you are doing actual production troubleshooting.  

Lab Overview

In this lab you will deploy software to devices and trace the content flow to determine why the software did not install.