Sunday, September 29, 2013

How to Rename a SharePoint Group using PowerShell

Requirement: On a marketing site, site owner wanted to rename "Marketing Members" group name to "Marketing Managers" as it makes more sense to him.  To rename a SharePoint 2013/2010 user group, Navigate to:
  • Site settings >> Site permissions >> Pick your target group
  • Click on "Group Settings" from Settings Menu
    how to rename sharepoint group
  • Supply a new name for your SharePoint permission group.
    sharepoint 2010 rename security group
  • Click on Ok to save your changes.
Pretty straightforward, isn't it?

Rename SharePoint group using PowerShell:
Renaming SharePoint groups can be achieved with PowerShell too. Here is my PowerShell script to rename a group in SharePoint 2013:
#sharepoint powershell change group name
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Variables
$SiteURL = "http://intranet.crescent.com/sites/marketing/"
$GroupName = "Marketing Members" 
$GroupNewName ="Marketing Managers"

#Get site and Group objects
$Site = Get-SPSite $SiteURL
$Group = $Site.RootWeb.SiteGroups[$GroupName]

if($Group -ne $null)
    {
        #sharepoint rename permission group
        $Group.name = $GroupNewName
        #Update the group
        $Group.Update()
        Write-host "Group Name has been updated!" 
    }
#dispose site object
$site.Dispose() 
This PowerShell changes SharePoint group name!

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Tuesday, September 24, 2013

Enable Barcodes in SharePoint 2013 / 2010 / 2007

Bar codes are part of SharePoint Information Management Policies (IMP) feature. If you need bar codes for your document, here are the steps to enable bar codes on SharePoint document library.

Steps to enable bar code in SharePoint:
In SharePoint 2013 (In SharePoint 2007 / SharePoint 2010 too!) enabling barcode is a simple two step process. (Lets use it with Document content type.)
  1. Create new content type and enable bar code through Information Management Policies.
  2. Add the content type to required libraries.
Step 1: Create new content type:
  1. Navigate to Site Settings >> Click on "Site Content Types"sharepoint 2010 barcode support
  2. Create New content type by clicking the link "Create"
  3. Give a Name to the content type (E.g. "Project Plan"). Specify the parent content type as "Document Content Type" sharepoint barcode documents
  4.  Enable bar code through Information Management Policies: From the content type settings page, Click on "Information Management Policies"sharepoint 2010 records management barcode
  5. Click on "Enable Bar code" check box, and click "OK" to save changes.sharepoint 2010 barcode support
 Step 2: Add the content to required libraries
We've our content type with bar code enabled ready! Next step is to associate our content types to libraries wherever required.
  1. Go to your target libraries where you need bar code functionality.
  2. Navigate to library settings >> click on "Advanced Settings" >> Enable content types by clicking "Allow management of content types" to "Yes"sharepoint 2010 barcode feature
  3. Now, from the library settings, Click on "Add from existing site content types" link under "Content Types" section.
  4. Choose the content type we created at step 1 (In my case, it is: "Project Plan") and click "OK"
  5. Modify the default view of the document libraries to include Bar code columns.barcode in sharepoint 2010
  6. That's all! We are done! Create new document under the document library, See the bar codes in action!!barcode with sharepoint
Same steps applies to SharePoint 2007/ SharePoint 2010 and for SharePoint 2013.
sharepoint 2010 barcode value
How to Set Custom value to SharePoint Bar Codes?
Well, But the problem is: SharePoint automatically generates unique 10 digit bar code value! we may not need it so in some cases, isn't it? we want to set bar codes to specific value.

Alright, How do I set bar code based on file's meta-data property? We can programmatically set Bar code values. Here is the sample code for SharePoint 2010 custom barcode generator.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
using System.Drawing;
using Microsoft.Office.RecordsManagement.PolicyFeatures;

namespace SetBarCodeValue
{
    class Program
    {
        static void Main(string[] args)
        {
            //Define the parameter values: Site collection URL
            string siteURL = "http://sharepoint.crescent.com/sites/operations";

            using(SPSite site=new SPSite(siteURL))
            {
                using (SPWeb web = site.RootWeb)
                  {
                      //Get a document library
                      SPList list = web.Lists["Design Documents"];
                      //Get an Item 
                      SPListItem item = list.Items[0];

                      //Set Bar code value
                      Image img;
                      string barCodeValue = "900";
                      Barcode.ProvisionBarcodeWithValue(item, true, ref barCodeValue, out img);
                      Barcode.SetBarcodePreview(item);
                      item.Update();                      

                     //Print a message
                     Console.WriteLine("Bar code has been Updated!");
                   }
            }

            //Pause
            Console.ReadLine();
        }
    }
} 
You can place this code under event receiver to set custom barcode values. One draw back with the OOTB SharePoint barcode integration is: it supports only digits!

SharePoint 2010 custom bar code generator:
There are 3rd party components to these limitations and provides enhanced functionalities. Aspose Barcode is one among them. http://www.aspose.com/sharepoint/barcode-component.aspx


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Monday, September 23, 2013

Migrate from SharePoint 2010 to SharePoint 2013 - Step by Step

So you are excited by SharePoint 2013's new features and tend to migrate from SharePoint 2010 to SharePoint 2013? Well, this article walks through moving from SharePoint 2010 to SharePoint 2013 step by step, assuming all necessary migration preparations and planning strategies are done, lets move to the core migration process.

Before you start:
  • Change the Authentication to Claims: Claims authentication is the default authentication in SharePoint 2013. Many dependent services (like Office Web Apps) require Claims authentication in SharePoint 2013. So before migration convert your SharePoint 2010 web applications from Classic mode (which is default in SharePoint 2010) to Claims. Technet Reference: http://technet.microsoft.com/library/gg251985 Also, If you have "Forms" authentication, make sure its configured in your target farm before migration. 
  • Cleanup Before Migration - Clean up an environment before an upgrade to SharePoint 2013 - This includes deleting unused sites/site collections, Removing unused features and solutions, Delete orphaned users and sites, Cleanup old document versions, Removing features which are not supported by SharePoint 2013 (such as Web Analytics). Technet Reference: http://technet.microsoft.com/en-us/library/ff382641.aspx
Its recommended that you run database consistency check before taking database backup from SharePoint 2010 farm.

No more In-place upgrade from SharePoint 2010 to SharePoint 2013! In other words - No direct upgrade is possible from SharePoint 2010 to SharePoint 2013. You can't install SharePoint 2013 on top of SharePoint 2010 (as we can install SharePoint 2010 on top of SharePoint 2007) . So only migration is allowed in SharePoint 2013. You can't re-use your existing Hardware for SharePoint 2013 (Also you can't install both SharePoint 2010 and SharePoint 2013 on same machine).

Migration Steps Summary:

  1. Create new SharePoint 2013 Farm, Setup necessary configurations.
  2. Backup - Restore SharePoint 2010 Content Databases to SharePoint 2013's SQL Sever (or perform a detach-attach process)
  3. Verify content databases by running: Test-SPContentDatabase from SharePoint 2013 farm.
  4. Attach Content Databases to SharePoint 2013 web application by running: Mount-SPContentDatabase
  5. Upgrade Site Collections to move them into SharePoint 2013.

Step 1. Create New SharePoint 2013 Farm:
Install and configure new SharePoint 2013 farm. All farm configurations should be setup as in source SharePoint 2010 Farm, including: All necessary configurations like AAM, Email settings, Managed pats, etc. Install any 3rd party software, language packs, custom features and solutions you had in your SharePoint 2010 farm into your new SharePoint 2013 Farm. Create web application(s) to SharePoint 2013 environment as in your existing SharePoint 2010 farm.

As we are going to use the existing content database from SharePoint 2010, Delete the default content database associated with your new web application. If you failed to delete the web application's root site database, you will get "Orphaned Sites" issue on running Test-SPContentDatabase cmdlet as part of migration process. This is because the root site collection exists in both content databases and leads to conflict!
    Alright, This article assumes new SharePoint 2013 Farm is already installed and configured.

    Step 2. Backup - Restore SharePoint 2010 Content Databases to SharePoint 2013 SQL Sever: 
    Backup SharePoint 2010 content databases, Restore them into SharePoint 2013's SQL Server instance.

    Identify and take a list of your source content databases either from Central Administration (Central Administration >> Application Management >> Manage Content Databases )
    get all content databases of a web application
    Or use this PowerShell cmdlet to retrieve all content databases of a particular web application:
    Get-SPContentDatabase -WebApplication "<Web App URL>" | Select Name
    Optionally, you can Setting SharePoint Content databases to read-only before taking backup. But why? because you may want users to continue using SharePoint 2010, same time preventing any data in-consistency on content migrated to SharePoint 2013. To do so: Go to SQL Management Studio >> database properties >> Options >> Set Database Read-only to "True".

    Backup Databases from SharePoint 2010 SQL Server:
    1. Log-in to SQL Server box of your SharePoint 2010 Farm
    2. Open SQL Server Management Studio, Expand Databases node
    3. Right Click your content database, Choose Tasks >> Backup backup SQL Server database
    4. Set the backup type to "FULL", specify the backup destination and click on "OK" to start backup processbackup SharePoint content database in SQL Server Management Studio
    5. Wait for the backup to complete.SharePoint content database backup
    Repeat this procedure for All content databases of desired SharePoint 2010 web applications.

    Restore Database on SharePoint 2013's SQL box:
    Next step is to Restore all databases taken from SharePoint 2010 to SharePoint 2013 SQL Server.
    1. Copy all required databases backup files to your target SharePoint 2013's SQL Server. 
    2. Open SQL Server Management Studio Right click databases node >>Click Restore DatabaseRestore SQL Server Database
    3. Specify the source as "Device" and Click on the "..." button to add backup files. Click on "Add" button to locate backup files. Restore SharePoint Content Database on SQL Server
    4. Once done, Click on "OK" to return to the restore window. Locate SQL Server backup source
    5. In Destination section , you can type new database name in Database field if you wish to rename your database.Restore SharePoint Databases in SQL Server
    6. Click on "OK" button to start restore process. Wait for the restore successful message.SharePoint Content Database Restore
    7. Once restored, Go to Database properties, Click on Options Tab, Set Database Read-only to False. (If you made it read-only before taking backup!) Set SharePoint Content Database to Read-only

    Step 3. Verify content databases with Test-SPContentDatabase: 
    No more STSADM -o PreUpgradeCheck and its replaced with the PowerShell cmdlet: Test-SPContentDatabase. So we got to execute Test-SPContentDatabase cmdlet which scans content databases of the provided web application and addresses any issues found.

    Syntax:
    Test-SPContentDatabase -Name <Database name> -WebApplication  <Web-App-URL>
    E.g.
    Test-SPContentDatabase -Name "SP2013_Operations_Content" -WebApplication "http://SharePoint13.Crescent.com"
    This would report potential issues such as: Missing Features & Solution dependencies, Orphaned Sites, wide Lists, etc. Resolve Migration issues reported by Test-SPContentDatabase.
    Test-SPContentDatabase Issues

    Test All Content Databases and produce Report
    Lets execute Test-SPContentDatabase for all Content Databases:
    Add-PSSnapin Microsoft.SharePoint.PowerShell -EA SilentlyContinue
    
    #Array to hold Content Databases to Test
    $ContentDBS= ("SP2010_IntranetRoot_Content", "SP2010_Sales_content", "SP2010_Operations_Content")
    
    #Web Application to Host
    $WebAppURL = "http://SharePoint13.Crescent.com"
    
    #Loop through each web web application
    Foreach ($DB in $ContentDBS)
     {
         "Checking Content Database - " + $DB | Write-Host -ForegroundColor Green
    
          "Report to Content Database: $($db)" |  Out-File -Encoding default -FilePath $("D:\DBCheck.csv") -Append 
          #Test Content Database and output report to a CSV file
          Test-SPContentDatabase -Name $DB -WebApplication $WebAppURL | ConvertTo-Csv -NoTypeInformation | Out-File -Encoding default -FilePath $("D:\DBCheck.csv") -Append 
    
      }
      
    This script gives nice report in CSV format for easier analysis. To troubleshoot upgrade issues reported, use http://technet.microsoft.com/en-us/library/cc262967.aspx

    Check the upgrade log and deploy any missing components and re-run Test-SPContentDatabase cmdlet to verify again. Make sure UpgradeBlocking is false to move further!

    Step 4. Attach Content Databases to SharePoint 2013 by running: Mount-SPContentDatabase
    After fixing all issues reported by Test-SPContentDatabase, we can start attaching content databases to SharePoint 2013 web application. Remember: Always mount the root site collection's database first! Also, if you migrating My sites, Migrate My Site Host First!

    Mount-SPContentDatabase -name "SP2013_Operations_Content" -DatabaseServer "G1-SP2013-DB01.Crescent.com" -WebApplication "http://sp13.crescent.com" -confirm:$false
    Once mounted the content database to web application successfully, The site collection is accessible in SharePoint 2010 Mode!

    Step 5. Upgrade Site Collections to move them into SharePoint 2013.
    One more step to complete our migration: Upgrading site collections.
    By default, after migrating from SharePoint 2010 to SharePoint 2013, All migrated site collections will be on SharePoint 2010 format, retaining its old look and feel and other functionalities. We've to explicitly migrate all site collections to SharePoint 2013.

    This can be done by Site collection administrators by clicking links from upgrade reminder banner.

    At Site Collection Level, you can make use of Site Collection Health Checkup:
    New in SharePoint 2013, Site collection Administrators can perform health checkup at site collection level before upgrading site collections from SharePoint 2010 mode to SharePoint 2013! Navigate to
    • Site Settings >> Site Collection Administration 
    • Click on Site collection health checks (Or use PowerShell Test-SPSite -identity <URL>)
    Site collection health checkup report gives customized files, missing galleries, missing Content Types, content type conflicts, missing site templates, unsupported language packs, etc. You can repair some of the issues by running: Repair-SPSite -identity <URL>
    Site collection Health Checkup

    Deferred site collection upgrade - Its a replacement for Visual Upgrade feature (Once site collection is upgraded, can't be rolled back). SharePoint 2013 shipped with files to Support SharePoint 2010. Not just user interface but actual SharePoint functionality itself. E.g. You can find 14 folder on SharePoint 2013 installation. So all files will still be maintained. E.g. Features, Event Receivers, Solutions can be deployed on 14 hive, etc. So, almost all of your existing SharePoint 2010 customizations should just work fine.

    You will see a banner on top of Site collections now!

    To upgrade the site collections: Click on "Start now" link on the banner (You can get there by going to Site Settings >> Site Collection Upgrade as well.)
    Upgrade SharePoint 2010 Site Collections Confirm the site collection Upgrade

    We can monitor the upgrade progress with SiteUpgrade.aspx page, which provides a link to an upgrade log for troubleshooting purposes. From here, you can either start the actual upgrade or create a preview site.
    Monitor Upgrade Status
    SharePoint Farm Administrators can do it through bulk through PowerShell script:
    Upgrade-SPSite -identity "http://sharepointsite" -VersionUpgrade

    We can upgrade all site collections under the specific web application with PowerShell cmdlet:
    #To upgrade all site collections in a Content Database
    Get-SPSite -contentdatabase <content database name> -limit All | Upgrade-SPSite -versionUpgrade 

    Once upgrade completed successfully, Verify Your site collection is with all new SharePoint 2013 features.
    SharePoint 2013 Upgrade Progress

    Get Upgrade Status:
    Upgrade can be time consuming where there is a large number of site collections exists on the given content database. Get the Status of  upgrade from "Upgrade Status" page in central administration page (Central Admin >> Upgrade and Migration >> Check upgrade status )!

    Or use the PowerShell script:
    Get-SPSiteUpgradeSessionInfo -contentdatabase "<Content DB Name>" -showInProgress -showCompleted -ShowFailed 
    Sites will be in locked state until upgrade completed.

    That's all, We are completed now! As a best practice, Review event logs and ULS logs after migration completed successfully!!

    Here is our SharePoint 2010 site:
    sharepoint 2010 to sharepoint 2013 migration
    Here is the SharePoint 2010 site migrated with SharePoint 2013:
    sharepoint 2010 to sharepoint 2013 upgrade
    The Final site after site collection upgrade:

    Additional Things to Consider:

    You can try the Demo Upgrade with Evaluation Site Collection:
    Demo upgrade allows to get the SharePoint 2013 preview of existing site collection by making a copy. You can try it by clicking "Try a Demo Upgrade" link either from "Upgrade Reminder banner " or by going to
    • Site Settings >> Site Collection Admin 
    • Site collection upgrade, click on Try a demo upgrade
    • Site collection admin receives an email when timer job “Create upgrade Evaluation Site Collections” creates a site collection
    Farm administrators can request an Evaluation Site Collection using PowerShell:
    Request-SPUpgradeEvaluationSite -identity <Site Collection URL>

    This Provisions a temporary site collection with SharePoint 2013's look and feel to validate your site collection to get the preview of your site collection on SharePoint 2013. Remember, the evaluation site collection expires after 30 days, and gets auto deleted!
    sharepoint 2010 to sharepoint 2013 migration step by step
    Remember, while upgrading: you can't downgrade! Meaning, you can't upgrade from SharePoint Server to SharePoint Foundation or You can't upgrade from SharePoint Server Enterprise to Standard version!

    Disable Self Service Upgrade
    In some cases, you may want to disable self service upgrade on specific site collections, for e.g. You may want to disable upgrade on heavily customized site collections. We can disable upgrade which hides the "upgrade Reminder" bar at the top of the site collection eventually.

    #Get the site collection
    $Site = Get-spsite "http://Intranet2013.crescent.com/sites/operations"
    #Disable Upgrade options from UI
    $Site.AllowSelfServiceUpgrade = $false

    This disables upgrade options from site the collection by removing the upgrade banner and the "Upgrade Site Collection" button from Site collection upgrade page of site settings. So now, the only option to upgrade is: using PowerShell cmdlet: Upgrade-SPSite

    What about Migrating Service Applications?
    Just because you can migrate service applications, doesn't mean you must! Consider upgrading service applications from SharePoint 2010 to SharePoint 2013 when you have some critical data in it and it involves lot of time to re-do!! I'm keeping it aside for now, will cover this in an another article.

    Upgrade from SharePoint 2007 to SharePoint 2013
    Want to migrate from MOSS 2007 to SharePoint 2013? Sure, But there is no way to migrate from SharePoint 2007 to SharePoint 2013 directly! We've to Migrate from MOSS 2007 to SharePoint 2010 first (can use Staging environment for this!) and then perform SharePoint 2010 to SharePoint 2013 migration again (Or you can use 3rd party migration tools to upgrade from SharePoint 2007 to SharePoint 2013 directly) Read my related posts:

    References:
    I would strongly recommend to go through these excellent technet resources:


    You might also like:
    SharePoint Usage Reports
    Usage reports, collaboration and audit for SharePoint.
    Document SharePoint Farm
    Automatically generate SharePoint documentation.
    *Sponsored


    Saturday, September 21, 2013

    Create SharePoint Site Collection in New / Specific Content Database with PowerShell

    Having a dedicated content database for each site collection is recommended for larger SharePoint site collections. 

    Create site collection in New content database in SharePoint 2010 using PowerShell:

    As the Central Administration doesn't provide any direct interface, lets use PowerShell cmdlet to create site collection in new content database for SharePoint 2010 / SharePoint 2013:
    #Create a New Content Database
    New-SPContentDatabase -name SP2010_Content_Sales -webapplication http://sharepoint.crescent.com
    
    #Create a Site collection in the specific content database
    New-SPSite -Name "Sales" -ContentDatabase SP2010_Content_Sales -url http://sharepoint.crescent.com/sites/Sales/ -OwnerAlias "global\User1" –SecondaryOwnerAlias "corp\user2"
    The above PowerShell script creates new content database and creates site collection in that particular database. Here, Use "-ContentDatabase" parameter to set the target content database.

    But wait, this will not stop SharePoint from placing new site collections to the content database created (SP2010_Content_Sales)! we've to set the MaxSiteCount and WarningSiteCount values to control any future sites.
    $SiteURL= "http://sharepoint.crescent.com/sites/Sales/"
    #Get the Content Database of the site collection and set Maximum & Warning levels for the Sites.
    
    Get-SPContentDatabase -Site $siteURL | Set-SPContentDatabase -MaxSiteCount 1 -WarningSiteCount 0
    

    PowerShell script to Create site collection in specific content database:
    If you want to create new site collection in an existing content database, use this PowerShell script: Say, we've an existing content database: SP2013_Content_Sales and want to create our new site collection in it.

    This PowerShell creates site collection in specific content database.
    Add-PSSnapin Microsoft.SharePOint.PowerShell
    
    $SiteURL = "http://sharepoint.crescent.com/sites/Sales"
    
    #Set exisiting Content Database
    $DatabaseName = "SP2013_Content_Sales"
    
    $PrimaryOwner = “Global\SPFarmAdmin”
    
    $SecondaryOwner = “Global\Salaudeen”
    
    #Create new Site collection on the specific content database
    New-SPSite $SiteURL -OwnerAlias $PrimaryOwner -SecondaryOwnerAlias $SecondaryOwner -ContentDatabase $DatabaseName
    
    
    If you don't want to use PowerShell, its still possible to create site collection in new content database using STSADM and with a Central Admin tweak! Here are the workarounds: Create site collection in new / specific content database SharePoint 2007

    You might also like:
    SharePoint Usage Reports
    Usage reports, collaboration and audit for SharePoint.
    Document SharePoint Farm
    Automatically generate SharePoint documentation.
    *Sponsored


    Tuesday, September 17, 2013

    Configuring Workflow Manager in SharePoint 2013 - Step by Step Guide

    Introduction
    By default, SharePoint 2013 doesn't come with SharePoint 2013 workflow engine. We get only SharePoint 2010 workflow platform type in SharePoint Designer 2013. So, we got to manually configure SharePoint 2013 workflows. This implementation guide walks through configuring Workflow Manager 1.0 step by step.
    sharepoint 2013 workflow manager

    Steps summary:
    1. Download and install Workflow Manager
    2. Register Workflow Manager with SharePoint

     

    Step 1: Download and install Workflow Manager

    SharePoint 2013 introduced isolation of Workflows from SharePoint. Meaning we can install workflow components either on server(s) which is part of SharePoint farm or we can have workflow components on server(s) which in NOT part of SharePoint farm (even to Azure - Cloud)! Here, Lets install workflow Manager in one of the SharePoint Application server. Its a best practice to use dedicated accounts for Workflow setup and workflow service. Workflow Setup account must have SysAdmin access rights on SQL Server and local administrator on workflow server.

    In Short: Workflow Engine can be hosted outside SharePoint 2013 Farm!
    1. To begin with installation, Log in to your target server where you are going to install workflow components by opening below download link.
    2. Workflow Manager uses the Web Platform Installer from Microsoft. So, opening this link http://go.microsoft.com/fwlink/?LinkID=252092 for the first time will install "Web Platform Installer".
    3. Installing Workflow Manager is pretty straight forward. Accept License agreement and click on “Install” button
      sharepoint 2013 workflow manager install
    4. Wait for the installation to compete.  
      sharepoint 2013 workflow manager download
    5. Once installed, open it again to start Workflow Manager Installation.  
      sharepoint 2013 workflow manager tutorial
    6. Click on "Install" button
      sharepoint 2013 workflow manager client
    7. Install the prerequisites by clicking “I Accept”
    8. Wait for the installation to be completed
    9. Once installed you will need to configure the Workflow Manager. Clicking Continue will pop up the configuration screen. 
    10. Choose the "Configure Workflow Manager with Default Settings (Recommended)" option
      sharepoint 2013 workflow manager Configuration
    11. In the New Farm Configuration wizard, enter the required fields, such as: Database Server, Service account user name & password, Make sure you remember or keep safe the Certificate Generation Key, as its needed when you want to add more servers to the WM farm. Make sure the service account is under local administrators group of the server. 
    12. Verify the configuration summary and proceed next.
    13. Wait for the installation to be completed  
      sharepoint 2013 workflow manager installation
    14. Click on "Finish" button to complete installation on the screen states that the installation successfully installed.
        
    Install Workflow Manager Client on All other servers of the Farm:
    If you have multiple servers, download and install Workflow Manager Client on every WFE Server: http://go.microsoft.com/fwlink/?LinkID=251617 

    Verify the Workflow Manager Installation
    Let’s verify the workflow manager Installation by accessing: http://localhost:12291 or http://<host url>:12291 (if host header configured).
    sharepoint 2013 workflow manager install verification

    Step 2: Register Workflow Manager

    Alright, We've Workflow components installed. Now, the next step would be registering workflow service with SharePoint 2013. Open SharePoint Management Shell and run as Administrator:
    Register-SPWorkflowService –SPSite "http://intranet.crescent.com" –WorkflowHostUri "http://G1SPWFE03:12291/" –AllowOAuthHttp
    Where
    • http://intranet.crescent.com - is my web application URL
    • G1SPWFE03 - is one of my WFE in SharePoint 2013 farm. 12291 is the port where Workflow Manager is configured (Get it either during installation summary or from IIS). You can also use: Get-WFFarm | ft HttpPort
      sharepoint 2013 workflow manager port
    • AllowOAuthHttp - I'm using HTTP protocol here to allow the communication between SharePoint and Workflow Manager over HTTP.
    Although the parameter -SPSite sounds like workflow manager will get activated only for the given site collection, It’s actually get activated all site collections in the given web application

    Done! Lets see the output in action:
    Restart SharePoint Designer 2013 and see "SharePoint 2013" listed under Platform type in addition to "SharePoint 2010 Workflow".
    sharepoint designer 2013 Platform type sharepoint 2013 workflow

    Still not getting "SharePoint 2013 Workflow"?
    This could be because, "Workflow Service Store" hidden Feature is not enabled (such as when you use "Blank" site template, This feature may not be activated! )

    Activate it with PowerShell:
    Enable-SPFeature -Identity WorkflowServiceStore –Url <your-site-collection-url>

    Technet Workflow Configuration Videos: http://technet.microsoft.com/en-us/library/dn201724%28v=office.15%29.aspx
    Install and configure workflow for SharePoint Server 2013: http://technet.microsoft.com/en-us/library/jj658588%28v=office.15%29.aspx

    You might also like:
    SharePoint Usage Reports
    Usage reports, collaboration and audit for SharePoint.
    Document SharePoint Farm
    Automatically generate SharePoint documentation.
    *Sponsored


    You might also like:

    Related Posts Plugin for WordPress, Blogger...