Migrated Drivers using old content location

[david_pvusd]

I have what seems to be a weird one.  My site server is Server 2019 and I am running MECM 2409 with no hotfixes.

About a year ago I migrated all my software from the old MECM server to the new one.  I updated the content source path for all the software and things seemed to be fine.  I finally got around to shutting down the old server around November.

I have added some new drivers recently and needed to add them to my boot image.  No problems on the import or package creation/distribution.

When I go to add them to the boot image it fails adding a driver (a driver imported imported before the migration).  Looking in the DISM.log, the driver that failed had a path of "\\oldserver\driver" instead of "\\newserver\driver".  Removing the failed driver from the boot image allows me to move on to the next failure.  When I look and search in the console all drivers show their content source path as "\\newserver\driver\*".  I see the correct source path when I look in the database table CI_ConfigurationItems and view vCI_ConfigurationItems.

When I copied everything over, I kept the same directory structure, so the only part of the drive path that changed is the server name.

My searches so far have only come up with how to do the migration, not how to troubleshoot issues such as this.

Right now my 'fix' is to remove the offending drivers from the boot image one by one as they fail during the "Update DP" wizard.

I have contemplated adding a DNS entry for the old server name to point to the new server IP, but I am not sure if it will work due to name mismatch.

I can not recall if I have done an "Update DP" on all driver packages since the migration.  I am thinking this may identify the "lost" drivers quicker as well as additional drivers that may be having issues that are not usually added to a boot image.

We are also on the verge of dropping support for about half of our computer models as they don't support Win11, so I am also thinking about just nuking the driver store from orbit and start over with only the drivers I need.  Unfortunately, I know this will take a lot of time so I will need to wait until late-June at the earliest to try this as we are in our end of school year push to build and rebuild computers before the summer break.

 

Thank you for any insight 

David