Re: Quick Host Registration not working on FOG 1.5.3

I am seeing this on a fresh install of 1.5.4. I was able to manually add the host from the web gui.

It works now! Thank you for all your help!

I decided to wipe the files and download them again. This time it worked. I ran the fixparts and then I restarted to capture the image. It booted up to capture it but says that the NTFS partition is unsafe.

There were no errors after the wget commands. I am running Fog 1.5.4 with bzImage 4.18.11 and bzimage32 4.18.11

Here is the error I get after following those directions:

It says fix parts is missing.

@Tom-Elliott Could not fix partition layout (runFixParts)
No matter what I do, I just keep getting that on trying to clone Windows 10. Windows 7 works just fine.

I am circling back to what prompted me to do the kernel update in the first place. When trying to clone Windows 10, I was getting a Could not fix partition layout (runFixParts) error. I updated the kernels to the ones released on October 2, 2018 and I am still getting the runFixParts alert.

You rock! It was .fogsettings file that had the old password. That timezone error just threw me for a loop.
Thanks!

I have a new FoG setup. It is on a HyperV Generation 2 VM. Everything seems to have gone ok but we can’t seem to clone Windows 10 machines. We received errors about the partitions. I researched this and found I should try some new kernel images. When trying to update the kernel, I received the following error:

Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 463, Message: ftp_login(): It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone ‘UTC’ for now, but please set date.timezone to select your timezone., Host: x.x.x.x, Username: xxxxxxx

I have made sure FOG and Centos 7.5 are both set to UTC. I have also tried EDT but that hasn’t changed this error. Is there anyone out there that has seen this?