Aug 28, 2012 at 1:02 PM
Edited Aug 28, 2012 at 1:03 PM
I suppose you are refering to that setting?
<!-- Specifies if checks and actions should be run on all servers in the farm or only the local server
<!-- ! Make sure that the deployment account is local administrator on all servers
<!-- ! Make sure that PowerShell Remoting is enabled on all servers and the deployment user is permitted-->
<!-- ! This can be done by running 'Enable-PSRemoting -Confirm:$false'
Maybe I have described it a bit unclear.
The solutions are always deployed to the entire farm, because, as you have mentioned, only deploying to one server in the farm is not recommended and wouldn't solve the purpose of this script :-)
The setting above refers only to actions which are done after the deployment/retraction/update process namely:
- Restart SPTimerV4, SPAdminV4, SPUserCodeV4
If you set <IncludeAllServersInFarm>false</IncludeAllServersInFarm>
then these actions will be performed only on the machine where you run the deployment script. If you set <IncludeAllServersInFarm>true</IncludeAllServersInFarm> then
SPSD will attempt to access all servers in the farm which have the ServerRole!="Invalid" through PowerShell remoting and run the actions also on these servers. The WarmUpUrls action will create a local proxy on each server to
warmup the urls on each separate WFE.
In order to use <IncludeAllServersInFarm>true</IncludeAllServersInFarm>
on all servers PS-Remoting has to be enabled, the deployment account requires PS-Remoting access (usually only granted for local admins) and the LoopBackCheck has to be disabled (in order to create the local proxy for warming up the urls).
I hope that clears things up a bit.