The Intel Unite® solution includes the following components:

Hub: The hub is an Intel® vPro system (OptiPlex 9020, 7040, or 7050 micro w/Intel vPro) that is connected to a conference room display and is intended to run without human interaction. This component will run a full-screen version of the Intel Unite® App, which will display a PIN, allow automatic incoming connections, and will allow users to securely display and collaborate.

Client: The client software will reside on the end-user’s mobile system. The application will allow users to connect to a hub, and also peer to peer. It communicates with the enterprise server and displays to the screen in the conference room (Enterprise Deployment Only)

Server: The enterprise server can be installed on a physical machine, or run as a virtual machine. This server provides the PINs, resolves the PINs, provides monitoring and alerting, and allows IT to manage the Intel Unite® deployment within their enterprise.

Plugin: This term refers to a software component that is installed on the Hub which extends the functionality of the Intel Unite® solution.

For Intel Unite® for iOS please go to:  https://itunes.apple.com/us/app/intel-unite/id1092339168

For Intel Unite® for Android please go to: https://play.google.com/store/apps/details?id=com.intel.unite

Deployment Guides:  http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11646.reference-documentsguides

The Dell Client Command Suite is the new name of our industry leading Client Systems Management tools.  These tools make Dell commercial client systems the world's most manageable client devices.

Here's how the existing tools you know and trust are included in the Dell Client Command Suite.

Check out our weekly webcast on Thursdays at 10am Central.

Easy link for this page is http://Dell.com/Command

(Please visit the site to view this video)

The new Warranty tool included in the Dell Command | Integration Suite for System Center has the following parameters

C:\Program Files (x86)\Dell\CommandIntegrationSuite>DellWarranty-CLI.exe /?

DellWarranty-CLI.exe (/I=<filename> | /Ics=<string>) [/E=<filename>] [/Ocs=<string>] [/F=<string>] [/Ps=<string>] [/Pu=<string>] [/Pd=<string>] [/V] [/W] [/H] [/U]

/H   Display usage (this information)
     (/Help)
     The parameter is optional

/U   Display usage (this information)
     (/Usage)
     The parameter is optional

/I   The full path to an input CSV file of service tags
     (/I=C:\FileName.csv)
     Required parameter, can be used with configuration manager connection string

/Ics Connection string to the Configuration Manager database
     (/Ics="Data Source=[host];Database=[Configuration Manager dbname];Integrated Security=true;")
     (/Ics="Data Source=[host];Database=[Configuration Manager dbname];User id=[username];Password=[userpwd];")
     Required parameter, can be used with input csv file

/E   The full path to a CSV export file. File will contain warranty information after CLI execution
     (Default: [ProgramData\Dell\Warranty\][WarrantyOutput_[yyyyMMddhhmmss].csv)
     (E/=C:\ExportFileName.csv)
     The parameter is optional

/Ocs Connection string to the output Warranty database. Will contain warranty information after CLI execution
     (/Ocs="Data Source=[host];Database=[dbname];Integrated Security=true;")
     The parameter is optional

/F   Filter for the Warranty API and DB
     (Default: AnyWarranty)
     (ActiveWarranty or ExpiredWarranty or WarrantyExpiringIn30Days)
     (/F=ActiveWarranty)
     The parameter is optional

/Ps  Proxy Server
     (/Ps=proxy.domain.com[:port])
     The parameter is optional

/Pu  Proxy User Name
     (/Pu=[proxy user name])
     The parameter is optional

/Pd  Proxy User Password
     (/Pd=[proxy user password])
     The parameter is optional

/V   Display additional information while executing
     (/V)
     The parameter is optional

/W   Wait for user input before terminating - best used when debugging
     (/W)
     The parameter is optional

Error: An invalid command line option (/?) was supplied

Table Notes:

1. Uses Intel PTT (Platform Trust Technology) firmware based TPM

2. Only available with Windows 7

Dell Wyse Datacenter for Citrix XenDesktop 14G RA   [direct PDF]

This RA is the recipe book for you to build a custom, flexible, on-premise VDI environment using XenDesktop/XenApp, with a choice of hypervisors (ESXi, Hyper-V, XenServer). Based on Dell EMC PowerEdge 14G servers, this solution allows you to use your existing networking and SAN infrastructure, or to use the Dell EMC ones recommended in the RA. The RA also supports high availability (HA), high-end graphics using Nvidia GRID GPUs, and recommends a series of compatible thin clients for an end-to-end solution.

TPM 1.2 versus TPM 2.0 - Cryptographic Support

The table of encryption algorithms below provides a summary; for a more comprehensive list of TPM algorithms, please reference the TCG Algorithm Registry. The list of mandatory algorithms for TPM 2.0 in a PC is defined in the latest PC Client Platform TPM Profile.

TPM 1.2 versus TPM 2.0 - Behavior Differences

TPM 1.2 supports a single "owner" authorization, with an RSA 2048b Endorsement Key (EK) for signing/attestation and a single RSA 2048b Storage Root Key (SRK) for encryption. This means a single user or entity ("owner") has control over both the signing/attestation and encryption functions of the TPM. In general, the SRK serves as the parent for any keys created in TPM 1.2. TPM 1.2 was specified as an opt-in device (see this TCG article for more information regarding the meaning of "opt-in" as it applies to TPM).

TPM 2.0 has the same functionality represented by the EK for signing/attestation and SRK for encryption as in 1.2, but the control is split into two different hierarchies in 2.0, the Endorsement Hierarchy (EH) and the Storage Hierarchy (SH). In addition to the EH and SH, TPM 2.0 also contains a Platform Hierarchy (PH) for maintenance functions, and a Null Hierarchy. Each hierarchy has its own unique "owner" for authorization. Because of this, TPM 2.0 supports 4 authorizations which would be analogous to the single TPM 1.2 "owner".  

In TPM 2.0, the new Platform Hierarchy is intended to be used by platform manufacturers. The Storage and Endorsement hierarchies, and the Null hierarchy will be used by OS's and OS-present applications. TPM 2.0 has been specified in a way that makes discovery and management less cumbersome than 1.2. TPM 2.0 has the capability to support RSA and ECC algorithms for Endorsement Keys and SRK's.

TPM 1.2 vs. 2.0 - Supported Applications and Features:

Note: * DDP | ST works on a system configured with TPM 2.0 but does not utilize the TPM 2.0 at this time.  

How is Discrete TPM 2.0 different from a firmware TPM (fTPM)?

A firmware-based TPM (fTPM) is a TPM that operates using the resources and context of a multi-function/feature compute device (such as an SoC, CPU, or other similar compute environment).

A discrete TPM is implemented as an isolated, separate function/feature chip, with all necessary compute resources contained within the discrete physical chip package. A discrete TPM has full control of dedicated internal resources (such as volatile memory, non-volatile memory, and cryptographic logic), and it is the only function accessing and utilizing those resources.

A firmware based TPM does not have its own dedicated storage.  It relies on OS and platform services to provide it access to storage within the platform.  One of the implications of not having dedicated storage involves the presence of an Endorsement Key (EK) certificate.  Discrete TPM devices can be delivered by the TPM manufacturer to the platform manufacturer with an EK certificate installed in the TPM storage for the TPM Endorsement Key.  This is not possible with a firmware TPM.  Firmware TPM vendors make certificates available to end users through manufacturer specific process.  To acquire the EK certificate for a system, platform owners need to contact the chipset/CPU vendor for that platform. 

Additionally, a TCG Certified discrete TPM is required to meet compliance and security requirements including hardening of the chip and its internal resources similar to smart cards. TCG compliance verifies the TPM correctly implements the TCG specifications. The hardening required by TCG certification allows a Certified discrete TPM to protect itself against more complicated physical attacks.

OS Support matrix:

OS Vendor Support

1. Windows 7 64bit with SP configured in UEFI + CSM boot mode can support TPM 2.0, supported on some platforms
2. Windows 8 launched with support for TPM 2.0, but only supports SHA-1
3. Requires Linux upstream kernel version 4.4 or newer. Linux distribution vendors may choose to backport support to older kernels.
4. RHEL 7.3 and later have basic kernel support. RHEL 7.4 has a tech preview of the userspace tools.
5. Supported on Ubuntu 16.04 and later.

Dell Commercial Platform OS Support

5. Dell supports TPM 2.0 with Windows 8 and 8.1 on a limited number of Tablets and Detachable PC's that support Microsoft Connected Standby.

6. TPM 2.0 support available on all Commercial platforms in Spring 2016, and the factory default TPM mode on Windows 10 is TPM 2.0.

7. TPM 1.2 is not officially support by Dell with Linux except on select IoT platforms.

8. Requires RHEL 7.3 or later. User may need to manually change the TPM mode from 1.2 to 2.0.

9. Dell has collaborated with Canonical on TPM 2.0 support on client systems that will ship with TPM 2.0. This requires that Ubuntu 16.04 ships with the system.

Dell Platform Support for TPM 2.0

Dell Command | Monitor is designed for Dell Enterprise Client systems, Dell IoT Gateway systems, as well as for Dell Embedded PCs.

With Dell Command | Monitor, system administrators can remotely manage assets, monitor system health, and inventory deployed systems in an enterprise.

NOTE: Dell Command | Monitor was formerly Dell OpenManage Client Instrumentation (OMCI). After the OMCI version 8.2.1, OMCI is rebranded as Dell Command | Monitor.

Dell Command | Monitor interfaces with leading enterprise management consoles that support industry standards. This approach helps to ensure that Dell systems can be managed by a broad array of existing enterprise management tools. It also interfaces with the Dell Integration Suite for System Center 2012, Dell KACE K1000 Management Appliance,  Dell OpenManage Essentials and our Client Management Pack for System Center Operations Manager (SCOM). Finally, tight integration with Windows Management Instrumentation (WMI) allows customers to take advantage of the rich scripting capabilities for collecting information and customizing system settings. This product is provided at no additional charge to Dell customers.

The latest version of Dell Command | Monitor is v9.3.

 Downloads

• Dell Command | Monitor 9.3 for Windows  (Released - 08/03/2017)
  
  • 32-bit
  • 64-bit
Dell Command Monitor 9.3 for Linux 
• Ubuntu Desktop 16.04 64-bit      (Released - 08/03/2017)
• RHEL 7.0 64-bit                          (Released - 08/03/2017)
• RHEL 6.0 64-bit                          (Released - 08/03/2017)

• Dell Command | Monitor Documentation

(Please visit the site to view this video)

(Please visit the site to view this video)

Dell Command | Monitor Quick Links

Enhancements included in the latest release

New Bios Settings introduced in DCIM_BIOSEnumeration Class:

MAC Address Pass Through
AMD Turbo Core Technology
AMD Simultaneous Multithreading Technology
AMD-V Technology
AMD-Vi Technology
Rear USB 3.0 Ports
AMD CPU Core Configuration
Front USB Port Collection
Early Beep
Early Display
Early Keyboard Backlight
Mini SAS 0
Mini SAS 1
Mini SAS 2
Mini SAS 3
VMD technology
Rugged Desk Dock NIC PXE
Computrace
Serial ATA Drive 8
PCIe LinkSpeed
Allow BIOS Downgrade
Limit system memory to less than 1 TB
Tablet Button Illumination
Trusted Platform Module Clear

Installing Dell Command | Monitor

Installing Dell Command | Monitor manually is pretty simple. Just download the latest version (links above) and install with administrative rights. 

To perform an unattended installation to be used with your favorite software distribution tool, perform the following steps:

1. Download the latest version of Dell Command | Monitor  (links above).
2. Launch the executable with the following parameters:

Systems-Management_Application_240JD_WN32_9.2.0.135_A00-00.EXE /s

Previous Releases

Download Dell Command | Monitor v9.1 for Windows 32-bit         (released 07/29/2015)

Download Dell Command | Monitor v9.1 for Windows 64-bit         (released 07/29/2015)

Dell Command | Monitor v9.1 Documentation

Sample Scripts

Check if a BIOS password is set

NOTE: Dell Command | Configure 4.0 or later requires platforms supporting WMI-ACPI BIOS. The complete functionalities of Dell Command | Configure is available for the supported platforms, refer the Supported Platforms for more information.

For the limited functionalities on non WMI-ACPI complaint platforms, see Windows SMM Security Mitigations Table Compliance section in Dell Command | Configure User's guide.

Overview

Dell Command | Configure is a packaged software application that provides configuration capability to business client platforms.

This product consists of a Command Line Interface (CLI) and Graphical User Interface (GUI) to configure various BIOS features. Dell Command | Configure supports following Windows and Linux operating systems: Windows 7, Windows 8, Windows 8.1, and Windows 10, Windows Pre-installation Environment (Windows PE), Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Ubuntu Desktop 16.04.

This is the 4.0 version of Dell Command | Configure.

Downloads

• Windows download  (Released - 12/19/2017)                           Error Codes
• Documentation

Fixes in the Release 

Not applicable

New in the Release

• Support for new platforms.
• Support for following new BIOS features/attributes:
  • --blocksid
  • --ppibypassforblocksid
  • --vmdpcieslot
  • --vmdnvmepcie0
  • --vmdnvmepcie1
  • --vmdnvmepcie0cpu1
  • --vmdnvmepcie1cpu1
  • --tpmppiclearoverride
  • --sata8
  • --emmcdevice
  • --speedshift
  • --reportlogotype
  • --dashsupport
  • --smmsecuritymitigation
• Support for WSMT Compliance. For more information about WSMT compliance, see Windows Security Mitigations Table (WSMT) Compliance section in Dell Command | Configure User's guide.

Known Issues

Issue: The exported SCE (.sh) file does not run on Linux, and displays the error message that "Improper version of OS used".

Description: The SCE (.sh) file exported using Dell Command | Configure GUI does not run on the systems running the following operating systems: RHEL 6.8, RHEL 7.3 & Ubuntu Desktop 14.04.

Resolution: Add the OS version of the target system by manually editing the exported .sh file.

Examples: 

For the systems running Ubuntu Desktop 14.04, edit the .sh file as highlighted below.

For the systems runningRHEL 7.3, edit the .sh file by as highlighted below.

Previous Releases

Dell Command | Configure 3.3

• Windows download  (Released - 08/03/2017)     
  
• Linux downloads       (Released - 07/21/2017)                     
  • RHEL6 64 bit
  • RHEL7 64 bit
  • Ubuntu Desktop 16.04 64 bit
• Documentation

Dell Command | Configure 3.2

• Windows download  (Released - 01/30/2017) 
• Linux downloads       (Released - 02/02/2017)                       
  • RHEL6 64 bit                                                                  
  • RHEL7 64 bit
  • Ubuntu Desktop 16.04 64 bit
• Documentation 

Dell Command | Configure 3.1.2

• Windows download
• Linux downloads
  • Ubuntu Desktop 16.04 64 bit
    
• Documentation

Dell Command | Configure 3.1

• Windows download  
• Linux downloads
  • RHEL6 64 bit
  • RHEL7 64 bit
• Documentation

Dell Command | Configure 3.0

• Windows download  
• Linux downloads
  • RHEL6 64 bit  
  • RHEL7 64 bit  
• Documentation

Whitepapers/Technical Documents

• Configuring Remote Wake-Up using Dell Client Command Suite
• Configuring Dell Business Client Systems using Dell Command | Configure
• Securing Dell Commercial Client Systems with Trusted Platform Module (TPM) using Dell
  Client Command Suite

Video

1. Activating the TPM with Dell Command | Configure

(Please visit the site to view this video)

2. Setting the BIOS defaults using Dell Command | Configure

 (Please visit the site to view this video)

0. Success.
1. Attempt to read write-only parameter '%s'.
2. Password cannot exceed 16 characters.
3. A BMC was either not detected or is not supported.
4. This username is already in use. Enter a unique username.
5. Access mode not supported.
6. Cannot return number of requested data bytes.
7. User ID 1 cannot be assigned a username.
8. Cannot execute duplicated request.
9. There was an error clearing the SEL.
10. Clear SEL cannot be accompanied with any other option.
11. racreset cannot be accompanied with any other option.
12. Cannot execute command '%s'. Command, or request parameter(s), not supported in present state.
13. Command not supported on given channel.
14. The community string may only contain printable ASCII characters.
15. Destination unavailable. Cannot deliver request to selected destination.
16. Cannot execute command. Insufficient privilege level.
17. Command illegal for specified sensor or record type.
18. Invalid commstring value.
19. Hardware subsystem error. Invalid data field in Request.
20. Invalid destination IP address.
21. The GUID is invalid.
22. Invalid gateway.
23. Invalid hostname.
24. Invalid IP address.
25. Invalid DNS IP address.
26. Invalid sub net mask.
27. Invalid value for PEF. PEF value should be between 1 and 16.
28. Reservation Canceled or Invalid Reservation ID.
29. Invalid Time to live value.
30. Invalid VLANID value.
31. Invalid Command. Used to indicate an unrecognized or unsupported command.
32. Command invalid for given LUN.
33. Load defaults cannot be accompanied with any other option.
34. There was an error loading the defaults.
35. Node Busy. Command could not be processed because command processing resources are temporarily unavailable.
36. Out of space. Command could not be completed because of a lack of storage space required to execute the given command operation.
37. This parameter is not supported.
38. Parameter out of range. One or more parameters in the data field of the Request are out of range.
39. The password may only contain printable ASCII characters.
40. Password test failed.
41. Requested data length invalid.
42. Requested data field length limit exceeded.
43. Requested Sensor, data, or record not present.
44. Request data truncated.
45. Command response could not be provided.
46. Command response could not be provided. BMC initialization or initialization agent in progress.
47. Command response could not be provided. Device in firmware update mode.
48. Command response could not be provided. SDR Repository in update mode.
49. Cannot execute command, SEL erase in progress.
50. Attempt to set the 'set in progress' value when not in the 'set in complete' state.
51. The SOL character 'accumulate interval' is invalid.
52. The SOL character 'send threshold' is invalid.
53. The SOL 'retry interval' is invalid.
54. Command completed successfully.
55. Timeout while processing command. Response unavailable.
56. Unspecified error.
57. The password may only contain printable ASCII characters.
58. Username cannot exceed 16 characters.
59. Invalid VLANID value. Enter in 'dddd' format.
60. Attempt to write read-only parameter '%s'.
61. BMC is busy.
62. Response data did not return successfully.
63. BMC time out error.
64. Invalid Configuration Option.
65. Cannot execute command.Parameter is illegal because command sub-function has been disabled or is unavailable.
66. Option '%s' requires an argument.
67. The asset tag for this system is not available.
68. The asset tag cannot be more than %s characters long.
69. The required BIOS interfaces cannot be found on this system.
70. The BIOS version information is not available.
71. There is not enough free system memory to complete the BIOS update.
72. The BIOS update file version is a different version class (A00, X00) than the current system BIOS. Use the --force option to use this BIOS image.
73. The BIOS update file version is older than the current system bios. Use the --force option to use this BIOS image.
74. The BIOS update file version is identical to the current system bios. Use the --force option to use this BIOS image.
75. The sequence list must be a comma-separated numerical list of valid unique boot device numbers (ex: 2, 1, 3).
76. The sequence list must be a comma-separated list of valid unique device names (ex: nic.emb.1, hdd.emb.1) or a comma-separated numerical list of valid unique boot device numbers (ex: 2, 1, 3).
77. There was an error setting the sequence.
78. The list is not formatted correctly. See the help for more details.
79. The size of returned buffer is larger than the size of allocated buffer.
80. There was a problem getting the state byte.
81. The state byte is not available on this system.
82. There was a problem setting the state byte.
83. The state byte must be a value between 0 and 255 decimal.
84. The CPU information is not available.
85. The dependent option '%s' required for this subcommand is missing in the command line.
86. Duplicate sub command '%s' has been entered.
87. The script file does contain not a valid DTK environment script signature. (%s)
88. The format of the environment variable is incorrect.
89. The --envar/-s option can only be used for a single option.
90. The --envar/-s option can only be used for report operations.
91. The individual sub commands should be specified for the -s option.
92. Getting external serial connector settings failed.
93. Setting external serial connector settings failed.
94. There was an error opening the file %s.
95. File '%s' does not have write permission.
96. The file contains invalid option '%s'.
97. The replication information does not match for this system.
98. There can only be one section in the input file.
99. Bad ini file, the required section [%s] cannot be found.
100. The format of the bios image file is incorrect.
101. Report operations and set operations must be separate.
102. Help is not available for the option '%s'.
103. The -x (--hex) option can only be used with -b or -r.
104. Input file '%s' not found.
105. Input file '%s' cannot be read.
106. Invalid argument for the provided option '%s'.
107. Function table lookup error.
108. The machine ID was not found in the file '%s'.
109. The system memory information is not available.
110. Mode can only be used with the --pci option.
111. The device name or index must be present in the boot order.
112. The output file '%s' could not be opened. Please make sure the path exists and the media is not write protected.
113. Could not write to output file, disk may be full.
114. The old password must be provided to set a new password using --valsyspwd.
115. The old password must be provided to set a new password using --valsetuppwd.
116. The current password can only be provided when setting a new password.
117. Actions are not allowed for this filter. Only alerts are allowed.
118. There was an error getting the option '%s'.
119. The option '%s' is not available or cannot be configured through this tool.
120. There was an error setting the option '%s'.
121. The -n (--namefile) option can only be used with --pci.
122. The password may only contain alphanumeric characters.
123. The BIOS passwords have been disabled via jumper.
124. The password length must be between 1 and 32.
125. This password is locked and can only be unlocked by the admin user.
126. There was an error setting the password.
127. The LCD string length must be between 1 and the maximum value %s.
128. The LCD string may only contain alphanumeric characters.
129. There was an error setting the LCD string.
130. The second channel can only be set if the RAID controller is set to RAID.
131. The set operation, '%s', requires sub commands.
132. The service tag for this system is not available.
133. The system ID value is not available.
134. The system information string is not available.
135. A system error has occured.
136. Usage error.
137. The uuid information is not present on this system.
138. The manufacturing/first-power-on date information is not present on this system.
139. Version cannot be accompanied with any other option.
140. The self-identify blinker timer should be set to 0..255 second(s).
141. Encrypt key is too long.
142. Encrypt key is invalid, accepted characters are 0 to 9 or A to F.
143. Parameter has been temporarily disabled due to a dependancy on other settings.
144. The old password provided is incorrect. The new password will not be set. Please try again.
145. Cannot start /etc/omreg.cfg file. Please ensure /etc/omreg.cfg file is present and is valid for your environment. You can copy this file from the DTK iso.
146. Getting nicselection settings failed.
147. HAPI Driver Load Error.
148. Filter action power reduction is only supported for the system power warn/fail filters.
149. TPM Clear settings requires setup password.
150. There is currently no TPM Clear request pending.
151. Password is not required for retrieving the TPM options.
152. Setup password is required for setting the TPM options.
153. Invalid Password override.
154. Invalid TPM set option.
155. There was an error setting the TPM option.
156. There is no setup password installed on this system.
157. The setup password provided is incorrect. Please try again.
158. Profile should be custom for setting cpupowermode, memorypowermode and fanmode.
159. There was an error setting the Power Option.
160. The power cap value entered is out of range. Please try again.
161. The power cap value entered must be between 0 to 100 if unit is percent.
162. Invalid IPv6 address. The IPv6 address cannot be link-local or multicast.
163. Invalid IPv6 address. The IPv6 address specified has incorrect address format.
164. Invalid IPv6 address. The gateway address specified has incorrect address format.
165. Invalid IPv6 address. The Primary DNS server address specified has incorrect address format.
166. Invalid IPv6 address. The Secondary DNS server address specified has incorrect address format.
167. Invalid IPv6 address. The gateway address specified is invalid.
168. Invalid configuration. Attempting to apply IPv6 configuration on a non supported platform.
169. Invalid IPv6 configuration. Attempt to set DNS server address manually while DNS address source is set to auto.
170. Invalid IPv6 configuration. Attempt to set IPv6 address manually while IPv6 address source is set to auto.
171. Invalid IPv6 configuration. Attempting to apply IPv6 configuration without loading IPv6 stack.
172. Invalid IPv4 configuration. Attempting to apply IPv4 configuration with IPv4 disabled.
173. Invalid IPv6 configuration. Ipv6 address cannot be specified without specifying prefix-length.
174. Invalid IPv6 configuration. dnssrcv6 cannot be set to auto when ipsrcv6 is set to manual.
175. Error while executing IPMI Set command.
176. Error while executing IPMI Get command.
177. Error during Trap Alert.
178. Unspecified error.
179. Unsupported device. Re-try with supported device
180. Setup password is installed. Re-try providing setup/admin password
181. System password is required. Re-try providing system password
182. The password provided is incorrect. Please try again.
183. Password verification failed.
184. Password not changed, new password does not meet criteria.
185. Password not installed in the system.
186. Password is DISABLED by jumper.
187. Error in Validation.
188. Error in Setting the Value.
189. The password length should not exceed the maximum value %s.
190. This is not a Dell machine. DCC supports only Dell machines.
191. Setup Password is required to change the setting. Use --valsetuppwd to provide password.
192. System Password is required to change the setting. Use --valsyspwd to provide password.
193. Password is not Installed. so use only --setuppwd
194. Password is not Installed. so use only --syspwd
195. The system password provided is incorrect. Please try again.
196. The Sequence list must be a comma-separated list of valid unique device names (ex: hdd,cdrom).
197. The system revision information is not available for this system.
198. The completion code information is not available for this system.
199. The BIOS characteristics information is not available for this system.
200. The password should not contain special characters. Password characters are limited to alphanumeric (A-Z, a-z, 0-9).
201. Please use 64-bit version of this application.
202. %s cannot be modified when TPM is OFF.
203. System password cannot be set when pwdlock option is in locked state (pwdlock=lock).
204. adddevice option not supported by this machine's BIOS
205. usb device already present in this machine.
206. Unable to get information from BIOS.
207. %s - Error : Unable to store BIOS information.
208. Duplicate entry found in the input list : %s , Operation Aborted.
209. Typo found in the input list : %s , Operation Aborted.
210. Asset tag can have only printable ASCII characters.
211. Multiple inputs will not be accepted.
212. Invalid Hex format.
213. Hex value range should be 0x0 to 0xffff.
214. %s - Only positive numeric values are acceptable.
215. %s - Length cannot exceed two characters.
216. Range for autoon hour value should be 0 to 23(24 hour format).
217. Range for autoon minute value should be 0 to 59.
218. This option Not supported on UEFI Bios.
219. Unable to Set Bootorder.
220. Invalid Arguments. Unable to Set Bootorder.
221. The provided command %s should not combine with other suboptions.
222. The property ownership tag for this system is not available.
223. The property ownership tag cannot be more than 80 characters for non portable machines.
224. The property ownership tag is limited to 48 characters for portable systems.
225. Property ownership tag can have only printable ASCII characters.
226. Error in Setting the Value. Note : In some machines, If Hdd password or System password is set, you can't set Setup password.
227. 'admin/root' privileges required to execute this application.
228. The option related BIOS information is not available in this machine.
229. Improper Output from Bios. Please try again.
230. ;Error in Bootorder.
231. The manufacturing/first-power-on date information is not present on this system.
232. Not Applicable.
233. ;Uefi bootlisttype is not supported in this Machine.
234. ;Error in Bootorder.
235. Unable to get information specific to machine.
236. The input file is invalid.
237. No Status Present.
238. File Do not have configurable Options.
239. Please provide the days to enable.
240. Password is not Installed. Please try again without providing --val%s
241. Please provide the old password to set the new password using --valownerpwd.
242. The owner password is incorrect. Please try again.
243. Error in setting the value. Note : Setup or system password might be set on the system. Clear the password(s) and try again.
244. Owner password is not supported in file operations.
245. Password operation is not supported on the system.
246. The owner of the system has enabled the Owner Access feature. To set the Bios configuration, create setup or system password.
247. Either the system hardware or the BIOS version does not support the option. To resolve the BIOS version issue, upgrade the BIOS to the latest version.
248. Unable to get password information.
249. Please provide the start and stop values. Example: custom:start-end.
250. The start and stop values should be in the range '%s'.
251. The stop value should be greater than the start value by 5 percentage.
252. The option '%s' is not supported in this machine.
253. Unable to set '%s'. Note: To set this Option Legacy Option rom(legacyorom) should be enable and secureboot should be disable.
254. Unable to set '%s'. Note: To set this Option bootmode(activebootlist) should be uefi and legacy option rom (legacyorom) should be disable.
255. Unable to set '%s'. Note: To enable this Option secureboot should be disable. To disable this Option secureboot should be disable and bootmode(activebootlist) should be uefi.
256. The allowed value for the option in the system are in between %s.
257. The option '%s' is not enabled.
258. Invalid argument! The possible values are: 0, 1-15, and 255.
259. Invalid argument. The arguments must be set in such a way that [Start time] less than or equal [End time] less than or equal [Charge Start time].
260. Unable to set the Non critical Threshold values.
261. Cannot set the passed value as it is not within the range. The value should be less than or equal to 'Upper Threshold Critical' and greater than or equal to 'Minimum value'
262. Error in Setting the Value. Note: To set TPM - 1. Admin Password must be set , 2. TPM must not be owned and 3. TPM must be deactivated.
263. Invalid format! Enter the value in the 'R,G,B' format.
264. Invalid value! Expected values are 'white', 'red', 'green', 'blue', 'customcolor1', 'customcolor2' and 'none'
265. Invalid value! Expected values are 'white', 'red', 'green', 'blue', 'customcolor1' and 'customcolor2'
266. Invalid format! Enter only one value.
267. Invalid format! No other value is allowed with 'none'
268. Invalid format! Duplicate entry found in the input list:'%s'
269. Invalid operation! Set operation for '%s' attribute is not allowed using file mode
270. Invalid format! String for '%s' attribute should contain maximum 4 characters. Supported characters are 0-9, A-F and a-f.
271. Invalid format! String for '%s' attribute should contain maximum 8 characters. Supported characters are 0-9, A-F and a-f.
272. Invalid set operation! '%s' attribute is read-only attribute.
273. The allowed possible values are %s.
274. The option '%s' is not disabled.
275. This system does not have a WMI-ACPI compliant BIOS. Update the BIOS with a compatible version, if available.
276. Couldn't get WMI-ACPI Buffer Size!!
277. Unable to get BIOS tables or Unknown type encountered!!.
278. The dependent file is not loaded from the appropriate path, repair or reinstall to fix the issue.

Note - Dell Command | PowerShell Provider 1.2 release has updated the names of attributes and possible values used in 1.1 and 1.0 releases.  To see the complete list please click Reference list for updated names of attributes and possible values link.

Overview

Dell Command | PowerShell Provider is a PowerShell module that provides BIOS configuration capability to Dell client Enterprise systems such as OptiPlex, Latitude, Venue 11 Pro, XPS Notebook, and Precision using Windows PowerShell Interface.

Dell Command | PowerShell Provider can be installed as plug-in software registered within Windows PowerShell environment. Dell Command | PowerShell Provider works for local and remote systems, and even in Windows pre-installation environment. This module, with its native configuration capability, makes BIOS configuration most manageable for system administrators.

Dell Command | PowerShell Provider can be used on Windows 7, Windows 8, Windows 8.1, Windows 10 and Windows Pre-installation Environment (Windows PE 4.0 onwards) operating systems.

This is the 1.3 version of Dell Command | PowerShell Provider. 

 Desired State Configuration Whitepaper

Downloads

Dell Command | PowerShell Provider module is available at PowerShell Gallery. To install the module from PowerShell Gallery, refer to PowerShell Gallery.  

Alternatively, Dell Command | PowerShell Provider is also available at Dell Support site for Download.

Download Dell Command | PowerShell Provider v1.2

(Released - 01/06/2017)

What's new 

1.3

• Support for Kaby lake platforms (Aspen, Kirkwood 13; pre-enabled support for Kona B  Kona S, Matira 3,5,7 , Steamboat13, LVST2 )

• Support for new BIOS features

• Support for WIN 10 Redstone 2

1.2

• Desired State Configuration (DSC) support
• New Platforms support
• Updated attribute names and Possible values. To see the complete list please click Reference list for updated names of attributes and possible values link
• Support for displaying platform-specific possible values for the attributes in PossibleValues property
• Support for new property: UnSupportedPossibleValuesfor showing additional possible values for the attribute that are not supported on current platform
• Support for displaying the meaningful attribute names that are similar to BIOS setup screen names, in a ShortDescription column
• Support for new BIOS attributes. To see the complete list of new BIOS attributes please refer What's new section is user guide. To download the user guide, click Dell Command | PowerShell Provider Documentation link in the Downloads section.

Fixes 

• Value of KeyboardIllumination can be set as 'Bright' (100%).
• MemoryTechnology attribute is now shown on the platforms with the latest technology such as DDR4, LPDDR, etc.
• HTCapable attribute displays the accurate information

Known Issues

Issue: Windows 7 may not recognize the digital signature validity.

Description: If the system is not connected to internet, Windows 7 does not recognize the digital signature validity of psd1 files.

Resolution: Connect the system to internet or manually install the certificate and validate the digital signature. 

Installation and Configuration

To know about installing and configuring Dell Command | PowerShell Provider module in your system, refer Download and Installation section in user guide. To download the user guide, click Dell Command | PowerShell Provider Documentation link in the Downloadssection.

Whitepapers/Technical Documents 

• Desired State Configuration for Dell Command | PowerShell Provider
• Configuring Remote Wake-Up using Dell Client Command Suite
• Securing Dell Commercial Client Systems with Trusted Platform Module (TPM) using Dell Client Command Suite

Articles/Blogs 

• Dell Command | PowerShell Provider Advanced Battery Charge feature
• Dell Command | PowerShell Provider Auto On feature
• Dell Command | PowerShell Provider BIOS Passwords feature
• Dell Command | PowerShell Provider HDD Password feature
• Dell Command | PowerShell Provider Peak Shift feature
• Dell Command | PowerShell Provider Secure Password feature
• Dell Command | PowerShell Provider Wake On LAN/WLAN feature

Videos

Changing boot sequence using Dell Command | PowerShell Provider

(Please visit the site to view this video) 

Previous Releases

Dell Command | PowerShell Provider 1.3  (Released - 08/09/2016)

• PowerShell Gallery Downloads 
  • 64-bit Dell Command | PowerShell Provider v1.3
  • 32-bit Dell Command | PowerShell Provider v1.3

• Dell Support Site Downloads
  • Dell Command | PowerShell Provider v1.3
  • Documentation

Dell Command | PowerShell Provider 1.2  (Released - 08/09/2016)

• PowerShell Gallery Downloads 
  • 64-bit Dell Command | PowerShell Provider v1.2
  • 32-bit Dell Command | PowerShell Provider v1.2

• Dell Support Site Downloads
  • Dell Command | PowerShell Provider v1.2
  • Documentation

Dell Command | PowerShell Provider 1.1  (Released - 08/09/2016)

• PowerShell Gallery Downloads 
  • 64-bit Dell Command | PowerShell Provider v1.1
  • 32-bit Dell Command | PowerShell Provider v1.1
• Dell Support Site Downloads
  • Dell Command | PowerShell Provider v1.1
  • Documentation

Dell Command | PowerShell Provider 1.0  (Released - 10/26/2015)

• PowerShell Gallery Downloads 
  • 64-bit Dell Command | PowerShell Provider v1.0
  • 32-bit Dell Command | PowerShell Provider v1.0
• Dell Support Site Downloads
  • Dell Command | PowerShell Provider v1.0
  • Documentation

 DOWNLOAD v1.0.0.10 (released April 20, 2017) Release Notes

1. Documentation
2. Helpdesk

The driver packs on this page work with ImageAssist, KACE, MDT& SCCM deployments.  They are consolidated, combining models by generation rather than being model specific.  These packs are developed and sustained by Dell's Global Configuration Services group.  For support, please post comments directly to this page.

Drivers used during the development process have been tested and qualified by our Dell Product Group for both platform and factory integration.  There are times when newer drivers are provided by vendors, but in order to get these drivers to customers more quickly they are validated and posted online to support.dell.com.  (where Dell Command Update pulls from) These updated drivers if deemed required or critical will be tested, validated and integrated into the factory process during a future release.  Hence, there may be a delta between when a driver is ‘web-posted’ to support.dell.com and when it gets added to the relevant driver package.

Turn on page notifications for updates. (bottom right - requires logging in.)

• Windows 7 Drivers
• Windows 8.1 Drivers
• Windows 10 Drivers
  
• WinPE CABs

 NOTE: Windows 10 32-bit is not supported with ImageAssist.

If looking for model specific driver packs, go to Command | Deploy Driver Packs for Enterprise Client OS Deployment.