This is my first time using the new UI - wow! Huge upgrade.
Posts made by MRCUR
-
RE: FOG 1.5.0 RC 13 and FOG Client v0.11.14 Released
-
RE: Hp 440 G4 boot issue
@george1421 That did the trick. Thanks @george1421!
-
RE: Hp 440 G4 boot issue
@george1421 I get a warning about CSM not being available but hitting enter allows the laptop to boot. I suppose I need to remove the “hdbios” and “biosexternal”.
-
RE: Hp 440 G4 boot issue
@george1421 That’s apparently the default in my conf file. I’ll set it back to refind and see what it does.
-
RE: Hp 440 G4 boot issue
@george1421 Having tried each of the exit types without success, any other suggestions? Perhaps a kernel update?
-
RE: 1.3.1 - Quick image fails with "operation not permitted"
@Tom-Elliott I didn’t see it mentioned in the release notes hence the post. I’ll update.
-
1.3.1 - Quick image fails with "operation not permitted"
Server
- FOG Version: 1.3.1
- OS: Ubuntu 14.04 LTS
Description
When attempting to run a quick image on a previously registered host from the PXE menu, you get hundreds of lines showing the ipxe URL. Eventually you see a “Could not boot: operation not permitted” error and the task ends. This does not happen if the task is done through the web UI.
Perhaps an issue with the location plugin?
-
RE: Help with Win10 Driver injection
@george1421 I can’t imagine the drivers would install correctly with the persist & do not clean set to true. This is probably your issue @kyle-heath.
-
RE: RC19 - Server sending magic packets to all hosts
@Tom-Elliott Haven’t had it happen again yet.
-
RE: RC23 - Pending hosts do not delete when deleted
@Tom-Elliott I upgraded to RC25 yesterday and have not been able to reproduce the issue again.
-
RE: RC23 - Pending hosts do not delete when deleted
@Tom-Elliott I agree that it should appear in pending if it’s not in the host DB but the client is installed on it and reporting to the server.
The issue is that when I delete the host from pending hosts (I’m not approving it), it should not still be added to the DB as a valid host.
-
RC23 - Pending hosts do not delete when deleted
Server
- FOG Version: RC23 (6018? Tom custom build we’ll call it)
- OS: Ubuntu 14.04 LTS
Client
- Service Version: 0.11.5
- OS: Win 10 Enterprise
Description
If a new host reports through the client and shows up as a pending host, deleting the host adds it to the DB. Selecting approve or delete does the same action - registering the host in the DB.
-
RE: RC19 - Server sending magic packets to all hosts
@Tom-Elliott Just want to clarify one bit of the WoL issue I saw - it wasn’t one big packet trying to wake a ton of MAC’s. It was thousands of individual WoL packets each with their own MAC to wake.
When I caught this yesterday, there was one task in the system to do a deploy. I couldn’t even find any WoL packets trying to wake this machine coming from Fog. Instead, of the few packets I checked, they were for random machines all over the district. And for many of them, there would be upwards of 50-100 WoL packets for just one MAC.
Is there a system level way for me to disable WoL? Could that be added easily? We don’t use WoL at all currently and that isn’t going to change anytime soon.
-
RE: RC19 - Server sending magic packets to all hosts
@Tom-Elliott Upgraded both primary & storage node to RC 23. Unfortunately now I can’t get the image replicator service to start (I’ll open a new thread). I’ll see if this crops up again and take another packet cap if it does.
-
RC19 - Server sending magic packets to all hosts
Server
- FOG Version: RC19
- OS: Ubuntu 14.04 LTS
Description
Since upgrading to RC19, I’ve randomly been getting notifications from a few switches about packet loss. All of these switches are in the same VLAN as the Fog server. After taking a packet capture, it’s clear that the Fog server is sending massive amounts of WoL (magic packets) to seemingly all the hosts in the DB (over 10k). There was only one task on the server at the time.
Restarting the server stops this behavior. Starting a single task (and selecting WoL) results in the appropriate WoL packets going to the host’s primary MAC.
-
RE: Surface Pro 3 - ipxe issues
@george1421 @Wayne-Workman This still exists and is working for me with SP3’s and SP4’s. I could not get either model working with ipxe.efi.
-
RE: Surface Pro 4 Type Cover
@Tom-Elliott This isn’t an urgent issue for me (I’m imaging the last SP4 right now), but I keep a SP4 w/ SP4 Type Cover so I can test in the future.
-
RE: Surface Pro 4 Type Cover
@Tom-Elliott Unfortunately I don’t have a USB hub so I’ve been using the SP3 Type Cover for our SP3’s & SP4’s. I’ll just keep this in mind if any of the SP4’s need reimaged.
-
RE: Surface Pro 4 Type Cover
@Tom-Elliott Yes, I believe so. Keyboard input works on the Fog menu (I was able to auth to do an image task).