Are the latest firmware versions for DRAC 8, 7 and 6 compatible with Java 8? Specifically the virtual console functionality?

iDRAC8 - 2.10.10.10

iDRAC7 - 1.66.65

iDRAC6 -  1.98

Oracle has announced that Java 7 is now EOL.

Hi!

I have 4 servers DELL PowerEdge R710 with CentOS 7, iDRAC and Openmanage Server Administrator 7.4.1

On the 1 and 2 server iDRAC shows me, than storage battery state is OK, but OMSA shows "Battery on Controller PERC 6/i Integrated: State Failed"

# omreport storage battery

List of Batteries in the System

Controller PERC 6/i Integrated (Slot Embedded)
ID                  : 0
Status              : Ok
Name                : Battery 0
State               : Ready
Recharge Count      : Not Applicable
Max Recharge Count  : Not Applicable
Learn State         : Idle
Next Learn Time     : 81 days 4 hours
Maximum Learn Delay : 7 days 0 hours
Learn Mode          : Auto

And in the 3 and 4 servers iDRAC thinks than storage battery state is OK, OMSA thinks than "Battery on Controller PERC 6/i Integrated: State Failed" and omreport thinks than battery status is critical.

omreport storage battery
List of Batteries in the System

Controller PERC 6/i Integrated (Slot Embedded)
ID                  : 0
Status              : Critical
Name                : Battery 0
State               : Failed
Recharge Count      : Not Applicable
Max Recharge Count  : Not Applicable
Learn State         : Idle
Next Learn Time     : 58 days 2 hours
Maximum Learn Delay : 7 days 0 hours
Learn Mode          : Auto

I don't understand what happend with storage battery. Is it OK or not?

I will be really appreciate any help. 

Hello,

So I have upgraded 91 servers from OMSA 7.3, 7.4 or 8.0.1 to 8.1 without any glitch.

But I have one R720xd server with a strange issue. Right after the 8.1 upgrade, I started receiving alerts from our monitoring software:

Problem running 'omreport chassis memory': Error: Memory object not found
Problem running 'omreport chassis fans': Error! No fan probes found on this system.
Problem running 'omreport chassis temps': Error! No temperature probes found on this system.
Problem running 'omreport chassis volts': Error! No voltage probes found on this system.
Chassis Service Tag is empty

When I log in OMSA 8.1, I don't get any info for the server except for the PERC.

I tried a DRAC reset, a roll back to 7.4, a DRAC firmware update (2.10.10), a BIOS update (2.5.2) and server was rebooted several times without any success. I can't deploy any in-band package as I get "Inventory failure: internal error: get inventory from LCL failure".

Server is running Win 2008 R2 Enterprise.

Anyone has an idea before I call support?

JP

Hello,

Dell Server Update Utility (SUU) v 15.04.00 is now available for download.

SUU carries updates only for Dell’s 10th generation to Dell’s 13th generation of PowerEdge servers. This release brings in the following enhancements and features: 

 Support for the following Dell PowerEdge servers:

• Dell’s 13th generation PowerEdge servers. The platforms supported are:
  • M630
  • M630P
  • R430
  • R530
  • T430
  • FC630
  • C4130
•  Platform support for Dell’s 12th generation PowerEdge server:
  • FM120

 New Operating System Support:

• SUSE Linux Enterprise Server 12
• Citrix XenServer 6.5

 Features:

• SUU 64 – bit support is available for all 64 – bit operating systems on Dell’s 12th generation and 13th generation PowerEdge servers (only for BIOS and Firmware updates).
• SUU support is available for Dell OpenManage Server Administrator 8.1 on Dell’s 10th generation PowerEdge servers and later generations.
• Latest update support for BIOS, Firmware and Drives.
• Latest update support for iDRAC 2.10.10.10 for 10th generation PowerEdge servers and later generations.
• Added support for the latest Network Interface Cards (NICs), Converged Network Adapters (CNAs).

Deprecated support for the following operating system:

• ESX 4.1 U3
• Citrix XenServer 6.2

To know more and download details, please refer the following Dell Support site:http://www.dell.com/support/home/us/en/04/product-support/product/dell-suu-v15.04/research#./manuals?&_suid=1429677977935037374197584484936

Direct Download Link:

For x32Bit SUU 15.04.00 {10G to 13G System support}-

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=HW7TW

 For x64Bit SUU 15.04.00 {12G to 13G System support}-

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=7J0JY

 Please continue posting your feedback on the forum.

-Change Management Team

Hi,

I've asked to evaluate OpenManager and I have a couple of basic questions. 

1. What I've asked to do is to create a VMWare instance running CentOS.  Is that viable is does the server have to be a Dell PowerEdge server?  Also, can a virtual CentOS server host the tool?
2. We have mostly Dell servers in our colo's and at customer sites, but we are not exclusively Dell?  Is it possible to use OpenManager against on Dell hardware?
3. Is there a client component that needs to be installed on the remote systems?  If so, can the client OS be CentOS?

Thanks,
Rob Tanner
Peak Hosting

Why does the the lifecycle controller require use of LOM ports rather than using the DRAC Dedicated NIC when Enterprise is available?

Some servers are in non publicly accessible networks so firmware updates via ftp.dell.com are not possible. DRAC is usually in OOB and always can reach ftp.dell.com

Are there plans to allow the LC to use the DRAC dedicated NIC for network access?

Where can I download the iDRAC7 30-day trial license file?

I don't want to use the installer that I need to burn to CD. I have access to the DRAC GUI with a temp CAT connection to LOM1 and want to just upload the temp license file to get the dedicated NIC working. I will then move my CAT to dedicated NIC and upload the perpetual license when I have it.

We usually update our iDRAC firmware using racadm commands when SSH'd into the DRAC allowing the update to pull the firming file from our tftp server.

Since the new version is DRAC and LC combined am I still able to do this or do I have to run the .BIN file from the OS?

Hi All,

Just setup new dell PowerEdge R320. Configured PERC H310 RAID 1 but the 2 hard disks status are 'non-critical'.

Any idea why?

Thanks

Good Morning,

Customer has a growing estate of 12G servers, and make good use of the iDRAC

They are implementing 13G servers - new iDRAC look and feel :-) - Very slick

Can we upgrade the 12G iDRAC's to the (13G) code - so that the estate has a standard look and feel?

I seem to remember seeing a iDRAC Web Session where they said you could..

New servers, firmware is current.  Server Administrator 8.1 opens fine, doesn't show storage (H730 Mini controllers).  Downgraded to version 7.4 to test, controllers still won't show in storage.  Everything else is showing in OMSA fine, just not the RAID controller.

Anyone else seen this/have a fix?  I've read through a few pages already without finding somethign similar.

Hi,

I have installed a new Dell R720 on a remote location and need to configure automatic email alerts generated by OMSA to me.

Since the server is remotely monitored so auto email alerts (Google Apps account will be entered) need to be setup on priority.

How can i achieve this using Windows 2012 Standard Edition

Hello,

I like the fact that most racadm subcommands can be used via SSH as this makes scripting easier when no racadm tool needs to be distributed. Looking in the documentation I also see that sslcsrgen is supported via SSH interface, and it also seems to do anything.

However I have no idea how to get the CSR message. (It could be printed to the output but it is not). With a remote racadm command the sslcsrgen safes to a local file. But I guess otherwise it is stored somewhere in the iDRAC - how can I access it?

I reallly like the 

Hi

all of our centos 6 (x64) servers are failing yum updates, I am assuming this is to do with open manager v8

error:

--> Processing Dependency: libdchapi.so.7()(64bit) for package: dell_ie_backplane-1.0.0-4.135.2.el6.x86_64
--> Processing Dependency: libdchapi.so.7()(64bit) for package: dell_ie_pcissd-1.0.0-4.107.2.el6.x86_64
--> Processing Dependency: libdchapi.so.7()(64bit) for package: dell_ie_nvme_pcissd-1.0.0-4.122.2.el6.x86_64
--> Processing Dependency: libdchbas.so.7()(64bit) for package: dell_ie_bios-3.1.0-4.105.2.el6.x86_64
--> Processing Dependency: libdchbas.so.7()(64bit) for package: dell_ie_backplane-1.0.0-4.135.2.el6.x86_64
--> Processing Dependency: libdchbas.so.7()(64bit) for package: dell_ie_pcissd-1.0.0-4.107.2.el6.x86_64
--> Processing Dependency: libdchbas.so.7()(64bit) for package: dell_ie_nvme_pcissd-1.0.0-4.122.2.el6.x86_64
--> Processing Dependency: libdchipm.so.7()(64bit) for package: libsmal0-3.1.0-4.132.1.el6.x86_64
---> Package srvadmin-hapi.x86_64 0:8.1.0-4.10.2.el6 will be an update
---> Package srvadmin-idrac.x86_64 0:7.4.0-4.12.6.el6 will be updated
---> Package srvadmin-idrac.x86_64 0:8.1.0-4.4.7.el6 will be an update
---> Package srvadmin-idrac-ivmcli.x86_64 0:7.4.0-4.5.3.el6 will be updated
---> Package srvadmin-idrac-ivmcli.x86_64 0:8.1.0-4.6.3.el6 will be an update
---> Package srvadmin-idrac-snmp.x86_64 0:7.4.0-4.12.6.el6 will be updated
---> Package srvadmin-idrac-snmp.x86_64 0:8.1.0-4.4.7.el6 will be an update
---> Package srvadmin-idrac-vmcli.x86_64 0:7.4.0-4.10.1.el6 will be updated
---> Package srvadmin-idrac-vmcli.x86_64 0:8.1.0-4.5.1.el6 will be an update
---> Package srvadmin-idracadm.x86_64 0:7.4.0-4.12.6.el6 will be updated
---> Package srvadmin-idracadm.x86_64 0:8.1.0-4.4.7.el6 will be an update
---> Package srvadmin-isvc.x86_64 0:7.4.0-4.42.2.el6 will be updated
---> Package srvadmin-isvc.x86_64 0:8.1.0-4.38.1.el6 will be an update
---> Package srvadmin-isvc-snmp.x86_64 0:7.4.0-4.42.2.el6 will be updated
---> Package srvadmin-isvc-snmp.x86_64 0:8.1.0-4.38.1.el6 will be an update
---> Package srvadmin-itunnelprovider.x86_64 0:7.4.0-4.14.1.el6 will be updated
---> Package srvadmin-itunnelprovider.x86_64 0:8.1.0-4.27.1.el6 will be an update
---> Package srvadmin-jre.x86_64 0:7.4.0-4.98.1.el6 will be updated
---> Package srvadmin-jre.x86_64 0:8.1.0-4.94.1.el6 will be an update
---> Package srvadmin-nvme.x86_64 0:7.4.0-4.178.1.el6 will be updated
---> Package srvadmin-nvme.x86_64 0:8.1.0-4.139.1.el6 will be an update
---> Package srvadmin-omacore.x86_64 0:7.4.0-4.97.1.el6 will be updated
---> Package srvadmin-omacore.x86_64 0:8.1.0-4.94.3.el6 will be an update
---> Package srvadmin-omacs.x86_64 0:7.4.0-4.97.1.el6 will be updated
---> Package srvadmin-omacs.x86_64 0:8.1.0-4.92.1.el6 will be an update
---> Package srvadmin-omcommon.x86_64 0:7.4.0-4.97.1.el6 will be updated
---> Package srvadmin-omcommon.x86_64 0:8.1.0-4.92.1.el6 will be an update
---> Package srvadmin-omilcore.x86_64 0:7.4.0-4.100.1.el6 will be updated
---> Package srvadmin-omilcore.x86_64 0:8.1.0-4.85.1.el6 will be an update
---> Package srvadmin-ominst.x86_64 0:7.4.0-4.97.1.el6 will be updated
---> Package srvadmin-ominst.x86_64 0:8.1.0-4.94.3.el6 will be an update
---> Package srvadmin-oslog.x86_64 0:7.4.0-4.100.1.el6 will be updated
---> Package srvadmin-oslog.x86_64 0:8.1.0-4.85.1.el6 will be an update
---> Package srvadmin-rac-components.x86_64 0:7.4.0-4.12.6.el6 will be updated
---> Package srvadmin-rac-components.x86_64 0:8.1.0-4.4.7.el6 will be an update
---> Package srvadmin-rac4.x86_64 0:7.4.0-4.1.158.el6 will be updated
---> Package srvadmin-rac4.x86_64 0:8.1.0-4.1.127.el6 will be an update
---> Package srvadmin-rac4-populator.x86_64 0:7.4.0-4.1.158.el6 will be updated
---> Package srvadmin-rac4-populator.x86_64 0:8.1.0-4.1.127.el6 will be an update
---> Package srvadmin-rac5.x86_64 0:7.4.0-4.1.157.el6 will be updated
---> Package srvadmin-rac5.x86_64 0:8.1.0-4.1.128.el6 will be an update
---> Package srvadmin-racadm4.x86_64 0:7.4.0-4.1.158.el6 will be updated
---> Package srvadmin-racadm4.x86_64 0:8.1.0-4.1.127.el6 will be an update
---> Package srvadmin-racadm5.x86_64 0:7.4.0-4.1.158.el6 will be updated
---> Package srvadmin-racadm5.x86_64 0:8.1.0-4.1.128.el6 will be an update
---> Package srvadmin-racdrsc.x86_64 0:7.4.0-4.12.6.el6 will be updated
---> Package srvadmin-racdrsc.x86_64 0:8.1.0-4.4.7.el6 will be an update
---> Package srvadmin-racsvc.x86_64 0:7.4.0-4.1.158.el6 will be updated
---> Package srvadmin-racsvc.x86_64 0:8.1.0-4.1.127.el6 will be an update
---> Package srvadmin-realssd.x86_64 0:7.4.0-4.178.1.el6 will be updated
---> Package srvadmin-realssd.x86_64 0:8.1.0-4.139.1.el6 will be an update
---> Package srvadmin-rnasoap.x86_64 0:7.4.0-4.152.1.el6 will be updated
---> Package srvadmin-rnasoap.x86_64 0:8.1.0-4.139.1.el6 will be an update
---> Package srvadmin-server-cli.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-server-cli.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-server-snmp.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-server-snmp.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-smcommon.x86_64 0:7.4.0-4.152.2.el6 will be updated
---> Package srvadmin-smcommon.x86_64 0:8.1.0-4.138.2.el6 will be an update
---> Package srvadmin-smweb.x86_64 0:7.4.0-4.152.2.el6 will be updated
---> Package srvadmin-smweb.x86_64 0:8.1.0-4.138.2.el6 will be an update
---> Package srvadmin-standardAgent.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-standardAgent.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-storage.x86_64 0:7.4.0-4.152.2.el6 will be updated
---> Package srvadmin-storage.x86_64 0:8.1.0-4.138.2.el6 will be an update
---> Package srvadmin-storage-cli.x86_64 0:7.4.0-4.152.2.el6 will be updated
---> Package srvadmin-storage-cli.x86_64 0:8.1.0-4.138.2.el6 will be an update
---> Package srvadmin-storage-snmp.x86_64 0:7.4.0-4.152.2.el6 will be updated
---> Package srvadmin-storage-snmp.x86_64 0:8.1.0-4.138.2.el6 will be an update
---> Package srvadmin-storageservices.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-storageservices.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-storageservices-cli.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-storageservices-cli.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-storageservices-snmp.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-storageservices-snmp.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-storelib.x86_64 0:7.4.0-4.177.1.el6 will be updated
---> Package srvadmin-storelib.x86_64 0:8.1.0-4.139.1.el6 will be an update
---> Package srvadmin-storelib-sysfs.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-storelib-sysfs.x86_64 0:8.1.0-4.1.1.el6 will be an update
---> Package srvadmin-sysfsutils.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-sysfsutils.x86_64 0:8.1.0-4.1.1.el6 will be an update
---> Package srvadmin-tomcat.x86_64 0:7.4.0-4.97.1.el6 will be updated
---> Package srvadmin-tomcat.x86_64 0:8.1.0-4.94.3.el6 will be an update
---> Package srvadmin-webserver.x86_64 0:7.4.0-4.1.1.el6 will be updated
---> Package srvadmin-webserver.x86_64 0:8.1.0-4.3.1.el6 will be an update
---> Package srvadmin-xmlsup.x86_64 0:7.4.0-4.24.1.el6 will be updated
---> Package srvadmin-xmlsup.x86_64 0:8.1.0-4.91.1.el6 will be an update
---> Package syscfg.x86_64 0:4.4.0-4.50.1.el6 will be updated
---> Package syscfg.x86_64 0:5.1.0-4.70.1.el6 will be an update
---> Package tzdata.noarch 0:2014g-1.el6 will be updated
---> Package tzdata.noarch 0:2015d-1.el6 will be an update
--> Finished Dependency Resolution
Error: Package: dell_ie_pcissd-1.0.0-4.107.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchapi.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchapi.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_nvme_pcissd-1.0.0-4.122.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchbas.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchbas.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_nvme_pcissd-1.0.0-4.122.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchapi.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchapi.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_bios-3.1.0-4.105.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchapi.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchapi.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: libsmal0-3.1.0-4.132.1.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchipm.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchipm.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_pcissd-1.0.0-4.107.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchbas.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchbas.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_backplane-1.0.0-4.135.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchbas.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchbas.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_bios-3.1.0-4.105.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchbas.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchbas.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
Error: Package: dell_ie_backplane-1.0.0-4.135.2.el6.x86_64 (@dell-omsa-indep)
           Requires: libdchapi.so.7()(64bit)
           Removing: srvadmin-hapi-7.4.0-4.28.2.el6.x86_64 (@dell-omsa-indep)
               libdchapi.so.7()(64bit)
           Updated By: srvadmin-hapi-8.1.0-4.10.2.el6.x86_64 (dell-omsa-indep)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

How can we fix?

Hello

Dell Linux Repository 15.04.00 (yum repository) is now available for update latest BIOS, firmware’s on PowerEdge servers and upgrade OMSA 8.1.0.

This release brings in the following enhancements and features: 

Support for the following Dell PowerEdge servers:

Dell’s 13th generation PowerEdge servers. The platforms supported are:

• M630
• M630P
• R430
• R530
• T430
• FC630
• C4130

Platform support for Dell’s 12th generation PowerEdge server:

• FM120

New Operating System Support:

• SUSE Linux Enterprise Server 12

Features:

• Latest update support for BIOS and Firmware.
• Added support for the latest Network Interface Cards (NICs), Converged Network Adapters (CNAs).
• Latest update support for iDRAC 2.10.10.10 for 12th generation PowerEdge servers and later generations.

Deprecated support for the following operating system:

• RHEL 5

To know more and download details, please refer the following Dell Wiki page: http://linux.dell.com/wiki/index.php/Repository/OMSA

Symbolic link for Linux Repository 15.04.00 (YUM Repository): http://linux.dell.com/repo/hardware/Linux_Repository_15.04.00/

Please continue posting your feedback on the forum.

 -DELL Change Management Team.

(Cross Post from the Dell OME Forum)

RM v1.9.0.155 and OME v2.0.1.2222

I downloaded from the FTP site all the necessary updates for my environment and saved the Repository to a local directory. I moved the files to a local directory within a DMZ. I have installed RM within the DMZ along with OME. OME was configured without issue and connects to a SQL 2008 R2 database. A discovery and inventory was then performed without error. I can then open the Repository Manager and select Application\Settings\Source Repository. I then point to the directory with the catalog.xml. I am able to View Source and update the RM database.

However, when I go to create a New Repository, I input a Name and then when prompted to select a Repository, all options are greyed out. I have tried to create the other types of Repositories after selecting New, but all of them are greyed out when I am prompted to Select.

What am I missing? Please advise.

TIA

When I update the iDRAC/Lifecycle controller to v 2.10.10.10 I'm not able to access the web interface after the update is complete. When I view the firmware versions in OpenManage that is installed on the server it shows both iDRAC7 and the Lifecycle controller as having 2.10.10.10 but I'm not able to ping the static IP address that I have assigned to the network card. I have used the command racadm racreset soft to reset the DRAC but that does not help. I have to roll back the iDRAC7 to version to 1.66.54 and then I can access the web interface again.

Any ideas?

Thanks

I need to update our 2950s running ESXi 4.1.

I downloaded the SBUU utility and booted it up to a point where I need to select a device that will contain the updates (BIOS, Firmware,,)

Where can I download the update files and how are they stored on USB or DVD so the SBUU can read the device?

 thanks

Hi! DTK 4.4 was released for Ubuntu; I was wondering if DTK 5.X will do the same. Right now on the TechCenter page only the Windows version is available, but you can find the 5.X Linux ISO (with RPMs) elsewhere. Is the Linux version not ready for wide release?

Thanks,

Alex