Thank you!

I don’t know all of the ports in use but here is a quick list of what I know:

UDP 9 (Wake on Lan)
UDP+TCP 20/21 (FTP)
TCP 80 (Web)

UDP 69 (TFTP/DHCP???)

NFS uses many different ports and We (fog) are telling NFS to go over TCP if that’s any help.

Multicast will generally use all UDP Ports and it varies. But our defaults are anything from 49152 thru 65534

Hopefully this helps. I may have missed a few ports too but this could help you out a little.

Ahh, good to know that’s the intent then. Thank you.

A simple method is to create a folder in “c:\windows\inf” . I use “c:\windows\inf\xinf”.

Because Windows 7 recursively searches folders for drivers, and since Windows 7 searches “c:\windows\inf” by default, there is no configuration required other than to drop each extracted driver into its own folder inside “c:\windows\inf\xinf”.

Be aware, that some drivers are coded for both x86 and x64. Some will load x64 when x86 is required or vice versa, causing a failure of varying degree.

Some drivers for some versions of hardware will load the wrong version and brick the system. I’m looking at you Intel USB 3.0 eXtensible Host Controller (series 7 vs series 8).

I’ve dropped x86 and x64 drivers that play nice together into my xinf folder. I then use a vb script called from sysprep that detects specific needs for specific make/models that we have in service, that then performs installations and configurations, all the while using auto-logon.

Importantly, I disable and set to manual, the FOG Service before I close an image with sysprep. Reactivating the FOG service is the last thing my script does because the FOG Service will ungracefully interrupt any running scripts and force a restart when an image is deployed with naming and domain-joining enabled.

There isn’t a specific number but the total number of hosts in the task, but what you could check is that the FOGMulticastManager service is frunning as well.

[code]sudo service FOGMulticastManager stop
sudo service FOGMulticastManager start[/code]

because the image part, iam working on. and iam not so good at making an universal image of evry singel windows version 🙂 thats why

from the licensing brief: “you may use an OEM recovery image on devices shipped by that OEM provided that the device is appropriately licensed.”
[SIZE=2]if you are restoring computers to backups of themselves, you are perfectly legal. you said you only have 14 computers, so i’m going to assume that the hassle of [/SIZE]acquiring[SIZE=2] volume licensing isn’t worth it for you.[/SIZE]

Thanks for the replies.

you’ll want to edit the default storage node info on the storage management page to change these settings.
i have never used clonezilla, but it might be more in line with what you want

Yes it is possible , no it is not a plugin. Fog configuration-> fog settings -> quick reg settings I think

The location plugin was built to do exactly this. Even down to downloading the init.xz and bzImage from the rekavant location.

Goto FOG Configuration -> FOG Settings -> Plugin and enable plugins. Then go to the plugin page and choose activate plugin. From there choose the locationbplugin. It will install kind of. Choose install plugin and select location. It will ask to install itself. Then you will have a new menu option available. Go to the location page and set up you locations.

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.