/build/static/layout/Breadcrumb_cap_w.png

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?
0 Comments   [ + ] Show comments

Comments


All Answers

0
As far as I know there is no way to link the driver shares like this. However, in theory you could make this happen. 

In the built in copy_drivers.vbs there are location adjusters that you could add to:
If (InStr(strProd,"Windows 8") > 0) Then strProd="windows_8"
Elseif strProd = "windows_8" and strArc = "x64" Then
strProd = "windows_8_x64"
ElseIf strProd = "windows_8" and strArc = "x86" Then
strProd = "windows_8_x86"

So you could uncheck the Get drivers from driver feed, Modify this vbs and set it as the last mid task. 
The file will be located under \\k2000\petemp\applications\*\copy_drivers.vbs. mine is in the 300 dir but i believe that changes.
Answered 06/16/2017 by: Desktop Jockey
Second Degree Green Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ