@marsface I seem to have resolved it with this line instead of the two provided ones
machine="${machine//[[:space:]]/}"
@marsface I seem to have resolved it with this line instead of the two provided ones
machine="${machine//[[:space:]]/}"
@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 I seem to have resolved it with this line instead of the two provided ones
machine="${machine//[[:space:]]/}"
@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?
@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!
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.
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.