@ITSolutions

Yup that is my current method so far, but if I were to do that, then my images would easily run past 40 GBs. Which is why I copy it to the mounted drive, then hop over with File Explorer and Cut/Paste it into a “Archived Folder” I have linked. Essentially the same thing just a bit more confusing than just being able write to the mounted drive. When I replace the drive locally, I’ll report back with the results and maybe we can figure something out thats not as step-intensive.

If you want a complete list of steps that I do, it goes:
Instructions dependant on cifs-utils package

Login to the Ubuntu Navigate to the /images folder (cd <folder path>) Delete any old images being used (rm –r <dirname>) Pull Needed image from Archive Directory from the external drive (Copy + Paste to NetworkImages) Navigate to the NetworkImages Directory Copy the image you want to use (cp –r <dirname>) Set the permissions for everyone to read/write/execute (chmod 777 <dirname) Review the folder contents using ls –l and make sure its highlighted green Set task in FOG using correct image Profit

I know this seems like a lot of work, but it really isn’t. Still takes less time than manually running to each PC and plugging my USB in and entering needed commands. With this, can run 10 PCs to a switch and image them all at the same time, which is exactly what we need because we build 10 - 15 PCs every quarter and in the start, there wasn’t ANY imaging solution. I had to build each OS by hand.

@Yamakazi It’s all explained in the man page I posted:

–mcast-rdv-address address
Uses a non-standard multicast address for the control (rendez-vous) connection.
…
By default “mcast-rdv-address” is the Ethernet broadcast address if “ttl” is 1, and 224.0.0.1 otherwise. …

So multicast control connection should be on address 224.0.0.1 I suspect! And then:

–mcast-data-address address
Uses the given address for multicasting the data. If not specified, the program will
automatically derive a multicast address from its own IP (by keeping the last 27 bits
of the IP and then prepending 232).

Means 232.x.x.x if I don’t get that wrong.

That’s why I post both. I have no idea what type your system is going to use so I just brute force them all.

In either case, this shouldn’t be a problem even on subsequent updates now.

@Wayne-Workman Yes fog is working fine, I use plex as a media server on the same system. I use it so I can use the xbox in my room to view many media I have on my drives.

I simply used the gui to set the permissions on the drive.

Trunk installed without issues.

@splatterbuns Also some documentation here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Ubuntu_13.04_14.04_15.04_and_higher_with_FOG_1.2.0

@Sebastian-Roth

You don’t need to reinstall you Ubuntu system all the time if you stick to the trunk version for now. No need to bother you VM admin. Just try to fix things and re-run the installer. As well you can easily update to a newer version without having to start from scratch. Note down the things you fixed and where to find logs and stuff. Then when you feel you got it all fine you can still get back to your VM admin, get a fresh one and pull up a clean new system then.

This is what I ended up doing and it fixed the problem I was having. Thanks again for your help!

For Win10, gpt disks, and uefi firmware yo must use the trunk build of fog. The last stable release 1.2.0 stable doesn’t support the previously mentioned features.

Understand that the trunk build is a dev build so there are still a few bugs in the system. But they get patched quickly when reported. Plan on updating your install a few times to get new functions before 1.3.0 is finally released.

@Junkhacker @Quazz Thank you both ! I did try re-installing FOG on one server and it worked. Then I tried just restarting another server and that worked too. I then restarted ALL the affected servers and they all worked. Don’t know why the problem occurred, never seen that happen in 10 years so I guess I learned something today and I can sleep well tonight 🙂

@Sebastian-Roth Ours was quite a few firmware updates behind and we weren’t able to jump from our current strait to the newest, but stepping up just one version solved it.

@TreyBentley Ultimately, it will break MUCH more than just ldap. It will break pretty much ALL of fog.

Thanks a lot for letting us know! Feel free to post again if you find this is still not properly working somehow.

I had this issue too
I ran ./installfog.sh -K to fix it
I am running CentOS Linux release 7.2.1511

@Wayne-Workman Yes, force people to set a MySQL root password when installing. But it would still fail if people have MySQL server pre-installed (with empty password)… Other than that I don’t think we have any chance to hook into the auth_socket thing. See if you can find anything related to php and auth_socket

@robertkwild As I posted in the other thread,

“I would recommend that you install the FOG trunk version (1.2.0 trunk a.k.a pre1.3.0) and not 1.2.0 stable if you need support for uefi, gpt, and windows 10 support. https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
You can install the trunk version directly and don’t need to install 1.2.0 stable first. Just go directly to the trunk. Use svn or git to get the installer then launch the installer. For Centos FOG installs clean without any problems.”

@Wayne-Workman That did the trick. It said something about “file not found” but I know it got its address. I’ll get all the files worked out later. Thank you for your help!!

@Wayne-Workman Just want to update you that for some reason I kept running into the issue, instead I made MySQL services be the first services to boot and I have not ran into the issue since. (just another work around)

Just got mine working with FOG svn destribution. The problem with FOG 1.2.0 is likely the kernel can’t support the hardware. In my case the network card.

In my opinion, we should only worry about the current version of Raspbian.

@Tom-Elliott @ch3i I changed it to my password. Thanks, I was thinking there was something like that, just didn’t know where.

Thanks!