Creating an image from scratch was the solution to my problem. So further trouble shooting/hacking is not necessary :-) Thanks for the help!

@Sebastian-Roth I believe there is a configuration where you can (ICH9 chipset + virtio-net network adapter)

@Sebastian-Roth Works fine for me on all the flavors of 10 we use. LTSB LTSC and 1703 1803

@samuel You can set a kernel parameter in the iPXE menu options to make machines shut down on deploy (or other tasks). Go to the FOG web UI -> FOG Configuration -> FOG Settings -> General Settings and add shutdown=1 to the field FOG_KERNEL_ARGS.

@Sebastian-Roth said in Debian Buster upgrade: @George Upgrading from 8 to 10 is quite a step. Probably something we have not tested. Please take a look at the settings file in /opt/fog/.fogsettings - find the line starting with packages=… and remove that from the file (good idea to make a backup copy of the file before you do this). Then re-run the installer. Thank you that solved the issue. I had to remove also from apache the php5.conf and php5.load and everything now is up and running.

As we have had so many requests about this topic I have tried to sort this out and properly fix it. Turned out to be quite hard but I hope I got it now without causing any other harm. @Tom-Elliott Can you please take a look at this commit and let me know if something jumps at you that could cause us trouble. I mean I have tested things a bit but as I had to change code right in the FOGController class I am unsure about side effects this might cause. What do you think?

@merrittw What tools are you using to manage your linux infrastructure. I know Ubuntu is the bane of FOG devs but we use it in our environment because i can push updates regularly to all our hosts with Landscape.

@george1421 Looked into this and it is exactly what I am looking for. Thank you very much George.

@danblu3 said in Issues with cloning from 1TB HDD to smaller SSD: deploy began but exited on error 4 Can you take a clear screen shot of the error? The context of the error as well as the kernel parameters might help diagnosing the issue. Also can you post the output from these commands cat /images2/<image_name>/d1.fixed_size_partitions cat /images2/<image_name>/d1.minimum.partitions This will give the geometry of the original drive. Also just be aware that if bitlocker was enabled it could cause issues restoring to a smaller drive, plus you will need to enter the bitlocker unlock key to boot the new target system. Lastly depending on how the data is spread out in the partitions it may not be possible to shrink the partitions to fit the smaller media.

@rhulet Ok, nice! You will find the new kernel binary in fos/kernelsourcex64/arch/x86/boot/bzImage. Copy that to your FOG server in /var/www/html/fog/service/ipxe/ but I suggest you rename the original bzImage in that directory instead of overwriting it. Just so you have a surely working backup copy of the kernel. Now, applying the patch I notice that I gave you instructions for building our current kernel version. But for this stuff you need to use a newer one. Sorry for that. Move that 4.19.64 code out of the way, you might want to use it some other time: cd fos mv kernelsourcex64 kernelsourcex64_4.19.64 Now add the patch and build the newer kernel: export KERNEL_VERSION=5.1.16 ./build.sh -kn -a x64 wget https://ozlabs.org/~benh/nvme-mac-5.1.16.diff cd kernelsourcex64 patch -p1 < ../nvme-mac-5.1.16.diff make This will get you the same kernel version I built for you some days ago. But there also seems to be a patch for kernel 5.2. If you want to give that a try instead: export KERNEL_VERSION=5.2 ./build.sh -kn -a x64 wget https://ozlabs.org/~benh/nvme-mac.diff cd kernelsourcex64 patch -p1 < ../nvme-mac.diff make This last one is untested.

@TigerTran What Linux OS do you have? My guess is you have Ubuntu, right? Did you read what is mentioned in the official release message? https://forums.fogproject.org/topic/13488/fog-1-5-7-officially-released Please make sure you say NO if asked about removing and re-installing PHP and Apache when upgrading to 1.5.7 on Ubuntu!!! There is an issue within the installer trying to switch to MariaDB that causes a problem on Ubuntu installs otherwise. If you have such an issue see here: https://forums.fogproject.org/post/126476 and https://forums.fogproject.org/topic/13447/lost-database

@Sebastian-Roth https://github.com/FOGProject/fogproject/commit/d3a70dd417eb1d08b48a637e26ec8776f4409d29 I commented out the “style” info you put, and moved it to push info out to the left instead of the right so that the form field is still accessible when reading the information.

@ITCC Let us know what exactly you are trying to achieve. The AD settings are meant to be used for domain join and from what you write I get the impression that you want to misuse “Name Change/AD Join Forced reboot” to forcefully log off people from their machines. Maybe this is just a misunderstanding on my side but you keep calling it “force logout” and therefore I get the impression. There are other ways of doing this. The web is full of it: https://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-to-force-logoff-from-command-line/8e7507e0-12c8-4ac7-8d5e-a1917e4af997 (using shutdown /l /f command) https://social.technet.microsoft.com/Forums/en-US/1c525aa7-5b09-45fb-ad47-56c41f1df2bc/force-user-logoff?forum=win10itprogeneral (using GPOs) If you can’t make it work this way you need to explain to us what exactly you want to do. We won’t change this otherwise! Just as a side node: I have not really looked into what needs to be changed but I can imagine this being a change in the fog-client code as well. There are many other things that needs fixing before we’d get to change that in fog-client. You are more than welcome to dig through the code yourself and implement the change. I am not saying it cannot be done.

@Wayne-Workman Sorry this has been without attention for a long time! Not only this topic but all the others: https://forums.fogproject.org/topic/11868/how-to-change-colors-on-bandwidth-graph https://forums.fogproject.org/topic/11999/bandwidth-line-colours https://forums.fogproject.org/topic/6912/can-i-change-the-colors-of-the-tx-rx-graph I played with the things mentioned in the other topics and figured that it seems to pick colors just by itself if we don’t force it to use our colors. When I remove the color scheme as described I get the following picture: Please vote if you find this appropriate. Sure the more nodes you have the less obvious distinct colors there are. But from it’s still better than using a successive shade of whatever color you start from. I’ve tested this in three different browsers on a Linux machine. I would imagine this working nicely on Windows and Mac OS browsers as well. What do you think @Tom-Elliott?

@JJ-Fullmer I commented on your PR, I’m concerned about the licensing.

@Sebastian-Roth hi, yes: they have the same settings, they are all from the same batch (production wise) I believe the system partition is the issue. I tried imaging on legacy and uefi, issue doesn’t change. Tried to wipe the disks first, also no change. Will try the full copy tomorrow, thanks for your suggestion.

@Lugga said in Installed Snapins shown as not installed: BUT: In the FOG Webinterface it is shown as not installed. As Tom said, FOG only tracks the return code but not the status of a software installation. Do you mean the return code? What happens if you run your silent office installer from the command line and check the return code? Be aware that fog-client runs as a service and uses the SYSTEM account therefore. So testing things with a user account might give you a different return code. If you want to try it as SYSTEM you need to look into using PsExec. Search the forums for that.

Hey George, No worries on the delays. Work’s been busy for me too, but today is slow finally. I realize I messed up how I explained things. I was creating a template host with the same exact name as the group. After not being able to get it working, I tried your example name of TemplHost01 for both a new group and new host. I set the details on the host, added it to the group, and still nothing. So I just tried again today, and the functionality is working as expected. Curious … I wonder it just needed a little more time. I’ll play with it a bit more and see if everything seems to be good. Yeah, it definitely seems to be working better now, including with groups/host-templates that I name. I’m not sure what was happening the other day. One thing which seems like a bug: if I’m in a group and I navigate to Membership to then search for and add additional hosts, it only adds one at a time even if I click the checkbox for multiple.