Topics created by Paul Fuller

The FOG client and service will rename and join computers to the domain if you have the following:

[LIST=1]
[]Client registered with FOG and given a name
[]Fog Client installed on the client machine/image.
[]FOG server running on the client machine
[]HostNameChanger enabled on the client through the ini file or settings when you installed the FOG client software
[]HostNameChanger enabled globally on the server settings: FOG Configuration -> Hostname Changer -> enabled
[]HostNameChanger enabled for the host in the host record’s service settings.
And Optionally:
[*]You have FOGCrypted a password for a user account that can join computers to the domain and you have put this info in the FOG Settings.
[/LIST]

Paul, have you tried a different kernel? Sounds like the driver for your Lenovo might not be in the kernel you are using.

As I understand it, multicast is a form of broadcast which means that it will be sent to all nodes attached to that switch and on the same vlan.

What has an effect on speed is everything In between. Ie a cat 5 cable that snuck in there by accident, a FUBAR nic on one of the hosts etc etc.

IGMP allows the broadcast traffic to be directed towards those in the multicast session, rather than every device on the vlan.

After a switch upgrade, cabling and patching upgrade to make sure the lab was completely revamped, my multicast speed to 30 computers went from 500MiB/ min to 4.01GiB/Min.

The culprit was a dodgy patch on one of e hosts.

You can spend thousands on switching, but if you have a dodgy $5 patch, or a cat 5 cable in the mix etc, your multicast speeds will suffer.

I’ll have to experiment a bit more. I’ve had the machine start up several times remotely or started up + memtest but it won’t automatically start as part of an imaging task.