Its not a matter of creating a Remote deployment template, and finishing creating it, and then reusing it for each of your different SQL servers to which you want to deploy LiteSpeed
Instead, you specify all those different servers within one template while you are still doing the configuration of that template in the 'LiteSpeed Remote Deployment' UI screens.
Once a template has already been completed, it is too late to add to that same template, additional SQL servers to which you wish to deploy LiteSpeed.
That said, you can create a template that has all the SQL Servers to which you wish to deploy LiteSpeed. So that is one template with which to control (deploy) them all.
When you are in the Remote Deploy Configuration, when you are in the 'SQL Server' UI screen, like shown in screenshot1.jpg and screenshot2.jpg, that is where you set up the SQL Servers to which you are going to install LiteSpeed.
Only one SQL server shown in the screenshot because I just have the one machine with SQL Server on my network. If I had more remote machines with SQL server installed, they would also appear and I would be able to check their checkboxes to add them as well.
And then, when I would get to the 'Deploy LiteSpeed' UI screen (screenshot3.jpg), when the LiteSpeedRemoteDeploy_Configuration.xml file is being created, it would include multiple deployments (screenshot4.jpg). Again mine only has one deployment, the one going to the my TOR-DMANNING host via the LiteSpeedRemoteDeploy_TOR-DMANNING.xml. If I had add added more hosts earlier, I would have an additional xml created for each one and referenced in LiteSpeedRemoteDeploy_Configuration.xml .
And as shown in screenshot3.jpg, you can choose how many simultaneous installs to have the system perform--all with this same template, this same xml file. The default is 5.
Though you can add as many severs as you want during creation when running the Remote Deploy Configuration, once created, the template cannot be expanded to include additional servers.
