Topics created by xburnerx00

@Tom-Elliott @Wayne-Workman In this case here the installer error was actually helpful to prevent from later issues with two IPs on an interface that were not intentionally configured.

I don’t think it’s worth the effort changing the scripts but feel free to go ahead.

@xburnerx00 It is possible with most DHCP servers. You wanna read through this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Found and fixed - the .fogsettings file was clearly corrupted causing this issue. Very sure this was due to manual editing.

Edit the file /opt/fog.fogsettings and replace the IP address there.

Then edit the /tftpboot/default.ipxe file

in the fog settings and default storage node change the IP there.

Finally rerun the fog installer once again to fix the rest of the bits.

@Tom-Elliott Thanks for clarification. So from the description it sounds like this is working as intended. The queue is no handled in order but whichever comes along first grabs an open slot.

Thank you for this information. I will have to come back to this at a later date though. I really do want to continue with this but our school district is in the middle of preparing machines and we’re relying on FOG heavily right now. I am not a Linux user so everything is new to me right now, so if we lose FOG, it will set us back a bit. Once projects are done I will come back to this. Thanks again.

Yes, the Dell Latitude 3189 are laptops that do not have internet ports and we had to use USB adapters. At that time, the version of FOG didn’t like same MACs for multiple machines. So the way I got around that was deleting the hosts since it was tied to a MAC from a USB and I was more concerned with just getting them imaged. I guess I deleted them prematurely. Unless I just overlooked something completely and did something wrong.

As for the deploy task ones, I’m not sure why they were stuck in there. They may have been ones that seemed to be giving me imaging problems and I turned off the machine before canceling it in the task menu.

@xburnerx00 The short answer is it should just work if you have the dhcp boot options set.

With that said, let me explain why this usb boot disk exists in the first place.

We have historically seen the pxe booting process hang (stop/freeze/abend what ever you want to call it) in 4 spots that causes the FOG admin troubles.

Either the computer doesn’t have a pxe boot option or for what ever reason iPXE isn’t being sent to the target computer. iPXE is delivered to the target computer but iPXE will not startup iPXE will start up but will not start up the FOS Linux kernel (bzImage). We almost always see this in uefi mode due to buggy uefi firmware on the target computer. In uefi mode the imaging tech is using a network adapter not supported by the computer manufacturer so pxe booting isn’t an option.

So what the FOS Linux usb boot drive does is boot into Grub and then calls FOS Linux directly from the usb flash drive. This bypasses pxe booting and iPXE eliminating the above conditions. In this setup the Grub menu is a weak analogy to the more capable dynamic iPXE menus.

We did include iPXE boot loaders on the flash drive to boot iPXE directly from the usb boot stick instead of by PXE. By doing that we can eliminate issues 1 and 4 from above. But any issues with iPXE in 2 and 3 would still exist.

@xburnerx00 said in Image not compressing:

I wanted ssd but people in charge dont think they’re worth it for old machines

They are looking at it from the wrong direction. For $60USD you can extend an old machine’s life for 2 more years. Then you move the SSD to a new old machine. There is very little price difference to not switch to an SSD. Understand that you don’t need a 500GB disk because most of that is wasted. Windows 10 is happy to fit in 70GB of space. So if you don’t have much data a 127GB or 256GB is more than enough.

But I understand what you are saying, its not your checkbook that pays the bills.

Thanks for the information. Relieves some of my worries.

Yes, I’ll try to get to those. I am under a time crunch right now so I can not get to that right away.

I deployed the image that gave me the error after it was created, and it deployed successfully.

@george1421 Can confirm, had to switch to ProxyDHCP after the ISP upgraded the modem that has a buggy DHCP implementation (turning off DHCP makes it not give out IPs but the DHCP server is still running so it just NACKs all the IPs lol)

@xburnerx00 Sorry for the delay! It’s a topic that I need time to work on and I didn’t have much of continuous time to focus on this.

I totally understand that you’d like FOG to remove printers from a PC again. Did you use “FOG Managed Printers” or “Only Assigned Printers” in the settings. Both should remove printers that are not assigned to the host.

That said I understand that you are in doubt as using the PrinterManagementHelper left you with an undeleteable printer and the fog-client wouldn’t even create your printer in the first place.

I have just spun up a test setup and cannot replicate any of the issues. Don’t get me wrong, I am not saying there aren’t any problems with printer management but I can’t see them in my setup yet.

I have a Windows 10 1803 install, working as normal user (not Admin), assigned printers in the webUI were created properly and also removed when I unassigned the printer for this post.
As well I tested the PrinterManagementHelper, printer was created and I could also delete the printer (Right click -> delete) without any notice or issue.

So I guess there is a lot we have to dig up first before we can address the issues. Let’s start by comparing the setups. Which version of Windows do you have and is the account you are working on an Administrator or normal user account?

I can imagine this being caused

But this task is not as trivial as you might guess. E.g. when you remove a printer from the list of printers for one particular computer we’d need to keep track of this in the background to be able to do the removal on the client PC itself. We

Thank you. I’ll look in to it.

Yes, what you say helps. I am new to fog and coming from using other device management programs so I am learning how fog works. It’s just a little new way of thinking for me right now. Not that this is a bad thing, I’m truly liking how fog works.
Thank you

@xburnerx00 The fog-client is running as a service (system account). It’s probably not able to write into a users home (Desktop) directory. Try using something like C:\Temp and make sure that is writeable for everone…

@Sebastian-Roth
Ok, Thank you for the help. I will have to research snapins some more. It seems the issue for this post has been resolved. So I will mark that post as the answer. If I have anymore problems I will make a new post.