Owner's Manual

Overview 9
5 After creating the bundle, Peter clicks the Components tab and clicks
Add to add the components that comprise the bundle.
6 Peter adds components relevant to driver updates. The components are
added to the repository that Peter selected in step 1. Peter now needs to
export these components to the bundle he created in step 4.
7 On the Components tab, Peter clicks Export.
8 In the Export Destination dialog, Peter selects Export to existing
Bundle and selects the properties of the bundle he wants to export to.
For information on exporting a bundle, see the "Exporting Bundles"
section. This feature is applicable for the Windows bundles.
The components are added to the selected bundle.
9 Peter now wants to deploy the bundle he created on the PowerEdge R710
system. On the Bundles tab, he clicks Export.
10
In the Export Destination dialog, Peter clicks Raw Driver Pack and
specifies a location in which to save the driver pack. Repository Manager
creates the RawDrivers directory that contains the .bat file which Peter
must run on
PowerEdge R710 .
NOTE: Bundles containing Linux components are skipped during
the export process.
11 Peter runs the .bat file on PowerEdge R710. The PowerEdge R710 system
is updated with the latest drivers contained bundle Peter exported.
Export to Light Weight Deployment Scripts
Let us assume that Peter wants to deploy the bundles relevant to the
PowerEdge R710 and R610 systems. Because these systems already
have operating systems installed, Peter selects to export the bundles
as deployment scripts.
1
Peter selects all the bundles he wants to export (relevant to both systems)
from the repository he created.
2
Peter clicks Export.
3 In the Export Destination dialog, Peter clicks Export to light weight
deployment scripts and specifies a location in which to save the scripts.
Repository Manager creates a directory for each bundle Peter has selected
to export in the specified location.
drm.book Page 9 Tuesday, July 21, 2009 6:30 PM