12.0

Dragon 12 Administrator Guide
MSI Options for Roaming User Profile,
Tuning, and Data Collection Setup
This section summarizes the Roaming User Profile, acoustic/language model tuning, and data col-
lection options for command line installations of Dragon NaturallySpeaking . Other options are
listed under:
n Summary: MSI Windows Installer Options
n Summary: MSI Options Specific to Dragon
n Summary: MSI Options for Installing Dragon Features/Advanced Options
Options Description
PERIODIC_TASK=<string> Sets schedule for either one, two, or three tasks — an acoustic
model optimization (ACO) task, language model optimization (LMO)
task, and/or data collection (DC) task. You can schedule each task
to run daily or weekly, but need to set the schedule for each task
only once.
See PERIODIC_TASK for more details.
ROAMINGUSERINI="c:\xyz.ini" Specifies a roaming user .ini file (roamingdef.ini) that contains the
Master Roaming User Profile location and any associated HTTP or
HTTPS settings for a Roaming User Profile. These are the same options
set in the Network Directories field of the Roaming tab of the
Administrative settings dialog box and the HTTP and HTTPS Set-
tings dialog boxes.
See ROAMINGUSERINI for more details.
PERIODIC_TASK
The <string> of PERIODIC_TASK contains these arguments, separated by semicolons:
aco | lmo | dc — One, two, or all three of them with a vertical bar separating each. If
you do not pass the acronym for the feature, that feature is set to its default.
Administrator login name. Be sure you use the fully qualified <domain name>\<account
name> in a case where the end-user is a local administrator but the computer is on a
domain.
Administrator password.
When to run the task(s), with times for each of multiple tasks separated by a vertical bar
(|). Each scheduled time should be in the format DayOfWeek, hh:mm, where the day of the
week is the three letter abbreviation (no period), the time is the 24-hour time, and the
comma between them is required.
The task runs once a week on the day/at the time you indicate. If you omit the DayOfWeek,
the task runs every day at the time given.
The first of multiple times becomes the schedule for the first task named in the first param-
eter, the second time the schedule for the second task, the third the schedule for the third
200