@Sebastian-Roth if my memory serves correctly, GUI watcher was a part of the now very old client

https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberImageIDs

Found and should be fixed if you do the latest pull.

Thank you,

The forums are fine, unless you’re comfortable posting them as issues on github!

Thanks for letting me know.

I’ll try to get this fixed once I can nail down what the issue is.

Of note, I’m calling it 1.6 because when we do release it, that’s what this will become.

It is using the current latest version (1.5.7) and the .XXX after is the number of commits ahead of the master branch the working-1.6 branch is at.

While I have no grounds to substantiate the claim, I really believe 1.6 will handle this kind of thing much better. Sure I don’t have 22k worth of entries (or more depending on the use case) in my userTracking table, but now that we have pagination, things should be a little better here. This, of course, makes reporting for “all” of the rows a little more difficult. But at least it allows searching and viewing information a little simpler without having to go to the extreme of truncating the whole table.

I’m sorry it took so long for us to have this implemented.

@george1421 I agree with it all.

I can’t imagine a need for latency being enabled by default. I added it to 1.6 for safety. Shouldn’t be hard to port to 1.5.x

@AdrianW If you could, please post the contents of the output in text format. Particularly the one from the MAC address.

I’m wondering if you have hostnames using - in the name? I’m not sure if this could pose a problem, but there’s always the possibility.

@AdrianW the Mac of the computer that gave the issue should be used