-
Notifications
You must be signed in to change notification settings - Fork 14
Manual Installation
Peter Kjaer edited this page Mar 21, 2015
·
10 revisions
- Ensure that you can run unsigned local scripts, by calling
Set-ExecutionPolicy
. We recommend theRemoteSigned
policy. See Using the Set-ExecutionPolicy Cmdlet for more information. - Download the ZIP for the latest release.
- Open the Properties of the ZIP file and click the Unblock button (if available).
- Extract all files from the ZIP and rename the root folder from "tridion-powershell-modules-x.x.x" to "Tridion-CoreService".
- Copy the Tridion-CoreService directory to your PowerShell Modules folder.
- The default on most desktops is: %UserProfile%\Documents\WindowsPowerShell\Modules.
- You can see the current folders where PowerShell looks for modules, by typing '$PSModulePath'. If you don't know which one to use, just pick the first one.
- Create the necessary directories if they do not exist already.
- Start a new PowerShell terminal and type:
Import-Module Tridion-CoreService
- Optionally, set the Tridion version and connection options by calling
Set-TridionCoreServiceSettings
. By default it will connect to a 2011 SP1 Core Service on the local machine using wsHttp. That works on all supported Tridion versions, but if you have a newer version installed you may wish to update the version used by the modules. - Call
Get-TridionUser
to test if everything is working.
You can get the list of all of the commands by typing this in PowerShell:
Get-Command -Module Tridion-CoreService
Each of the commands also has help information available (including examples), which you can read by calling Get-Help nameOfCommand
(e.g. Get-Help Get-TridionUser
).
If you have any issues or questions, feel free to add an entry under Issues.