When I have experienced the issue in the past I have always found that the phantom hosts added to new groups were only the most recent hosts that were registered. Whether that be 2 hosts or 5 phantoms
Running the SQL maintenance commands from the wiki (as mentioned I think updates also helped) seemed to resolve
I was also having this issue, finding that when my co-workers created a group from the hosts page with even just 1 selected computer, it would add over 200 computers to the new group! I was able to avoid this issue by going to groups, creating a new group there, then adding members from the groups screen.
@librarymark Looks like the binaries failed to download, which caused the later error you are seeing when it tries to unzip & move them to the right spots. Look earlier in this log, you should find an error related to the binary downloading.
It’s just that for my situation, in a public library with public hosts on a network totally separate from our staff net, I am not sure I have a need for bullet-proof security there.
You’re public users are not a security risk? And I know you say you have HDD locking software (Centurion SmartShield or Faronics DeepFreeze probably), but this doesn’t really matter. If there’s a security hole and someone knows how to exploit it, they can exploit it every time they want. Once there’s a compromise, those computers are no longer safe for users to use, no matter how many times they are rebooted and ‘reset’. The legacy client is not secure. The legacy-enabling functionality server-side is also not secure. It is advised that once you have moved to the new fog client, to remove legacy passwords from the FOG server.
We are using Reboot Restore Rx. Are you talking about the fog client still?
@george1421 - thanks for your help. The problem with RRRx is it’s freeware, and I would suspect that the company that makes it is not interested in supporting it unless you buy a copy (or 100 in my case). I have been testing it for several days now and it seems to perform quite well and I would bet it would be more reliable then what we had been using, Fortres Grand’s Clean Slate. The only problem is you have to install it at the first boot after the sysprep stuff finishes, and it does not include a silent install option. Again, it’s freeware and the company says it’s not supposed to have any bells and whistles. Fortunately, there is an AutoIT script that can install it hands off, so I intend to put that at the end of my post install script and see where that takes us.