Enter the full URL for the ActiveEfficiency Server service: https://<serverFQDN>/ActiveEfficiency

This is a common setting optionally used by Nomad. The URL is optional and validated if non-blank.

Enter the UNC of the Configuration Manager Application Content Source share where the wizard saves application files for use by Configuration Manager. The wizard will create 1E folders below it.

For example, your applications UNC may be: \\acme-server\dsl$\Applications.

Enter the UNC of the Configuration Manager Package Content Source share where the wizard saves package files for use by Configuration Manager. The wizard will create 1E folders below it.

For example, your packages UNC may be: \\acme-server\dsl$\Packages.

Determines if an application for the client is created in Configuration Manager.

You must check Create Application and/or Create Package option to enable and click on the Next button.

If this option is not checked then the CDA Wizard will not copy files and create an MST transform in the Application Content Source specified in the General settings screen.

Only enabled if you choose Create Application and determines whether a required deployment type for the application is created in Configuration Manager.

The device collection used to deploy the application. If specified then the CDA wizard will also create a deployment for the application's deployment types and the specified collection.

A default name is suggested, which you can change. If the name you entered for Create/Select Device Collection does not exist, one is created. You must manually populate the created device collection after running the CDA wizard.

You can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC. If you do this, you will not have the option to associate the device collection with a Limiting Collection .

If you are creating a new device collection, you must also choose an associated Limiting Collection.

This limits administrators to populating the new device collection with devices only from the selected Limiting Collection. By default, this is All Systems, but you can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC.

The path to the 1E NightWatchman Agent logs. The default path keeps the log files together with the Configuration Manager client logs. It uses [WindowsFolder] which is a Windows installer property name that refers to the Windows folder.

Check this option if you have a NightWatchman Management Center server installed, and want NightWatchman to report power state changes and retrieve policy settings.

Select either the HTTP or HTTPS protocol.

Determines if an application for the client is created in Configuration Manager.

You must check Create Application and/or Create Package option to enable and click on the Next button.

If this option is not checked then the CDA Wizard will not copy files and create an MST transform in the Application Content Source specified in the General settings screen.

Only enabled if you choose Create Application and determines whether a required deployment type for the application is created in Configuration Manager.

The device collection used to deploy the application. If specified then the CDA wizard will also create a deployment for the application's deployment types and the specified collection.

A default name is suggested, which you can change. If the name you entered for Create/Select Device Collection does not exist, one is created. You must manually populate the created device collection after running the CDA wizard.

You can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC. If you do this, you will not have the option to associate the device collection with a Limiting Collection .

If you are creating a new device collection, you must also choose an associated Limiting Collection.

This limits administrators to populating the new device collection with devices only from the selected Limiting Collection. By default, this is All Systems, but you can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC.

Determines if an application for the client is created in Configuration Manager.

You must check Create Application and/or Create Package option to enable and click on the Next button.

If this option is not checked then the CDA Wizard will not copy files and create an MST transform in the Application Content Source specified in the General settings screen.

Only enabled if you choose Create Application and determines whether a required deployment type for the application is created in Configuration Manager.

The device collection used to deploy the application. If specified then the CDA wizard will also create a deployment for the application's deployment types and the specified collection.

A default name is suggested, which you can change. If the name you entered for Create/Select Device Collection does not exist, one is created. You must manually populate the created device collection after running the CDA wizard.

You can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC. If you do this, you will not have the option to associate the device collection with a Limiting Collection .

If you are creating a new device collection, you must also choose an associated Limiting Collection.

This limits administrators to populating the new device collection with devices only from the selected Limiting Collection. By default, this is All Systems, but you can click Browse to choose from a list of existing collections which you have access to using Configuration Manager RBAC.

Enter the Default Stagger Range Seconds. The default is 300 (5 minutes).

Uncheck this option to disable the Inventory module of 1E Client.

The Inventory module supports the Tachyon Activity Record feature (also known as Tachyon Inventory, and Historical Data Capture) which is required when using the Tachyon Connector for AppClarity or Application Migration. You can enable this separately from Tachyon, but the captured data cannot be used unless the Tachyon is enabled.

Uncheck this option to disable the Interaction module of 1E Client. This feature was introduced in Tachyon 5.1.

The Interaction module supports the User Surveys and Notifications feature (also known as 1E Client UI) which is required when using the Survey feature of Tachyon Experience application, and user-centric sampling features. You can enable this separately from Tachyon, but the captured data cannot be used unless the Tachyon is enabled.

The port number used for local communication between the 1E Client service and the 1E Client UI.

Port is configurable between 100 and 65535. The default is 7766.

Check this option to enable support for Microsoft Edge/Windows App browsers.

This option is available only if Shopping is enabled.

Check this option to enable the WakeUp client module of 1E Client.

Check this option if you have a NightWatchman Management Center server installed, and want WakeUp to report subnet changes.

Select either the HTTP or HTTPS  protocol.

These options are available only if WakeUp is enabled.

This option is especially useful for computer which change location frequently. WakeUp reports subnet changes immediately, whereas NightWatchman reports changes according to its inventory reporting schedule. WakeUp only supports Wake-on-LAN for wired connections and not for wireless, therefore a laptop reporting a subnet change from wired (docked) to wireless helps the WakeUp Server avoid wakeup attempts on the wired connection, and a wakeup failure will be attributed to the wireless subnet.

Enter the path to the Nomad logs. The default path keeps the Nomad log files together with the Configuration Manager client logs. It uses [WindowsFolder] which is a Windows installer property name that refers to the Windows OS folder.

This default is useful for client OS. For location may be different for CM servers. For example CM logs on a Management Point server may be located in C:\Program Files\SMS_CCM\Logs if the MP roles was installed prior to the CM client.

Select the size of for the Nomad log files. We recommend 5 MB.

Check this to enable Nomad's single-site download feature where Nomad master caches can service an entire local site not just the local subnet.

You must have ActiveEfficiency Server installed for this feature to work. See also SSPBA below.

Check this to enable WakeUp integration so that machines where the Nomad cache contains a particular package can be used by the Nomad master even if the machine with the cache is currently switched off.

You must have ActiveEfficiency Server installed for this feature to work.

Check this to enable Nomad's PBA feature. See also SSPBA below, and SDD above.

This OS deployment feature enables Nomad to be used as a data store for USMT data to migrate user settings from the old OS to the new one. It removes the necessity for specifically provisioning state migration points or servers to hold the backup data.

Check this to enable Nomad's SSPBA feature (only enabled if Peer Backup Assistant is checked).

You must have ActiveEfficiency Server installed for this feature to work. See also SSD above.

Check one or more of the following:

• SMB
• HTTP
• HTTPS

When selecting HTTPS you can also check one or both of the following:

• Use PKI Client Auth cert
• Use PKI Server Auth cert

The path to the PXE Everywhere logs. The default path keeps the PXE Everywhere log files together with the Configuration Manager client logs. It uses [WindowsFolder] which is a Windows installer property name that refers to the Windows folder.

The location of the Windows ADK. If this has been installed on a Configuration Manager site server, the location should be:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit

PXE Everywhere requires that certain files are in its TftpRoot folder in order to be able to service PXE requests. These files mostly come from the winpe.wim file in the WinPE addon for the Assessment and Deployment Kit (ADK). 1E cannot bundle these files with PXE Everywhere because Microsoft does not allow their redistribution. The wizard automates this process by creating a CAB file and MST data so that the boot files are put in place as PXE Everywhere is installed. So you must locate the Windows ADK that will be used as the source.

Check this to enable support for DHCP Snooping. This feature requires you have at least one PXE Everywhere Responder installed, and configured your network to forward PXE requests to the Responder(s) on the specified DHCP port, and authorize them to receive and respond to requests. For more detail, please refer to PXE Everywhere 4.0 - Introducing PXE Everywhere.

When you enable this option, you can also specify the DHCP port that the PXE Everywhere Agents listen for responses from the Responder. If you change this then you must configure Responders to use the same port. By default, this is port 2067.

If you do not check the DHCP Snooping option, then you do not need Responders and PXE Everywhere Agents listen for responses on port 67.