Hi Splunkers, I had the same issue in a Splunk Cluster Environment (Cluster Master as Monitor Console hosting) and I have fixed the issue by: Settings ---> Monitoring Console ---> Settings ---> Apply Changes As soon as you have clicked on "Apply Changes" Splunk will prompt you the "Refresh" option, just click on Refresh and check if your Splunk distributed instances are still shown the "Unknown" label. ... View more

you have two options for migration. In both options, you touch the client. option 1 (easy) - use a software distribution system, (landesk, sccm, puppet, etc) to change the value for the targetUri. Simply update the file option 2 (preferred) - Create a TA specifically to manage the UF client settings. Add the deploymentclient.conf file to that TA. Use a software distribution system to remove the /etc/system/local/deploymentclient.conf and copy the TA files to the client. This setting is now part of the client build and if you even need to move the deployment server, you can by simply updating the TA. This also means that any new installs must have this TA as part of the package. ... View more