I'm using Repo Manager 1.9 Data Center Version and trying to create a bootable SUU iso for a R710 running ESXi to update the BIOS and other firmware. When I try to export the latest bundle from the Dell online catalog I only get 72 of 147 files downloaded and then can't create the SUU iso because the bundle is incorrect.

I've tried numerous times over a number of days already to re-export the bundle to my system and it always fails with a large number of files failing to download. I have about 4 GB of free disk on the system after 1.09GB is downloaded. It does manage to download bin and exe files so don't think its a firewall problem

As a quick fix is it possible to download a pre-generated bootable .iso of the system bundle somewhere?

The complete log from the export is attached but only able to attach 1 file so listed the failed files here

List of failed downloads

SAS-DRIVE_FIRMWARE_FY10F_LN_YSFA_A04.BIN
SAS-DRIVE_FIRMWARE_5YYKW_LN_DG02_A00.BIN
SAS-DRIVE_FIRMWARE_5YYKW_WN64_DG02_A00.EXE
SAS-DRIVE_FIRMWARE_3JVY1_LN_YS0A_A07.BIN
SAS-DRIVE_FIRMWARE_HWWCK_WN64_U5E0_A02.EXE
SAS-DRIVE_FIRMWARE_HWWCK_LN_U5E0_A02.BIN
R710_DRIVERS-FOR-OS-DEPLOYMENT_APPLICATION_M5VGR_LN_7.4.0.10_A00.BIN
R710_DRIVERS-FOR-OS-DEPLOYMENT_APPLICATION_M5VGR_WN64_7.4.0.10_A00.EXE
SAS-DRIVE_FIRMWARE_TPF6G_LN32_D906_A02.BIN
SAS-DRIVE_FIRMWARE_2GDH5_LN32_EH04_A09.BIN
SAS-DRIVE_FIRMWARE_XJ1HM_LN32_FS66_A08.BIN
SAS-DRIVE_FIRMWARE_VP540_LN32_HTF6_A01.BIN
SAS-DRIVE_FIRMWARE_WPV4X_LN32_MS0C_A06.BIN
SAS-DRIVE_FIRMWARE_C1MY4_LN32_KS6B_A06.BIN
SAS-DRIVE_FIRMWARE_39Y67_LN32_KSF4_A02.BIN
SAS-DRIVE_FIRMWARE_YT047_LN32_J516_A01.BIN
SAS-DRIVE_FIRMWARE_PVD82_LN32_FSF9_A01.BIN
FRMW_LX_R283321.BIN
TAPE_FRMW_LX_R200813.BIN
FRMW_LX_R165842.BIN
FRMW_LX_R243266.BIN
R710_BIOS_4HKX2_WN64_6.4.0.EXE
R710_BIOS_4HKX2_LN_6.4.0.BIN
SAS-RAID_FIRMWARE_D0KPX_LN_07.03.06.00_A10.BIN
SAS-RAID_FIRMWARE_8TPD2_LN_07.03.06.00_A09.BIN
SAS-DRIVE_FIRMWARE_9M0DG_LN_ESF7_A01.BIN
SAS-DRIVE_FIRMWARE_9M0DG_WN64_ESF7_A01.EXE
SERIAL-ATA_FIRMWARE_740GN_WN64_AA09_A09.EXE
SERIAL-ATA_FIRMWARE_740GN_LN_AA09_A09.BIN
SAS-DRIVE_FIRMWARE_FHY61_LN_RA0B_A07.BIN
SAS-DRIVE_FIRMWARE_12C05_LN_D321_X04.BIN
SAS-DRIVE_FIRMWARE_12C05_WN64_D321_X04.EXE
SAS-DRIVE_FIRMWARE_8GMKG_LN_A007_A04.BIN
OM-SRVADMIN-DELL-WEB-LX-7.4.0-866_A00.TAR.GZ
SAS-DRIVE_FIRMWARE_X1XDC_LN_D1R4_A03.BIN
SAS-DRIVE_FIRMWARE_X1XDC_WN64_D1R4_A03.EXE
SAS-DRIVE_FIRMWARE_5KN73_LN32_KA0A_A09.BIN
SAS-DRIVE_FIRMWARE_GJ0KV_LN_DCAD_A03.BIN
FRMW_LX_R282647.BIN
SAS-DRIVE_FIRMWARE_0JYGF_WN64_DA0B_A03.EXE
SAS-DRIVE_FIRMWARE_0JYGF_LN_DA0B_A03.BIN
SERIAL-ATA_FIRMWARE_4N1N0_LN_DL10_X01.BIN
SERIAL-ATA_FIRMWARE_4N1N0_WN64_DL10_X01.EXE
SAS-DRIVE_FIRMWARE_DGY1G_LN_M440_A04.BIN
SAS-DRIVE_FIRMWARE_GXCDR_LN_PS08_A04.BIN
SAS-DRIVE_FIRMWARE_F5NH4_LN_N440_A06.BIN
SAS-DRIVE_FIRMWARE_K7HV3_WN64_D321_A00.EXE
SAS-DRIVE_FIRMWARE_K7HV3_LN_D321_A00.BIN
SAS-DRIVE_FIRMWARE_G9CVG_LN_DB08_A03.BIN
SAS-DRIVE_FIRMWARE_6PM3Y_LN_CS09_A07.BIN
SAS-DRIVE_FIRMWARE_WD3HJ_WN64_D1S6_A06.EXE
SAS-DRIVE_FIRMWARE_WD3HJ_LN_D1S6_A06.BIN
SERIAL-ATA_FIRMWARE_6XP00_LN_PA09_A04.BIN
SERIAL-ATA_FIRMWARE_PP3VH_LN_DA0A_A03.BIN
SAS-DRIVE_FIRMWARE_2X4NR_LN32_C590_A02.BIN
SAS-DRIVE_FIRMWARE_7TW7W_LN32_D598_A03.BIN
SAS-DRIVE_FIRMWARE_NYHRG_LN32_S52C_A01.BIN
SAS-DRIVE_FIRMWARE_288PJ_LN32_HS11_A07.BIN
SAS-DRIVE_FIRMWARE_3HFT8_LN32_CSF8_A03.BIN
SAS-DRIVE_FIRMWARE_HRCKN_LN32_ER66_A08.BIN
SAS-DRIVE_FIRMWARE_V38WK_LN_ES68_A07.BIN
SAS-DRIVE_FIRMWARE_41N5D_LN32_FM0A_A05.BIN
SAS-DRIVE_FIRMWARE_F50FD_LN32_D80A_A01.BIN
SAS-DRIVE_FIRMWARE_4VM2N_LN32_HT66_A06.BIN
NETWORK_FIRMWARE_T7KTR_WN64_03.10.07_6.0.0.8.EXE
NETWORK_FIRMWARE_T7KTR_LN_03.10.07_6.0.0.8.BIN
NETWORK_FIRMWARE_NMTC3_LN_03.20.06_6.0.0.8.BIN
NETWORK_FIRMWARE_NMTC3_WN64_03.20.06_6.0.0.8.EXE
SAS-DRIVE_FIRMWARE_5CX8G_WN64_DE09_A04.EXE
SAS-RAID_FIRMWARE_C3X7D_WN64_12.10.6-0001_A12.EXE
SAS-DRIVE_FIRMWARE_5CX8G_LN_DE09_A04.BIN
NETWORK_FIRMWARE_68WFG_WN64_02.20.07_6.0.0.8.EXE
NETWORK_FIRMWARE_68WFG_LN_02.20.07_6.0.0.8.BIN
NETWORK_FIRMWARE_2G4HC_LN_2.10.07_6.0.0.00.BIN
NETWORK_FIRMWARE_2G4HC_WN64_2.10.07_6.0.0.00.EXE

Hey,

Just wanted to report some issues we are having, since the new v511 updates,

1. When booting to start firmware updating the DUP packages are no longer auto selecting the correct chassis so this is not automatic anymore.

2. DTK_740 has some issues with finding correct files/directory's to update such as. the following reported:

Collecting System Inventory...........

Unable to find file/directory.

3. DTK_720 works a charm however its dated :)

4. DRM crashes when trying to rename the System Bundle (everytime) DRM 1.9.1 (aka patch)

Looking forward to hearing from you.

Kind regards,

When trying to boot from dvd created using the repository manager on my R610s, I'm receiving the following errors (see screenshot)

I have found several articles discussing this issue, mostly related to attempting to boot from USB.

Any ideas?

(Please visit the site to view this file)

Hello,

I had some trouble to download components with DRM 1.7 or 1.8 on a Win 2012 server. Jobs were failing every time: "Failed downloading some components".

I tried different things and then decided to install DRM on a Win 2008 R2 server. Same DRM configuration, download is working fine now.

Just for you to know.

JP

Good Afternoon,

  I'm trying to setup and use the Dell Repository Manager (v 1.8), however, after I've created the repository and bundles, I can't find the driver for the Perc 6/i for our R710s. It has the driver for the H700 however. Since the driver is missing, I tried to import it into the correct R710 bundle. The server it's currently running on is a VM running Server 2012 R2. Here's how I'm doing it and how it fails:

1) I click the Import button

2) I search for the driver I downloaded from Dell (Windows Update file) and click OK

3) After it "thinks" for a few seconds, I get the following error:

Here's the text in the log file:

</E2ETraceEvent><E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent"><System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2014-01-31T20:52:30.2683561Z" /><Source Name="RepositoryManager.exe" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="RepositoryManager" ProcessID="932" ThreadID="14" /><Channel/><Computer>CORP-IT-DRM-1</Computer></System><ApplicationData>BundleImpl.AddComponent: Error adding SAS-RAID_Firmware_F96NR_WN32_6.3.3-0002_X00.EXE to bundle &quot;System Bundle (Windows x64)PER710 v490&quot; due to validation error: ERROR_INVALID_TYPE </ApplicationData></E2ETraceEvent>

What am I doing wrong? I should mention that the bundle for the R620s that we have include the correct RAID SAS firmware, so I'm really not sure why the R710 would cause an issue.

Hi, I am a new poster in here and have really tried to do my homework on this before posting. Sorry if I missed anything. Here goes:

We are currently implementing Altiris Deployment Solution 7.5 with just one base Windows 7 image. We then wish to add drivers by scripted installation from a network share as part of the deployment job. For Hewlett-Packard and Lenovo computers this is an easy job, using SSM and Thinstaller.

Not so much for Dell. We have tried using Dell Repository Manager in conjunction with Dell Client System Update = no dice.

DRM works reasonably well with DCSU on a single client using the GUI, but apparently the built-in command line client cannot do the same, refusing to detect missing drivers and install them. This seems inordinately silly.

Is there a better way that does NOT involve buying add-ons to Altiris just for this simple purpose? How has everyone been solving the issue of automating driver installation to newly imaged Dell systems with Altiris?

Regards,

Nicklas P. Sørensen, IT-administrator, Holbæk County, Denmark.

I am using repository manager v 1.7.0.158. I am trying to find the best way to apply firmware and BIOS updates to my vmware clusters.  I have been creating custom linux bundles and exporting them to a iso to boot from, then it will apply the updates. However  If there are iDRAC or Lifecycle Controller updates it breaks the virtual media connection and doesn't find the remaining files. i sometimes have to run the boot process three times to get all of the updates applied.

So i though maybe i could export to a ISO and run all the updates from the USC  (v1.5.1.57) and see if that would work better. No matter what i enter in to the options i could not the platform update to work from the ISO. OK, let's try Network share. Nope, it keeps saying it cannot find the catalog no matter what path i try to specify to it. OK, lets try FTP, even though i'd rather not download everything 12 times. No that doesn't work either as it says the updates i am trying to install are not Dell Authorized Updates.

I also have some M610 blades that i tried doing through the chassis management controller and an idrac update failed because said it wasn't the right kind of SUU for the system.

With all of the ways to potentially apply updates to a server, why do none of these work?

I have noticed there has been an update for the packages i believe this is v492 according to the repository manager, it seems this has broken the Dell Linux ISO Bootable this cannot find any file or directory and the old ISO was 7.8GB big and now its 500MB.

Kind regards,

Hi

Firstly I would like to check does Repository Manager can manage Server iDrac / firmware upgrade matters?

If yes, how can I update the Repository Manger Properties URL to Server side catalog?  As currently I find it using Client Dell Online with

URL: ftp.dell.com/catalog/catalogPC.cab

after default installation with OME

Currently my Repository Manger version is 1.9.0.155

Thanks!

Running Data Center v1.9.155, selecting any bundle from the Dell Online DB shows 0 bytes - clicking a bundle and then the Components TAB shows as empty - no components. When you try downloading the bundle(s) - the bundles are empty. This error appeared after Dell removed the older versions leaving only v511 and v512 available. This needs to be addressed ASAP, we need to get the latest firmware updates for over 400 servers in our organisation.

I'm trying to create a customized package to update a group of Dell M610 and M620 servers.  After downloading and manually importing a selection of linux DUP's that are newer than what is in the 520 repo's I'm getting an error when I try to export to a linux bootable ISO.  These two packages are consistently failing to download:

BIOS_PXVNN_LN_2.4.3.BIN (BIOS for M620)
ESM_Firmware_61W8X_LN32_3.65_A00.BIN (iDRAC firmware for M610)

They add to the repo fine, and show up in components, but refuse to download.  I have removed and re-added, and verified the .sign files were there when I imported, as well as tried to just download the files from the Components tab and export to SUU or lightwieght directory with the same issue.

Could someone at Dell verify these two files are on the ftp site correctly?

Also, from a design perspective, why if I import a DUP locally does it need to go back to the online repo to download it again? 

Is there any way to enable the serial console on the Linux ISO created by DRM? I don't see any option in DRM itself, I can't find the relevant files (e.g. isolinux.cfg) to be edited on the server with DRM installed, I don't see any relevant option in genisoimage, and my attempts to unpack the generated ISO, edit isolinux.cfg, and reassemble the ISO so far haven't been successful.

Any ideas?

I want to create a new Source catalogue in DRM, but there are no instructions or any information on how to do so.

The reason why is that I only want my OpenManage Essentials System Update utility to compare certain items to make it a "Compliant System". I want to point OME at this new catalog so that I can gain an accurate comparison as to what is up to date based on our requirements.

I can create repositories and bundles from the Online catalog, but I haven't found any info to my requirement above. Any help is greatly appreciated.

Grant.

Hi guys, I'm trying to update an R310, I've created a bootable Linux ISO with latest DRM and latest DUP, but the update process stop at 38 out of 106 packages with message: "apply_bundles.sh execution is completed, press enter to reboot"

A couple of firmware has been updated (SAS disk and NIC), but BIOS, SAS Controller other firmware remain at old version

I've updated the iDRAC before running the bootable ISO

Please find attached a couple of pictures

(Please visit the site to view this file)(Please visit the site to view this file)

Hi,

I have the latest Repository Manager 2.0.0.187 with x86 plugin 743 and x64 plugin 730 but when I export a Linux or Windows R810 bundle to SUU as ISO, the ISO doesn't work. I'm testing it using 1) my VMWare virtual machine (i.e. launch the VM directly from the ISO) and 2) my Dell Optiplex 9010 desktop. In either case the system doesn't find an operating system to boot to.

On the other hand, I can boot to a Linux bootable ISO generated from Repository Manager just fine in my VM, which would indicate some issue with the SUU ISO. Similarly I can boot my VM to a Fedora Live ISO with no problems.

I'm trying to update a Dell PowerEdge R810 running 64-bit RHEL 5.11. Do I use the Windows 32-bit SUU or the Linux SUU (32 or 64-bit)?

Manuals and Documents for Dell Repository Manager Version 2.0 are available over the Dell support site.

This release of Dell Repository Manager (DRM) supports the following new features:

• Creating an update repository for Integrated Dell Remote Access Controller (iDRAC) inventory.
• Creating a repository with Dell Modular chassis inventory.
• Saving a repository in multiple locations.
• Automatic detection of the bootable ISO by the system.
• Concept of Schedule Repository Search, which helps locating updates that are newer than what is there in the selected repository.
• Concept of Archived bundle - After you download updates to a specific repository using the Schedule Repository option, one Archive folder is created automatically. You can see and use the old files (components) which are saved under the Archive folder.
• Configuring Email settings - Helps you to configure DRM with pre-defined email addresses which can be used to get an Email notification when a new update is available.
• Configuring New Catalog Notification - Helps you get an alert or notification for new FTP catalog or new Dell online catalog.

Hi. I'm trying to use Repository Manager to speed up firmware updating for our servers. For an easier understanding those are the steps I've already done:

1. Downloaded RM (I'm using the DataCenter ver.), created a repository with server models I work with, chose all SO options (Win 32/64, Linux, Other); downloaded all files from the bundles for those servers (mostly 12G rackservers, about 25GB data);

2. Set up an IIS FTP (with anonymous access) in order to connect my hosts to the local repository/catalog.

My servers connect to my local FTP and download the catalog just OK, but when I try to download any firmware I get a SUP0531.

Am I missing something here? Any help is appreciated. Thanks.

Hi, I'm using Repository Manager 1.9 and trying create my first repository, but from servers list I can't select 1950 or 2950 servers.. it's not supported anymore? for version 1.9 it's listed in compatible systems here http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=J2K7T 

Thank you.

i have downloaded DRM 2.0.0 to run on Windows Server 2012R2, running as Administrator and receiving .NET Unhanded Exception when trying to create a new Local Repository.

Changed FileStore location from both default to separate HDD with more space same error.

has anyone else had this issue and if so how did you overcome it?

Event ID 1000: Application Error

Faulting application name: RepositoryManager.exe, version: 2.0.0.187, time stamp: 0x547ecc82
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54504ade
Exception code: 0xe0434352
Fault offset: 0x00014598
Faulting process id: 0x1f18
Faulting application start time: 0x01d04ab832cd105a
Faulting application path: C:\Program Files (x86)\Dell\Dell Repository Manager v2.0.0\RepositoryManager.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 9588cfc3-b6ab-11e4-80f0-0050568ec892
Faulting package full name:
Faulting package-relative application ID:

This is a new install of Dell Repository Manager v.2.0.0.187

A new Dell Catalog is available, however when I go to check for it the "Import Screen" closes after a few seconds of checking for the update. Please see below for log entries:

<Execution ProcessName="RepositoryManager" ProcessID="4352" ThreadID="11" /><Channel/><Computer>'ServerName'</Computer></System><ApplicationData>Downloader.Download: [WebException][Downloader] -&gt; [Download File] -&gt; The remote server returned an error: 227 Entering Passive Mode (10,166,104,55,206,161).&#xD;&#xA;.: ftp.dell.com/sysman/DRMPluginsVer.cab&#xD;&#xA;   at System.Net.WebClient.OpenRead(Uri address)&#xD;&#xA;   at System.Net.WebClient.OpenRead(String address)&#xD;&#xA;   at DownloadManager.DownloadBase.DownloadFile(String strSourceFile, String strDestFile, Boolean bWebFile, WebClient&amp; downloadClient, String&amp; strError) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\DownloadManager\DownloadBase.cs:line 300&#xD;&#xA;   at DownloadManager.DownloadBase.ProcessTempFile(Boolean bWebFile, Token token, String strSourceFile) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\DownloadManager\DownloadBase.cs:line 491&#xD;&#xA;   at DownloadManager.FtpCopy.CopyHelper(Token token, Boolean bAsync) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\DownloadManager\FtpCopy.cs:line 33&#xD;&#xA;   at DownloadManager.FtpCopy.Copy(Token token) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\DownloadManager\FtpCopy.cs:line 42&#xD;&#xA;   at DownloadManager.Downloader.Download(Token token, Protocol protocol, Boolean bAsync) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\DownloadManager\Downloader.cs:line 403</ApplicationData></E2ETraceEvent><E2ETraceEvent xmlns="schemas.microsoft.com/.../E2ETraceEvent"><System xmlns="schemas.microsoft.com/.../system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2015-02-24T17:00:51.3356353Z" /><Source Name="RepositoryManager.exe" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="RepositoryManager" ProcessID="4352" ThreadID="3" /><Channel/><Computer>'ServerName'</Computer></System><ApplicationData>CheckCatalog.GetPublishDate: The remote server returned an error: (403) Forbidden.&#xA;Stack:&#xA;   at System.Net.HttpWebRequest.GetResponse()&#xD;&#xA;   at RMDataServiceLibrary.DataServiceAPI.CheckCatalog.GetPublishDate(String catalogPath) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\RMDataServiceLibrary\DataServiceAPI\CheckCatalog.cs:line 85</ApplicationData></E2ETraceEvent><E2ETraceEvent xmlns="schemas.microsoft.com/.../E2ETraceEvent"><System xmlns="schemas.microsoft.com/.../system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2015-02-24T17:00:54.4856353Z" /><Source Name="RepositoryManager.exe" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="RepositoryManager" ProcessID="4352" ThreadID="3" /><Channel/><Computer>'ServerName'</Computer></System><ApplicationData>CheckCatalog.GetPublishDate: The remote server returned an error: (403) Forbidden.&#xA;Stack:&#xA;   at System.Net.HttpWebRequest.GetResponse()&#xD;&#xA;   at RMDataServiceLibrary.DataServiceAPI.CheckCatalog.GetPublishDate(String catalogPath) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\RMDataServiceLibrary\DataServiceAPI\CheckCatalog.cs:line 85</ApplicationData></E2ETraceEvent><E2ETraceEvent xmlns="schemas.microsoft.com/.../E2ETraceEvent"><System xmlns="schemas.microsoft.com/.../system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2015-02-24T17:00:57.5746353Z" /><Source Name="RepositoryManager.exe" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="RepositoryManager" ProcessID="4352" ThreadID="3" /><Channel/><Computer>'ServerName'</Computer></System><ApplicationData>CheckCatalog.GetPublishDate: The remote server returned an error: (403) Forbidden.&#xA;Stack:&#xA;   at System.Net.HttpWebRequest.GetResponse()&#xD;&#xA;   at RMDataServiceLibrary.DataServiceAPI.CheckCatalog.GetPublishDate(String catalogPath) in c:\RepoMgr_Jenkins\workspace\RepositoryManager200\src\Libraries\RMDataServiceLibrary\DataServiceAPI\CheckCatalog.cs:line 85</ApplicationData></E2ETraceEvent>