Does your system run on SharePoint 2010? Do you want to migrate it to the 2013 version? Is the Project Server involved in the game? If you answered “Yes” at least once – read on! In this article we share our experience on what pitfalls we faced while migrating SharePoint 2010 with Project Server 2010
When you use PowerShell for SharePoint administration, it is pretty frustrating to use the “Add-PSSnapIn Microsoft.SharePoint.PowerShell” every time you open your PowerShell console. Next time, try this: asnp *sh* This will add all SnapIns that contain “sh”. In most cases, this is just the Microsoft.SharePoint.PowerShell one. Saves time!
#Login to server with farm account# #============================================================== #Search Service Application Configuration Settings #============================================================== $SearchApplicationPoolName = “<SP2013_Search_Service>” $SearchApplicationPoolAccountName = “<Search Service acoount>” $SearchServiceApplicationName = “SP2013 Search Service” $SearchServiceApplicationProxyName = “SP2013 Search Service Proxy” $DatabaseServer = “<Database Instance name>” $DatabaseName = “SP2013_Search” #Confirm permission given on SQL Search instance #Create search index folder on each server where
Now that Microsoft has officially announced that InfoPath 2013 will be the last version, this adds a dilemma for those customers wanting to select a forms technology that’s future proof. After all, if you pick InfoPath now, it’s probably not going to be supported on SharePoint 2016. (That’s a guess on the name). Anyway, so
Let’s begin by taking a look at the “managed metadata navigation” feature. One of the big challenges to navigation inside SharePoint is that it needs to be set up in each site. This causes a problem if any of the links are removed because then I need to go in each site and delete or update the links
As usual, when I embark on a PowerShell project it’s always a learning curve. One might think with all PowerShell’s flexibility, you could just use PowerShell’s” export-csv” command with an array and be on your merry way. It never turns out to be that easy. While working on a PowerShell script for SharePoint 2013 to
1. Error: Unable to properly communicate workflow service. Resolution : Re-installed workflow manager by removing FQDN(servername.domainname) with Service Bus 1.0 cumulative update 1. Do not use FQDN (fully qualified domain name). Ex: SP2013DEV01.Contoso.com à SP2013DEV01\SP2013DEV01 Reference: For Install and Uninstall Workflow Manager http://technet.microsoft.com/en-us/library/jj193448 2. Error : Create designer WF for testing. When you trying to publishing
An enterprise client recently asked us to create a solution for reserving company conference rooms. The client is a technically savvy company with numerous offices throughout the country and 5-6 conference rooms at each location. The challenge was for employees who were constantly traveling from one office to another to be able to find a
A sample powershell script to import a CSV data into a list after deleting the existing items using the client object model. $csv = Import-CSV data.csv $siteUrl = “https://office365 url” $listName = “listName” $userName = “username” $password = Read-Host -Prompt “Enter password” -AsSecureString $ctx = New-Object Microsoft.SharePoint.Client.ClientContext($siteUrl) $credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($userName, $password) $context = New-Object
If you plan to install standalone SharePoint 2013 server on workgroup machine (not part of domain), there is additional prerequisite you need to do, or you will have error in SharePoint configuration wizard with comment “The SDDL string contains an invalid sid or a sid that cannot be translated”. Steps are: Add the account for
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
