I have been successfully using IEM for OSD purposes. Now we have to upload the new set of updated drivers for the existing Hardware models.
But I am not sure while uploading will it upload only the new drivers or the existing drivers also(duplicate entries), And if for a same HW model if we have different drivers for same component, which driver will be applied (old or new).
We have around 30 models in the environment, So manually binding the drivers will take up lot of time.
at import time, duplicate drivers are skipped but newer versions of the same driver are added in the Driver Library.
When you have an updated driver package for a specific hardware model you can operate in two ways.
search in the Driver Library all the drivers that were imported from the old driver package (for instance, search for Bound Models or the Imported From field), delete these drivers and then proceed with the import of the new driver package binding the new package to the specific hardware model.
This approach lead to the use of newer drivers.
Advantages: It has the advantage to limit the numbers of drivers loaded in the Driver Library.
Disadvantages: Manual binding operations that had been performed on drivers from the old package are lost. Since drivers loaded for a given model may be also used for other models, this approach will lead to use the newer drivers potentially with all models that have the same device installed.
Import the new driver package directly on top of existing drivers. You could use a Label at import time to later be able to easily distinguish new drivers from old ones for a specific model. Once your new drivers usage has been consolidated you can delete old duplicate drivers.
This approach is more conservative as drivers imported from the older package have the precedence at deployment time.
Advantages: you preserve the existing manual binding operations.
Disadvantages: To use the newer drivers, without deleting the existing ones, a manual binding operation has to be performed.