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:
install Deployment server in the same way,
create an App (called e.g. "TA_Forwarders" in which there are only two files: deploymentclient.conf and outputs.conf, in deploymentclient.conf there the correct Deployment server Addressing (the same of previous item);
design your deployment policy: define server classes (a list of server with the same apps) and apps;
copy TA_Forwarders in $SPLUNK_HOME/etc/deployment-apps
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.