You know I read through that… And could have sworn it was for .32

Many thanks !! It’s been a long week 🙂

[quote=“Ericsj860, post: 36176, member: 25563”]I was wondering if anyone has experience imaging Ubuntu across different hardware? With windows machines I know there are different steps to take when imaging across different hardware. Does anybody know if this is the same for Linux?[/quote]

If I get this correctly, your asking about deployment for Linux (Ubuntu) clients?

If yes, then here’s what I would surmise:
A) most current distro’s/kernels are all modular - EG, the kernel will load any needed modules (other than disk access) as needed for most hardware. HBA modules should be for the most part included (ata for the large majority of client computers).
B) Video support could be an issue - Linux frame buffer and X11 (Gnome) settings are usually tailored to the client computer’s video adapter and monitor.
C) Ethernet devices tend to get static names if they are not virtualized = EG, a NIC that came up as ETH0 in the master computer is not available in the client computer, and while there’s only one NIC available, the “new” NIC will be ETH1. A script would have to be written to remove the persistent-net-dev entries.

Other than that, I don’t see anything off the top of my head that would pose an issue. If your familiar with linux (Ubuntu), this should all be scriptable. FOG itself does not have any “oobe” type prep tools, and I’m not aware of any that are available otherwise for Ubuntu.

You can click on Fog Configuration icon across the top, it will, by default, show your version information when it loads. It will also tell you whether you are up to date.

performance can depend on a great many things.

I run fog in a VM, and I can throw data out at speeds where I can image a PCs in 10-15 mins. multiple at a time.

Hi everyone

Does anyone tried to boot hirens boot cd from network

The kernel that you update in the gui is only for the Host architechture.

The defaults are:
bzImage (64 bit)
bzImage32 (32 bit)

With manual deploy i used fdisk -c=dos to create partition with start sector 63. Don’t know if it makes any difference.

[quote=“Junkhacker, post: 35813, member: 21583”]technically, yes
easily, no[/quote]

Fair enough. I’m off to re-upload a new image, then. 🙂

In my production env, I’m using Debian 7.6, fog 1.2.0 stock (with a patch to make multicast/scheduled tasks work), in a VM running under ESXi. Single storage node. Crazy reliable and fast. 6.3 GB/Min. Pushes an image out to a lab of 30 computers in ~10 minutes for a 30 G image. Task start to finish including sending Adobe CS 6 Master Collection as a snap in (yes… a snapin), along with several other largeish snapins is about 23 minutes.

Debian 7.6 is pretty much point and shoot for fog 1.2.0. I purging network-manager (debian and ubuntu) (apt-get purge network-manager network-manager-gnome) and statically configuring the network in /etc/network/interfaces as should be done for any server.

Thanks, for all your help. With windows I know there is different steps to take when imaging across different hardware. Do you know if this is the same for Linux?

Thanks ccmiens for link I now know the difference between the 2

Thanks
Gary🆒

Congratulations,

Wife/Home should always come first.

Ages ago I did some testing with BTSync for this. might be worth investigating… unless RSYNC suits you better.

the image folder would apply to one image. the images (note the ‘s’) would be all images.

thanks for your reply

Hi,

i was maybe a little unprecise 😉
Yes you can Update but expect some little problems that can be fixed.
And you need to know that your old images will work but you have to use the information i gave you above.

Regards X23

It can be yes.

You could make a NAS or SAN that automounts to the FOG server in the /images location as well.

gunzip -d -c d1p1.img > d1p1.img.clz
gunzip -d -c d1p2.img > d1p2.img.clz

Also, .ps1 (powershell) scripts will work if you have a system script policy of unrestricted
run with “powershell”
run with arguments “-File”

in the script, don’t forget everything must have a full path by default!