Exercise Overview:

Using Single Site Download and FanOut

So far, you have observed Nomad with its default configuration where a master is elected in each subnet. This lab environment has been configured to represent two distinct locations (a datacenter and a remote office), with the servers all located in the datacenter and the workstations all located in the remote office. It just so happens that the remote office has two subnets. Active Directory Sites have already been defined to reflect this configuration.

In this lab, you will implement the Single Site Download feature, which enables a 1E Client to obtain content from a peer in an adjacent subnet (within the same defined location) if that content is not available on a peer in its own local subnet.
You will then enable FanOut and observe the behavior when this feature is enabled to allow multiple 1E Clients to serve content simultaneously within the same subnet instead of relying on a single elected master.

Prepare ActiveEfficiency for Single Site Download

The role of ActiveEfficiency in the Single Site Download scenario is to provide a client requesting content with details of computers that are in 'neighboring' subnets within the same location. To do that it needs to know which subnets make up each site. Because not all Active Directory infrastructures are set up with content distribution in mind, this information might not exist in AD, or the information in AD may not be suitable for Single Site Download. Fortunately, our AD administrator has done a good job in defining this in Active Directory Sites and Services. Doesn't hurt that we only have a single remote site with only 2 subnets.

In this exercise, you will execute a PowerShell script that imports site and subnet information from Active Directory into the ActiveEfficiency database. You will also execute a PowerShell script that will import Site and Subnet information from a CSV file. This prepares ActiveEfficiency to support the Single Site Download feature.

Import Site Information from AD

1ETRNDC

  1. Log on to 1ETRNDC as 1ETRN\Administrator and from the Start screen start typing active directory then click Active Directory Sites and Services from the Search results to launch the Active Directory Sites and Services console
  2. Note there are two AD sites (Datacenter and RemoteOffice). Right-click each of these and select Properties to view the Subnets assigned to each of these sites
  3. You are now going to execute a PowerShell script that will read the site definitions from Active Directory and replicate these in ActiveEfficiency.

1ETRNAP

  1. On 1ETRNAP, open SQL Server Management Studio and connect using default credentials
  2. Expand Databases and select the ActiveEfficiency database
  3. Enter the following query and hit CTRL + E (Execute)
  4. select * from Locations
  5. Note that zero rows are returned
  6. From the SkyTap Shared Drive shortcut on the desktop browse to 1E Nomad - Course Content\Nomad 7.0 Course Content and download and copy the Scripts.zip to C:\Temp once copied right click and extract all
  7. Browse to the C:\Temp\scripts folder, right-click on PostADSitesandSubnets.ps1 and select Edit. This will open the file in Windows PowerShell ISE
  8. Browse around the script to review the logic
  9. Scroll down to Line 147 and note the value that is specified for $url uses 'localhost'
  10. The script is written to be executed locally on the ActiveEfficiency server but may be executed anywhere provided that the $url value is modified accordingly.

  1. Hit the F5 key or click on the button to execute the script. It will take a moment to complete and will echo results similar to the figure below (the GUIDs will be different):

  1. Open the 1E ActiveEfficiency web service page (http://localhost/ActiveEfficiency) in Internet Explorer and click the Locations link (http://localhost/ActiveEfficiency/Locations). We now have site information from Active Directory in ActiveEfficiency
  2. Also look at the devices link, and notice this has populated, this occurred when the 1E Client was installed on the devices
  3. Observe the data that has been imported into the Locations table. Note that each subnet imported by the script is represented by a unique row (with a GUID) in the Locations table. As we imported from AD, the AD site name is used to name the site in ActiveEfficiency.
  4. Switch back to SQL Server Management Studio and hit CTRL + E to execute the query again and note the results
  5. Close the Windows PowerShell ISE

Import Site Information from a CSV File

In case the site information in Active Directory is either missing or inappropriate for Single Site Download, the site information may be imported from a simple CSV file.

The design and configuration of Active Directory sites in many enterprises do not consider content distribution. For example, a large region such as North America may be defined as an Active Directory site. While this may work well for authentication and AD Policy distribution, using this configuration would result in Nomad Single Site Download identifying locations in Chicago and Miami as being 'local' to each other and allow machines in each location to attempt to share content as peers. In situations such as this, it would be necessary to use a data source other than Active Directory to define sites in ActiveEfficiency to support Nomad Single Site Download.

1ETRNAP

  1. On 1ETRNAP, right-click on the c:\temp\scripts\AELocations.csv file, and open with notepad. Note the locations defined in the file, and the format. Close the file after reviewing it
  2. Right-click on PostCSVSitesandSubnets.ps1 file in C:\Temp\scripts and select Edit
  3. Scroll down to line 125 and note that there is a # at the beginning of the line so that the sites we just imported from AD are not deleted

  4. The DeleteAll function would be appropriate if we wanted to use the CSV file as the definitive source of information. In the lab, our clients are located in the AD Sites so we want to keep them.
  5. Scroll down to line 127 and note the location of the csv file that will be used to define the sites
  6. Hit the F5 key or click on the button to execute the script. Click OK when prompted that this action will cause the script to be saved

  1. It will take a moment to complete and will echo results similar to the figure below (the GUIDs will be different):


  1. Return to the 1E ActiveEfficiency web service page (http://localhost/ActiveEfficiency) in Internet Explorer and click the Locations link (http://localhost/ActiveEfficiency/Locations). You will see all of the sites from AD and the CSV file
  2. Execute the query again in SQL Server Management Studio and observe the results
  3. Close Windows PowerShell ISE

Reboot All Workstations

1ETRNDC

  1. If you didn't reboot the workstations after the Software Updates section then Log on to 1ETRNDC as 1ETRN\Administrator
  2. Double-click on the RebootAllWorkstation.bat file in C:\Temp
  3. As stated in the Software Updates lab, we need a reboot before anything can be further deployed to the clients. You can carry on with the next lab while the machines reboot.

Enable Single Site Download on clients

Now that we have site information in the ActiveEfficiency database, we need to tie it together with clients. Single Site Download is enabled on Nomad clients by setting the SSDEnabledContentRegistration and PlatformURL registry values. These settings can be defined during installation using installer properties, but in this exercise, we are going to use the ConfigMgr Compliance and Settings Management feature to manage these registry values.


If you enable Single Site Download during installation of the 1E Client, you only need to define the SSDENABLED and PLATFORMURL installer properties. However, if you enable the feature after installation through modification of the registry, you must also explicitly set the ContentRegistration value to 1.

The Compliance Settings feature of ConfigMgr is recommended for all post-installation configuration of the 1E Client, so this is a good example to demonstrate how to do it.

Import a Configuration Item to configure Single Site Download

In this task, you will import a predefined Configuration Item that is configured to set the ContentRegistrationSSDEnabled and PlatformUrl registry values. You will then add these to a new Configuration Baseline and deploy the baseline to the lab workstations in the next task.

1ETRNCM

  1. On 1ETRNCM earlier we downloaded the ConfigurationItems folder to C:\Temp
  2. Open the ConfigMgr console and select the Assets and Compliance workspace
  3. Expand the Compliance Settings node, right-click Configuration Items and select Import Configuration data to start the Import Configuration Data Wizard
  4. On the Select Files page, click Add…, select C:\Temp\ConfigurationItems\EnableNomadSSD_CI.cab and click Open
  5. You will be prompted with a warning that the publisher of this cab file cannot be verified. Live dangerously and click Yes to continue with wild abandon
  6. Click Next. Review the details on the Summary page then click Next again to import the Configuration Item. Close the wizard when complete

Update the Existing 1E Client Configuration Baseline

In this task, you will add the Enable Nomad SSD Configuration Item imported in the previous task to the existing 1E Client Configuration baseline. 

1ETRNCM

  1. From the Assets and Compliance workspace select the Configuration Baselines node, right-click the 1E Client Configuration baseline you created earlier and select Properties
  2. From the 1E Client Configuration Properties dialog box, select the Evaluation Conditions tab, then click Add and select Configuration Items
  3. In the Add Configuration Items dialog box select the Enable Nomad SSD Configuration Item and click Add to add this to the 1E Client Configuration baseline. Click OK to return to the 1E Client Configuration Properties dialog box, then click OK to save the changes

Validate SSD Settings

All workstations

  1. To speed up evaluation (and remediation – i.e. setting the required registry values) on the clients, perform the following steps on each workstation
    1. Log on as 1ETRN\User and open the Configuration Manager client UI (from the shortcut on the desktop)
    2. From the Actions tab, run Machine Policy Retrieval & Evaluation Cycle
    3. Select the Configurations tab
    4. Select the 1E Client Configuration baseline, ensuring the revision shows 2
  2. If the baseline is not showing Revision=2, click Refresh until it changes
    1. Click Evaluate
    2. Confirm that the evaluation completes and the Compliance column shows Compliant

Observe the Nomad ActiveEfficiency Registrations

Once the 1E Client Configuration baseline has been applied, the 1E Client service will restart and then register with ActiveEfficiency. In this exercise, you will observe the information that is registered by the 1E Client.

1ETRNW71

  1. Open NomadBranch.log and observe the Nomad service starting up after the configuration changes were made. First, you will see the computer register with ActiveEfficiency and note that a DeviceId has already been posted

When the 1E Client was initially deployed, we specified the ActiveEfficiency URL and this value was set in the PlatformURL value. There is no need for the device to register again.
The VMWare virtual machines in this lab environment do not correctly populate the WMI class that Nomad queries to determine the device type, and Nomad therefore returns 0 (UnknownDeviceType). This is an issue specific to these VMWare virtual machines (physical computers are correctly identified) so we'll fix it in the database later.

  1. With the DeviceId, Subnet and NomadDeviceType already registered, the next action will be that the 1E Client has the Single Site Download feature enabled. This is displayed as indicated in the log entries below

  1. Lastly, it registers this client as a Content Provider (meaning other clients can obtain content from this computer) and the Single Site Download feature is ready


1ETRNAP

  1. On 1ETRNAP, open SQL Server Management Studio from the Start screen and connect to the local database server
  2. In the left hand pane, expand Databases and select the ActiveEfficiency database
  3. Click the New Query button in the toolbar
  4. Enter the following query and click the Execute button
  5. select * from Devices


    As each 1E Client registers with ActiveEfficiency, it is assigned a unique ID (Id column). This is stored in HKLM\Software\1E\NomadBranch\ActiveEfficiency\DeviceId on the client as you saw earlier.
  6. Now run the following query
  7. select * from AdapterConfigurations


    When the 1E Client starts up it registers the subnet that its primary network adapter is connected to and this is stored in the AdapterConfigurations table. This record is given a unique ID and the record is updated whenever the client's primary adapter changes subnet.
  8. Each record in the AdapterConfigurations table is joined to a Device in the Devices table on the Device ID. Run the following query to see the device and subnet information joined in a single result set
  9. select d.Id, d.HostName, d.DomainName, ac.ipv4subnet 
    from Devices as d
    join AdapterConfigurations as ac on d.Id = ac.DeviceID
  10. Execute the following query, which demonstrates the relationship between the Devices, AdapterConfigurations and Locations tables that enable ActiveEfficiency determine which Location a Nomad client is currently in
  11. select d.Id, d.HostName, d.DomainName, ac.ipv4subnet, l.Site 
    from Devices as d
    join AdapterConfigurations as ac on d.Id = ac.DeviceID
    join Locations as l on ac.ipv4subnet = l.subnet

Fix the DeviceType Tag

As already noted, Nomad is unable to correctly identify the chassis type of the VMWare virtual machines in this lab environment, so the DeviceType tag for these workstations is set to 0 (Unknown). Nomad will not use a client for Single Site Download if the DeviceType tag is unknown, so in order to get Single Site Download working in this lab, we need to set the DeviceType tag to a valid type. In this task you will run a simple query to update the DeviceType tag for all the devices to a value of '1'.

The queries in steps 48 and 50 below are located in the CommandLinesAndQueriesQueries.txt file from the SkyTap Shared Drive shortcut on the desktop and browsing to 1E Nomad - Course Content\Nomad 7.0 Course Content to allow easier copy and paste into SQL Management Studio.

1ETRNAP

  1. On 1ETRNAP, from SQL Server Management Studio with the ActiveEfficiency database selected, run the following query
  2. select d.Id, d.HostName, dt.Name, dt.StringValue from DeviceTags as dt
    join Devices as d on d.Id = dt.DeviceId
    where Name='DeviceType'
  3. This will return the DeviceType device tag for each of the devices (1E Clients) that have registered with ActiveEfficiency. Note that these are all set to zero currently
  4. Execute the following query to set the DeviceType value to 1 on all devices
  5. Update DeviceTags set StringValue = 1
    where DeviceTags.Name = 'DeviceType'
    This step is only necessary in this lab environment. In a production environment using physical computers, Nomad will correctly identify the DeviceType. You can of course confirm this in your production database by running the query in step 48.
  6. Re-execute the query in step 48 to confirm the DeviceType tag has now been updated and is set to 1 for all devices

Enable DBS logging

Nomad 6.3 introduced a new mechanism to speed up downloads. Dynamic Block Size, or DBS. With DBS, Nomad can automatically determine the appropriate block size for a given link and adjust it as needed during a download, same as it can change the rate of download dynamically. As a result, Nomad becomes even more efficient and often faster on all types of connections while still accounting for business traffic. DBS works on transfers between the DP and a master as well as between peers.

In version 7.0 of Nomad DBS is disabled by default. And DBS logging is turned off on Nomad clients due to its verbose nature

Import a Configuration Item to enable DBS Logging

In this task, you will set the Compatibility flags so that DBS Logging is enabled, this is done via a Configuration Item configured to amend the compatibilityflags registry value and then create a registry value under HKLM\Software\1E\NomadBranch. The value, DebugDynamicBlock will be created by the CI and will be set to 3. You will then add these to a Configuration Baseline and deploy the baseline to the lab workstations in the next task.

1ETRNCM

  1. On 1ETRNCM earlier we downloaded the ConfigurationItems folder to C:\Temp
  2. Open the ConfigMgr console and select the Assets and Compliance workspace
  3. Expand the Compliance Settings node, right-click Configuration Items and select Import Configuration data to start the Import Configuration Data Wizard
  4. On the Select Files page, click Add…, select C:\Temp\ConfigurationItems\Enable Dynamic Blocksize LoggingCI.cab and click Open
  5. You will be prompted with a warning that the publisher of this cab file cannot be verified. Live dangerously and click Yes to continue with wild abandon
  6. Click Next. Review the details on the Summary page then click Next again to import the Configuration Item. Close the wizard when complete

Update the Existing 1E Client Configuration Baseline

In this task, you will add the Enable Nomad SSD Configuration Item imported in the previous task to the existing 1E Client Configuration baseline.

1ETRNCM

  1. From the Assets and Compliance workspace select the Configuration Baselines node, right-click the 1E Client Configuration baseline you created earlier and select Properties
  2. From the 1E Client Configuration Properties dialog box, select the Evaluation Conditions tab, then click Add and select Configuration Items
  3. In the Add Configuration Items dialog box select the Enable Dynamic Blocksize Logging Configuration Item and click Add to add this to the 1E Client Configuration baseline. Click OK to return to the 1E Client Configuration Properties dialog box, then click OK to save the changes

Validate DBS Logging Settings

All workstations

  1. Run regedit.exe. Navigate to HKLM\Software\1E\NomadBranch. Confirm a value of debugdynamicblock does not exist
  2. To expedite the process of evaluation (and remediation – i.e. setting the required registry values) on the clients, perform the following steps on each workstation
    1. Log on as 1ETRN\User and open the Configuration Manager client UI (from the shortcut on the desktop)
    2. From the Actions tab, run Machine Policy Retrieval & Evaluation Cycle
    3. Select the Configurations tab
    4. Select the 1E Client Configuration baseline, ensuring the revision shows 3
  3. If the baseline is not showing Revision=3, click Refresh until it changes
    1. Click Evaluate
    2. Confirm that the evaluation completes and the Compliance column shows Compliant
  4. Run regedit.exe. Navigate to HKLM\Software\1E\NomadBranch. Confirm a value of debugdynamicblock has been created, and set to 0x3(3)
  5. Also confirm the value for CompatibilityFlags is set to 0x2018000a (538443786) (this is the sum of the bit flags for the default settings, the value for each flag can be found in the product documentation at help.1e.com

Deploy a Package using Nomad with SSD Enabled

In this exercise, you will configure a legacy package to use Nomad and then deploy it to the Lab Workstations Collection and observe the behavior.

The download behavior would be the same if an Application or Software Update (rather than a Package) was deployed in this exercise.

Launch Monitoring Tools on All Client Computers

At the end of an earlier, the Windows 7 client computers required a reboot to finish the installation of Software Updates and we actually restarted all the workstations. The NomadBranch Download Monitor and Event Viewer will need to be started so that the SSD Deployment may be monitored.

1ETRNW71

  1. Log on to 1ETRNW71 as 1ETRN\User
  2. If not already running, browse to C:\Tools\NomadEventViewer and double-click NomadEvtVwr.exe to launch the Event Viewer

All workstations

  1. Log on to All Workstations as 1ETRN\User
  2. Launch the NomadBranchGUI application from the Start menu

Configure the Package to use Nomad

1ETRNCM

  1. In the ConfigMgr console, open the Software Library workspace, expand the Application Management node and select the Packages node
  2. Right-click the RDC Manager Package and select Properties from the context menu
  3. In the ConfigMgr Properties dialog box, select the Nomad tab and enable Nomad. Set the workrate to 10. Click OK

Deploy the Program to Lab Workstations

1ETRNCM

  1. With the Packages node selected, right-click the RDC Manager Package and select Deploy to start the Deploy Software Wizard
  2. On the General tab browse for the Lab Workstations Collection. Click Next
  3. On the Content page, ensure the content is on the 1ETRNCM DP and click Next
  4. On the Deployment Settings page ensure Purpose is set to Required and click Next
  5. On the Scheduling page, create a new Assignment Schedule to execute at the current time (default). Click Next
  6. On the User Experience page, check Allow users to run the program independently of assignments and click Next
  7. On the Distribution Points page, ensure that both Deployment Options are set to Download content from distribution point and run locally. Click Next
  8. On the Summary page click Next to complete the wizard, then close the wizard when it completes
  9. For this exercise, we will wait for the clients to refresh their policy at the configured interval (5 minutes) rather than forcing them all to refresh at exactly the same time.

Monitor the download

In this task, you will monitor the download process across two subnets

To make it easy to remember, computers with a name ending in an odd number are in subnet 10.0.1.0, while those with a name ending in an even number are in subnet 10.0.2.0.

1ETRNW71

  1. On 1ETRNW71, observe the Nomad Event Viewer to identify the first elected master. The example below shows 1ETRNW71 being elected (this client is in subnet 10.0.1.0). In your lab, it could be any of the workstations in either of the two subnets, but you're looking for the first client to be elected

  1. Open NomadBranch.log on this elected master and observe the normal election process, followed by a request to ActiveEfficiency. As this is the first client in the site to request the content, it is not available on any other client in the site and ActiveEfficiency returns no content available

  1. Observe the agent then registers with ActiveEfficiency that it is now going to download the content. From this point on, ActiveEfficiency will be able to return this client as a possible source for the content to clients in other subnets within the same location

  1. Observe as this client then downloads the .LsZ file from the DP, after which it updates ActiveEfficiency once again to indicate the download has actually started


1ETRNAP

  1. On 1ETRNAP, from the SQL Server Management Studio with the ActiveEfficiency database selected, run the following query

  2. This useful query joins the data from the Devices, Contents and ContentDeliveries tables in the ActiveEfficiency database to show the current status of a particular piece of content (defined as ContentName in the Contents table – in this case the RDCMan package PS100015).
    select d.HostName, cd.StartTime, cd.EndTime, cd.[Percent]
    from ContentDeliveries as cd
    join Contents as c on cd.ContentId = c.Id
    join Devices as d on cd.DeviceId = d.Id
    where c.ContentName = 'PS100015'
1ETRNW71

  1. Return to the Nomad Event Viewer on 1ETRNW71 and identify the first election request from the other subnet. You may see other clients in the same subnet initiate election requests first – you are looking out for the first election request from the other subnet. The example below shows 1ETRNW72 as the first client in the other subnet to request an election, but it could be any machine on the other subnet

Note that the event viewer shows two MASTER CHANGED events from 1ETRNW72. The first of these is the election of itself as the master on its own subnet. The second is the selection of the Site Master (in this case 1ETRNW71) in the adjacent subnet.

  1. Open NomadBranch.log on the client that was elected as the master in the second subnet

  1. Observe the normal election activity where this computer gets elected as the master

  1. Observe immediately after this that the client queries ActiveEfficiency to determine if the content might be available on an adjacent subnet. In the example below, ActiveEfficiency has returned one possible client (1ETRNW71). Nomad then sends a Package Status Request to the returned client and selects it. If more than one client had been returned, the client that has the most content already cached becomes the Site master

  1. Observe as this elected subnet master now starts to download content (starting with the .LsZ file) from the Site master on the adjacent subnet. After downloading the LsZ file, the agent registers with ActiveEfficiency that it has now started the download. Every client that has ContentRegistration enabled will update ActiveEfficiency in this way whenever it starts to download content


1ETRNAP
  1. Return to 1ETRNAP and re-execute the query to observe how the status of the download has progressed
  2. Note that each client (not just the elected masters) registers with ActiveEfficiency when it starts to download the content.

Any Client

  1. Observe NomadBranch.log on any of the clients as the download completes

Note that each client registers with ActiveEfficiency when content download has completed.

Review DBS Logging

1ETRNW71

  1. Open the Nomadbranch.log if not already open
  2. Search the log for BlkSz

  1. Note that with each block download, the log shows multiple variables such as BlkSz, Tim, Spd, PrevSpd, Del and PercDel

This is the DBS functionality in action. With each block download, based on what is happening across the network, Nomad will dynamically determine the appropriate block size, allowing for further efficiency on the content transfer

Deleting content with Single Site Download enabled

In this exercise, you will observe the behavior when content is deleted from the Nomad cache and Single Site Download is enabled.

Delete content using CacheCleaner.exe

1ETRNW71

  1. On 1ETRNW71, open a Command Prompt (run as administrator) and change directory to C:\Program Files\1E\Client\Extensibility\NomadBranch
  2. Execute the following command line to delete the RDC Manager package content

  3. Cachecleaner -DeletePkg=PS100015 -PkgVer=1

  1. Observe the activity in NomadBranch.log to confirm that the content has been deleted


When Single Site Download is enabled, the agent will register any content deletion with ActiveEfficiency so it will no longer be considered a possible source for that content.
1ETRNAP

  1. On 1ETRNAP, re-execute this SQL query. Note that 1ETRNW71 is no longer returned in the query results

  2. select d.HostName, cd.StartTime, cd.EndTime, cd.[Percent]
    from ContentDeliveries as cd
    join Contents as c on cd.ContentId = c.Id
    join Devices as d on cd.DeviceId = d.Id
    where c.ContentName = 'PS100015'
  3. Repeat the above steps to delete this content on 1ETRNW73 (for the next exercise, we want to leave the content for this package on just one client in the 10.0.1.0 subnet)

Using Fanout

You have already seen in Review the Installation on the Workstations steps that by default the Nomad cache share (NomadSHR$) is created with a connection limit of six. The same limit of 6 applies for HTTP(S) content transfers. This means that up to six Nomad peers can obtain content from the master at any given time. Under normal circumstances, if a 1E Client tries to connect to the master and all six connections are in use on the master, that agent would back off and retry later. The Fanout feature enables the 'rejected' agent to ask for an alternative peer in the same subnet that has the content it needs. Any other peer on the subnet can respond to this request, but will only do so if it meets certain criteria:

It must have more of the content than the agent that is requesting content

It must have available connections and it must not already be connected to a Fanout peer – we only support one level of Fanout currently)

In this exercise, you will observe the Fanout behavior in action.

Enable Fanout on Nomad clients

Fanout is enabled by setting bit 6 (which corresponds to the hex value 0x40, or 64 decimal) of the SpecialNetShare registry value. In a previous task, the 1E Client installation was configured without Fanout being enabled, so Fanout will need to be enabled. To accomplish this, we will import a Configuration Item (CI) and use ConfigMgr Settings Management to enable Fanout on the 1E Clients.

1ETRNCM

  1. On 1ETRNCM earlier we downloaded the ConfigurationItems folder to C:\Temp
  2. In the Configuration Manager console on, open the Assets and Compliance workspace
  3. Under the Compliance Settings folder, right-click the Configuration Items node and select Import Configuration Data to start the Import Configuration Data Wizard
  4. On the Select Files page, click Add… and select C:\Temp\ConfigurationItems\EnableNomadFanOut_CI.cab. Click Open. You will be warned that the published of this file cannot be verified – click Yes to accept the risk and return to the Select Files page of the Import Configuration Data Wizard
  5. Click Next, review the settings on the Summary page then click Next
  6. When the wizard completes, click Close
  7. From the Assets and Compliance workspace select the Configuration Baselines node under Compliance Settings, right-click the 1E Client Configuration baseline you created earlier and select Properties
  8. From the 1E Client Configuration Properties dialog box, select the Evaluation Conditions tab, then click Add and select Configuration Items
  9. In the Add Configuration Items dialog box select the Enable Nomad FanOut Configuration Item from the available configuration items list and click Add to add this to the 1E Client Configuration baseline. Click OK to return to the 1E Client Configuration Properties dialog box, then click OK to save the changes

1ETRNW71, 1ETRNW73 and 1ETRNW101

  1. Log onto each machine and initiate a Machine Policy Retrieval & Evaluation Cycle
  2. Use the process you learned in earlier to manually re-evaluate the 1E Client Configuration on each of the clients in subnet 10.0.1.0 (1ETRNW71, 1ETRNW73 and 1ETRNW101). Ensure that revision 4 of this baseline has been evaluated and is compliant on each of these workstations
  3. Since FanOut works on a per subnet basis, we'll only work with the 10.0.1.0 subnet machines.


  1. Check activity in NomadBranch.log on each of the clients. Search for Fanout

Note that changing SpecialNetShare causes the 1E Client to restart. The can also be observed in the NomadEventViewer as each machine will log a SERVICE RESET when the setting is applied.

Observe FanOut on the clients

In this task, you will reinstall the RDC Manager package on 1ETRNW71 and 1ETRNW73 in the 10.0.1.0 subnet to cause Nomad to re-download the content (remember you manually deleted the content on these two clients earlier). You can then observe as Nomad uses FanOut to obtain content when the NomadSHR connection limit (1) is reached on the elected master (which should be 1ETRNW101 as this client still has the content in its cache from the previous exercise).

1ETRNW71 and 1ETRNW73

For this example to work, it is important that the Nomad download of content on both 1ETRNW71 and 1ETRNW73 is started within about 10 seconds of each other. If there is a delay of more than a few seconds when completing the task, the first client (1ETRNW71) may have time to complete the download from 1ETRNW101 so by the time 1ETRNW73 attempts to connect, there is an available connection and Fanout will not be invoked. If you encounter this scenario, you can always delete the content again from 1ETRNW71 and 1ETRNW73 and repeat the task. The easiest way to accomplish this is to have 2 separate browser tabs open with the two machines. It is possible that the process below is reversed and that 1ETRNW71 gets the connection and that 1ETRNW73 calls for the fanout

  1. On both 1ETRNW71 and 1ETRNW73, open Software Center, go to the Installation Status tab and select RDC Manager – Install RDCMan
  2. On 1ETRNW73, with RDC Manager – Install RDCMan selected, click Reinstall, which will start the content download, then as quickly as you can, do the same on 1ETRNW71

  1. Open NomadBranch.log on 1ETRNW73 and observe the election. 1ETRNW101 should win the election and become the master as it has 100% of the content in its cache

  1. Now open NomadBranch.log on 1ETRNW71 and observe the election process. Note that the elected master (1ETRNW101) does not change, but as there is only one connection available on the NomadSHR, which is currently being used by 1ETRNW73, you will observe that 1ETRNW71 fails to connect to the master. It then polls for a FanOut Peer and gets a response from 1ETRNW73 and starts to download the content from 1ETRNW73

Reset 1E Client to remove Fanout

Now that the Nomad Fan-Out feature has been demonstrated, we no longer want to have Fanout enabled, as we want to see Nomad working in native fashion with the 6 connection limit. As such, we will reset the SpecialNetShare value back to its original value.


1ETRNCM

  1. On 1ETRNCM earlier we downloaded the ConfigurationItems folder to C:\Temp
  2. In the Configuration Manager console on, open the Assets and Compliance workspace
  3. Under the Compliance Settings folder, right-click the Configuration Items node and select Import Configuration Data to start the Import Configuration Data Wizard
  4. On the Select Files page, click Add… and select C:\Temp\ConfigurationItems\DisableFanOut_CI.cab. Click Open. You will be warned that the published of this file cannot be verified – click Yes to accept the risk and return to the Select Files page of the Import Configuration Data Wizard
  5. Click Next, review the settings on the Summary page then click Next
  6. When the wizard completes, click Close
  7. You may notice that the Enable Nomad Fanout CI is no longer present. This is because the Configuration Items for Enable FanOut and Disable FanOut are specially configured so that they will automatically replace one another when added to the Configuration Manager console. Since both work with the same registry setting, they need to be configured in this manner or they will conflict with each other at each evaluation. As such, the CI doesn't need to be added to the Configuration Baseline.

1ETRNW71, 1ETRNW73 and 1ETRNW101

  1. Log onto the machine and initiate a Machine Policy Retrieval & Evaluation Cycle
  2. Use the process you learned to manually re-evaluate the 1E Client Configuration on each of the clients in subnet 10.0.1.0 (1ETRNW71, 1ETRNW73 and 1ETRNW101)
  3. The baseline revision will remain 4 because we are making a change to the same exact setting as the previous Configuration Item did. Review the setting manually per the next step.
  4. Check the HKLM\Software\1E\NomadBranch\SpecialNetShare value on each workstation to ensure it is reset back to 0x2030(8240)

Lab Summary

In this lab, you have learned how to prepare ActiveEfficiency Server to support the Single Site Download feature of Nomad, which allows 1E Clients to obtain content from a peer in an adjacent subnet rather than going across the WAN to the DP. 

You defined the subnet-to-location mapping by importing sites and subnet data already defined in Active Directory, and also imported site and subnet information from a CSV file. You observed how each 1E Client registers with ActiveEfficiency as content provider on start up when Single Site Download has been enabled. By deploying a package to clients that spanned two subnets within the same location, you were then able to observe the master in one subnet obtaining content from a peer in a different subnet but in the same location. You observed how each client updates ActiveEfficiency when it starts and stops downloading content. You also observed how deleting content from a Nomad client reflects in ActiveEfficiency.
You enabled verbose logging for the DBS setting, and reviewed the pertaining log entries showing the changes in block size during content transfer.
You then learned how FanOut can be enabled to allow multiple peers within a subnet to serve content to others in the scenario where there are insufficient connections available on the elected master. This feature will typically enable faster distribution of content in larger subnets compared to the standard behavior you observed earlier, where a maximum of six clients (in addition to the master) can be simultaneously obtaining content within the subnet.
You also learned in this lab how the ConfigMgr Compliance and Settings feature can be used to manage 1E Client configuration in the registry post installation. Specifically, you created and deployed a Configuration Baseline that enables Single Site Download and FanOut on clients. We recommend using Configuration Baselines as the best way to manage the configuration of your 1E Clients in a production environment.

Next Page
Ex 5 - Nomad 7.0 - Preparing for OS Deployments