obijon

The FOG Service (you did include it in your image didn't you?) will make the change after imaging a computer, generally within a minute or two after the client boots. It only does this once, it won't keep trying to join. Before you uploaded the image the FOG Service should have been installed and the FOG server IP entered into the client. You don't need netdom with newer versions of FOG. Make sure you have followed the FOGCrypt instructions to set up the AD section on the server with hashed password. Some people (myself included) ran into trouble with the backslash in "domain\user" being stripped out. To fix this I had to use "domain\\user". I think this was fixed in a recent version IIRC. Hope some of these random thoughts help.

I found the problem, it was a desktop broadcasting DHCP requests but never getting an IP for some reason. This was flooding the network with 3.7Mbps of broadcast traffic, apparently enough to overwhelm the APs. Not sure yet if the nic is bad.

I'm stumped, and must not be seeing something obvious. Yesterday everybody who connects wirelessly lost their connection to the Internet. Once or twice they regained the connection for a very short period. They stay connected to the AP but with "limited or no connectivity" (auto-IP is assigned). I can remotely manage the APs so I know they are not down. DHCP is provided by a single domain controller, and it is working fine for wired computers. Windows Firewall is disabled domain-wide via group policy. I have about 700 wired and 70 wireless computers at my school. Laptops are serviced by several APs of various brands (some DD-WRT but not all). The APs are scattered across the school, and are not centrally managed (most are of the Linksys WRT54G variety but there are a couple Cisco WAP4410s as well). On one of the laptops I set a static IP in my subnet and was still unable to ping through the AP to anything on the other side. This rules out DHCP as a factor. Several laptops became the Master Browser for the domain and when I disabled the Computer Browser service for the most recently elected laptop the DC immediately generated an event that the DC had been elected the master browser. This seems to indicate that some traffic is getting through the AP - how else could the DC have known that the laptop was no longer the master browser? I confirmed that Windows Firewall is disabled. I think the browser elections are a symptom, not the cause. My gut feeling is that there is elevated broadcast traffic on the network and the wireless clients are effectively experiencing Denial of Service. What am I missing?

Workaround for that bug is to use DOMAIN\\user in group settings (double-backslash).

I've seen malware proxies that stop serving pages after awhile (probably buggy). Does your network use a web proxy by chance?

By "dysfunctional" do you mean the mouse cursor jumps around the screen and randomly selects or deletes text as they are typing? If so, it's probably because they are brushing the touchpad with their palm ever so slightly. Try disabling Tapping in the touchpad settings of the Dell touchpad software (touchpad icon in the system tray). When they carry their laptop to another room they may be sitting higher or otherwise changing how they use the laptop. If they must have tapping you can reduce the sensitivity of the touch later (after you've established the problem is due to tapping).

Flashing amber is often a failed power supply - easy swap if you have a spare.

Good to know, thanks for the correction.

Something else to be aware of is that AD is joined only after imaging. To my knowledge you can't force a join via FOG without reimaging. Edit: See post below.

Thanks, setting FOG_HOST_LOCKUP to 0 made all the difference!

I think it is due to the new "Host is up" red/green lights that display beside each host name. Viewing the page source shows that jquery is loaded in the HTML HEAD section. Not sure if it was being loaded with 0.28, though I don't recall any javascript being used before 0.29. I see the slowness in IE8, Chrome7, and Firefox3.6, especially listing hosts and editing hosts. The 0.29 web gui is much slower for me than 0.28 was. As much as I like the idea of the "Host is up" feature I'd rather have the quickness of the GUI back. I am on a gigabit LAN with ridiculously well-spec'ed server and web client, so it definitely appears to be a slowdown that was introduced into the latest web admin gui. I would like to see an option to disable the javascript portions, assuming that is what is taking so long to load.

Thanks Cools, I should have tried updating to 0.29 first - that did the trick!

Sorry to resurrect this topic, but I am having the same problem with FOG 0.28 and am wondering if you found a solution? I have tried every kernel. This has unexpectedly started happening with ALL my systems (including systems that used to boot fine).