You'll need to rename them something unique, like D420 Audio XP or D420 Audio 7. The driver association window is not designed to support multiple entries with the same name, so I believe it would probably just take whichever was injected first.
When it comes time to download the drivers we will use the OS that you select in the deployment script to know which drivers to get. This step is required for both provisioning templates and for OSD scripts that use sysprep (which is a requirement for HII), so it should cover any use case.
Let me know if you have any questions.
Is there a way to go about changing the names now? Rather than deleting the driver then re-adding it?
Not that I am aware of, unfortunately.
I won't lie, that's not exactly what I wanted to hear.
Usually = ER