Best posts made by adukes40

The scripts I use do that. They get the model, and architecture, then using that pulls the needed drivers for the machine. All automated.

@george1421 Just got the new master pushed up, and the M.2’s are now working great.

I had that as well. It seems if you told the client to put the log in the install directory, it still creates the program file in C:. I just placed the new client on my master images over the weekend, and told the log to install to C:. I am imaging right now to test this.

It has been recommended if this does occur to have a script delete the additional “Program” file in the root of C:. I will also comment back to verify changing the location from the install directory to the default root of C causes the extra file to disappear.

Have a confirmation line at the end of the registration script. Doing a couple thousand registrations this summer, and it appears if you typo, you have to reboot and start over again. Could the confirmation be set as the last line, with a Y or N. Y would do the registration and move on, where the N would either clear it out and go back to the top and start over, or maybe retain the information typed in, then ENTER down to the line with the typo and make a quick change.

As always if there is a way to do this currently I will give it a shot, if not thanks for listening

Organization: Milford School District
Location: Milford, Delaware, USA
Approximate number of systems: 3200 total
How long: Implemented March 2016

For our 3350’s you have to set

Host Kernel Arguments pci=noacpi

for each host. (maybe needs to be for 5520s as well??) We do not have any here, so I don’t know.

But I created a group, registered them all to the group, and mass updated all the host arguments.

@dclark Checking in from Milford School District. I heard you guys switched over to FOG.

@Seydoo Have you tried updating to RC-11?

@pencils As far as the exit types go, I don’t think you need to worry about those (I don’t)

As far as the capture goes. Basically, you find the host in fog gui, make sure the image is set (which it looks like you have), go to basic tasks, Capture, create task.

Next time that machine is PXE booted, it will see there is a task and execute. If you are having to hit F12 each time, change the boot order in the BIOS to network boot first.

Make sure your MAC address in the host info matches what your machine MAC is.

I do all the cab extractions before placing them in FOG. It copies the driver folders over, and it works. Of course your scripts look different than mine because I didn’t edit it that far from the original from the other post.