Best Practices Question
K2000 creating a Symlink for drivers_postinstall
06/12/2017 696 views
Have not seen anything on this topic but I am sure others are affected as well.
With the recent updates to Windows 10 it changed the entire drivers_postinstall path for our driver feed.
What used to be windows_10_x64 for example is now Microsoft Windows 10 Pro_x64
Sometimes we may have reason to use an older or newer version of Windows 10 so I need both feeds at the same time, but it makes little sense to have two copies of several gigs of driver data and makes it harder to maintain.
I know on my local computers I can use Junctions/Symlinks for this kind of problem, but you cant do that for a remote resource like a UNC path. It has to be done local.
Is there any official fix for this? Or, would this require some kind of shady hacking by running a rule or script on the K2000 to do the task?