We have our Intel Unite 4.0 server and 4 hubs up and running. We have created a group for our hubs and assigned a configuration to the group.
This has worked well for us but we notice that the hubs are moving back to the 'root' (i.e. out of the group) and therefore getting the default policies instead of the ones for the group. We can move the hubs back into the group and all will be well for a couple of days and then one will pop back up to the default area again. We've seen it happen with all of our hubs at some point.
I'm looking to see if the move events are related to client connections, hub restarts, server issues (e.g. IIS appPool recycle). While I continue investigations, I thought I would post here to see if anyone else has seen this.
Thanks for this !
We noticed that the default policies were being applied when the hubs moved out of the group. So, we’ve applied our group configuration at the default/root level so that the configuration is now consistent whether a machine is in the group or up one level. That does mean that we cannot have different configuration policies and we have a couple of groups that might want different configurations (so we really need the hubs to stay put).
Thanks also for the information on the debug. I’ve struggled without success to put the hub in debug mode based on information here https://www.intel.com/content/www/us/en/support/articles/000024124/software/software-applications.ht.... So this information is really, really useful.
I have a monitor that queries the unite_server database every 10 minutes looking for moved machines and I got a hit between 10:33am and 10:43am so I can send you log files with a 10 minute interval to inspect.
What is the best way to send you the files?
I have updated the server and hubs to 4.0.3190.18 as recommended. We rebooted the clients and logged in on the hub machines. All hub machines have Intel Unite configured to launch at login. Intel Unite starts on the hubs and all of the hubs moved back to the root after startup. We also notice that the server admin console is still showing the all hubs at version 4.0.991.430 when we can confirm the hubs are all updated to 4.0.3190.18.
Let me know if you would like logs from this morning.