I suggest to follow the documentation about this topic: https://www.splunk.com/blog/2016/08/31/adding-a-deployment-server-forwarder-management-to-a-new-or-e...
In addition, you can find yhis useful video: https://www.youtube.com/watch?v=uiU_jGxnnuc
Anyway, the way to proceed is easy:
if you are only testing distributed deployment you have to:
$SPLUNK_HOME/bin/splunk set deploy-poll servername.mydomain.com:8089
you can do the same thing inserting in the file $SPLUNK_HOME/etc/system/local/deploymentclient.conf the following rows
targetUri = deploymentserver.splunk.mycompany.com:8089
restart splunk on Forwarder
You'll see the Forwarder on the Deployment server at [Settings -- Forwarder management]
If instead you need a Forwarder management, you have to use a different approach:
On Deployment Server:
On Universal Forwarder:
In order to make a Server a Deployment Server, you just need to put one app in the $SPLUNK_HOME/etc/deployment-apps folder.
Then you go to the Splunk UI, Settings-> Forwarder Management and you can start creating your serverclasses. That;s all.
A standalone instance is a searchhead of itself, and you don't need to configure anything for it to search hits own data. If you have a set of instances that are functioning as Indexers only, then you can configure your search head (s) to distributed their searches to the Indexer Layer.
More details on that here: https://docs.splunk.com/Documentation/Splunk/7.0.2/DistSearch/Whatisdistributedsearch