many many thanks 🙂 I really appreciate you guys so much!

[quote=“Tom Elliott, post: 36510, member: 7271”]If you have the po, can you post the file and I can try getting it compiled for you?[/quote]

The po file is from the [U][URL=‘http://fogproject.org/?q=node/26’]FOG 1.2 archive[/URL][/U].
I put it in attached file.

[url=“/_imported_xf_attachments/1/1366_fr_po.zip?:”]fr_po.zip[/url]

Okay in that case, I would build the image on a virtual and a physical machine. You need to enter audit mode and then sysprep your image and upload.

I recommend using a physical and virtual environment, as my machines I had to build the image on the physical machine (it has something to do with the hardware in the computer.) After doing so and uploading the image, I was able to image my problematic machines without errors.

perhaps what you need is a snapin that replaces the config file with site specific versions

[quote=“prince xyryl, post: 36350, member: 25316”]up…

[B][COLOR=#ff0000]how? Where?[/COLOR][/B]

I cant see this on my FOG management page ([B] Download the FOG Client Service)[/B][/quote]

[url]http://youripaddressofyourfogserverhere/fog/client[/url]

Alternatively you can use the links at the bottom of the management page to get to the client.

technically yes, in a practical sense no

Thank you, that really helps a lot!

Thanks [URL=‘http://fogproject.org/forum/members/mentaloid.4362/’][B]Mentaloid[/B][/URL] for your reply.

No, I am not using Multicast. The last time I used it (with FOG .32), when I went to deploy Multicast, the switch and PCs chocked (it said something ridiculous like 10 hours or so to deploy the image). I don’t know if the switch supports it or not. Unicast to 1 PC does yield much better download speeds, at least 3 GB/min, sometimes more. When you start adding, though, the speed decreases to around 900 KB/min to 1ish GB/min for all 15 PCs being imaged. The switch is a gigabit switch. All 15 nodes are Dell 780s with Gigabit ethernet, and the server also has 2x 1 GB ethernet ports. The server runs Ubuntu 14.04 LTS. (I built the server in early July.)

So, if I try to implement bonding, I take it that it will not help much if the switch doesn’t support it? The reason I ask is that when I looked into this, there were several bond modes and only mode 4 (802.3ad) specifically specified needing support on the switch end.

Thanks again!

if you run that again, it will probably say 1.3.0. i think Tom changed those values now
the svn trunk is the developers branch, it is what will become 1.3.0 when we decide to label it as such, just as it became 1.0.0 1.1.0 1.2.0 and 1.2.1 when we felt it was worthy of those labels. as a developers branch, it is always increasing in features, and varying in stability/functionality.

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?