@Sebastian-Roth Thanks for the reply! Did an update to 1.5.5.1 two weeks ago. Everything works fine so far!

make sure clients have boot rom enabled in the BIOS - otherwise they won’t boot at all. in my environment :- 066 points to fog /tftp server 067 bootfile = undionly.kpxe

@AsGF2MX said in Compatibility check for X1 Carbon 2018: Well I’m now at the USB method and @george1421 thanks for the img. I got the usb to work. However I can’t remember the cli for the fog command. and the wiki page has the deploy section empty. Not sure why you need the debug command. You should schedule the task in the FOG server then usb boot the flash drive. Pick option 1 and it should boot into fos doing what ever the FOG server told it to do (capture/deploy).

@hancocza I totally missunderstood this whole topic right from the start. It would have helped a lot of you’d clearly mentioned that you are using a custom SSL certificate. Might be obvious but I did not get it. So what you describe here has nothing to do with FOG as far as I understand it. The password input stuff is something Ubuntu is doing when you start the apache webserver and you have a password protected private key. We as in the FOG installer does not add anything to that. So my guess is that Ubuntu changed things with one of the latest updates. Probably you just need to install the correct extra package to make this work again…

@Tom-Elliott I see, the storage nodes themselves are not meant for capacity but redundancy and throughput? Is mounting a network storage location viable to expand my capacity?

Unless, of course, you’re trying to make it core usable? But the only time this would be viable would be if LDAP plugin is in use. Of course other plugins may want to make adjustments here as well. I need to think on this a little bit.

@federico The ACPI messages sure look dangerous but usually aren’t. THe machine seems to have a buggy ACPI implementation. If you register this client manually in the FOG web UI you can set Kernel Parameter acpi=off to get rid of the messages. How long have you waited on that screen. It should eventually go ahead. Have you waited for 10 minutes to see if it proceeds?

@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.

@george1421, @Sebastian-Roth the only thing I foresee and maybe missed. Selinux won’t automatically be disabled because you made the change to the config file, it would require a reboot of the machine first. I would also, suggest changing from disabled to permissive. Disabling forces the file system to be unsupported and require being reestablished should you turn selinux back on. Placing into permissive mode keeps the file system contexts active and does not hinder usage. Plus you enter the command setenforcing 0 to switch selinux into permissive mode for the current running session which doesn’t require immediate reboot. DERP — Don’t mind me, I’m dumb. Looked again and see you do have it set to permissive and do run the setenforce command.

@Wayne-Workman Probably one of the configs were changed and the updater is asking what to do. The best I could find quickly is: https://serverfault.com/questions/259226/automatically-keep-current-version-of-config-files-when-apt-get-install/593640 Try: apt-get update;DEBIAN_FRONTEND=noninteractive apt-get dist-upgrade -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" --force-yes What a monster of a command…

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

@martial said: USB\VID_0BDA&PID_8153… Ok, we definitely have that driver included in our kernel config (since a long time). So I was wondering if other people had issues with Linux on this device. But seems like people are happily installing Linux on it despite some video card issues - see here. But no one complaining about network issues. So I went hunting for those USB messages and read about USB hubs or other faulty USB hardware here and there, e.g.: It seems the hub in the monitor went bad and was screwing with all other USB ports on the system Maybe just some faulty hardware? Have you tried different ones. Always getting the exact same error on every try? Then again I ask you for the third time (and last!), have you tried adding the Kernel Parameter has_usb_nic=1 to the host settings?? If this device is still unregistered and the error happens on registration you might just add the host manually via the web UI, add the parameter and try a capture task to see if that helps.

@Sebastian-Roth 1. This is a very new idea. Did not have chance to test wimlib yet. Next week will do so for sure. I have Samba NAS , will try with centos. 2. Another interesting wim usage scenario: WIM keeps in the A-image base Windows + B-snaphot with drivers + C-snaphot with sql server. And you decide what you want to restore after the Base. So for a host1 u have A+B. For host2 A+B+C. Instead of 3 images you must keep only one image +2 deltas.

@Tywyn I’ve tried to replicate the issue but just cannot get around. For me it works perfectly fine no matter there being only one or several hosts in the group. I am not saying there is no bug but I just couldn’t figure it out. As well looking through the could I could not see where things might go wrong with this. I know this sounds stupid but can you give me a detailed step by step run down on what exactly you do to make this error happen. I mean the exact things you click and enter. There might be a slight chance that the error only happens if one of the steps is done exactly the way you do it.

@tian Trying to catch up with older bug reports. Sorry for the late reply. As we moved to bootstrap this is just how those progress bars look like. Probably not as easy to change. I am marking this solved - won’t add.

@bretfred Trying to catch up with bug reports, sorry for the late response. I just tested creating multicast tasks with names like 123 and 2. Creating the task as well as multicasting worked like a charm. Possibly Tom has fixed that already. Marking as solved.