Did you press the “Reset Encryption Data” button?

@DarkEnergy
Just a quick note, with the forums, if you put a space after the @, @NAME it won’t notify the person. So @ Jbob would not work, but @Jbob would

Fixed in v0.8.1

I’ll re-iterate my message. I’d wait until we fix v0.8.0

Just a heads up, you installed the beta client.And the specific version you install won’t work with hostname changer. I’d either switch to the legacy client OR wait until I fix v0.8.0 of the beta.

Here’s my 2 cents:

Option 1.) Make a plugin. Please don’t even attempt to edit FOG gui without using a plugin. The plugin API is much simpler to use.
Option 2.) Make a bash script. It could copy the image directory and the appropriate SQL data.

You can still edit a post. Click the three dots on the right of your post and click Edit.

@Wayne-Workman To be frank, you’re spot on. Tom is just … Tom. And I have to balance my university studies, job(s), FOG coding, FOG forums, and the website contact form. So we don’t really have the time nor motivation to have regular updates. But with that said, with FOG 2.0 we are aiming to have almost all of the development team far more active, and we plan to have relatively constant updates on our progress with 2.0 simply because of how long it will take.

it breaks the new client because we have been implementing our entire security system for the new client. v0.8.0 of the client will be a million times more secure then the current beta.

@Wayne-Workman For the record, the legacy client will not be dropped in v1.3.*. However, what will happen is that we will create a checkbox for disabling it. Why? Security. The legacy client opens up many security holes, which the new client does not have.

In *nix systems putting a / infront of a path means it’s at the root. So what you were doing is this:

cd /var <-- Basically C:\var
cd /log <-- Basically C:\log

You need to enter the whole path like this :

cd  /var/log 

OR

cd /var
cd log

Our redirects are not in place. This issue should be fixed relatively soon.

@Polii123 Are you sure SQL is running?

Sorry about that, it would appear only a moderator can do that. (We’ve appointed a few to help out with this).

We are actually going to add old forum redirect this up coming week. This new forums runs on Nodebb

If posting a problem / question with FOG, please click the down arrow next to Submit and click “Ask as question”. This will flag the thread as a question for us and put a status flag next to the title.

Well, the code is documented! But other than that, the only documentation available so far is this:
https://portal.fogproject.org/projects/fog-client/wiki/Wiki

Right now I am the only developer working on the client, so updating the wiki is quite time consuming. We are (hopefully) getting a couple more c# developers to help out soon though.

Ideally though the new client’s modules will act exactly the same as the old one (minus a few bug fixes).

By “new” I mean the beta client. (As opposed to our legacy one that has been around for years).

Assuming this is the beta client, GreenFOG will force reboot even when a user is logged in. This will change, but not immediately. The easiest way of removing the GreenFOG tasks is to re-enable it and remove the greenFOG tasks. The other way is to open TaskSchedular and remove all tasks in the FOG folder.

Note that attachments were transferred. We need to do a little more work for the current links to them to be active (attachments are now urls to download the file, we simply need to process the old attachments into a new format).

Is this the new client?