@Psycholiquid I don’t mind, I use VMWare myself 🙂

Yes, that portion seems to be working now. On to the next bug…

@Quazz @Tom-Elliott I set the task to capture and the progress bar on the desktop computer goes all the way though
Upgrading to the latest ver worked.

Thanks

A while ago I wrote a proof of concept tutorial for turning a Windows server into a FOG storage node. https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-proof-of-concept-blog

You can not add additional space to your fog server by sharing disks on another server. This method is asking for problems. But you can turn another server into a FOG storage node (so to speak). By using a fog storage node and a the fog location plugin you can train all of your computers to image from the storage node instead of the master node.

@Tom-Elliott

The IP the machine is getting both in PXE and when selecting any menu option is 192.168.91.242… within the specified range for that vlan. FOG server is on 192.168.91.243. No, the nic is an onboard broadcom nic on a dell optiplex 580

thanks. I emptied the drivers folder and it went through - perhaps the extra script information will assist me to find out why it failed when i had drivers in it. let’s mark this resolved.

@mahir I recommend you also update your IP in /opt/fog/.fogsettings (and other relevant IPs) so that when you update FOG it can put everything the way it’s supposed to be.

@Tom-Elliott

Very good, fantastic!
Re-insalled using the existing installfog.sh - did its thing (checked packages, database scheme etc.)

cd /root/fogproject/bin ./installfog.sh

WOL and postdriver scripts seem to be working again!
Thanks! I shall run this command below so it doesn’t happen again until I am prepared to get Ubuntu updates.

apt-get -y remove unattended-upgrades

Which, after running the install script again, worked fine. Thanks, @Tom-Elliott

@Tom-Elliott When I said I changed from zstd to gzip, I changed it in the image settings via the GUI, pictured below. Then I recaptured & redeployed and it worked fine.
0_1493855732085_zstd and gzip.png

@najeebrehman df -h will show you all of the mounted devices. lsblk will also show you the mounted (connected) devices, just in a different layout. Look for a device that has the same size as your usb flash drive. Then follow tom’s commands below substituting the drive (/dev/sda, /dev/sdb, etc) that is identified as your usb device.

RESOLVED: I was forcing https on the forward and as soon as I removed that it started working and I have already had 3 machines check in and they were the ones I just installed the client on remotely.

Thanks Tom. Just the switch on the AD Username did the trick. Thanks for your help so quickly…

James

@george1421 Windows was telling me after the second boot (inaccessible boot device) this was after the bootloader.

Regards X23

@Seydoo A “hash was the same no matter the snapin” leads me to think it was failing to get the file. When this would fail, it would cause the file to be nulled, so the hash being returned was that of a null value. (for all cases, which is why it was the same).

@garysaxon I sure would like to see the results of the following commands.

ls -la /images
ls -la /images/<image_name>

And then a screen shot of the image definition in the fog management gui.

Ok, so it looks like the default image engine was changed. Once we got the images added to the system and changed them from PartImage to Partclone Gzip they started deploying correctly.

Thank you Tom!

@Tom-Elliott
That did it. After that last update, I was able to deploy the raw image successfully! Thanks for working with me on this.

@fogusers That really doesn’t answer the question what happens after stopping web services failed? Does it return you to a command prompt?

Also in the …/bin directory (where you ran the ./installfog.sh command from) there is a log directory and in that log directory there is an install log with error and the version you are installing. Post that error log here for review.

@Jaymes-Driver

Late response, I know, but you’re right. I think the Ubuntu updated itself and reverted a change I had made with the link below. I had to go back in and blank out the SQL password again:

Is this Ubuntu 16.04? See here: https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_16.04#MySQL_password_behavior