I have looked at permissions, and it's not that. My situation is slightly different as I am using the DS to send apps to two different locations. ../etc/master-apps for building cluster bundles as well as .../etc/apps/ for monitoring the Manager Node (aka CM)  So in the serverclass.conf I have [serverClass:<some serverclass name>] machineTypesFilter = linux-x86_64 restartSplunkd = false stateOnClient = noop targetRepositoryLocation = /apps/splunk/etc/master-apps whitelist.0 = <manager_node> [serverClass:<some serverclass name>:app:<some app name>] restartSplunkWeb = 0 restartSplunkd = 0 stateOnClient = enabled Well this end up as failed to install app ERROR DeployedServerclass - name=<some serverclass name> Failed to install app=<some app name> ERROR DeployedApplication - Failed to install app=/apps/splunk/etc/shcluster/apps/<some app name>; reason=Application does not exist: <some app name> Now when I do this: [serverClass:<some serverclass name>:app:<some app name>] restartSplunkWeb = 0 restartSplunkd = 0 #stateOnClient = enabled  We get this: INFO DeployedApplication - Installing app=<some app name> to='/apps/splunk/etc/shcluster/apps/<some app name>' INFO DeployedApplication - Downloaded url=<host DS server>:8089/services/streams/deployment?name=default:<some serverclass name>:<some app name> to file='/apps/splunk/var/run/<some serverclass name>/<some app name>-1633360622.bundle' sizeKB=10   And this has nothing to do with permissions - something 'buggy(?)' I have a case raised. This is my work around not elegant but seems to do the trick. Regards Duncan PS The version is 8.1.6    ... View more