Hi Dan,

OME keeps a local repository of the packages so that it does not have to download the packages again. So, you do not have a way to undo it. 

From this OME location, it is in turn copied to the managed nodes.

Duplicate post

Hi Pupul,

To give you a better idea of the environment:

We have one OpenManage Essentials server with 2 drives. One for the OS, another for the file repository. I used the repository manager to sync the Dell Online Catalog to the local one and then exported a new Catalog file and the repository to the file repository drive. This then downloaded all of the files and I've made the local Catalog the source in the System Update section.

Whenever I try to apply firmware to another server (Lets say it's a Backup server) rather than copy files to the "managed node" it just copies them to the C drive of the OpenManage Essentials server. I can't find any update files on the servers we have applied firmware to through System Update in OME.

Is this correct? It seems extremely odd if so.

Thanks

Dan

Hi Dan,

You are going in the right direction except for one thing. OME first copies the package to OME server folder location "....\SystemUpdate\Packages". From there, it is copied to the "Managed Node". Once the task completes on the managed node, it is deleted from there. This is because we do not want to fill the managed node memory using system update Packages.

OME v2.1 has a feature where you can limit the size of "System update >> Packages" folder such that it does not keep getting filled with Packages and OME will purge packages from this folder once it reaches the limit.

Hi Pupul,

That appears to have done the trick. Thanks for your help!

Dan

Perfect!!! Thanks for updating the post.