Tuesday, July 19, 2016

Approval Workflow Missing in SharePoint 2013?

Problem: SharePoint approval workflow not available! This happened after migrating from SharePoint 2013 to SharePoint 2016!
sharepoint 2013 approval workflow missing

Solution: This is due to workflow feature not activated for the site collection. To resolve this issue, Just Activate "Workflows" feature for the site collection. Steps in detail:
  • Login to your the target site collection as Site collection administrator
  • Click on Site settings gear >> Click on "Site collection Features" and click activate button next to "Workflows" Feature.
  • That's it! This brings approval workflows back!and all other out of the box workflows like collect feedback, Collect signatures, etc
sharepoint 2010 approval workflow not available

PowerShell Script to activate Workflows feature for all site collections:
You can use PowerShell to activate workflow feature on all site collections, which resolves approval workflow template missing issue.
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
#Workflow Feature ID

#Get all Site collections in the farm
$SiteColl =  Get-SPSite -Limit All 
#$SiteColl = Get-SPWebApplication -Identity "http://intranet.crescent.com" | Get-SPSite -Limit All

#Get the Target Feature to Activate
$FeatureToActivate = Get-SPFeature | Where {$_.ID -eq $FeatureID}
#Iterate through each site collection
ForEach($Site in $SiteColl)
    #Check if Feature is already activated
    $FeatureActivated = Get-SPFeature -site $Site | Where {$_.ID -eq $FeatureId}
    If($FeatureActivated -ne $null)
        Write-Host "Feature is already activated at: "$site.Url -ForegroundColor Yellow
        #Activate the feature
        Enable-SPFeature -Identity $FeatureID -URL $Site.URL -Confirm:$False
        Write-Host "Activated Feature on "$site.Url -ForegroundColor Green
Tags: approval workflow missing in sharepoint 2013, approval workflow missing sharepoint online, approval workflow not available sharepoint, sharepoint 2010 approval workflow not available, sharepoint approval workflow missing, sharepoint approval workflow not showing, sharepoint approval workflow template missing

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

Friday, July 15, 2016

How to Change Server MinRole After Installing SharePoint 2016

One of the exciting new feature in SharePoint 2016 is Minrole. It defines server's role in the SharePoint 2016 farm, and makes sure all necessary services are running in that server! SharePoint 2016 comes with below Minroles:
  1. Single Server Farm
  2. Front End
  3. Application
  4. Distributed Cache
  5. Search
  6. Custom
Change MinRole in  SharePoint 2016:
Server roles are selected during the installation of SharePoint 2016 or when you join a server to your farm. Based on the Server role selected, certain services will get activated on selected servers. What if you want to change the server role after SharePoint has been provisioned?  With the introduction of MinRoles in SharePoint 2016, its fairly straightforward to switch server roles between anyone among them:
  • Go to SharePoint 2016 Central Administration >> System Settings 
  • Click on Convert server role in this farm under Servers
How to Change Server Role in SharePoint 2016
Now, It takes you to the "Role conversion" page, where you will see the options for all Minroles. Pick the new role from the dropdown and click Apply,  Your server will be changed to New role!
swith server MinRole after provisioning SharePoint 2016
You can't combine two or more MinRoles in one server. However, You can use the Custom role  to achieve the same! To check roles assigned to servers in the farm, Go to: SharePoint 2016 Central Administration >> System Settings > Manage servers in this farm. This page lists all servers and their roles in the farm.

How to Switch Server MinRole using PowerShell?
To change the server role using PowerShell, use Set-SPServer cmdlet.
Set-SPServer -Identity SERVER1 -Role Application
#Set-SPServer -Identity SERVER2 -Role WebFrontEnd

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

Friday, July 8, 2016

How to Configure Secure Store Service Application in SharePoint 2016 - Step by Step

Secure store service enables you to securely store credentials required for connecting to external systems and associating those credentials to a specific identity or group of identities.  Secure Store Service solves the problem of having to sign into many applications and entering different usernames and passwords. This is managed through the SharePoint central administration and keeps the credentials stored secure and safe within a secured storage. Secure Store Service was introduced as a replacement to Single Sign-On in MOSS 2007.

Purpose of secure store service in SharePoint 2013
Primary purpose of Secure Store Service is to maintain credentials for target applications on external systems. When we connect to external data sources, it needs to pass the user credentials like user name and password. These type of scenarios we can solve with configure an unattended service account for the external data access.

E.g. When you want to use external data, such as data from your other business applications, in SharePoint, you can use Business Connectivity Services (BCS) together with Secure Store Service. And, you can manage BCS and Secure Store right in the SharePoint central administration site. The external data source that you can connect to is called a Secure Store Target Application. BCS makes it possible for you to set up a connection to the Target Application, and the Secure Store enables you to manage the credentials that are required by the external data source.

SharePoint has its built-in services that can be supported through Secure Store Service. They are as follows:
  • Excel Services
  • Visio Services
  • Business Connectivity Services
  • PowerPivot for SharePoint
  • PerformancePoint Service

How to Create Secure Store Service Application in SharePoint 2016?
Lets see how to create secure store service configuration SharePoint 2016 step by step.
  • Go to SharePoint 2013 Central Administration >> Manage Service Applications
  • In the Service Applications ribbon click on New button and then select Secure Store Service
    how to create secure store service application in sharepoint 2013
  • Enter a name for the Secure store Service Application, database Server and Database name details
    secure store service sharepoint 2013 step by step
  • Scroll down and either choose an existing application pool or create a new application pool using the managed account. To run the application pool, you need a domain account. No specific permissions are required for this account. Click OK to create secure store service.
    secure store service configuration sharepoint 2013
  • Wait for the secure store service application created message.
Generate new key in Secure Store Service:
Secure Store Service requires a key/ pass phrase to encrypt-decrypt credentials. The first time you access the Secure Stored Service it will ask you generate a new encryption key. Before using the Secure Store Service to create target applications, you must provide it with a pass phrase.
  • Go to Central Administration site >>  Application Management
  • Service applications page, pick your newly created Secure store service application.
  • Click on Generate New Key from the ribbonsecure store service in sharepoint foundation 2013
  • Enter the passphrase and click on OK to complete secure store service configuration. Remember it or save a in safe place to have access it when you need.
    use of secure store service sharepoint 2013
Now the error message that displayed on the secure store has gone and it should read something like there are no Secure Store Target Application.

Start the Secure Store Service Instance on the application server(s)
The next step is to start secure store service on the server if its not started already.
  • Go to Central Administration >> System Settings >> Manage service on server (Under Servers).
  • Select the application server >> Locate the Secure Store Service then click start next to it.
The next step is to create Target Application, which I'll explain in an another article.

Technet reference: Configure the Secure Store Service in SharePoint 2013

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

Monday, July 4, 2016

Add-Remove Permissions to SharePoint Group or User with PowerShell

Updating the permission level of a SharePoint group or user is fairly straightforward. To add or remove permissions levels of the SharePoint group, Navigate to:
  • Site Settings >> Site permissions
  • Select the person or group you want to change >> Click on "Edit User Permissions" ribbon button update user permissions using powershell in sharepoint 2016
  • Select or deselect any relevant permission levels required
    add remove permissions of a SharePoint group or user using powershell in sharepoint 2013
  • Click "OK" to save changes.

PowerShell script to update Permissions of a SharePoint group or User:
Here is my PowerShell script to change permission level of SharePoint group: Say, We want to remove "Edit" permission level and add "Contribute" to Members group of the SharePoint site.
Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue

#Configuration parameters
$GroupName="Crescent Intranet Members"

#Get the Web & Group objects
$Web = Get-SPWeb $SiteURL
$Group = $web.SiteGroups[$GroupName]
$RoleAssignment = $Web.RoleAssignments.GetAssignmentByPrincipal($Group)

#For User, Use:
#$User = $web.EnsureUser("Crescent\Salaudeen")
#$RoleAssignment = $Web.RoleAssignments.GetAssignmentByPrincipal($User)

#Get the permission Levels to Add - Remove
$AddPermissionRole = $web.RoleDefinitions[$PermissionToAdd]
$RemovePermissionRole = $web.RoleDefinitions[$PermissionToRemove]

#Add Permission level to the group
if (!$RoleAssignment.RoleDefinitionBindings.Contains($AddPermissionRole))
    Write-host "$($PermissionToAdd) Permission Added to the Group!"

#Remove Permission Level from the Group
if ($RoleAssignment.RoleDefinitionBindings.Contains($RemovePermissionRole))
    Write-host "$($PermissionToRemove) permission removed from the Group!"

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

You might also like:

Related Posts Plugin for WordPress, Blogger...