SharePoint 2013

Disable Loop Back Check in SharePoint 2013

Posted on

Problem: When you access web application with in the SharePoint sever, it keeps on prompting for authentication.

Solution: Disable Loop Back Check

The following step has to be followed to disable the loop back check in SharePoint Servers,

Step 1: Open the Registry Editor (regedit)

Step 2: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa in registry

Step 3: Create the dword32 for DisableLoopbackCheck

Step 4: modify the value to 1

Recommended Option: Run this power shell command

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword

You may have to restart the servers and will have run this from all of your SharePoint servers.

Advertisements

Box to SharePoint migration (vice versa)

Posted on Updated on

I came to a scenario to migrate the Box content to SharePoint (Office 365). The cost effective solution is the BOX site/folder owners can use the SharePoint Library Open with Explorer features to move the files from Box to SharePoint Online.

If you would like to automate the process for large content, there are many 3rd party Tools are available in market. I explored the skysync http://www.skysync.com/ which is very straight forward to migrate the content from Box to SharePoint or SharePoint to Box.

Skysync software can be used to Sync or Migrate Files between SharePoint, Box, Office 365, Huddle, Dropbox, Network File Systems & more!

Skysync software is available in 3 editions (Pro, Business and Enterprise) , prices and features are different is each model.

It is very easy to setup a new job for sync or migration. The details features can be find here.

Building SharePoint Farm in Azure using Template for Dev & Test

Posted on

The Microsoft Azure Preview Portal automatically creates a pre-configured SharePoint Server 2013 farm for us. This can save you a lot of time when we need a basic or high-availability SharePoint farm for a development and testing environment.

The basic SharePoint farm consists of three virtual machines in this configuration.

Small_SPFarm

We can use this farm configuration for a simplified setup for SharePoint app development or first-time evaluation of SharePoint 2013.

The high-availability SharePoint farm consists of nine virtual machines in this configuration.

Medium_SPFarm

We can use this farm configuration to test higher client loads, high availability of the external SharePoint site, and SQL Server AlwaysOn for a SharePoint farm. We can also use this configuration for SharePoint app development in a high-availability environment.

Microsoft Azure Preview Portal:

PortalPre

SharePoint Online (SPO) Migration PowerShell Cmdlets public preview

Posted on Updated on

The Long waited utility for migrating On-Premises File Share or On-Premises SharePoint server site to Office 365 SharePoint Online is release recently from Microsoft.

This utility/API is PowerShell cmdlets and its called “SharePoint Online (SPO) Migration PowerShell Cmdlets”.

SharePoint Online (SPO) Migration PowerShell Cmdlets public preview is a new API dedicated to migrating data from on-premises file shares to Office 365. To join this preview go to SPO Migration Preview.

SPO Migration PowerShell cmdlets are designed to move on-premises content from file shares and SharePoint Server libraries and One Drive to SharePoint Online and OneDrive for Business. Requiring minimal CSOM calls, it leverages Azure temporary BLOB storage to scale to the demand of large migration of data content.

The detailed information can be found here,

https://technet.microsoft.com/en-us/library/mt203923.aspx

Register Workflow Manager with SharePoint 2013

Posted on Updated on

This article describes how to register the SharePoint 2013 Workflow platform to work with SharePoint Server.

I Assumes you have already installed the Workflow Manager product and configured the Workflow Manager and Service Bus farms using either the Configuration Wizard or through PowerShell. Here, we shall go ahead and set SharePoint up to use the Workflow farm.

The Register-SPWorkflowService cmdlet  will be used to configure the SharePoint host to use a workflow service by using the SPSite and WorkflowHostUri parameters.

Syntax

Register-SPWorkflowService -SPSite <SPSitePipeBind> -WorkflowHostUri <String> [-AllowOAuthHttp <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [-Force <SwitchParameter>] [-PartitionMode <SwitchParameter>] [-ScopeName <String>]

From <https://technet.microsoft.com/en-gb/library/jj663115.aspx>

Example

The following script will be used for http communication,

Register-SPWorkflowService -SPSite “http://SharePoint.Contoso.com” -WorkflowHostUri “http://WorkFlowManager.Contoso.com:12291/” -verbose -force

The following script will be used for https communication,

Register-SPWorkflowService -SPSite “https://SharePoint.Contoso.com” -WorkflowHostUri “https://WorkFlowManager.Contoso.com:12290/” -verbose -force

Validation

Once the above script is executed the following script can be used to validate the registration,

[Void][System.Reflection.Assembly]::loadwithpartialname(“Microsoft.SharePoint.WorkflowServicesBase”)

$web = Get-SPSite -Limit 1 -WarningAction SilentlyContinue | Get-SPWeb

$wfm = New-Object Microsoft.SharePoint.WorkflowServices.WorkflowServicesManager($web)

$wfm | SELECT *

MS Reference: