Running the wizard

Enter the UNC of the Configuration Manager Application Content Source share where the wizard saves content source for use by Configuration Manager applications. 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 content source for use by Configuration Manager packages. The wizard will create 1E folders below it.

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

Check this option if you want Configuration Manager to distribute application and package source to the distribution points after the wizard has been run.

When enabled, a warning is displayed indicating Distribution is enabled, which can be helpful if this option had been enabled in the AppImport.xml answer file.

Select a Distribution Point Group.

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 size of for the NightWatchman Agent log files. We recommend 5 MB.

Check this option to enable the FIPS Encryption for NightWatchman and WakeUp.

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

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 connection details for the 1E Switch in the format:

<DNSnameFQDN>:<port>

Where DNSnameFQDN is normally a DNS alias, as used in the 1E Switch certificate, which is normally the same as the 1E Web Server certificate.

Port is normally 443.

Enter the URL list containing one or more Client Deployment Assistant Background Channel URL in the format:

https://<DNSnameFQDN1:443/Background/;https://<DNSnameFQDN2:443/Background/

Where DNSnameFQDN is normally a DNS alias, as used in the 1E Web Server certificate.

Add a Provisioning key to use this with your 1E Client deployment.

Refer to Enhanced Settings

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

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

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

Uncheck this option to disable the Interaction module of 1E Client. This feature was introduced in 1E 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 Experience Analytics, and user-centric sampling features. You can enable this separately from 1E, but the captured data cannot be used unless the 1E is enabled.

Uncheck this option to disable Do not disturb mode and allow the Client UI to show notifications from startup. Check this option to enable Do not disturb mode and stop the Client UI showing notifications, causing any surveys sent to this device to time out.

If Notification icon is enabled, users will be able to enable or disable notifications by using the Do not disturb option. However, each time the user signs in, the Do not disturb mode will be reset.

Uncheck this option to disable the 1E Client UI notification icon. If enabled, the icon appears shortly after the user signs in.

Uncheck this option to disable Experience Analytics sampling the performance of user interactions with application windows in user sessions.

Enter the Shopping Web URL in the format:

http://<serverFQDN>/Shopping

where serverFQDN is normally a DNS alias.

This option is available only if Shopping is enabled.

Check this option to enable the FIPS Encryption for WakeUp.

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 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 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 log files. We recommend 5 MB.

Select one of the following: IPv4Only, IPv6Only, Hybrid

• 0x0000 - Decimal 0: No special features enabled.

• Bit 0- 0x0001 - Decimal 1: Administrators can configure and manage custom share permissions. The service doesn't create the NomadSHR share on start-up, leaving the administrator to manually create and set the permissions. The existing share permissions are preserved when the service stops.

• Bit 1 - 0x0002 - Decimal 2: Enables support for IPv6. If the network supports both IPv6 and IPv4, enable support for both and set bit 1 but not bit 2.

• Bit 2 - 0x0004 - Decimal 4: Disables support for IPv4. If the network supports only IPv6, disable IPv4 and set both bit 1 and 2.

Check this to enable the hidden share feature and to prevents end-users from accidentally accessing the share.

Check this to enable the Fanout feature. This feature is especially useful in large organizations with many networks.

Check this to prevent downloads from reverting to using BITS if an error occurs. It ensures that any download errors are reported back effectively with minimum impact on remote sites.

Check this to ensure that Content Distribution is FIPS compliant in its communications.

Check this to enable Content Distribution to monitor and report on Delivery Optimization (DO) downloads.

Delivery Optimization monitoring and reporting is only supported in full versions (OS with UI) of Windows Server 2016 and Windows 10 Version 1909 onwards.

You must have 1E enabled and 1E Platform installed for this feature to work.

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

You must have 1E enabled and 1E Platform installed for this feature to work.

See also SSPBA below.

Check this to enable WakeUp integration so that machines where the Content Distribution 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 1E enabled and 1E Platform installed for this feature to work.

You will also need NightWatchman and WakeUp system.

Check this to enable Content Distribution PBA feature. See also SSPBA below, and SDD above.

This OS deployment feature enables Content Distribution 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 Content Distribution SSPBA feature (only enabled if Peer Backup Assistant is checked).

You must have 1E enabled and 1E Platform installed for this feature to work.

See also SSD above.

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 size of for the PXE Everywhere log files. We recommend 5 MB.

Check this to ensure that PXE Everywhere is FIPS compliant in its communications. This is only available from PXE Everywhere 3.0 and later.

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.

The full URL of the PXE Everywhere Central web service which the agent uses:

http://<serverFQDN>/PXELite/PXELiteConfiguration.asmx

You must have PXE Everywhere Central installed for this feature to work.