Topics created by dvlsg

Ahh okay – yeah I had been eyeing the wiki article about buildroot: ([url]http://www.fogproject.org/wiki/index.php/Build_FOG_file_system_with_BuildRoot_-_init.gz[/url])

I was holding off on diving in to that, since I was hoping there would be a way to mount the init.gz, import the installation (somehow or another), and gzip init back up without having to rebuild the whole thing. But if there’s no other way, then that’s what I’ll do.

Man I hate batch script some days. I actually got it working with my .bat file.

I had to use set vmvar=VMWare%% (double for the escape)
and then use SELECT * FROM inventory WHERE iSysman NOT LIKE ‘%vmvar%’;

Batch must’ve been trying to do something with the % originally, but once I had it placed in a variable it knew not to touch it. What a headache. >_<

Thanks for the help! I’ll have to look into php sometime when I’m not on a bit of a time crunch.

Honestly, the reason I’m interested in it is - just because. Haha. The extra reboot certainly isn’t the end of the world. I would technically save a bit of time, but it’s more an excuse for me to learn more about how FOG works, and how PHP works, so I’m just playing with it when I have extra time (which isn’t very often). I don’t actually use snapins to deploy software - I have a lot of VBS that pulls info from active directory and deploys software from a networked drive based on that information.

Lee, I actually have been working on your post – I don’t have it in production yet, but I still have to fiddle around with buildroot. Although, I’m not sure I’ll need to - I think sed is actually included in whatever build of init.gz I have.

Thread resurrection! This actually happened to a member of our IT department again, today.

Has anyone else ever run in to this problem? Some possibilities of causes:

Computer had the original OS hard drive and the secondary drive in the computer before, while FOG imaged it The original OS drive was removed, and replaced with a new SSD The hard drive mode was switched from RAID to AHCI in the bios After all those changes were made, FOG imaged the secondary drive, instead of the SSD Post installation, the SSD is listed as /dev/sda and the secondary drive is listed as /dev/sdb

Still pretty stumped. Anyone think any of those options would have temporarily caused the secondary drive to be read as /dev/sda?