This project has moved. For the latest updates, please go here.

Adding additional servers to a farm

Jul 12, 2012 at 1:25 PM

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.

Jul 15, 2012 at 3:40 PM

Good catch and suggestion. I think I realized this before but at the time I couldn't imagine a scenario where a server in the farm wouldn't at least be a Query server or run at least one service instance.


Jul 15, 2012 at 3:40 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.