Posts made by Andrew Single

Is there a post with links to the pre-1.3 branch? Sourceforge only has the 1.2 branch and older listed.

It depends on the driver. Usually, you just need the folder from the driver that has the .inf for the device. (Copy the entire folder contents, not just the .inf file) You can test that driver by going to a machine that doesn’t have the driver installed, and doing an “update driver” in task manager, and pointing to the folder. If it installs, you should be good.

For some devices, the driver is an .exe that you can launch with a silent install command. In that case, the driver folder should have the exe, any associated files, and a drvinstall.bat file as per [url]http://www.fogproject.org/wiki/index.php/Auto_driver_Install#Adding_Silent_Install_drivers[/url]

It looks like for whatever reason doing the sanboot causes windows 7 to screw up on boot. Changing to exit seems to resolve the issue. Tom: Is there a downside to using exit over sanboot?

Well, it’s something with the iPXE. If I remove the boot.php file, Windows doesn’t hang. I’ve tried different pxe files, and so far they just fail on PXE boot. I’ll keep investigating.

Clean install of Windows from Win 7 Pro SP1 x64 media, same issue on the E5530. This one is really quite bizarre.

Vostro 3550’s exhibit the same behavior, even failing to make it through the sysprep process if it’s connected to the network with PXE DHCP options specified & apache running on the FOG server. Optiplex 745, & 7010 are both fine.

I’m doing a clean install from media now to see if it’s perhaps an issue with making the image in VirtualBox.

Dell Latitude #5430
FOG 1.2 on Ubuntu 14.4.1
Official Kernel 3.14.2

I’m getting a PXE error of:
"XZ-compressed data is corrupt

– System halted"

When I attempt to do a full host reg. It does the same if I register it via the web UI & give it an imaging task.

I’ve tried with the 3.8.8, 3.17 and v 2 kernels with no success. It’s the only one I have of this model in the admin office though, so it’s possible I’ve got bad RAM or a defective unit too.

I’ve done a clean install of Unbut server & FOG, and I still have the same issue. Doing packet caps from the FOG server to see if that gives me any clues.

I’m having what appears to be the exact same problem with a Latitude E5530 in our test environment testing FOG 1.2. I’ve ruled out the image as the issue, as I’ve tried a couple of images. It’s not a driver issue, as I’ve tried it both with & without drivers present during sysprep.

If I disconnect the network cable during boot, it boots fine. If I stop apache on the fog server, it boots fine. If I connect the system to our production network (Running FOG .32) it works fine. It happens both with an image having the .32 FOG client, and an image with the 1.2 fog client. If I disable the FOG client, it still happens. If I remove Option 66 DHCP information from Windows Server 2012 R2 DHCP, it boots fine.

The machine is still running in the background. If I hit the power button, it goes into hibernation. I can use remote command prompt tools to issue a restart command. If I do a remote screen view, it simply shows a black screen.

FOG 1.2, Ubuntu 14.04.1 LTS
Image made in VirtualBox (Both images tested)
FOG Service installed (.32 in one image, 1.2 in the new one)
Used sysprep, I’ve tried it both with & without drivers injected by FOG and with and without SetupComplete.cmd.

Jamie: A tip for you re: Dell BIOS options. You can use the Dell BIOS utility from their website to create a EXE file that will change BIOS settings when executed on a machine. When you want to image, you make a script that you push out with active directory that changes the boot options to something that will work with FOG.

Inside your image, you have another version of the file that changes it back to secure boot, and is executed from your SetupComplete.cmd. I haven’t used it to do that, but I have used it in our general image to make sure that BIOS settings are universally the same.

Okay, the script is now posted, along with documentation in: [url]http://www.fogproject.org/wiki/index.php/Auto_driver_Install[/url]

Please keep in mind that I only updated from FOG .33 to 1.2 3 days ago, and that this script is a complete re-write from what I used to use. I’ve tested it locally on a couple of different systems, and it seems to be running cleanly, but test this script in your environment before going crazy with it, and please post comments on any issues you have.

A similar script in .33 is how Frontier School Division keeps thousands of mostly Dell computers in 40 separate locations imaged with minimal management effort (6 network administrators). We have two Image files and a driver repository that we maintain centrally. Each of the remote FOG servers sync from the central driver store with rsync.

Any time we encounter a computer that has a missing driver post imaging, we simply add that driver to the central store, and re-image the computer. When we order machines in mass from Dell, we supply them with a list of computer names, and they send back a csv with the computer name to MAC address list, and they add an asset sticker to the systems. If it’s a new model to us, I have Dell send one machine to my office where I image, and add any drivers required to the central store. I then import the CSV into FOG, assign the image, and create the imaging task.

At the school, we arrange for the systems to be unboxed, plugged in and turned on. The systems boot, image, join the domain and are ready to use. FOG is an amazing project that saves us a ton of time and effort.

Looking for wiki access. I’m going to document my auto driver install script there with screenshots & how-to’s. I’ve noticed there’s also a lot documentation that’s not up to date for 1.2.

Somewhat like that, but organized in such a way that FOG can automatically inject the correct drivers into the firstboot process. If I were to use the Driverpacks, I’d need to build a database linking device IDs to folder structure, and that complicates the script significantly.

Looks like I can parse dmesg to get the pnp device ID of SMO8810 for the freefall sensor. Adding PNP drivers to the script.

I built a script with FOG .33 that copied drivers from a central store as a part of the imaging process based on the BIOS model identifier.

I’ve finally had some time to play with FOG 1.2, and I’m making the following adjustments to my script:

-I’m using the postdownloadscripts folder to add the scripts required without having to edit the init.xz file
-I’ve changed the script from using the BIOS model # to using lspci & lsusb to enumerate the PCI & USB devices detected on the machine and then pull those specific drivers.

What this means, is that we can develop a community driver library over rsync that allows people to build universal images where FOG does the work of installing the correct driver.

[url]http://www.fogproject.org/wiki/index.php/Auto_driver_Install[/url]

Attached are the two script files. Machinedrivers is called from DriverInstall. Rename to .sh make executable.

[url=“/_imported_xf_attachments/1/1471_DriverInstall.txt?:”]DriverInstall.txt[/url][url=“/_imported_xf_attachments/1/1472_machinedrivers.txt?:”]machinedrivers.txt[/url]

Heads up: I’ve got an updated version of this script written for the new FOG using the postdownloadscripts folder.

We’re also changing the method for things from being model specific, to actually checking the PCI & USB device ID’s & pulling the exact driver required. That way, when we get a new model, most of the drivers are already there, and it’s just a matter of adding one or 2 new devices.

Additionally, people could collaborate & build beautiful driver repositories together. Someone new to FOG can come in, sync a driver folder via public rsync, and BAM, sexy driver auto installs.

We’re starting to use Intel SSD’s as a standard on all new systems, and there’s a few generally accepted optimizations for Windows 7 that aren’t necessarily done by sysprep.

I’m going to be building a routine for funcs.sh to detect SSD post imaging & apply registry changes to disable prefetch/superfetch, System Restore, Defrag, etc.

Before I get started, I just wanted to check to see if this has been done already.

We run 50 sites with FOG, and do them as standalone, but with special scripts.

I’ve modified FOG to automatically deploy machine specific drivers post boot, and we sync those driver repositories, and our standard image using rsync.

FOG is so easy to build that it’s no big deal to deploy it everywhere on a VM.

Zabbix (Network monitoring)
Asterisk
Smoothwall (We use their commercial product)
VirtualBox
GNUGk

Nice work guys. I haven’t been by the forums in a while, and I noticed this thread was resurrected. The other thing we’re doing now with the auto driver install is addressing drivers that are installables, but not windows drivers in the technical sense. For example, a touchscreen calibration tool. It’s something you need on certain models, but don’t want on everything. Certain Dell models have an internal speaker that doesn’t work without a helper system tray program installed, etc.

We have the auto driver install also copy a script for each model that launches those types of programs post setup. That way you install those machine specific programs without having to make a specific image.

[url]http://technet.microsoft.com/en-us/library/dd744268(v=ws.10).aspx[/url]

You can add [FONT=Segoe UI][COLOR=#000000]%WINDIR%\Setup\Scripts\SetupComplete.cmd to your image, and windows 7 sysprep will launch that at the end of the setup process. Just add a copy command that sends your model specific setupcomplete.cmd to the drive to the location above.[/COLOR][/FONT]