Installation
Review prerequisites and details on how to get setup with SPE.
Last updated
Review prerequisites and details on how to get setup with SPE.
Last updated
Take a quick look at the to see which version of SPE you should be installing that is compatible with your Sitecore environment. Generally SPE has pretty good backwards compatibility but may require a new version to support the latest Sitecore CMS release.
Windows Management Framework 5.1 (PowerShell) is generally available for most Windows environments.
PowerShell set to RemoteSigned
(probably optional)
Working with Docker is going to be the preferred method of installation.
You can find two flavors of the images:
Ex: docker pull sitecorepowershell/sitecore-powershell-extensions:6.4-1809
Sitecore Built
Ex: docker pull scr.sitecore.com/sxp/modules/sitecore-spe-assets:6.4-1809
With this approach, you essentially add a new layer during your image build to include the files from the asset image. Here are some samples of what you can add to your existing setup. Check out Sitecore's samples for additional guidance.
docker-compose.yml
Dockerfile (mssql-init)
Dockerfile (cm)
The SPE module installs like any other for Sitecore. This approach is appropriate for installations not within a containerized environment.
For Sitecore 10.1 and newer along with Identity Server you should enable the provided configuration Spe.IdentityServer.config.
For Sitecore 10.1 and newer you can leverage the IAR packages. There is still the need for dacpac deployments because SPE includes a security user and role.
We've tried to make upgrading SPE as seamless as possible. The following should provide you with some basic information on what to expect when upgrading.
You should be able to install directly over the previous installation of 6.0+.
For Sitecore 10.1 and newer along with Identity Server you should enable the provided configuration Spe.IdentityServer.config.
For Sitecore 10.1 and newer you can leverage the IAR packages. There is still the need for dacpac deployments because SPE includes a security user and role.
These versions used a different name for the assemblies and configs. You may find it easier to delete all files originally distributed with SPE before installing a newer version. Here are a few steps to consider:
Delete all files in the bin and App_Config/Include directories prefixed with Cognifide.
Delete /sitecore modules/Shell/PowerShell
Delete /sitecore modules/PowerShell
Reference the original SPE package (if available) to identify if any other files were included.
Sitecore items in the content tree will potentially shuffle around into their new location. Be sure to backup your custom scripts first.
the module from the GitHub releases page and install through the Installation Wizard.
An additional patch is required for 10.1 to include the location /sitecore modules/items/
. See .
An additional patch is required for 10.1 to include the location /sitecore modules/items/
. See .
Using packages with the Items as Resources (IAR) files will require additional steps to remove database records that correlate with the contents of the *.dat files. Refer to the Sitecore documentation when upgrading for the process to cleanup the databases. may be helpful if you wish to take a more precise approach.
See the troubleshooting section