Recently I did a presentation on “Search Display Templates” at Sri Lanka SharePoint forum. In that session I discussed about display templates in general and different customization options.
If you need more information on Display Templates, you can refer these posts I have written so far.Following is the presentation I did
User profile service synchronization in SharePoint is not the favorite among administrators. If not its prerequisites are addressed properly it will definitely cause you problems. Fortunately those steps are discussed in Technet as well as in some technical blogs.
Although I’ve followed best practices, I had trouble in starting the “User Profile Synchronization Service” service in the services on this server section. It got stuck in Starting and later it showed as Error.
Luckily ULS logs came in to rescue. following is the full error message I received.
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB
at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result)
at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2()
at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).
It seems that SharePoint Server 2013 farms without April 2014 Cumulative Update does not support user profile synchronization in SQL Server 2014. Following is the exact text from the CU download page (KB)
Once it is installed in all SharePoint servers I was able to easily start profile synchronization. I will dig little deeper in to the cause of the issue later. But for the time being will stop in this point. One thing to remember is that you should install SharePoint Server 2013 SP1 prior to the cumulative pack update
Following is the presentation I did at PUCSL, with some demonstrations using a sample Office 365 tenant created using www.microsoftofficedemos.com
Following is the PowerShell script I used to change current application pool identity to a different managed account.
That’s all I had to do :)
I described how to change application pools for service applications in this article. It has answers to your questions like, “Why can’t I change the application pool identity directly from the IIS itself?”.
Sometimes we need to have copies of same document in multiple SharePoint sites. Let’s assume that each site should contain important documents as shown below.
Above setup prompts us following questions
Q1. Is it a good practice to upload documents manually in each site?
Q2. What if we have thousands of sites?
Q3. What if those documents need to be updated regularly?
Above valid questions leads us to keep those documents centrally and publish copies to whatever locations they need to be.
We can achieve above task using SharePoint search, but with few limitations
How can we overcome above limitations?
Instead of using search, we can use out of the box and heavily underrated “Manage Copies” feature.
Following are the steps to publish and share documents using “Manage Copies” feature
1. Store documents in a document library
2. Select the document and click on “Manage Copies” icon
3. Click on “New Copy” link and provide the URL of the destination site
3. I prefer to click on “Update Copies” link to copy documents instantly
3. We can check destination libraries to see the success
As shown above we can maintain multiple copies of the same documents, where we can store the original document centrally.
As we have now solved half of the problem, let’s focus on how to update copies of a particular document.
Let’s say that there is an amendment to the leave policy and we have thousands of project sites those having copies of that leave policy. How can we reflect the change to those sites? It’s very easy. Following are the steps
1. Check Out the document in the original document library
2. Do the change to the document
3. Save the document and Check In. Remember to select “Update copies of this document with the new version” option
4. This will prompt another window showing all the copies of that document. If we don’t want the update to reflect on a particular site we can leave it by not checking the checkbox.
5. We can check destination libraries to see the success
In this article I explained the usage of “Manage Copies” feature to effectively manage copies of important documents.
Hope this helps someone
Install-SPRSService
4. Start SQL Server Reporting Services service in App serverInstall-SPRSServiceProxy
I was lucky to be a part of Sri Lankan pavilion in Gartner Symposium 2014. I presented and demonstrated SharePoint 2013 and Office 365 capabilities. Following were the most looked after business requirement
