The workaround was found. When I used diskpart and removed all partitions from the disk before cloning (used boot from regular Win10 installation usb media), after that Partclone ran as usual. Need to test on more laptops to be sure.

@pnwbsi I think we have a new fog.download file with some additional debugging output. This file will not fix the issue, but hopefully it will give us an idea what’s happening. We’ve identified the point in the code where it could be failing. I have this debug mode fog.download file here: https://drive.google.com/open?id=1yppCONpwr6zCOXA541rhOfiQNb-LoTYS What I want you to do is download this new fog.download file. Then I want you to follow these instructions to setup a postinit patch. What we are going to do is dynamically replace the current fog.download in FOS Linux with the debug patched version. https://forums.fogproject.org/topic/13500/dynamically-patching-fos-using-a-postinit-script You will follow the instructions but replace the top lines to this # Current File in FOS Linux to be replaced currfile="/bin/fog.download" #Patch file to send to FOS Linux virtual hard drive newfile="${postinitpath}fog.download" So the testing protocol I want you to use is this: Confirm you are still getting the error in the picture about unable to mount images folder. Then power off the target computer. Don’t touch the web ui, just power off the target computer. Setup the patching environment per the tutorial Download the fog.download file from my google drive and move it into the postinit directory on the fog server. reboot the target computer When the target computer throws the error again, snap a clear picture of the debugging information. This output will help us understand why…

@ckasdf I just pushed two commits to dev-branch to fix some of the warnings. Will work on the rest when I find the time.

@Fernando-Gietz Seems like we have introduced some PHP warning when adding that fix to dev-branch. See the PHP Warning: Illegal offset type in /var/www/html/fog/lib/fog/fogmanagercontroller.class.php on line 296 messages here: https://forums.fogproject.org/topic/13602/errors-in-apache-log-and-www-error-log I won’t revert your fix as I think you are totally right. It shouldn’t query the full userTracking table if it only wants the information for one particular host! But the problem seems to be the action array send with the query. I’ll have a closer look at this now. Edit: Nevermind, just pushed out a fix to dev-branch.

@ians said in Fog Client fails to join AD Domain with error 1326: I hadn’t even thought of the possibility that it could be the special characters in the password. I went ahead and created a new domain admin account and used only letters and it worked! Ohhh, do we actually have a special character issue?! Updating the settings on my groups also updated the settings on my hosts, yay! So this sounds like you were able to get things right and domain join on the client worked? Shall we mark this solved? About the group settings you want to use the forum search and ask it for “persistent groups”. My guess is that you are expecting something from FOG’s group capabilities that it doesn’t have.

@NTLINUX Yes right, fresh installs are not affected by this! Fresh installs on Ubuntu with 1.5.7 work perfectly fine.

The Menu I want to implement is the first file. The screen I want to paste into is the second file. As you notice, The pasted Menu contents goes sideways not taking the line breaks. How do I implement the menu that I was able to do in the old versions of fog?

@brakcounty said in Updating FOG and retaining settings: so i went ahead and ran the update and broke mysql and mariadb beyond repair. apt update --fix-broken wasnt working. so i backed up my images, and reinstalled ubuntu server and fog 1.5.5 fresh. i luckily had a .sql backup file i exported two days ago and was able to import it via web ui successfully. i also mounted my RAID array to “/images” and its working fine. i will hold off on updating FOG to 1.5.7. Thanks for the input! Sorry to hear you went through this. I thought my warning a day ago was clear enough but obviously it wasn’t. There was no need to re-install Ubuntu as the database was still existing in a different directory (/var/lib/mysql-5.7). I suppose it’s all gone now. On the other hand it’s good to know that you got things up and running again using the sql backup file. But it would have saved you a lot of work and trouble if you’d waited for my instructions. It’s fairly easy to upgrade to 1.5.7 and not break things but I needed to do a test on my end to make sure this is really working as I think it is before I would tell you. When you start the 1.5.7 installer you get to a point where it asks this question: *** Detected a potential need to reinstall apache and php files. *** This will remove the /etc/php* and /etc/apache2* directories *** and remove/purge the apache and php files from this system. *** If you're okay with this please type Y, anything else will *** continue the installation, but may mean you will need to *** remove the files later and make proper changes as *** necessary. (Y/N): If you upgrade from 1.5.5 or 1.5.6 you are save to say No (n) here! In this case you upgrade to 1.5.7 without running into the database issue!

As always, the community comes through! Not sure how this got askew, but following these directions I was able to fix the issues. The image pulled correctly and at the end updated the database info. The image is good, I am all set. Thank you again this was awesome!

@Atton If resolve.conf is managed by the NetworkManager (typ ubuntu or debian variant) application then you need to make those settings inside the networkmanager program. The other thing that would overwrite that file is if your fog server has its address defined by dhcp. I would go ahead and set the file manually and see if something along the way changes it. No guts no glory, I say…

@Wayne-Workman @george1421 I figured this one out… I was having problems with security. One of Windows 10’s recent updates (as in the last 3 months or so) was blocking connections to anonymous shares. It allowed them but they needed to be authenticated. For those of you who stumble across this post… Add your FOG server to your domain and configure Kerberos. After you do this you will need to configure your driver share. I have included the way I did mine and it works. This configuration is for using an existing domain controller. In our case, we use Windows Server 2012 to do domain control. Do the following: yum install samba* yum install krb5-libs krb5-workstation Confuguration Kerberos /etc/krb5.conf [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = YOURDOMAIN dns_lookup_realm = false dns_lookup_kdc = false ticket_lifetime = 24h renew_lifetime = 7d forwardable = true [realms] DOMAIN.TN = { kdc = dns-name-your-domain-controller } [domain_realm] netbiosnameyourdoamin = NETBIOSNAMEYOURDOMAIN netbiosnameyourdomain = NETBIOSNAMETYOURDOMAIN Configuration samba /etc/samba/smb.conf [global] workgroup = DOMAIN password server = dns-name-your-domain-controller:88 realm = NETBIOSNAMETYOURDOMAIN security = ads idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/bash winbind use default domain = false winbind offline logon = true log file = /var/log/samba/log.%m max log size = 50 passdb backend = tdbsam load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printerdrivers] comment = All FOG Printers path = /PATHTODRIVERS browseable = no guest ok = no writable = yes Add dns name in /etc/hosts Install and configuration ntp server (It’s important for use Kerborose authorization) yum install ntpd edit /etc/ntp.conf server ip-address-your-ntp-server prefer Create ticket kinit account-admin-for-active-directory@NETBIOSNAMETYOURDOMAIN Add server in domain net ads join -S dns-name-your-domain-controller -U account-admin-for-active-directory Create keytab for Kerberos net ads keytab create -U account-admin-for-active-directory Edit file /etc/nsswitch.conf passwd: files winbind shadow: files winbind group: files winbind Restart samba and windind Test net ads info wbinfo -t

@kkptrck said in Skipping partition restore (MBR Only): /dev/sda1 : start= 64, size= 1076291, type=27 I have missed one important thing here when you first posted this. The start sector 64 is quite unusual (usually it’s 63 or some other sector but I have not seen 64 yet) and I can imagine this being the cause of your issue. Did you manually do the partitioning?

@Luc-Novales Still waiting for you to test 01_undionly.kpxe! Please let us know.

@NIoSaT Thanks for testing! I will see if I can still fix this issue in the init scripts.

Hi Sebastian, Would you help us write the texts and find a good way to place them in the web UI so people definitely see them but don’t get annoyed? Although I am a developer, I’m not great with UX design. But I would think that some kind of info icon next to the drop-down list with a popup saying something like “Read about the image types here: [insert wiki link]” would suffice. It would draw the attention of anyone who is confused about the options, but is unobtrusive enough not to annoy anyone else. I’ve seen this somewhere, and wanted to make a screenshot, but can’t find it, so I made a mockup: This could be used in all kinds of places in the UI. You could even color it red, green or yellow depending on the importance or level of danger. These are just suggestions, and I’m not trying to do your job for you. If you want a pull request for this, I’ll need to figure out where the source code is, first. I’m not acquainted with your source code at all. The system restore actually worked. It seems that /dev/sda5 (the recovery partition) was still intact, and the “HP recovery” simply formatted /dev/sda3 and rebuilt the entire OS. I think the reason it failed before was because /dev/sda3 was not properly sized to fill the partition, which is what I fixed by rewriting the boot sector with testdisk. I won’t waste you time with this anymore, and I’ll make sure to take backups with Clonezilla and/or the Single disk (not resizable) option in FOG.

@zagaeski Definitely follow what George suggested! As well I am just wondering if this is a single machine or do you have several of those HP Probook x360 11 G1 EE and all show this issue?

@bogle The FOG server talks to the target computer via the FOG Client/service. That service has a check in interval that is set in the fog settings. So the default may be 5 minutes (300 seconds), so if you issue a task to the target computer it could take up to 5 minutes before the target system reacts. Also on the fog up/down indicator it doesn’t use a ping, but a connect to port 445 to confirm the system is up or not. If your windows firewall is blocking connections to port 445 then fog will assume its down.

@nelsonnc Sounds a bit like STP issue to me as well. The quickest way to check is to connect a dumb mini switch between that client and your building switch. See if that makes a difference. How do you know the client can reach the FOG server? When it’s booted to it’s OS from disk, can you open that exact URL in the browser on that client? http://dlk.fog.local/fog//index.php (double slash is not an issue)

Turns out someone was annoyed that our network went down and plugged in their personal router. Thank you for the advice.