Thanks for your reply and suggestion. Really appreciate it.
I am not using "deploy-poll" to set deployment manager rather I set deployment manager during UF installation which still creates deploymentclient.conf in /etc/system/local.
splunkforwarder-xxx-xxx.msi INSTALLDIR="C:\dir" AGREETOLICENSE=Yes DEPLOYMENT_SERVER="Dep_Server:8089" SERVICESTARTTYPE=auto /quiet
Some background:
I have used the same method for thousands of servers during Splunk rollout so that they can report to DS and I can assign server class and app to clients. But, Splunk scope has increased and now I have ~ 6000 servers reporting to one DS which makes DS UI unresponsive and it's difficult to deploy the app.
I am building a few more DS to distribute the load and also wants to increase the PhoneHomeInterval to reduce client checking app update every minute.
If I just go for vanilla UF install and don't set Deployment Server during install, the client server will not report to DM & I will have to push deployment client config using configuration mgmt or manually.
The solution?
If I keep the same install process intact and when a client reports to DS, I assign the deployment app via DS which will go to /etc/app directory. There will be two deploymentclients.conf and as per precedence, the /etc/app configuration will take charge.
Is this a good way to do these changes or anything that you can suggest?
Sorry about the long message & thanks for your time on helping in this.
... View more