fog.drivers script will not run correctly in postdownloadscripts
-
@THEMCV I did create a write up for creating a single golden image for multiple platforms here: https://forums.fogproject.org/topic/7391/deploying-a-single-golden-image-to-different-hardware-with-fog But because of my NDA with my company I can’t include any of my own scripts. Now with what Tom, Lee an other produced I can compile that into a single document.
But this next one will be short and to the point copy and paste this and it “should” work as designed. I’ll leave the big words on the other documents.
-
@george1421 Ah yes, I did read over that one a bit! I finally got it figured out, but I didn’t end up using MDT. Very thorough.
-
apologies both - i could of jumped in sooner to point out about the /fog directory confusion and assisted with the partition code but been swamped as of late but luckily @Tom-Elliott had already sorted partition bit of magic for you guys!
@THEMCV if you do only have dell machines and want to use cab files - you can use cabextract which is built into the FOS.
something like:
cabextract -d /ntfs/Windows/DRV "/fog/Drivers/$osn/${machine}"/*.CAB &>/dev/null;
/ntfs/Windows/Drv - Change to wherever you want your drivers to be extracted to
/fog/Drivers/etc… - Change to match the directory you store the .cab file on the server. i.e. /images/Drivers/E7270-WIN7-A02-8924F.CAB
if you go down the .cab route - use the enterprise cabs as they are tested and put together specifically for image deployment.
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deploymentif for whatever reason the cab isn’t sufficient and you need to add drivers, you could incorporate both .cab and folders using both sets of code. if you know what i mean?
as @george1421 pointed out scripts are a lil’ flawed but where written and posted sometime ago and for my own environment at the time and my own postscripts have come a long way since then.
the wiki post would be a very good idea as easier to keep up to date, once that’s done it may be worth changing any old posts with code in, redirecting users to the wiki so they don’t put conflicting or outdated code together. but like @george1421 said, a lot of it is personal preference and there is so many ways of achieving the same thing…
Glad you got there in the end though
-
This post is deleted! -
Hello,
Is it possible to have the script complete and that works?It would be nice to have this feature directly integrated into fog in a future version.
The management of the drivers customized by machine model is paramount now in the windows images.
Thanks Jacky
-
@Jacky94 Its a start: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/5
But coming up with a universal driver install would be difficult since each company is unique.
-
Hello,
Is it possible to have the script complete and that works?It would be nice to have this feature directly integrated into fog in a future version.
The management of the drivers customized by machine model is paramount now in the windows images.
Thanks Jacky
-
@Jacky94 As @george1421 stated, this is not something that can be done considering the sheer number of companies and products available. And, each person’s layout is 100% unique to their configuration.
-
Do not worry I know how to fetch my Dell drivers.
But I would like to be able to inject the drivers from the Fog web interface.
-
@Jacky94 A feature request that, this late in the game, will not be processed.
-
postscripts once setup, its literally the case of dropping drivers onto server, you could even setup permissions and map drive onto windows machine so you can “inject” there without even needing to go on the server (or give engineers permission to whole server)… pretty much what ur asking for but rather than through web interface, its network share
-
I agree with you that it works wonderfully well with postdownloadscripts,
Thanks to the scripts provided by the forum community. Thanks to them.But we must look for a bit before we find the existence of this functionality.
Many people will turn to OPSI because it is better indicated in the documentation and it is native in the application.
I always love Fog because it’s very light.
Thanks to the Fog team