@sourcaffeine You’re not at all having the same issue.

The old client isn’t really supported any more. Please understand that the messages you’re seeing in the fog.log file are totally different and give an overall picture.

Basically, the messages are saying the CA you’re using are not the CA that was generated for the FOG Server.

You can retry this with: ./installfog.sh --recreateCA -y

I can’t be sure what spawned the issue to begin with though. It also means after you recreate the CA certificates, you will need to reinstall the client to get the client to repin the updated CA chain information.

@sourcaffeine you’re using the old fog client?

Most often, this happens because of what Microsoft has enabled to make rebooting much faster (or booting after a shutdown specifically.) This is called Fast boot in windows and basically flicks the “dirty bit” on the HDD which causes issues like this.

You can disable fast boot with: powercfg /h off as an administrator of course.

@kafluke You’d want to checkout dev-branch.

Working is more or less a stand in for Alpha RC’s now.

Dev-branch is a bug fix branch

This issue is known about and unfortunately doesn’t have a good fix that I’m aware of, for 1.5.x

This is due to the order of loading of things. The access control menu item is loaded before the rule that modifies it has a chance to prevent it from loading.

This is addressed in 1.6 branch, mainly because we changed how menu items are loaded entirely. (Specifically to address the order of loading issue.)

@processor And for what 1.5.X (Dev-branch) has vs 1.6:

https://github.com/FOGProject/fogproject/compare/dev-branch...working-1.6

Eitherway, @Sebastian-Roth is correct.

While I hope 1.6 is nearly ready for “prime time” there’s a few things I need to work out before it will be ready. That and some time. I’ve been taking it relatively easy as to what I do these days for coding.

I’ve added something similar to 1.6 now too.

Thanks for the suggestion.

I think this is perfectly sufficient and much more descriptive, however, I might suggest adding the date/time as well?

Something like:

->set('name', $taskName . ' - ' . $this->get('name') . ' ' . self::niceDate()->format('Y-m-d H:i:s'))

This way you have more direct knowledge of the tasks and timing of said tasks.

@agray I think the biggest issue is the speed at which fog renames. It’s blazingly fast. Faster than windows has time to finish completing. Simple to disable the service and reenable it when ready. That’d be the first step and I’m pretty sure it will fix most of the issues you’re seeing.

I’m quiet but always readying. Sorry for not helping sooner.```
Insert Code Here

@Sebastian-Roth what about staying true to fog project itself? How about username fogproject?

As most users seem to use fog for our normal stuff I think this would be descriptive enough for admins to know who and why it was created and limit the number of issues with just plain fog