Hi,

Everything is now fine with RC-12, thread can be closed 😉

Thanks !
Matthieu

@uwpviolator You should be able to use the new client, but it won’t automatically update. As far as the communications between the client the server, nothing has changed.

The only other difference, your devices won’t automatically update to 0.11.13, unless you download the files from github, place them in place of your current files (under /var/www/fog/client/), and then edit the /var/www/fog/lib/fog/system.class.php FOG_CLIENT_VERSION line to 0.11.13.

@tom-elliott Should I assume this is an Evince problem because it is not viewable and seek other options or is there something funky with the PDF generated from htmldocs. Do you have a Ubuntu 16.04.3 install to test this. Just wondering if wkhtmltopdf could be used instead. I could investigate this further for you if you like.

@tom-elliott Yes indeed, thanks very much!

@RobTitian16 Maybe do some datebase cleanup: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

I’ll mark this solved as the AD joining issue is actually solved. Please open a new thread if you still have the group assignment issue after the DB maintenance.

git checkout dev-branch
git pull

now running 1.5.0 RC11
Interesting new GUI.

I added a location - it said it was successful however it seems no location was created.
When i clicked to list locations none appeared.

I uninstalled the plugin and re-installed it and it now works.

Thank-You for the quick reply 🙂

It does. Thanks!

While George’s solution might have worked for the “bug” the cleaner solution is probably doing it right with the partition order…is it “frech” to mark my own post as solution?

@tom-elliott Thanks!

I was in the throes of migrating all our images over to 10v1709 so I was only just barely able to accomplish what I’ve detailed above before I had to return the unit to its owner.

Not an issue any longer sorry for the delayed post.

And if you want the latest file that appears to be working FAR more accurately/appropriately:

wget -O /var/www/fog/lib/fog/fogcron.class.php https://raw.githubusercontent.com/FOGProject/fogproject/working/packages/web/lib/fog/fogcron.class.php

I believe I’ve found and fixed the task active tasks page to refresh properly and stop displaying completed tasks. I tested this very minimally as I don’t have my normal dev environment setup currently.

It appears to be working properly, and should be fixed for RC-11.

As I don’t have a means to properly test this issue, I am not going to solve it, but just wanted to give a heads up so people don’t think it’s just been forgotten.

I’m solving this topic for now. @Jim-Graczyk if you are still having the issue, mind creating a new one? I will work on this in the meantime, but I would much prefer a new bug report for the issue (after updating to latest rc of course) .

Marking solved as this was not a bug, it really was a valid db connection not being able to be made. (this means the storage nodes it was asking for could not communicate to the main server).

@sebastian-roth said in Cant PXE Boot = PXE-T01: File not Found:

So here is another reason to push for the next release.

I think we are ready for another RC.

The best way to delete hiberfil.sys is to disable hibernation in Windows:

Go to Start menu, type “cmd” open up command prompt Type “powercfg.exe -h off” [make sure you are an Administrator] ENTER Type “exit” ENTER RESTART YOUR PC and you are all set

After the restart, you should be able to see more free space on your hard drive.

This generally works for 90% of the time but if it doesn’t work for you then you can refer to other available methods.

Ahh my bad, the description was just blank as I was just testing the Menu.
I copied every other field but the description from my previous server. All good now cheers.
Sorry about that.

I had the same issue with T540p’s, a git pull and the 1.5.0-RC-10 resolved this for me also.

@joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee after double checking, the FOG Client does not force log offs; this means that any other user process can stop the log off. This indicates the problem is likely another program on the computer, that or a GPO policy is blocking it.

Could you try running:
shutdown.exe /l manually on a problematic machine and see what happens?

This command works and logs me out. For some reason it isn’t happening automatically

However, ultimately I would recommend using GPO to handle inactivity log outs. There are some known restrictions with the log out module (https://github.com/fogproject/fog-client#autologout)

Can you tell me how I would do inactivity logouts via GPO? The reason I use Fog for this purpose is because there was never any other way to do this.

@cojohnson Well, just let us know when you need further help on this.