PowerShell - Solution deployment simplified

As a SharePoint developer or Admin, what we do most frequently in our day-to-day activities; is to play around with SharePoint solutions (WSPs) and Features..

And since we cannot memorize all the available operations, here are simplified PowerShell commands:

SPSolution Operations:

Add Solution to SharePoint Farm- You are ready with solution package (WSP) for deployment and this is a fresh deployment; first time deployment to the farm. SharePoint can consume a solution only if it is uploaded in SP solution store, and the operation to upload a solution is Add-SPSolution

Command:

Add-SPSolution -LiteralPath -Confirm

Parameters:

LiteralPath: Mandatory, Takes full path of WSP as string

Confirm: Optional, Ask for confirmation before operation

Example:

Add-Spsolution -Literalpath "C:\Solutions\MySolution.wsp"

Install Solution - Now solution is available in farm, next step is to use it. Installing a WSP comes with many options based on scope (for specific web application or all) and content (DLL(s) for GAC or files).

Command:

Install-SPSolution -Identity -GACDeployment

Install-SPSolution -Identity -AllWebApplication -GACDeployment

Install-SPSolution -Identity -WebApplication -GACDeployment

Parameters:

Identity: Required, Full name/GUID of WSP as string

AllWebapplications: Optional, If WSP to be used by all webapplications in farm

WebApplication: Optional, If WSP is for specific web application, URL as string

GACDeployment: Optional, If WSP includes some DLL to GAC

Force: this parameter can be used if installation is throwing some error due to feature activation or time job issue.

Confirm: Optional, Ask for confirmation before operation

Example:

Install-SPSolution -Identity "MySolution.wsp" -GACDeployment

Install-SPSolution -Identity "MySolution.wsp" -AllWebApplication -GACDeployment

Install-SPSolution -Identity "MySolution.wsp" -WebApplication "http://mysite.mydomain.com/" -GACDeployment

Upgrade a deployed Solution- Your solution package (WSP) is already deployed and installed; now you did some changes in code and want to deploy the latest, here comes Update-SPSolution. This command will upgrade the deployed solution with latest DLL(s) and files.

Command:

Update-SPSolution -Identity -LiteralPath -GACDeployment

Parameters:

Identity: Required, Full name/GUID of WSP as string

LiteralPath: Mandatory, Takes full path of WSP as string

GACDeployment: Optional, If WSP includes some DLL to GAC

Force: this parameter can be used if installation is throwing some error due to feature activation or time job issue.

Confirm: Optional, Ask for confirmation before operation

Example:

Update-SPSolution -Identity MySolution.wsp -LiteralPath "C:\Solutions\MySolution.wsp" -GACDeployment

Deployment Rollback: There are scenarios where we may need to rollback the deployment; If the deployment caused some major issue in farm/application or you added a big component (i.e.-site/list definition) in you solution and want a fresh deployment. To rollback a deployment, first retract/uninstall the WSP and then remove it from farm.

Retract Solution - Similar to installation, uninstalling a WSP comes with many options based on scope (for specific web application or all).

Command:

Uninstall-SPSolution -Identity -Confirm

Uninstall-SPSolution -Identity -AllWebApplication -Confirm

Uninstall-SPSolution -Identity -WebApplication -Confirm

Parameters:

Identity: Required, Full name/GUID of WSP as string

AllWebapplications: Required, If WSP to be retracted from all webapplications in farm

WebApplication: Required, If WSP is for specific web application, URL as string

Confirm: Optional, Ask for confirmation before operation

Example:

Uninstall-SPSolution -Identity "MySolution.wsp"

Uninstall-SPSolution -Identity "MySolution.wsp" -AllWebApplication -Confirm:$false

Uninstall-SPSolution -Identity "MySolution.wsp" -Webapplication "http://mysite.mydomain.com/" -Confirm:$false

Remove Solution to SharePoint Farm- After retraction, solution can be removed from SharePoint farm solution store.

Command:

Remove-SPSolution -Identity -Confirm

Parameters:

Identity: Required, Full name/GUID of WSP as string

Confirm: Optional, Ask for confirmation before operation

Example:

Remove-SPSolution "MySolution.wsp"

Remove-SPSolution -Identity "Unilever.Global.CDF.wsp" -Confirm:$false

SPFeature Operations:

Install/Uninstall Features in SharePoint Farm- Normally feature installation/un-installation are taken care with SPSolution operations which contains the feature. But we come across situations where features needs to be Installed/Uninstalled separately. Below are the commands and examples.

Install Feature Command:

Install-SPFeature -Path -Force -Confirm

Parameters:

Path: Mandatory, Takes relative path from the folder “$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\” to the feature as string

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force installation.

Example:

Install-SPFeature -Path "MyFeature"

Un-Install Feature Command:

Uninstall-SPFeature -Path -Force -Confirm

Parameters:

Path: Mandatory, Takes relative path from the folder “$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\” to the feature as string

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force operation.

Example:

Uninstall-SPFeature -Path "MyFeature"

Activate/Deactivate Feature- Below are the commands and examples.

Activate Feature Command:

Enable-SPFeature –Identity -URL Force -Confirm

Parameters:

Identity: Required, Name or GUID of feature as string

URL: Optional,Site/Web URL depending on feature scope

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force installation.

Example:

Enable-SPFeature –Identity "MyFeature" -URL "http://mysite.mydomain.com"

Deactivate Feature Command:

Disable-SPFeature –Identity -URL Force -Confirm

Parameters:

Identity: Required, Name or GUID of feature as string

URL: Optional,Site/Web URL depending on feature scope

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force operation.

Example:

Disable-SPFeature –Identity "MyFeature" -URL "http://mysite.mydomain.com"

PowerShell : Start up

Windows PowerShell (PS) is a shell scripting, provided by Microsoft. This is mainly used for Windows and Server administration. This is very powerful tool for administrators. Here we’ll cover basics of PowerShell. Refer http://msdn.microsoft.com/en-us/library/windows/desktop/aa973757(v=vs.85).aspx for more details.
In this post I would give a start-up that how PowerShell is used for SharePoint.
Start: Assuming PowerShell is installed on your machine. Open the PS (PowerShell) console. [Start-> All Programs->Accessories -> Windows PowerShell]
Type Dir on blue console and enter-> Enter : It will show your directory information. Similarly we can do all kind of windows activities from this console. PS is packaged with large number of cmdlets, which are light weight commands to perform different activities, check http://msdn.microsoft.com/en-us/library/windows/desktop/ms714395(v=vs.85).aspx and http://technet.microsoft.com/en-us/scriptcenter/dd772285.aspx for details on PS cmdlets.
So now we know what PowerShell is and how to use it. Now, how to use this for SharePoint? SharePoint cmdlets are available in a snap in which should be added to Windows PS first to use it.
Type below command on console and enter [on SharePoint server]:
Add-PSSnapin Microsoft.SharePoint.PowerShell
Now, we are all set..
Enter Get-SPSite on console, hit Enter and you’ll get list of all the site collections available in your SP Farm.
Some important points:
1. SharePoint 2010 Management Shell is a PS console for SP packaged and installed with SP2010 and can be used directly, no additional snap-in required.
2. Login account need appropriate permissions on SP Server and SP Databases to execute cmdlets/scripts.
It’s just a beginning..
Happy scripting :) 

SharePoint Incoming Email Configuration - PowerShell

PowerShell is a strong windows shell scripting, which is widely used in SharePoint 2010. Here I am sharing small and useful scripts we use for SharePoint Farm administration.

Requirement:
Configure Incoming Email settings in SharePoint farm.


Script:

# *******************************************************************
## Function - Configure Incoming Email settings in SharePoint farm
## Author - Deepak Solanki
## Checks to ensure that Microsoft.SharePoint.Powershell is loaded, if not, adding pssnapin
## Configure Incoming Email settings in SharePoint farm
# ********************************************************************
#Add SharePoint Add-ins
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue 
# if snapin is not installed then use this method
[Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")


Write-Host "Script started to Configure Incoming Email." 


  #Variables to get config values    
 [boolean]$Enabled = $true;
 [boolean]$UseAutomaticSettings = $false;
 [boolean]$UseDirectoryManagementService = $true;
[boolean]$RemoteDirectoryManagementService = $false;
$ServerAddress = "EXCHANGE.DOMAIN.COM";
[boolean]$DLsRequireAuthenticatedSenders = $true;
[boolean]$DistributionGroupsEnabled = $true;
$ServerDisplayAddress = "sharepoint.company.com";
$DropFolder = "c:\inetpub\mailroot\drop";

#Test the drop folder location exists before proceeding with any changes
$dropLocationTest = Get-Item $DropFolder -ErrorAction SilentlyContinue
if ($dropLocationTest -eq $null)
{
Throw "The drop folder location $DropFolder does not exist - please create the path and try the script again."
}

    #Configuring Incoming E-mail Settings
    try
    {
$type = "Microsoft SharePoint Foundation Incoming E-Mail"
$svcinstance = Get-SPServiceInstance | where { $_.TypeName -eq $type}
$inmail = $svcinstance.Service


if ($inmail -ne $null)
        {
Write-Log "Configuring Incoming E-mail Settings."            
#Enable sites on this server to receive e-mail
                $inmail.Enabled = $Enabled
            
#Automatic Settings mode
                $inmail.UseAutomaticSettings = $UseAutomaticSettings
            
#Use the SharePoint Directory Management Service to create distribution groups
                $inmail.UseDirectoryManagementService = $UseDirectoryManagementService
            
#Use remote: Directory Management Service
                $inmail.RemoteDirectoryManagementService = $RemoteDirectoryManagementService
            
#SMTP mail server for incoming mail
                $inmail.ServerAddress = $ServerAddress            

#Accept messages from authenticated users only
                $inmail.DLsRequireAuthenticatedSenders = $DLsRequireAuthenticatedSenders
            
#Allow creation of distribution groups from SharePoint sites
                $inmail.DistributionGroupsEnabled = $DistributionGroupsEnabled
            
#E-mail server display address
                $inmail.ServerDisplayAddress = $ServerDisplayAddress
            
#E-mail drop folder
                $inmail.DropFolder = $DropFolder;  

$inmail.Update();
Write-Host "Incoming E-mail Settings completed."
        } 
    }
    #Report if there is a problem setting Incoming Email
    catch { Write-Host "There was a problem setting Incoming Email: $_" }

SharePoint Diagnostic Configuration - PowerShell

PowerShell is a strong windows shell scripting, which is widely used in SharePoint 2010. Here I am sharing small and useful scripts we use for SharePoint Farm administration.

Requirement:
Setting SharePoint Diagnostic and logging configuration.


Script:

# *******************************************************************
## Function - Configure Diagnostic Setting in SharePoint Farm
## Author - Deepak Solanki
## Checks to ensure that Microsoft.SharePoint.Powershell is loaded, if not, adding pssnapin
## Check log file location exists before proceeding with changes
## Reset all log levels to default
## Change Trace Log settings
# ********************************************************************


#Add SharePoint Add-ins
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue 
# if snapin is not installed then use this method
[Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")


Write-Log "Script started to Configure SharePoint Diagnostic settings."  
#Reset all log levels to default
Write-Host "Resetting all log levels to default."
Clear-SPLogLevel
Write-Host "Reset Completed."


#Declare variable for config values
$LogLocation = "E:\Logs"
$DaysToKeepLogs ="14"
[boolean]$LogMaxDiskSpaceUsageEnabled = [Boolean]::Parse("true")
$LogDiskSpaceUsageGB = "10"

#Test the log file location exists before proceeding with any changes
$logLocationTest = Get-Item $LogLocation -ErrorAction SilentlyContinue
if ($logLocationTest -eq $null)
{
Throw "The log file location $LogLocation does not exist - please create the path and try the script again."
}
#Trace Log settings
Write-Host  "Starting SharePoint Diagnostic configuration."
try
{
    Set-SPDiagnosticConfig -LogLocation $LogLocation `
                        -DaysToKeepLogs $DaysToKeepLogs `
                        -LogMaxDiskSpaceUsageEnabled:$LogMaxDiskSpaceUsageEnabled `
                        -LogDiskSpaceUsageGB $LogDiskSpaceUsageGB
}
#Report if there is a problem stopping the service instance
catch {  Write-Host  "There was a problem in diagnostic setting: $_" }
Write-Host  "Diagnostic settings changed successfully."