@kratkale Ok, I finally got the time to get into fog-client development again. I am trying to answer your questions step by step.
About port naming: The field Printer Port is what you see in the Windows printing dialog as “Port name”. So if you put in 9100 it will be named 9100 but if you put in an IP the port will be named exactly as you want it. On the other hand if you want to specify a different TCP port for printing you put in x.x.x.x:9111 in the Printer IP field. I will change the field labels in the FOG web UI to make this clear.
Changing the printer setup on FOG changes sometimes nothing. (e.g. the name of the inf file - the printer …) My solution was to deploy the computer again …
I am not exactly sure if I get what you mean. Let’s see… If you change any of the settings in the FOG web UI while the fog-client is running on the computer the changes won’t be sent out to the client immediately. This is something I hope to change in the future but that’s how it is right now. But if you change things and then reboot the client machine it should use the changed settings!
-) Group management with Printers: If I update a group with the option “only Assigned Printers” the clients are not updated. The are still in the mode “No Printer Management”
This is a known issue I just fixed a couple of days ago. It will be in the next release!
-) How to install a local pdf Printer, when I use the option: “Only Assigned Printers”
Find out the settings used in the PDF printer (using the fog-client PrinterManagerHelper.exe or manually from the printer properties…) and set it up in FOG as well?! Should work I suppose.
@AsGF2MX said in Compatibility check for X1 Carbon 2018:
Is it just the kernel and init.xz that need to be swapped out?
You can try using the latest binaries but no promise this will work. Download and extract the archive. Then put bzImage* and init* into /var/www/html/fog/service/ipxe - probably best to rename the original ones and not overwrite.
We have seen numerous devices that simply hang after loading init.xz and quite often it turned out to be for different reasons. Some of them George has already mentioned. Also we had devices with buggy firmware that needed a specifically patched kernel binary to work around firmware issues.
If you are keen to get this working I am sure we can work on this. All depends on how much time you have. When do you need to deploy those (tomorrow, in a week, two weeks, after Christmas?) and how much time to you have to test debug kernels I would provide?
@cristianvalente said in ADK provisioning package settings won't apply after an PXE Boot:
Is somebody familiar with ADK and PXE?
Yes and they are not related. Provisioning packages are deployed from inside the OS. FOG doesn’t now or care about windows applications. Are you trying to deploy a provisioning package as a fog snapin?
Immediately before capturing CentOS 7.x I do the following.
# Direct next Kernel recompilation to include AHCI drivers & be HW generic
sed -i 's|#add_drivers+="|add_drivers+="ahci|g' /etc/dracut.conf
sed -i 's|#hostonly="yes|hostonly="no|g' /etc/dracut.conf
# Clean & Update the OS (includes Kernel recompilation)
yum clean all
yum makecache
yum update -y
# Shutdown
shutdown now
@DarkSwordsman said in Auto Deploy restarts PCs, but boots back into Windows:
We were originally playing with the idea of keeping PXE boot on and using the exit type to boot into Windows,
There is no way around it! FOG needs to have the clients to boot from PXE to be able to run the tasks.
but no matter what I can’t get it to work on UEFI with Windows Boot Manager.
This is the way to go. You need to play with the Boot options in the host settings till you get this to work. Please try all the different options like rEFind, sanboot, GRUB and so on. Take pictures of errors and document what you tested and why it wouldn’t work. I am sure we can help if we know exactly what is going wrong.
