Last week we upgraded our test environment with SP1 of SharePoint 2013. After some testing we found that publishing of a Content Type went wrong with the following error. With a quick search on the Correlation ID with PowerShell Merge-SPLogFile-PathC:\proxylog.log-Correlatione9a8929c-5756-20e8-2a9f-e38b648bc237 We found the following message Failed to get term store for proxy ‘Managed Metadata Service Application Proxy’. Exception: System.Security.SecurityException: Requested registry access is not allowed. So the Managed Metadata Service has not enough rights in the registry, this can be solved to manually add the correct rights for the accounts “WSS_Admin_WPG” and “WSS_WPG” to the registry key “HKLM\Software\Microsoft\office Server\15.

This week we had an issue where we had some differences in the Content Types that where pushed from the Content Type hub. We wanted to make sure all Content Types where updated in the next push. After some digging around on the internet I found that there is a property in the SPWeb.Properties called “MetadataTimeStamp”. This property contains the date of the last sync with this site collection. If you clear the value of this property, the Content Type synchronization Job will update this sitecollection.

Today I did a presentation at Portiva’s SharePoint & Sushi about PowerShell for IT Pro. In this presentation I told the public about PowerShell en how the IT Pro can use this in his daily work. The presentation is in Dutch. 20140429 - PowerShell for IT Pro—Arjan Cornelissen

This week I listened to a session from the SharePoint Conference in Las Vegas about ‘Site provisioning techniques with SharePoint apps’. This session was all about how to use the app model to provision sites, libraries and everything else you need in SharePoint. The had a lot of examples how to do this and what is changed in both SharePoint Online and SharePoint 2013 SP1. The overall point the made is that with the use of an SharePoint app you can make a template that will work both on premise and online without the use of web templates and sand boxed solutions A other benefit of this is that you can use one of the default templates that Microsoft supplies and you only have to change what you want to be different instead of creating complete new templates.

With the release of SharePoint 2013 SP1, Server 2012 R2 is now supported. With this release I wanted to try to upgrade my dev environment to Server 2012 R2. My dev machine has all roles, so AD, SQL and SharePoint. The steps below I used to upgrade the machine. Install SharePoint SP1 as you usually install an update Make sure you have enough free space, I needed 12GB. Mount the ISO of Server 2012 R2 and run the following command ‘adprep /domainprep’, the adprep command can be found on the disc in the folder ‘\sources\adprep’

All the sessions of the SharePoint Conference 2014 are now available on Channel9. Like many other people I like to watch some of the sessions I missed during the conference. I also do not like to watch this from my laptop so I wanted to download the sessions I would like to see. After a few hours of trying myself I found on Yammer that there were many others trying the same thing and 1 had created and shared a really nice PowerShell script to download everything.

Last week I had a question to remove a document library with items that where records. Then you have an option to remove the record status of every document by hand, this is ok for a few items but in this case there were a few thousand items and only some of them had the status Record. With some searching on the internet I found a code snippet to remove the record status of a document.

The last couple of weeks I was creating and configuring 3 SharePoint 2013 farm (Test, acceptance and Production) on Windows Azure. We did the provisioning, installation and configuration with PowerShell. This way we had the basics within 1 week running. Because we are on Windows Azure and the company did not want their AD extended to the Windows Azure environment we configured SharePoint with ADFS 3.0. This way we could give the end user a single sign on experience that they are used to and make it directly possible to let them connect from outside the company network.

Today I was running a PowerShell script to remove all records in a SharePoint List, but I got an exception that PowerShell did not have enough memory. By default PowerShell has a memory limit of 1GB You can check the amount of memory with the following command within a Admin PowerShell window get-item wsman:localhost\Shell\MaxMemoryPerShellMB To change this the following command can be ran set-item wsman:localhost\Shell\MaxMemoryPerShellMB 2048

I’m currently creating a SharePoint environment for a customer on Windows Azure with ADFS 3.0. Within this environment we have multiple front-end and back-end machines. Because we use ADFS the people picker will accept everything you enter, we installed and custom claim provider from codeplex (ldapcp.codeplex.com) to give the users a better experience We decided to create 2 backend systems only for search and enabled only the search components on these machines.