Before you begin, check out our demos article page.
- Download and Install latest edition of ShortPoint. Get it from our website here.
The demo will not work on the old edition of ShortPoint.
- All the work here should be done in your SharePoint Server 2013/2016.
- Create new team site or subsite at your server
- The account "SharePoint Admin" should have SPDataAccess permission to the content database
Step 1: Download Demo Content
- Download demo content zip file from this link.
- Extract the zip file in your SharePoint Server ( in this example we'll be extracting them into c:\backup )
Step 2: Import Demo Content
Open the folder where you have extracted the .zip file.
- Right click on this file "import.shortpoint.demo.ps1"
- Press Run with PowerShell
What is this script (import.shortpoint.demo.ps1)?
The script will import the list backup files of ShortPoint demos, and import them in your site
- The script will ask you about the site where you want ShortPoint demos to be imported
PowerShell now will prompt you for the following information:
Input the Root Site URL: This is the root site URL of your SharePoint Server ( in this example, our Site Url is http://sharepoint-2013 )
Input the Path to the Site: The path to the site or subsite, in our example we have subsite and the path is /demo
Leave it blank, and content will be imported to the root site.
The path where you extracted shortpoint demo contents: Full path of the folder that contains shortpoint .cmp files. In this example, we have exported them into c:\backup
... it will take few minutes ...
Once the import is done, refresh your demo site and open shortpoint_demos library.
Step 3: Have Fun :)
You should see the starter page of the demos:
If you faced issue while executing the script, try this method:
1. Open SharePoint 2013 Management Shell,
And paste the following command
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
This command is necessary before running the downloaded PowerShell script, as if you attempt to run our script, PowerShell will not execute the script because it is not signed, so here we explicitly tell PowerShell to set execution policy to baypass any non-signed scripts for the current session ( Don't worry, once you close the PowerShell window, execution policy will return to its default state and will not remain Bybass )
3. Type the full path of the script. You can drag the downloaded PowerShell script into the PowerShell window, and hit Enter
make sure there are no spaces in the path and the path is not between " "