SharePoint Solution Deployer 5
Other Available Downloads
Important: Make sure to "Unblock" the zip file before extracting (see here how to unblock a file). Otherwise you have to unblock each bat, ps1 and exe file one by one to get the script running.How to use it:
- Download SPSD, unblock the file and unzip it on a SharePoint Server
- Drop your WSP files into the "Solutions" folder
- Run Deploy.bat
- New: All extensions added: Blocked file extensions, content type hub, custom crawl connector, features, logging configuration, managed metadata, re-ghost, search schema, secure store, site structure, CSOM extensions for files and 2013 workflows
- Updated: SharePointVersions.xml
- Updated: Typos in comments fixed and some code clean-up
- First release based on GitHub repository
- Fixed CP16809: Error at Register-Extensions when running with PowerShell 2.0
- New: SPSD now has an extension system which allow you to create your custom PowerShell extensions and integrate them in the deployment process!
- New: Added and example extension
- New: Environment file can now be passed as parameter to the batch files
- New: Added timestamps to better measure execution time
- New: Added new deployment command "Ask" which asks the user for the deployment command.
- New CP16167: SPSD now works also when run though an application (e.g. console app), output will be just logged into the log file
- New: Countdown after deployment until windows closes
- Updated: SharePointVersions.xml to include new SharePoint versions for SP2010/SP2013
- Changed: Renamed CustomTarget SkipSolution to ProcessSolution
- Changed: Stability improvments
- Changed: Memory disposal improvements
- Fixed CP16490: Incompatible with Powershell 4.0 due to switch statements
- Fixed CP16441: Compatibility Level ignored for global deploys
- Fixed: CloseAllPSSessions had unused parameter in signature
- Fixed: Startup in batch with relative path when not running from cmdline was failing when user UAC was enabled
- Fixed (not to (-not in line #1054 of SPSD_Deployment.ps1)
- Changed license from GPLv2 to MS-PL
- Updated SharePointVersions.xml to include new SharePoint versions for SP2010/SP2013
- Updated Environment XML schema, existing environments files can be used by updating the version of the SPSD node to 188.8.131.529
- New attributes for CompatibilityLevel, RequiredSharePointLanguages are currently not maintained with SPSD Environment Editor
- New: Custom AppLogo/ProductInfo can be added by changing /scripts/AppLogo.txt
- New CP16175: Custom target "RunCustomPrerequisites": Use this target to run commands after the environment XML is loaded and before the preconditions are checked.
- New CP16175: Custom target "CheckCustomPreconditions": Use this target to run commands after all out-of-the-box precondition checks have been passed successfully.
- New CP16175: Custom target "Initialize": Use this target to perform commands after all precondition checks were successful and before any deploy/update/retract action is started.
- New CP16175: Custom target "Finalize": Use this target to perform commands at the very end before the deployment summary is shown. (runs also in case of an exception)(runs also in case of an exception)
- New CP16176: Custom target "SkipSolution": Use this target to skip a solution based on your own conditions or perform any custom command before the deployment step takes place. It will be run once for each solution for each deployment command.
- New CP16383: Prerequisite check for required Language Packs installed on the farm
- New CP16142: Allow adding SharePoint CompatibilityLevel Parameter (14,15) to each specified farm solution node in the xml. (only SP2013)
- New CP16252: Colorize final status message
- Fixed CP16026: Starting the script failed when running SPSD from a path with spaces
- Fixed CP16326: SPSD on Sharepoint 2010 cant run because of framework 4?
- Fixed CP16333: Deployment to multiple web applications
- Fixed CP16220: Issues with redeploying sandboxed solutions
- Fixed: Retraction error when there was still a previous deployment job running
- Fixed: Only write Transcript in PSConsole to avoid error in ISE
- Updated help for custom events in CustomTarget.ps1
- Changed logtype "Verbose" to "Normal", removed "VerboseExtended", added Success
- Fixed: Bug in editor which prevented from saving to a new file
- Fixed: Bug in editor: Save as file dialog uses now same location as where the file was opened before
- Fixed: Bug in editor: Browsing for files to be references used the wrong source directory
- Fixed (CP15991): Bug in editor: Configuration -> Actions -> Warmup -> All Sites was always checked if attribute was specified in the XML (even though it was false)
- Fixed: Bug in Editor: Environment -> Solutions/Prerequisite Solutions -> Saving custom defined solutions without having URLs specified caused NullPointerException
- Fixed: Method SPSD_Utilities:ReplaceBooleans made more robust
- Fixed: Bug in SPSD_Utilities:ReplaceUserVars when Comments in the variables section caused an exception
- Fixed: Bug in SPSD_Utilities:ReplaceVariables when user variables wern't resolved when reused in other user variables
- Fixed: Bug in SPSD_Deployment:CheckSPMinimalLicense when property was set to Standard but Enterprise was installed
- Fixed: Bug in SPSD_Deployment:GetSolutions if only one solution was configured in the environment XML
- New feature (CP15981): Added optional parameter to PS script allowing to configure an alternative location for the solutions files (thx to tommykri). Can be set in the batch files or when calling SPSD_Main.ps1 directly. Works both with relative or absolute paths.
- New feature (CP15984): Include Central Administation web application on retraction if bin solution has been deployed to it
- Fixed (CP15979): Bug when deploying farm solutions to specific web application urls on SP2010
- Fixed (CP15980): Error when loading external environment node with only one external node specified on SP2010
- Fixed: Bug exception if no variables have been defined in the environment XML
- Fixed: Issue in summary at the very end of the deployment, when the environment script filepath was to long to fit into the * box
- Changed: Changed some variable assignment for better automated testing of the script
- Changed: Logfile timestamp now with seconds
- Fixed: Reusing remote PSSessions instead of opening new ones
- Fixed: Bypass local cache when warming up urls
- Changed: Better error summary if deployment fails, detailled summary will be saved in separate log file
- New : Environment XML file editor, which allows you to configure your deployment configuration conveniently (separate download)
- Fixed: Bug when resetting IIS on multiple servers in farm
- Fixed: Bug when warming up all site collections
- Fixed: Bug when loading nodes from external environment files on SP2010 machines
- Changed: Setting "IncludeAllServersInFarm" to "RunOnMultipleServersInFarm" and allow it to be set to "OnlyLocal", "All", "WebFrontEnd" or "Application"
- Changed: Moved SharePoint versions and licenses lookup data into separate XML file which can be updated easier. The most recent XML file can always be retrieved from http://www.matthiaseinig.de/files/SharePointVersions.xml
- Refactoring / code cleanup
- Minor bugfixes
I love it, easy to use, does exactly what I need.
on Mar 26, 2014 at 2:15 AM
SPSD has enabled us to drop most of our custom scripts in favor of a more robust and reliable solution. I look forward to the next release!
on Oct 4, 2013 at 11:30 AM
Excellent, very stable deployment in farm environment.
on Jun 23, 2013 at 8:06 PM
Brilliant tool. I'm currently using it for 4 different projects. :)
on Feb 19, 2013 at 7:51 PM
Great tool - Very useful!
on Feb 5, 2013 at 11:41 AM
Amazing automated solution for SharePoint deployment. Very flexible and highly configurable. Bliss for SharePoint admins i must say.
on Feb 5, 2013 at 11:36 AM
Great work. I used it for a project and it awsome :)
on Feb 5, 2013 at 11:35 AM
This has been a very good help in a couple of recent projects. It is a very professional software and have been a real timesaver for me personally when administering deployments.
on Jan 24, 2013 at 10:16 AM
Opera does not support ClickOnce X
To install this application, save it and then open it. Opening it directly from Opera will not work correctly.