Topics created by fry_p

@Tom-Elliott I love the new theme. I have seen the interface through all of the stages of development, from the 0.29 (grey fog as I called it) days to now. I think the new look is clean, sleek, and professional. Plus there are probably a number of things I can’t see directly that are improved on the backend. Well done!

@dylan123 As stated earlier, I got an instant “Failed to get IP via DHCP” error when I had just the dongle plugged directly in. I also am already using the “has_usb_nic=1” argument. Lastly. I have both the dongle MAC and the USB hub MAC listed in the host.

@george1421 Ah ok. I think I may be fine with the i5 and 8GB of ram in that model, but I do have a Optiplex 780 image that I can improve by lowering the compression then. Thanks for the tips!

@fry_p Once you’re into MySQL CLI - you can copy all the SQL commands at once.

@fry_p Your current efforts has not gone to waste. When the other method is proven, you will just move your patched fog.mag.reg to the fog server postinits directory and add in the postinit scripts to copy it over each time. What you have created to day will work just fine moving forward, you just won’t have to unpack and repack the inits after each change.

@falko Probably.

There is going to still be a “trunk” branch and I’ll still be doing (albeit much less than in the past) work on the PHP side of FOG, but really limited to bug fixes and minor improvements. I don’t expect any new features to be added unless it’s to support some new functionality in regards to the new FOG Client that we find useful enough to be added to the current channel’s of FOG.

As we get closer and closer to a functional element of FOG 2.0 (which will likely take a while) we’ll most likely give up postings to try to get our testers and other developers updated to test and report things.

@fry_p It could be a monitor, keyboard, mouse, patch cable, video cable, or power cable causing the issue too.

We had a computer “Spot” once that was just voodoo’d. It blue screen’d, I said OK. Image it. Fixed. A few weeks later, blue screen. I said, OK it’s a hardware issue. PC Replaced, boom fixed. A few weeks later, another blue screen. I said, OK, this is highly unusual, but I’ll image it. Fixed. And again, another blue screen.

After that last one, I went in with a replacement monitor, replacement VGA cables, replacement power cables for everything, replacement keyboard, mouse, surge protector, and replacement patch cable. The whole 9-yards. Everything but the physical desk and chair was replaced. And that fixed it. All the old crap I pulled from there was marked “bad” and surplussed, I didn’t even bother testing those items as they were old and low-cost.

@Wayne-Workman said in Windows FOG storage node and multicasting mess:

If it’s configured correctly, it should be immediate. Did you enable the graph for the storage node? Did you assign the storage node to the correct storage group and enable it? When installing the storage node, did you input the correct fogstorage password?

God, I’m striking out left and right. I changed the settings in /opt/fog/.fogsettings, but didn’t re-install, expecting the changes to be instant. What a dope I am…

Thanks for the info on changing the IP of the node. That’s not too bad and you’re right, having the latest of everything every time would be good.

@Joe-Schmitt said in Snapin Pack:

the one thing I’m seeing from those screenshots is that you have a sub-directory in your zip file.

I knew this would be confusing for folks, and there’s no way around it, people just need to understand the pathing. It took me months of here-and-there moments to wrap my head around it. So nobody would have to go through that, In the SnapinPacks wiki article, I explained this at very great length.
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@fry_p I have no idea but it’s pretty concerning. Please do regular exports of your DB using the web interface via FOG Configuration -> Configuration Save -> Export, do this once a day, keep the files safe.

If it happens again, do another export - so we can see what is in it, then move to the last good export.

Also pinging @Tom-Elliott so he reads through this thread.

@george1421 Ah this makes sense. My colleague notified me he uploaded an image and it didn’t seem to finish the task. That is when I noticed the disk was full. Got it.

@Scott-Adams You should first update to RC-10. You already have the file you need, it’s /tftpboot/ipxe7156.efi

Please use wireshark to capture a DHCP conversation from the surface pro 4, we are collecting vendor strings for these devices, it’s kind of important to us. With this, we can tell you exactly how to configure your DHCP server to serve this particular file to your Surface Pros, and this will help everyone else too. And it’s not that big of a request. In wireshark, use the bootp filter.

@fry_p My department manually enrolls over 1K Chromebooks about every semester.

That easy compared to putting the carts for them together and wiring them, figuring 30 power adapters in a space the size of a mini-fridge. If it’s not done thoughtfully, the carts will be completely destroyed by usage - cables strung everywhere. Sometimes we use 100 zip ties per cart.

@Tom-Elliott I don’t know what happened, but due to another issue, I updated to 8440 and the new host joined with no issue. So adding all of the existing hosts to a group and applying AD changes to them took care of those, and the patch to 8440 seems to have changed something that was keeping my defaults from populating on new hosts. Thanks!

@fry_p You didn’t do anything wrong. Thanks for at least keeping us posted.

@Quazz the extra debugging was actually an error in code base for the bootmenu which I’m pretty sure I corrected yesterday.

@Wayne-Workman said in Surface Pro 4 on 7977:

@fry_p Once DHCP is configured, you will never have to change it. It takes 10 minutes to setup, every step is laid out for you in here:

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

I was able to set this up this morning. Works perfectly. The only thing is we have many scopes in the building I set up Surfaces at, so I set the policy at server level. Thanks for the tip!

@Tom-Elliott Confirmed fixed in 7845

That’s why I post both. I have no idea what type your system is going to use so I just brute force them all.

In either case, this shouldn’t be a problem even on subsequent updates now.