@kyletmanel The error you posted says you’re not using a password. You should be providing a password if one is set. The command to access MySQL when a password is set is mysql -u root -p, so any instructions you see that say to enter into mysql via the command mysql, you would instead use mysql -u root -p

@Tom-Elliott
My image was created with trunk version and what you said about d1 files work for me. Thanks a lot to all!

@boeleke Would you be able to do a TeamViewer session with me so we can look deeper? Message me if you’re interested.

They don’t lose storage groups going from 1.1.2 to 1.3.0 (any rc you want).

They don’t lose storage groups going from and version 1.2.0 and earlier because Storage Groups for snapins didn’t exist at all.

Trunk introduced the idea that snapins work in a similar fashion as images and because of this should be allowed to replicate and move around to different groups and nodes.

So it’s no surprise they don’t have group settings defined. This is because we don’t know (we being the FOG team) how you intend to use your snapins and think it’s safer to allow you to setup how you need it setup.

Please define your relevant storage groups and reupload the files as needed. This should fix the storage group problem for you too.

Thanks to all who participated in this thread. I killed the switch port that someone had a Netgear router hooked up to and everything is working fine now. FOG menu is showing up. I haven’t tried pulling down an image yet, but I have a good feeling. I will do my best to up-vote the proper answers even the earlier posts questioning the possibility of multiple DHCP servers. I had a feeling one was out there, but I didn’t think it would have a such a huge impact on FOG. Again thanks everyone for all the help!

@ecicerkofski You can do as you please, but we are a community of volunteers, and the Developers have already taken the time to put in place what’s needed for Surface Pros to work in the latest FOG Release Candidate. We will be more than willing to assist once you’re on RC-8. We’re also willing to assist with helping you get to RC-8. Generally this works for existing setups:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@RobTitian16 If you like, you can use my batchfile for this. It should work across all Windows ADK as far as I know

@echo off rem The fileserver IP set FILESERVER=192.168.1.155 rem Share on the fileserver. set SHARE=INSTALLERS\ISOFILES\0-WINPE rem Username for the share set SHAREUSER=root rem Password for the share set SHAREPASS=root rem amd64 or x86 set ARCH=amd64 rem Path to hold working files. Needs about 500MB of free space. set PEPATH="c:\winpe_%ARCH%" rem ########################################################## rem Don't edit anything below here rem ########################################################## echo Creating the PE image call copype.cmd %ARCH% %PEPATH% > NUL echo Mounting the image dism /Mount-Wim /WimFile:%PEPATH%\media\sources\boot.wim /index:1 /MountDir:%PEPATH%\mount /quiet echo Adding commands to the startup script in PE echo. >> %PEPATH%\mount\windows\system32\startnet.cmd echo ping %FILESERVER% >> %PEPATH%\mount\windows\system32\startnet.cmd echo net use z: \\%FILESERVER%\%SHARE% %SHAREPASS% /u:%FILESERVER%\%SHAREUSER% >> %PEPATH%\mount\windows\system32\startnet.cmd echo z: >> %PEPATH%\mount\windows\system32\startnet.cmd echo z:\64.bat >> %PEPATH%\mount\windows\system32\startnet.cmd echo Creating the pxeboot directory mkdir %PEPATH%\pxeboot > NUL mkdir %PEPATH%\pxeboot\Fonts > NUL copy /y %PEPATH%\mount\windows\boot\Fonts\*.* %PEPATH%\pxeboot\Fonts\ > NUL copy /y "%WinPERoot%\%ARCH%\Media\Boot\boot.sdi" %PEPATH%\pxeboot\ > NUL copy /y "%WinPERoot%\%ARCH%\Media\Boot\BCD" %PEPATH%\pxeboot\ > NUL echo Unmounting the image dism /unmount-Wim /MountDir:%PEPATH%\mount /Commit /quiet echo Optimizing the image imagex /EXPORT %PEPATH%\media\sources\boot.wim 1 %PEPATH%\pxeboot\boot.wim > NUL echo. echo All the files you need for your PXE server are in: %PEPATH%\pxeboot\

Adjusts the variables as needed.

Then you can have a 64.bat at the target location, which you can edit at any time to for example create a selection menu for different setup.exe files

@Joe-Gill Was it imaging from the main server or a node?

@Joe-Schmitt What in the world could have done that? Also - kinda scary too.

@Wayne-Workman Not sure, dynmically sized hard drives can cause all kinds of issues though, one of them being that you only get the space used when your image is deployed and you’re unable to expand it in Windows.

The developers just commented in another thread that 4.7.1 has been re-engineered to support FOG 1.2.0 for those that can’t migrate to 1.3.0 right now. You won’t get support for Win10, gpt disk format, NVMe disks, or the 1000s of improvements in 1.3.0 over 1.2.0, but you will get the latest sata and nic support with 4.7.1

You can access these kernels here:
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32

They go into the /var/www/html/fog/service/ipxe directory.

@AngryScientist In the web interface, in Storage Management. There’s a field called interface. Also, in FOG Configuration -> FOG Settings -> Multicast Settings -> FOG_UDPCAST_INTERFACE

@Wayne-Workman Ok. I’ll try that. I disabled that node for right now to get my immediate imaging tasks done. I’ll try that though later this afternoon if I get time. Thanks!!

I think I went through this before but I can’t seem to find my previous posts about it. Ugh…

Thanks!!

Cheers!

Wayne,

Thank you so very much that solved our problem!! We are a school district in Texas and this was slowing things down a bit.

@Wayne-Workman
"“make sure that both the server and node (via logviewer–>multicast show that multicast session is actually tasked…I’ve had to cancel both active multicast task and active tasks, along with restarting FOGMulticastManager on both server and node, after killing mysql (TASK=8). Restart multicast tasking and it should start right up. I’ve even done a travel node, and can swear to it working. The key is making sure the logviewer multicast from server and node, show same tasking”

That’s all I got, not sure how to elaborate much more.

Also: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

My experience is sanboot works on most computers.

Dell Optiplex 9020s need Grub, even if they are in BIOS mode - not sure why on that but since it works I didn’t really spend time on it.

HP EliteBooks need Grub, even though they are in BIOS mode.

I should mention, every computer in my building - and we have maybe 15 different models - is successfully booting to the network every time they are turned on, and getting kicked to Windows when there isn’t a task scheduled. We’ve been working towards that for a long time, and finally got them all over the summer. Imaging is a dream now.

UEFI computers need various settings - I just go through the list until I find one that works. It’s usually refind.

Our environment has the correct exit mode per-machine. We have the global default set to sanboot, but we use fog groups when needed to set exit types where needed.

@Wayne-Workman it is there yes, but for some odd reason the wipe tasks don’t work correctly. They do not queue. The image task queues fine but wipe tasks do not.

The installer has an option to not exit if something fails. It’ll likely be a disaster in most cases to use, and it’s been a pretty flaky option in the past, but the argument is:

./installfog.sh -X

This - if it works - should not exit when the kernels/inits/client fail to download, and then you can place the files later.

Get a full description from the installer’s help menu:

./installfog.sh --help Usage: ./installfog.sh [-h?dEUuHSCKYXT] [-f <filename>] [-D </directory/to/document/root/>] [-c <sslPath>] [-W <webroot/to/fog/after/docroot/>] [-B </backup/path/>] [-s <192.168.1.10>] [-e <192.168.1.254>] [-b <undionly.kpxe>] -h -? --help Display this info -d --no-defaults Don't guess defaults -U --no-upgrade Don't attempt to upgrade -H --no-htmldoc No htmldoc, means no PDFs -S --force-https Force HTTPS redirect -C --recreate-CA Recreate the CA Keys -K --recreate-keys Recreate the SSL Keys -Y -y --autoaccept Auto accept defaults and install -f --file Use different update file -c --ssl-file Specify the ssl path defaults to /opt/fog/snapins/ssl -D --docroot Specify the Apache Docroot for fog defaults to OS DocumentRoot -W --webroot Specify the web root url want fog to use (E.G. http://127.0.0.1/fog, http://127.0.0.1/) Defaults to /fog/ -B --backuppath Specify the backup path --uninstall Uninstall FOG -s --startrange DHCP Start range -e --endrange DHCP End range -b --bootfile DHCP Boot file -E --no-exportbuild Skip building nfs file -X --exitFail Do not exit if item fails -T --no-tftpbuild Do not rebuild the tftpd config file -P --no-pxedefault Do not overwrite pxe default file

@Tom-Elliott I ended up just resetting the fogstorage password and replacing the $ with an s and ran a script to change this on all nodes.

I can continue to test escaping at home though.