Configuring FlexEngine in NoAD Mode

You can provide the settings for configuring FlexEngine in NoAD mode by creating an XML file and making the file available on the central configuration share. When a user logs in, FlexEngine reads the settings from the XML file and applies them to the registry.

The XML file that you create on the central configuration share is called NoAD.xml and must reside in the …\General\FlexRepository\NoAD subfolder.

The NoAD.xml is a UTF-8-encoded XML file with an explicit UTF-8 BOM.

Configuring the NoAD.xml file

You can configure the NoAD.xml file using one of the following options.

• (Recommended) Agent Configuration tab on the Management Console. See Using Agent Configuration Tab.

• Manually create the file.

Sample NoAD.xml File

The following sample NoAD.xml file configures the profile archive path, a log file at the INFO level, allows users to log in if the Flex configuration files path or the profile archive path is not accessible, and enables certain Windows event logging options.

<?xml version="1.0" encoding="utf-8"?>
<userEnvironmentSettings>
	<setting type="noAD"
		ProfileArchivePath="\\Filesrv\DemUsers$\%username%\Archives"
		LogFileName="\\Filesrv\DemUsers$\%username%\Logs\FlexEngine.log"
		LogLevel="1"
		ConfigPathMissingAction="0"
		ArchivePathMissingAction="1"
		AppBlockingEventLog="1"
		EventLog="1"
		EventLogAsync="1"
		EventLogDirectFlexRefresh="1"
		EventLogUEMRefresh="1"
	/>
</userEnvironmentSettings>

For integration-mode scenarios, the download package also contains a sample configuration file for use with Workspace ONE UEM. The main difference with the standalone-mode sample is that the profile archive path and the log file configuration settings use local paths instead of paths on a file share.