https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382020#M68880 <P>If you current have an app that tells the UFs where to find the DS then all you need to do is update that app with the new DS's address. Each UF will update itself and contact the new DS.</P> <P>Since you are asking this question, I'll assume you do not have such an app today. You probably have $SPLUNK_HOME/etc/system/local/deploymentclient.conf on each UF. This practice is strongly (perhaps not strongly enough) discouraged for exactly this reason.</P> <P>Create your app. Call it something like 'org_all_deploymentclient' and push it to all UFs.</P> <P>Then comes the hard part. You need to delete the $SPLUNK_HOME/etc/system/local/deploymentclient.conf file from every UF. Let's hope you have a centralized way to do that (Puppet, Chef, etc.), otherwise you will have to log in to each UF to delete the file.</P> Tue, 29 Sep 2020 23:53:28 GMT richgalloway 2020-09-29T23:53:28Z https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382019#M68879 <P>Hi,<BR /> I have not found the post if it already exists...<BR /> But I have to reconfigure a lot of UF(s) to check-in with a new DS.<BR /> Unfortunately the original DS was not configured with a FQDN.</P> <P>Is there a method to send the UFs an app (e.g. "update_DS_IP) that will configure the UF to connect to the new DS (i.e. replace the DS IP)?</P> <P>Thank you!</P> Tue, 29 Sep 2020 23:53:22 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382019#M68879 Log_wrangler 2020-09-29T23:53:22Z https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382020#M68880 <P>If you current have an app that tells the UFs where to find the DS then all you need to do is update that app with the new DS's address. Each UF will update itself and contact the new DS.</P> <P>Since you are asking this question, I'll assume you do not have such an app today. You probably have $SPLUNK_HOME/etc/system/local/deploymentclient.conf on each UF. This practice is strongly (perhaps not strongly enough) discouraged for exactly this reason.</P> <P>Create your app. Call it something like 'org_all_deploymentclient' and push it to all UFs.</P> <P>Then comes the hard part. You need to delete the $SPLUNK_HOME/etc/system/local/deploymentclient.conf file from every UF. Let's hope you have a centralized way to do that (Puppet, Chef, etc.), otherwise you will have to log in to each UF to delete the file.</P> Tue, 29 Sep 2020 23:53:28 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382020#M68880 richgalloway 2020-09-29T23:53:28Z https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382021#M68881 <P>If you're brave...<BR /> Scripted input to run a bash script which rm's $SPLUNK_HOME/etc/system/local/deploymentclient.conf<BR /> Tried it once. Worked, but didn't sleep for 3 days afterwards.</P> Wed, 27 Mar 2019 15:26:04 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-use-the-current-Deployment-Server-to-configure-remote-UFs/m-p/382021#M68881 nickhills 2019-03-27T15:26:04Z