OK, thanks for the answer. I had read that documentation before but it wasn't clear on that specific point about when the restart occurs: "immediately after a deployment client downloads the app" - I read this to mean splunkd restarts after the UF downloads the app, but this doesn't mean subsequent changes to the app result in a splunkd restart. If it does indeed mean splunkd restarts each time the deployment client phones home and downloads updates, then that is of course a good feature, but the documentation needs to be clearer on that point. The main reason I'm querying this is that I recently had a problem where my UF (Deployment Client) wasn't sending data to Splunk Cloud even though it had been restarted via the CLI (e.g. $SPLUNK_HOME/bin/splunk.exe restart). When I ticked the 'Restart splunkd' box, Splunk Cloud started receiving data from UF shortly after. Hence the reason I asked if there's a difference between these two methods for restarting the UF service. Furthermore, this is on a Windows 2019 server. I've not had this issue on Linux server deployment clients. I have built 6 deployment apps for 6 different applications running on Linux boxes, and none of them have the 'Restart splunkd' box ticked within the Deployment Server, yet they all respond to deployment app updates via a UF restart from the command line.
... View more