Scribd
Upload
147 views4 pages

DASHConfig RT Guide

DASHConfigRT is a command line application that can be used to configure DASH systems from Windows. It allows provisioning DASH systems using an XML file to configure settings like users, roles, and Active Directory integration. The utility deletes the XML file after processing to remove passwords. It requires updated DASH software like firmware and client software to support Active Directory configuration.

Uploaded by

robiion969
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
147 views4 pages

DASHConfig RT Guide

DASHConfigRT is a command line application that can be used to configure DASH systems from Windows. It allows provisioning DASH systems using an XML file to configure settings like users, roles, and Active Directory integration. The utility deletes the XML file after processing to remove passwords. It requires updated DASH software like firmware and client software to support Active Directory configuration.

Uploaded by

robiion969
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

DASHConfigRT (v1.

0)

DASHConfigRT is a command line application to configure DASH Systems for the


windows. This utility can be used with management console such as Microsoft SCCM
to provision all the DASH Systems in a set of collection.

In order to support the Active directory for the DASH target. OEM needs to update
the following DASH software.

Prerequisites:
1. The DASH firmware which supports the Active Directory.
2. Windows DASH client software which supports the in-band provision for the
windows.
3. Renew the latest DASH console tool for the windows.

Usage:
There is the command line parameter:
-xf:xmlfile
For example:
“DASHConfigRT -xf: config.xml” ---> no default password
“DASHConfigRT -u:old_username -p:old_password -xf:config.xml”

The -xf:<xmlfile> parameter informs DASHConfigRT of the file system location


for the XML file which will be used to provision the management target.

DASHConfigRT utility will delete the provision XML file after processing the
provisioning file has been completed. This is important due to the inclusion of
password values in the XML file.

The -v parameter will print the version information to the utility.

Provisioning XML File Format

XML Nodes List:


<DASHPROVISIONSETTINGS> - Required, root node
GLOBAL List:

<GLOBAL> - Optional, necessary if any global management target values are to be


provisioned.

<HTTPS> - Optional necessary if any HTTPS protocol values are to be provisioned.

<HTTP> - Optional, necessary if any HTTP protocol values are to be provisioned.


<ENABLESUPPORT> - Optional. If defined, it will enable or disable the HTTP and/or
HTTPS protocol support depending on which protocol parent node in which it is
included. false = disabled, true = enabled.

<TCPIPPORT> - Optional. If defined, it will cause the management target to use


provisioned value as the TCP/IP listening port for WS-MAN requests being sent over
the HTTP or HTTPS protocol depending on which protocol parent node in which it is
included.

USER List:
<USERS> - Optional. Necessary if any user accounts are to be provisioned on the
management target. Currently there is a limit of 10 provisioned users on any single
management target.

<USER> - One or more is required if the <USERS> node is included in the XML
provisioning file.

<USERID> - Required. Provides the name of the account to be created.

<PASSWORD> - Required. Provides the passwords used to authenticate against the


associated USERID.

<ENABLE> - Required, determines whether the newly created user account is


enabled for use. false = offline, true = enabled.

<ROLES> - Required, defines the roles (privileges) given to the newly created user
account. Up to 3 roles can be defined for a particular user account.

<ROLE> - Required. Currently there are only 3 acceptable values ,namely,


Administrator Role, Operator Role and Read Only Role. Administrators have full
control over the management target and its settings, operators can invoke any
operational methods like text console redirection and usb redirection.

ACTIVEDIRECTORY List:

<ACTIVEDIRECTORY> - Optional, necessary if any Active Directory support is to be


provisioned.

<ENABLESUPPORT> - Optional. If defined, the Active Directory support enablement


state will be modified, false = disabled, true = enabled.

<ACTIVEDIRECTORY_SPNACCOUNT> - Optional, necessary if any Active Directory


group(s) are to be provisioned on the management target. This is the name string of
the Active Directory user account whose SPN property has been updated to include
the target's service principal name (SPN).

<SPNACCOUNT_PASSWORD> - Optional, necessary if any Active Directory group(s)


are to be provisioned on the management target. Active Directory stored password
for the user account defined by the <ACTIVEDIRECTORY_SPNACCOUNT> node.

<ACTIVEDIRECTORY_GROUPS> - Optional, necessary if any Active Directory group(s)


are to be provisioned on the management target. Currently there is a limit of 3
provisioned groups on any single management target because a DASH Role can only
be associated to a single Active Directory group and are only 3 defined roles.

<ACTIVEDIRECTORY_GROUP> - Required, if the <ACTIVEDIRECTORY_GROUPS> node


is included in the XML provisioning file.

<GROUPNAME> - Optional, necessary if any Active Directory group(s) are to be


provisioned on the management target.

<OBJECTSID> - Required, security descriptor string in the standard string


representation (S-R-I-S-S) for the Active Directory User Group defined by the
<GROUPNAME> node.

<ROLES> - Required, defines the role(s) (privileges) given to the associated Active
Directory group. Up to 3 roles can be defined for a particular Active Directory group.
The individual DASH roles can only be associated to a single Active Directory group.
<ROLE> - Required. Currently there are only 3 acceptable values ,namely,
Administrator Role, Operator Role and Read Only Role. Administrators have full
control over the management target and its settings, Operators can invoke
operational methods.

You might also like