This week I was trying to make some PowerShell scripts to set the auditing in SharePoint. This can be done very easy with the GUI, but I had to set this on a few thousand sites. With the GUI you can go to the site collection and then settings. Under ‘site collection administration’ you find ‘Site collection audit settings’ Just select the options you want and you’re all set to use auditing.

Just got the confirmation that I may go to the SharePoint Conference in Las Vegas this year.? I am very excited to go this year. Now I have to find out what sessions to go to, there are a lot. For everyone that is going James Callaghan made a nice PowerShell script to download an overview of all Sessions (http://www.jcallaghan.com/2014/01/all-spc14-sessions-available-in-a-single-spreadsheet/)

Lately I was working on Windows Azure with PowerShell at a customer. As most of my customers have a proxy, I had some issues with the cmdLets to get to Azure. After searching the web I found a nice solution to use to get authenticated with the proxy for PowerShell. Start your PowerShell with the following command or use it in your scripts $proxy = [System.Net.CredentialCache]::DefaultCredentials [System.Net.WebRequest]::DefaultWebProxy.Credentials = $proxy

This week I was asked to create some content types with Managed Metadata field in it. This of course is not hard to do if you do it from the UI, but we wanted to have a nice solution to deploy. After searching the internet I found several posts how to do this, but none had a complete solution so here it is. First of all you need to have a field that looks like this:

If you want to have a Taxonomy field that can have mulitple values you can follow my previews blog and change in the field part the type to Type=“TaxonomyFieldTypeMulti” And add the following attributes Mult=“true” Sortable=“false”

?For a customer I was building a SharePoint farm on Windows Azure. The SharePoint environment should be available only thru HTTPS. But for the user this was hard because they never type https in front of the URL so we had to redirect the http calls to https. After looking around on the internet I have found a very easy solution with SharePoint AAM. The only thing you have to do is create in the same zone an extra internal url that is pointing to the http address and add an extra binding in IIS for the front-end machine.

In the previous versions of SharePoint we always had the option to sign in as a different user. since SharePoint 2013 we only have the option to sign out.? For the majority of users this is no problem at all because they only have 1 account to log in, but for an administrator this can be a issue as they usually have a separate administrator account. To solve this we have a few options: