Skip to main content

Run powershell from CMD or Task Scheduler


If you want to run a Powershell script against SharePoint on a timely schedule the Windows Task Scheduler is fast an simple approach.

A simple example of this could be a SharePoint warm-up script which hits a number of sites on a regular schedule. However it is maybe not as straight forward to figure out the syntax for the Powershell command as you might think.

Run in CMD



The first step is to verify you can run the script from a command prompt. (you might want to start the command prompt as the account that is going to run the scheduled task).

1. Click start and type CMD, press enter.

2. Paste the following command and replace the script-path with the location of you own script.
    Powershell -file "C:\PathToFile\SharePointWarmupScript.ps1"

3. Press enter and see the script being executed successfully.

Create Task Schedule


The next step is to create the scheduled task.

1. Click start and type Task Scheduler, press enter.

2. Left click Task Scheduler and click Create Task.



 3. Give the task a name, ex. SharePoint Warmup Task.



4. Select your desired options on the Triggers tab.

5. On the Actions tab click New and type the following.
    Program/Script: Powershell
    Add arguments (optional): -file "C:\PathToFile\SharePointWarmupScript.ps1"



6. Click OK to create the task.

The scheduled Powershell task is now created and you can test it out in the Task Scheduled Library if you like.




Comments

Popular posts from this blog

Azure DevOps - Gantt Chart

It's been a while since my last post - in the past couple of weeks I have played around with some videos of topics I find interesting. One of these topics are a very cool way of displaying a Gantt Chart upon your Azure DevOps board's. Check it out here!

Project Server - Change field name on PDP for standard fields (like the Owner field)

Project Server - Change owner field name on PDP The field names on the PDPs (Project Detail Pages) has been preselected on the standard fields for a project. If you want to change the Owner to something else it is quite difficult. In the following i will explain how we can change this field through the Content Editor webpart. To change the owner field add a Content Editor webpart to the PDP page where the field is inserted. Select the webpart and from the ribbon select HTML->Edit HTML Source. Copy/Paste the following code into the Content Editor webpart. < script type ="text/javascript">     var old_name = "Owner" ;     var new_name = "Ansvarlig" ;     var ttnA = document.getElementsByTagName( "div" );     for ( var j = 0; j < ttnA.length; j++) {         var orig = ttnA[j].innerHTML;         var stripped = orig.replace( /^\s*/ , "" ).replace( /\s*$/ , &quo

PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated. Problem: If you for example run the Test-SPsite command you might see something like the following: Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd,