Time for a New FOG Tutorial
-
Hi All,
I recently got a FOG environment set up, but it was a huge pain. The documentation is all over the place, and often very outdated, but we got it done.I have a W11 image that I captured, and syspreped using an unattend file. I followed this guide for driver injection, the top one in tutorials. It was missing a ton of context. I had to deep dive to even understand the terminology and locations that were referenced.
My question is now, is there a new tutorial or method for using FOG with autopilot that will inject drivers without having to create a new golden image for each type of device, or need to include drivers in the golden image. I have the CAB files set up in the FOG server, so why do I need to put the drivers on the C drive as well?
Any help is appreciated, thanks.
-
@marsface said in Time for a New FOG Tutorial:
I recently got a FOG environment set up, but it was a huge pain. The documentation is all over the place, and often very outdated, but we got it done.
How much exactly did you pay for the rights to install and setup FOG?
Probably not the way I would go about asking for help from a forum driving support system. There is always room for those folks who would want to update or create the perfect FOG documentation.
My question is now, is there a new tutorial or method for using FOG with autopilot that will inject drivers without having to create a new golden image for each type of device, or need to include drivers in the golden image. I have the CAB files set up in the FOG server, so why do I need to put the drivers on the C drive as well?
As the person who wrote the tutorial on drive injection using FOG that was written before autopilot. And truth be told autopilot is a windows “thing” not a FOG thing. FOG only moves data blocks from here to there. I can tell you at the time I was deploying a single golden image to 14 different hardware platforms by injecting the drivers as I had laid out in the tutorial. The issue you have is that FOG is linux based and not MS Windows based (as with SCCM/WDS/MDT) so there are only a limited things FOG can do during deployment (move data blocks from here to there). FOG can’t step in and run windows applications. Once FOG imaging is done, its up to the target OS to complete the setup.
-
@george1421
I apologize for my tone, obviously I came across as hostile. Not the intention. I would be more than happy to write the updated documentation, but I still have so many questions before we even get there.Also, I am grateful for the work and effort you’ve put in so far!
-
@marsface So outside of the autopilot thing, are you having any specific issues with FOG?
-
@george1421 Currently the only issue I am having is the copydrivers script, it keeps hanging saying “Driver package not found for Latitude5540/win10/x64”, except the stars are square blocks. This is after trying it with the built in and then getting and using Jeffrey B’s space removal snippet. The strange blocks surrounding “Latitude5540” happen when using the alternative method.
machine="$(echo -e “${machine}” | tr -d ‘[:space:]’)"I believe my file structure is correct as shown below. When I use the built-in method:
machine="${machine%"${machine##*[![:space:]]}"}";It doesn’t remove spacing at all. Should I just change the file structure name to have a space?
-
@marsface I seem to have resolved it with this line instead of the two provided ones
machine="${machine//[[:space:]]/}" -
@marsface Well done finding the solution, the regex expression might need to be updated in the tutorial then. It could have been FOS linux changes since the tutorial was written, or a different way that the dell firmware is reporting the model. Either way well done.
