spanning tree, spanning tree la la la la la (jingle bells)
I’m saying this from 2 months 😄
I’m glad to read you saying it ^^

For some reason Microsof thought it would be a great idea to constantly fake your Wifi MAC. Despite the MAC being a common identifier for various purposes.

And of course they enable it by default so that it’s the maximum amount of pain for everyone.

@Seydoo Is this still an issue? Do you use proxy authentication?

@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).

It works,

Thank you so much

Do you think my snapin problem (post from 5hours ago) is link to this one ?

Yes hostname is correct 🙂
I just have to test my snapin deployment

Ok so I have the same problem than my old server, some snapins failed to deploy due to “hash does not match”
This is a known issue for me, some snapins, I don’t know why simply doesn’t download correctly (my .exe is 1KB instead of 75203KB in server)

It seems something wrong in the settings, 3 snapins download at 1KB

BTW thanks Joe and Tom for you help, I’ll try to find out why my snapins doesn’t download correctly (all are 1ko in C:\Program Files (x86)\FOG\tmp with hash does not match in fog.log)

RC11 solve the problem, thank you
You can close this topic

Thx Wayne, your method worked I’m now in RC11

You can close this topic

https://forums.fogproject.org/topic/8758/fog-installation-error-cannot-restart-mysql/9#

I’ve found and fixed the cause of the issue. It was my scans looking to correct other issues. I didn’t realize some distros were adding that particular if statement. Sorry 😞

The new client will not work with FOG 1.2.

If you want to use the new client, I’d highly recommend you upgrade to trunk.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

While I do understand hesitation of upgrading to an “development” version, I can assure you this version works with the new client as the new client and FOG where built together with a lot of collaboration between @jbob and myself.

@Sebastian
My HERO !!! 🙂

Tanks a lot it works

@admin
You can solve this post

From my personal experience I would recommend updating to the latest trunk version of FOG. It is much more advanced and I can capture and deploy W10 images without issues.

You need to install “subversion” and then download the latest package with

svn checkout https://svn.code.sf.net/p/freeghost/code/trunk

From there you install as usual. But be aware that updating might not always work flawlessly so I would test it in a non-productive environment and consider a clean install of the trunk version.

Tom,

Yes pb mean problem 🙂 no misunderstanding for me with your answer 😛

You can solve this post, all is ok now, thanks to Sebastian who told me how update / change my boot pxe

I found where the problem was, in the /etc/php file I changed the values for a Fedora distrib :
UPLOAD_MAX_FILESIZE to 1900MB
POST_MAX_SIZE to 1900MB
but i didn’t change the value of Limit Memory (Ubuntu and VmWare) who was still at 128MB, change it to 1900MB and it works

@Seydoo said:

My problem is solve, due to a bad password (user fog on linux with not the same password than fog tftp user)
tanks to ch3i for his help

The problem was that you have a password policy that does not accept the password “password”.