I was looking into the option of auto deploying an custom developed app at the time of creating a site in O365 / SP2013 environment. Scenario: 1. Custom app (MVC – Azure hosted) – Need to deploy it automatically so that it can customise the site created using a site template. (i.e. attaches the remote
After Configuring Excel Service (too many information regarding configuring Excel Service in SharePoint available on net), I faced following issue: We’re sorry. We ran into a problem completing your request. Please try that again in few minutes. (Message from SP 2013) Unable to process the request. Wait a few minutes and try performing this operation
In our University environment we decided to pre-configure MySites for our 18,000+ users across 30 different content databases using a Powershell script. While running a file to update composed looks, our log file indicated that 13 MySites weren’t created. These users all had a site collection under our MySite host web application, however, clicking on
I faced this issue and just wanted to pass on the resolution. I added the CA service role to 2 of my app servers and wanted to remove it from my WFE. So to accomplish this I used CA UI and moved on (few days ago). Today I noticed that the status was still ‘Stopping’.
Promoted Links – Tiles view webpart is one of the easiest way to present the new Tile interface to the user. The default view only renders the Tiles horizontally and to have wrapped tile view, we have to customise it. For our O365 project, we have customised the Tiles view using the following Javascript. Default
From my last PowerShell Article “PowerShell from an Array to Comma Separated file (CSV) via the PSObject“, http://goo.gl/3ATJgp, I pointed out that a CSV or Comma Separated Value file is kind of like a Hash Table where every value is associated with a column heading. In PowerShell, just because you get somewhere is no guarantee you
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
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
