@carrjd Have you considered the project I made that makes FOG completely mobile? It’s designed specifically for your use case - you’ll be able to do more than one at a time.
https://github.com/wayneworkman/FOGUpdateIP

@kwetiaw Well, dnsmasq in proxy mode might be a different story. I have to admit that I read your initial post about using dnsmasq because you are not allowed to touch the real DHCP servers but somehow wasn’t aware of that fact when posting my answer.

From the dnsmasq man page:

For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is optional: dnsmasq will determine it from the interface configuration. For networks which receive DHCP service via a relay agent, dnsmasq cannot determine the netmask itself, so it should be specified, otherwise dnsmasq will have to guess, based on the class (A, B or C) of the network address.

So we are back to my question on how is you server (running dnsmasq) connected to those two networks?

Maybe this could work (if you have two different NICs for those two networks - please post the full output of ip a s on that server):

dhcp-range=eth0,10.3.0.1,proxy dhcp-range=eth1,10.40.0.1,proxy

@Avaryan Thanks matey.

I shouldve mentioned my environment on my post. Windows 10 Enterprise and I just tested with the powershell script you mentioned.

WORKED FLAWLESSLY!!!

Thanks and really really appreciated!

All set - it was the files being sent to a single filename * - that was just a syntax error on my part for using the Windows cli too often.

@Wayne-Workman - i had to change my /opt/fog/.fogsettings file back to pointing the storage at ‘/images’ because the entire imaging process breaks. Also re-added my /etc/fstab line to point /images to the home directory where the 177G volume is. I understand you think my system will fail if I fill up more than the 50G available on the root drive, I’m confident it won’t. Thank you greatly for your assistance, it was the file copy problem.

@dureal99d Really nice, thank you!!

Any update on this? I have just started universal imaging using Hyper-V, which is working great. However, the upload speed from VM to FOG-server is slow. Currently uploading now, and am getting >300MB/min

@Satheesh I don’t agree with what you want changed.

Currently, - if a computer is off, a scheduled task will wake it up and perform the task.

If it is on - and you’re using the FOG Client - the fog client will ask the user to allow maintenance, or to delay 10 minutes (currently). The client at the end of the delay will reboot the computer, and the computer performs the task.

I don’t see how this isn’t good enough. You are asking for the computer to purposely hang during the boot process for - how long? That’s not acceptable. And why can’t WOL be turned on? You’re asking the developers to do a very major change because you don’t want to turn on WOL. We’re in Release Candidate mode - and this is way far out there - and not only is it way far out there, I just wouldn’t ever use a scheduled image task anymore because I don’t want my organization’s computers just hanging on boot. It’s unacceptable.

My advice to you, turn on WOL like the rest of us did.

Coincidentally, another person asked about this today. here’s the thread:
https://forums.fogproject.org/topic/8435/multiple-blank-images-with-no-data-new-post

@lgauthier see my edited post.

@george1421 Trunk installed and is up and running. Will try imaging and restoring of computers tomorrow. Now reading up on how to do it 🙂

Thank you all for the help!! I guess this one can be marked solved.

@Dave-Wolf The article says minutes for a 100GB+ image - this isn’t a stone-cold figure. If your system is older, running on older hardware, is under higher load, has slower RAM/Processor/Bus speed - this figure will vary quite a bit I imagine. Even more if it’s using a SAN that is less than amazing.

And, what you’ve described is exactly what’s described by Sebastian. Credentials check out, seems like a timeout, using Ext3… I am not sure you’re not affected - I’m almost positive you are. Ext3 is the issue, it’s how it operates, there’s no configuration you can do to fix it besides moving to Ext4 or better.

And - several people here have used FreeNAS with Fog, there’s a wiki writeup about it in two different spots I think, I’ll see if I can find them.

Newer note and features on the subject:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#FTP_Path

Older stuff:
https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS

@george1421 I did briefly, but it doesn’t appear that Veeam Endpoint would be compatible. Target requirements.

Oh nice! So I’ll update my server and I let you know if it fix the problem, maybe it could help someone in the futur.

Thank’s for everything @Quazz

@Wayne-Workman said in Bootable USB drive to re-image a machine:

Conezilla is better suited for what you’re wanting - it already can do imaging from a local flash drive.

I agree here, you would be better served by tweaking the clonezilla code to make it a bit more automated and friendly by a nice menu program and to make it use the usb stick directly as a stroage device. In this situation you would only want a deploy option for out in the field.

@kinger37 While now this is off point, it started me thinking…

There is an older linux version that could be used in FOG post install script to set/change the boot order, I may need to play a bit with my dev environment.
http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=K3RNG

While this reference shows how to enable the TPM chip with MDT, the concepts are the same for dealing with a bios password with cctk.
http://www.daina84.org/bitlocker-mdt-dell-and-tpm

@Wayne-Workman said in Rudimentary Shell Script - SVN Update for CentOS 6.7:

The best suggestion still stands though - move to CentOS 7. There’s no reason not to, it’s a free and open OS.

I would be totally for it, although this server does nothing but sit there and run fog – which is what a server is supposed to do, now that I think about it.

That main reason is redoing the hardware RAID and making sure that is all set right as rain, and that all of our images make the transfer. It’s one of those too much to do in too little of a time frame – I mean this server has been here about 4 years before I got this position and it was still running FOG .29 (While the most updated version was 1.2.0).

More or less, I am stuck with it for the time being.

In place upgrade probably should not mess anything up, but the should is what I am skeptical about.

Hi,

normally every common installer has silent parameters, if not just googling will bring you sites that may list such parameters, even when hidden. So installing software is in normal not more then a single batch line.

One example: http://www.itninja.com/

Regards X23

@cerebron That is a great tip! Thank you for posting!

#wiki worthy