Within PowerShell their are two different types of comments: Inline comments and Block comments.
Inline comments are denoted by a # symbol at the start of the line. This comment only affects a single line.
Block comments are opened using <# and closed using #> these comments can span multiple lines.
“This post details the steps for backing up the content database of a SharePoint site through PowerShell. Click here to view the steps for backing up a content database through Central Administration.”
PowerShell provides a means to backup data within SharePoint through the following command:
Further information on each of the parameters in this command are outlined bellow.
The Directory parameters specifies the path where the backup will be generated. This can either be a UNC path or a location on the server. “You don’t need to enter the spbr* folder name as this will be auto generated”
BackupMethod
The backup method parameter details the type of backup that will be performed. This can either be Full or Differential:
In order to get the path to the item you can use the following command:
This will list the tree structure of items within the farm. In my experience the path to a content database within the farm is in the following format:
“Farm\Microsoft SharePoint Foundation Web Application\[Site Name]\[Content Database Name]”
This parameter is optional. The verbose parameter provides more information about the operation being run.
This parameter is optional. The percentage parameter can be used to report progress about the operation at defined percentage intervals.
“This post details the steps for backing up the content database of a SharePoint site through Central Administration. Click here to view the steps for backing up a content database through PowerShell.”
Within Central Administration within the Backup and Restore section click on Perform a backup
Next you need to select the component that you wish to backup.
Select the component you want to backup and click Next
The next step in the backup process allows you to choose the type of the backup and its location.
A backup can be either Full or Differential
The backup file location can either be a UNC path or location on the server, however, the process running the backup will need to access to write to this location.
Once the details of the backup have been entered click Start Backup
When the backup is running the following screen will be displayed indicating that backup is currently in progress.
When the backup has finished running the following screen will be displayed indication the status of the backup components.
When deploying a change to an existing timer job you need to restart the SharePoint Timer Job (owstimer.exe) service before the changes will be applied.
This can be achieved through:
In my experience you need to restart the time job service on each web front end.
I recently came across a tool that makes authoring PowerShell scripts easier PowerGUI.
PowerGUI and its in-built intellisense allows you to browse through the different PowerShell commands and unlock the power of PowerShell to automate administrative tasks and quickly change objects within the SharePoint API.
You can download it from here
Once you have downloaded and installed the program you need to load in the Microsoft.SharePoint.PowerShell library snapin.
Within PowerGUI Click on File then PowerShell Libraries
In the Snapins/Modules window Select the Microsoft.SharePoint.PowerShell library and Click OK
You are now ready to start using the SharePoint PowerShell library. Click New File
Within the PowerGUI code editor when you type you should know have IntelliSense on the different SharePoint - PowerShell commands.
Once you have created your new script you can run it by clicking on the Start icon
The output from your script will know be output in the console window.
Within an anonymous access SharePoint site you may wish to prevent users from navigating to the underlying lists e.g:
This can be achieved by activating the ViewFormPagesLockdown feature. This is a hidden feature, however, you can access it through PowerShell.
Get-SPFeature | where { $_.DisplayName -eq "ViewFormPagesLockdown"}
Enable-SPFeature -url http://sharepoint -identity 7c637b23-06c4-4724-9a9a-7c175762c5c4 -confirm:$falseAnonymous users will now need to authenticate in order to view the underlying SharePoint lists and libraries.
Note
“As this feature is activated across a site collection this can lead to issues with anonymous users posting comments on blogs etc.. However the following blog details a method for overcoming this.”
When creating an external facing SharePoint site you are probably going to have to configure anonymous access to allow users to view your site.
You can achieve this by following these steps:
Within central administration Click on Application Management then Manage web applications.
Select the web application that you want to configure anonymous access for and Click on Authentication Providers.
Within the Authentication Providers window Click Default
Within the Edit Authentication window scroll down and Select the Enable anonymous access checkbox. Then Click Save.
After editing the authentication Select the desired web application and Click Anonymous Policy
Within the Anonymous Access Restrictions window select None – no policy then Click Save
Within the web site you have configured anonymous authentication on navigate to Site Permissions
You can achieve this through Site Actions – Site Permissions
Within Site Permissions Click Anonymous Access.
Within the Anonymous Access window you can specify what items have anonymous access. Select Entire Web site then click OK.
Anonymous access should now be configured and your site permissions should display something similar to the following:
Note
“After enabling anonymous access you may wish to prevent anonymous users from accessing the underlying SharePoint lists and libraries e.g:
The can be achieved through the ViewFormPagesLockdown feature. Click here for details on how to configure this.”
