IT issues and solutions

I was building a new Dev machine for SharePoint 2013 and the upcoming SharePoint 2016 release and noticed i couldn't connect to my Windows 2012 R2 Hyper-V host on which i do most of my "Proof of Concept" stuff.  I got the following error: "Hyper-V encountered an error trying to access an object on computer <host> because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running." After trying enter-pssession in PowerShell, (which worked of course...) pinging, firewall rules, winrm settings, etc. I resorted to rebuilding the configuration for hyper-v. This can be fixed by running the following command on your Hyper-v Host itself.     MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof This finally resolved the issue. 

In SharePoint 2010 or 2013 it's possible that when try to open "content or structure" on the settings.aspx page or when try to open a list or all lists that you get an error telling you that a duplicate key exists. The duplicate key is related to a list somewhere in the SharePoint site-collection. The issue is at hand is that you won't be able to find it using the GUI. So i thought i would share my powershell script that will check for duplicate lists / keys so that you know which list to remove via disabling a feature or just by removing it with powershell. (will also work with host named site collections) code: Function Get-Duplicate {     param($array, [switch]$count)     begin {         $hash = @{}     }     process {         $array | %{ $hash[$_] = $hash[$_] + 1 }         if($count) {             $hash.GetEnumerator() | ?{$_.value -gt 1} | %{                 New-Object PSObject -Property @{                     Value = $_.key                     Count = $_

When you work with the fedauth cookie an issue might arise with the Size or information of the fedauth cookie. This could be the size of the cookie according to the information you put in to the claim or secondly the information itself in the cookie which might be sensitive (Privacy). Now you might be thinking, the fedauth isn't readable? Copy the information in the cookie in a basedecoder and you will be able to read the information that is put in the identifying claim. .. and some more stuff! According to a post published by Vittorio Bertocci you should be able to solve this by using the WIF functionality "IsSessionMode=True" and since SharePoint uses WIF..... (Windows Identity Foundation) We should be able to use this to in our SharePoint scenario's... Wrong ! We tried to get this to work (in various ways!) and quickly ran in to some strange situations wherein according to the post of Vittorio we should see it in action.  It just didn't work, then

SharePoint 2016 is almost here.... I just wanted to share with you guys this important piece of news, SharePoint 2016 will be here in q2 of next year. The  http://blogs.office.com/2015/04/16/sharepoint-server-2016-update/ Public CTP's will probably arrive somewhere around Q1 2016 is my guess.

Sometimes we are looking for some piece of a request that fails in our SharePoint web application / site-collection / site.....And we are not getting that nice SharePoint error that gives us the correlation id which will help us narrow / pin down the error in the ULS logs. In case SharePoint isn't registering an error when your so called "exception" hits it can be difficult to find the culprit in ULS logs. So how then do we get the correlation id if don't get one? Simple, download the debugging proxy called "fiddler" from http://www.telerik.com/fiddler . Install fiddler on your client that you are using to debug / analyze the issue at hand. Remember that fiddler must be installed on a client with the necessary access to the sharepoint web application / site-collection / etc. Open up the fiddler client which will automatically integrate itself in to your browsers (firefox, IE, Chrome, etc.) as a proxy between your client and the SharePoint environment

Rewriting URL's for ADFS with SSO support. As stated in my previous post " One ADFS to serve them all!  (part I) " I'd supply you with a method that's necessary for rewriting you're ADFS host federation service name and still be able to keep SSO working with a custom vanity host name for your federation service name.  I'm going to assume you read my previous post to get acquainted with the basic requirements and other aspects of working with Microsoft Application Request and Routing module. If you're not acquainted with the subject matter were about to walk-through I'd recommend you read my first post which will walk you through a very the basic installation, and tell you a bit about the workings which i will skip in this post. One new component I am going to introduce is the web application proxy feature that's introduced in Windows Server 2012 R2. This feature was introduced to replace ADFS reverse proxy functionality and Microsoft's

One ADFS to serve them all (part I)! The goal is to use a vanity URL host names that your site is using and to also use that same host name to resolve ADFS, without having you redirected back to the ADFS original service name (hostname + URL). Because for the end users this shouldn't look like anything else but the vanity domain they are already connected to. Thus how do we solve this? Follow this basic lab entry to get a feeling for the end solution. (I will post more about this subject in greater detail) The ADFS Limitation. The limitation I'm speaking of, in this case is the endpoint for SAML 2.0 / WS-Federation: "/adfs/ls"  (but as you can imagine it's pretty much every endpoint listed in ADFS) We connect with the 1 possible value set during installation for the federation service name: "your.host.name"  Which results in all endpoints only being accessibly under that federation service name.    Figure A: Federation service

Hi,  My name is Reinout Pennings. I've been active within the IT sector for over 20 years now. During that time I've found a lot of help online searching for existing solutions or something close to it which saved me a lot of time resolving issues.  In that time i always felt bad for not sharing my knowledge with you guys, the public who helped me out on so many occasions.  So i finally decided to put in some time and effort to start this blog. I will use this blog to post on things that I think, could help you out, with reducing cost and simplify situations within your IT infrastructure.  It doesn't matter whether your hosting in the cloud, on premise or both. You will find solutions here that will be beneficial in whatever scenario your in.