Well, image size on server is now working, but I don’t see the storagenode information anymore…

@Wayne-Workman

Funny, that doesn’t work, still the sizes in the web gui are correct

@ch3i
That solved the problem

Thanks found it by myself ten seconds ago, now i just have to figure out why it is displaying 0 Byte

I’m dealing with this problem since 2 Months, so the FOG version doesn’t matter i assume.

Well the size isn’t 0, there is nothing ^^ The Filed ist missing completly in the Web UI.

Jessie doesn’t work, tried that as well yesterday, so i had to reinstall Linux with Wheezy and install fog again.

Personally i would recommend Fedora or CentOS

Hi

New day new problem Well the problem accually isn’t that new, just didn’t bother me.

The problem is, that there is now size display for image size on server, i checked the databases, there is no field for size on server, don’t know if there should be one.

SVN is 3412

What i noticed, is that the search is not working really well. If search “image size on server” i get every result matching one of these words. I tried diffrent search phrases, but the problem is the same.

Ok, i will use Wheezy then. Thanks for the fast answer.

Im trying to install FOG on a Hyper-V VM with Debian 8.

Tried to install the latest SVN, but the installation doesn’t run through. Always got the the error

Starting FOG Multicast Management Server…Failed

I have to say, I don’t like the new design at all. It looks nice but the usability was, in my opinion, better in the old version.

Just

Ok, will try that on monday.

How can I do that?

Sorry I was sick over Easter thats why i didn’t write here.

I contected the client directly to the core switch today, but that didn’t change anything.

Intel Ethernet Connection I217-LM

Every client. T540p also was on 5GB/min.

%20 is an encoded space. Check your DHCP-Settings for a space.

I meant we didn’t touch the compression before the problem occured.

Iperf result on the testing client, is the same as the one i posted.

I will do the test on the same switch tommorow.

Compression was on 3 so it is still at 3. We have never touched the compression, so this can’t be an issue.