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

@tom-elliott strangley my fog clients all reported Middleware::Response ERROR: so I reset encryption on my ‘all hosts’ group. Not sure if there was something else I needed/should have done but that sorted it.

@tom-elliott that was quick! Upgrade seemed to go through fine.

@tom-elliott thanks

Hi,

when I try to upgrade to 1.5.1 it fails at the database backup
(running Debian 8.10 & FOG 1.5.0)

• Setting up Apache virtual host (no SSL)…OK
  sed: can’t read /etc/php/5/fpm/pool.d/www.conf: No such file or directory
• Starting and checking status of web services…OK
• Changing permissions on apache log files…OK
• Backing up database…Failed!,

@tom-elliott cool, not sure if it’s just me/my setup but since moving to rc12/13 the server UI seems more responsive :-)

Tom, just upgraded (switched from working to dev) and the FOG_CLIENT_VERSION is still defined as 0.11.13 in system.class.php

Thanks Tom & Team

@sebastian-roth true we could do that and have gained a field back for other use like asset tags that @Wayne-Workman mentioned but mostly because it stops information from being stored wrongly. (I know… how hard could it be to put site/room into one field.) I’ll have another think about merging them.

Good question. I’m not sure to be honest, the reason I set the current ones the way I do is mostly for the inventry CSV that goes to our finance team during audit. (I know where the machines are just from the hostname)

I also use the primary user field if a device is on loan, I think altogether this has us covered. (Admittedly I don’t have an urgent requirement for another ‘other tag’ field just yet but thought I would request it in case the need arises.

What did you use the field for, if I can ask?