@Wayne-Workman said:

@jayphizzle said:

Can some mod mark the tread as unsolved?
Or should i open a new thread?

I’d say open a new thread, I’d call this a bug as it doesn’t work right if a different language is being used by the system.

@Jbob

Ok ‘new’ Bug reported here: https://forums.fogproject.org/topic/6934/endless-windows-key-activation-burning-oem-keys

@ch3i said:

@boeleke The legacy password is for the legacy client : it’s useless in your case.
Could you post the fog.log present on a client at c:\fog.log ?

Hi ch3i,

i was testing it again today & all i working fine till now.
Thanks!

Bump… would be good for CentOS fresh install as well.

@Sebastian-Roth Thank You Sebastian. Really appreciate all developers effort here. FOG is wonderful tool. I simply love it. You guys are extremely responsive as well.

@BardWood I don’t think it will work. The FOG Trunk methods involved with synchronizing storage nodes with their masters has greatly changed, along with the ability to now cross-share images with storage groups. I would not advise mixing versions as you would like, I think it’ll only lead to disaster. The location plugin has also been modified to cause remote nodes at a remote location to PXE boot directly from their local node. Also, the 1.2.0 nodes probably can’t support this functionality

You’d be better off just updating everything to fog trunk, OR just staying at 1.2.0 till 1.3.0 is released.

@Sebastian-Roth I’m in the habit now of looking at what is stored in the DB for the nfsGroupMembers table. His credentials stored there worked for connecting to the fog server via FTP. 😕

I also checked firewall and SELinux. Both were disabled.

Only thing I could see that was different and unusual was PHP 7.

That said - I don’t disagree with a packet capture.

Needed to not use root as msqluser for storage node.
Set it back to fogstorage with password from the fog webgui fog config →fog settings → storage node settings (something like that)
Put that in the storage node servers /opt/fog/.fogsettings and redid the install again. All is well again

@Sebastian-Roth The real question is the original issue that caused this post to be opened in the first place fixed?

@Kiweegie, are you solving this because the password/snapin issue is fixed or your server is no longer sufferring from the High CPU Usage from multiple httpd processes?

@Wayne-Workman

okay 😢

@Sebastian-Roth @clemens.g For more details here’s the thread I created on it : https://forums.fogproject.org/topic/6862/can-t-remove-multicast-image-task-through-webgui/7

@kortnor Thanks for letting us know! From what I can read between the lines you’ve changed A LOT of things and now it is all working. Unfortunately we won’t be able to find out what was casing your initial problem. Seams like you just solved it by re-installing… I am pretty sure this was some kind of permission problem (maybe tftp daemon started without the --secure optione?!? I don’t know!).

NFS has nothing to do with FOGs PXE bootup! (Just for you to know)

Hi guys, i just noticed that my reply from friday is not there. I did the installation of the last version of Fog. I still had the same problem. I then tried to install another image and this time it worked. (It did not work previously after the update!) So i used my backup copy of my images and everything is ok now. Thank you for your help again! 🙂

@Wayne-Workman said:

https://wiki.fogproject.org/wiki/index.php?title=Add_%26_Extend_a_2nd_Virtual_HDD

That wiki page seems strangely familiar, some now. 😋

Great find!!

Disregard. I found the issue.

This server was migrated from a backup, and the backup had my old FTP password in there. Updated the master storage node with the correct, new password, page loaded fine.

@xcvtop On the WebGUI if you click on FOG Configuration it should tell you when you’re no longer up to date (and what version the newest is). Although I’ve found I have to refresh the page after navigating to it before it will tell me so.

@Sebastian-Roth

Hi there,

i tried it again and it was workign now.

Thanks!

@dustindizzle11 It would be nice, and this has been asked for several times. In order to implement it, I believe a lot of code would need edited and rewritten. It would include changes in the database, the inits, the web interface - we would likely need an entire new management page just for domains.

I would even like the feature. But I would rather put it off till 2.0 in order to get 1.3.0 out faster.

Right now, if you want to be able to have the right domain info inserted for a host during a full-registration via the boot menu, the way to do this currently is to set your AD defaults to what you would want them to be.

@nickkcsd 0 doesn’t necessarily mean anything. Can you deploy the image?

@mikepel What version of FOG?

@Tom-Elliott Okay, I’ll look into all this. Just happy to be able to get PXE to work! Again, thanks.