Release Notes
4 | P a g e
11th GENERATION SERVERS
Table 5 - VMware Version Support
MODEL
VMWARE VERSION(S)
T110, R210, T310, R310, T410
ESX Classic
R210 II, R410, R415, R510, R515, T610, R610,
M1000e, M610, T710, R710, M710, M710D, R810,
R910, M910, M915, R715, R815
ESX Classic, ESXi Embedded
С1100, С2100, С6100
ESXi Embedded
Table 6 - Feature Support
MODEL
FEATURE(S)
T110
SNMP alerts, Hardware Inventory, Blink Server LED,
View/Clear SEL logs, Warranty Info
С1100, С2100, С6100
SNMP alerts (IPMI)
R210, R210II, T310, R310, T410, R410, R415, R510,
R515, T610, R610, M1000e, M610, T710, R710,
M710, M710HD, R810 R910, M910, M915, R715,
R815
SNMP alerts, BIOS/Firmware Updates, Hardware
Inventory, Power on server, Bare Metal Deployment,
Hardware Config, Blink Server LED, View/Clear SEL
logs, Link and Launch iDRAC, Change Configuration
Settings, Warranty Info
User Notes
For customers upgrading to version 1.0.1 Update 1, after applying the update, the “Licenses in Use” field in
Administrator Portal and Management UI shows “0.” You must run an Inventory job to show the correct
number of licenses in use.
Time stamps are converted to the user’s local time zone and the Dell Management Plug-in displays
Coordinated Universal Time (UTC) time offsets.
If you run a security scanner tool (such as Nessus) against the Server Administrator Web server, certain
security warnings against port 1311 running the Server Administrator Web server may be displayed. These
warnings have been investigated by Dell engineering and are determined to be false positives.
If the proxy settings are provided in the configuration, then the proxy settings are used to access the
Repository URL provided in the Admin Portal. However, if the URL to the Update Repository is an internal
URL, then disable the proxy setting. If you do not disable the internal proxy setting, then the appliance
attempts to connect to the URL with the proxy.
A hardware profile created using a reference server with a certain BIOS version could cause deployment to
fail. Some BIOS versions do not give accurate information for certain BIOS settings, such as the Embedded
NIC1 and NIC2 settings. When a server with BIOS version is used as a reference server in a hardware profile,
the fields are ignored both by the UI and by deployment. A problem could arise, however, if the settings in
question are required to have a certain value for deployment to complete successfully.
The solution to this issue is to use a server with an up to date BIOS as a reference server for a hardware profile.
Note: Servers being used for deployment should also have an updated BIOS. If deployment tries to apply settings to a
server with a problematic BIOS, deployment fails. Currently the BIOS version is not checked for compliance, but it is
displayed on the server compliance page. Warnings are displayed on the hardware profile reference server and BIOS
settings pages, as well as when they select a deployment template with an affected hardware profile during deployment.