Sitecore Powershell Extensions - enable SPE Remoting with media upload

Discover the seamless setup process and troubleshooting tips for running Sitecore PowerShell Extensions scripts remotely, empowering you to automate tasks effortlessly.

Posted: 8/7/2020

Sitecore Powershell Extensions is a powerful tool which allows to automate various tasks within the Sitecore platform. Sometimes it may require running SPE scripts remotely. This is why Sitecore PowerShell Extensions Remoting was developed. There are few things you need to remember while setting up your instance to run scripts remotely. Below I have described the installation process of SPE Remoting, the problems I encountered and their solutions.

Here you can find official documentation on this topic - Sitecore PowerShell Remoting.


  • Sitecore PowerShell Extensions installed on your instance (in my case - version dedicated for Sitecore XP 9.3)
  • Sitecore PowerShell Extensions Remoting - download.

Create SPE Remoting user

Start with creating a new user in the User Manager. Assign a role dedicated for remoting - sitecore\PowerShell Extensions Remoting. Of course, you can use the Sitecore Admin account instead, but it’s not good practice to give the remote user full access to the instance.

User creation window - Sitecore XP User Manager.

Enable SPE Remoting and Media Upload

Sitecore PowerShell Extensions has its own dedicated config file which you can find here:


You can enable remoting by changing enabled attribute value of remoting setting to true. I do not recommend this. With this approach, you cannot track the history of changes to the file and you will irretrievably lose the way config looked originally. I propose preparing patch file in your VS solution folder instead.

Example patch file code with mediaUpload enabled (based on official documentation).

<configuration xmlns:patch="" xmlns:role="" xmlns:security="">
  <sitecore role:require="Standalone or ContentManagement" security:require="Sitecore">
          <patch:attribute name="enabled">true</patch:attribute>
          <patch:attribute name="enabled">true</patch:attribute>

Besides the mediaUpload mentioned above, you can enable various kinds of services via a patch file depending on your needs. Full list and descriptions - SPE Service Descriptions.

Remember about config files patching order!

There is one problem with using patch file - if you’re following Helix principles and naming conventions, your patch file will be overwriten by the SPE.config file. Adding “classic” Z to the beginning of the file name is not enough, because files from Project folder are loaded before SPE folder (alphabetical order). My suggestion is to add SPE folder on the same level as your project configs - as on the screen below.

Project structure - SPE config patch file location.

To check if your config was properly patched, go to your-instance-url/sitecore/admin/showconfig.aspx page and find remoting setting.

Config file with patch applied.

Testing solution

After completing the above steps, it’s time to test your solution. Here’s a sample code to verify that everything is set correctly.

Scenario: Running SPE script on local machine/VM, SPE module downloaded to modules folder in the script location.

# Parameters declaration

# Import SPE module
Import-Module -Name ".\\modules\\SPE"

# Create session and log to Sitecore
$session = New-ScriptSession -Username $SitecoreUser -Password $SitecorePass -ConnectionUri $url

# Publish item
Invoke-RemoteScript -Session $session -ScriptBlock { 
	Get-Item -Id $itemId | Publish-Item -Recurse -Target web

# Stop session
Stop-ScriptSession -Session $session

Bonus: Download failed. The specified media is invalid.

There is also one special error which may occur while working with SPE Remoting media upload. When I was trying to upload test CSS file I got following error in console:

Download failed. The specified media is invalid.

I had no idea how to fix it - everything seemed to work fine except the upload data part. The solution was quick and easy but hard to find. It turns out that Sitecore (or SPE) detects that the file being uploaded has no content. So remember, even for test purposes don’t use empty files.


Hero photo by Kelly Sikkema on Unsplash