Hello

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.

Did you just copy the files and the catalog.xml or did you use repository manager to create the repository? The files and repository need to be in a specific format for it to be recognized. I would suggest that you set your source repository back to the default ftp.dell.com or ftp.us.dell.com and use DRM to create the repository using the online catalog.

Thanks

I started by creating a repository on my workstation, pointing to ftp.dell.com. I then downloaded all the Bundles I needed. Once complete, I Saved the repository to a local directory. I then copied that directory over to my DMZ. I can go to Settings and select Source Repository, and find the Catalog.xml. I then select View Source Catalog and the Database is populated.

I am under the assumption that I can create a Local Source Repository at this point, but all New Repository options are greyed out.

I just tested it and it worked without issue for me. I am running the latest DRM though. I exported SUU as directory and pointed to it as the source. Creating a repository using local source is working fine.

The first thing I would do is update DRM.

I did update DRM.

I have been exporting and saving from the DRM (on the internet facing workstation) to a Repository, but this time I exported to a SUU directory. When I move that directory to the DMZ, that instance of DRM can find the catalog.xml, but I still get a greyed out option to create a new Repository.

I tried launching the SUU (sulauncher.exe) and it inventories the server/s, but then has no boxes to update any drivers/firmware. This is my first time setting up this environment, so I don't know if there are special considerations for a DMZ.

Thanks

I can't think of anything specific to DRM that you would need to configure. All of the network, firewall, and folder permissions would be unrelated to DRM. Something is likely being blocked by some form of security or network policy.