I had a situation where I had a farm created with the script , and I had to extend it onto the machine that was to run SQL reporting services in integrated mode. This requires that server to be a farm member, but there was no need to mention it anywhere
in the XML configuration file for the script, but none of the items that specify a server name in the configuration need to be deployed to this server. A similar scenario would exist for Web front ends.
When I attempted to run the script on this server, it thought I was trying to do a remote deployment to the machines that were mentioned in the script and refused to install anything on the local machine.
I was able to work around this by creating the following node inside the farm tag:
<AdditionalServers Provision="MachineName1 MachineName2 etc"/>
This works because when the script sees any tag that has a Provision= attribute, it adds those servers to the list of those that are known to be in the farm, even though there is no code in the script that looks for a tag named <AdditionalServers>.
Can I suggest this is added to the template XML.