- Notes, cautions, and warnings
- Overview
- User scenarios
- Difference between Schedule Automatic Search and Schedule Repository Search
- Downloading the updates for the systems, which are not there in the Dell Online Catalog
- DUP Dependencies
- Creating repository
- Using FileStore to save disk space in system drive (C: Drive)
- Searching the Dell Support Site for updates
- Export updates to LightWeight Deployment Package
- Updating the local repository
- Creating Bootable CD or USB Keys for updates
- Creating a custom repository using Dell OpenManage Essentials
- Launching DRM using command line options
- Launching DRM using command line options from client
- Creating an update repository using Dell OpenManage Integration for VMware vCenter Inventory
- Using Repository Manager in client mode to Create and Manage Components
- Frequently asked questions
Välkommen
Dells webbplatser
Dells webbplatser
Välkommen till Dell
Mitt konto
- Lägg beställningar snabbt och enkelt
- Visa beställningar och kontrollera leveransstatus
- Skapa och kom åt en lista över dina produkter
- Hantera dina webbplatser, produkter och kontakter på produktnivå från Dell EMC med hjälp av företagsadministration.
Dell Repository Manager Version 2.0 Troubleshooting Guide
DUP Dependencies
DRM 1.9 onwards,
DRM supports DUP Dependency. This feature articulates the relationship
between two different DUPs. SUU enables certain rules and submissions
to determine if a set of conditions or requirements are met. These
conditions or requirements are called dependencies. Dependency exists
when a DUP of a particular kind has a dependence on additional DUP
for further execution. This helps the users to determine, which DUP
to install first and which one to follow. There are two types of dependencies:
Hard Dependency and Soft Dependency.
- Hard Dependency — Dependency that must be applied in order to be able to apply the update.
- Soft Dependency — Dependency that needs to be applied in order to use certain new features coming with the update.
NOTE: In certain
scenarios, for a complete update or upgrade, you must install two
and more DUPs. It is possible that for individual DUPs, you are
forced to restart the system, to realize the impact of other installed
DUPs.
- When you update a component, if the dependent component is a pre-requisite and it needs a reboot, it is recommended to reboot the system to update the remaining components.
- When you import components using Import option, if the component has a missing dependency a warning message is displayed informing you about the missing dependency.
- When you select the Export option, the pre-requisite components are downloaded and copied to the output location.
The following flow chart describes the process
in detail.
Ange betyg (1–5 stjärnor).
Ange betyg (1–5 stjärnor).
Ange betyg (1–5 stjärnor).
Ange om artikeln var användbar eller inte.
Kommentarer får inte innehålla följande specialtecken: <>()\