When you want to run SharePoint 2010 on either Windows Server 2012 or Windows Server 2012 R2 make sure your SharePoint 2010 is at least running Service Pack 2 (SP2)!Although Hardware and software requirements (SharePoint Server 2010) does not make a note about Windows Server 2012, the KB article 2724471 does outline the support for Windows Server 2012 and Windows Server 2012 R2.
Before the release of Service Pack 2 (SP2) for Microsoft SharePoint Server 2010, Microsoft did not support SharePoint Server 2010 in a Windows Server 2012 or Windows Server 2012 R2 environment.
However, SharePoint Server 2010 with SP2 has now been released, and this configuration is supported in Windows Server 2012 and Windows Server 2012 R2.
So, it’s supported to run SharePoint 2010 on Windows Server 2012, check out the KB article 2724471 and the description of SharePoint 2010 Service Pack 2. Enjoy all new goodies from Windows Server 2012!
[Update: SharePoint 2013 is not supported on Windows Server 2012 R2 for now. This will be supported when Service Pack 1 is released. Check KB article 2891274 .]
[Update: SharePoint 2013 Service Pack 1 is released, check Announcing the release of Service Pack 1 for Office 2013 and SharePoint 2013. Resulting in SharePoint 2013 being supported on Windows Server 2012 R2]
Posted by Bram de Jager on December 3, 2013
To play around with SharePoint 2013 I need a decent setup of a Domain Controller, SQL Server 2012 and SharePoint 2013 Server. To achieve this I use Hyper-V and want to reuse as much as possible, but it has it limits…
Every machine, virtual of physical, has it’s own SID. This can be retrieved via PsGetSid.exe from Sysinternals.com. The thing is, it seems that the Domain Controller needs to have an unique SID within the domain. Although the domain members are allowed to have similar SIDs.
When I setup my topology I use a base image for every machine. Meaning these all have the same SID. After I installed my Domain Controller and second machine which I wanted to join to the domain I got this error “The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine”.
The solution to this is renewing the SID of the member machine. I needed to run sysprep.exe to change the SID of my base image, which I use to create the SQL Server 2012 and SharePoint 2013 machines. After running sysprep everything worked as expected!
Posted by Bram de Jager on February 21, 2013
Last week it happened again, one of my virtual machines crashed. And I needed a way to repair the virtual machine or at least retrieve the files located on the virtual hard disk.
Important note: This is (probably) not supported and I can’t guarantee your virtual machine is recovered. Please only use this how-to as your last resort! It might help you 🙂
What happened?: When the virtual machine (VM) crashed it needed a forced shutdown. When restarting the VM it came back with Recovery mode. I wasn’t able to start Windows normally!
Solution: Within VirtualBox (I’m currently using Oracle VM VirtualBox), or any other virtualization software, you are able to mount multiple hard disks. You need to mount the hard disk of the crashed VM to another healthy VM (which works normally). Pay attention to snapshots, mount the latest snapshot! Start the healthy VM.
What happens?: The healthy VM will pick up the crashed hard disk and starts scanning and repairing the hard disk. After repairing Windows will start normally and you are able to browse the hard disk and retrieve your files.
If you are having a lucky day? You could try to shutdown the healthy VM. Unmount the hard disk (which was repaired). And try starting your crashed VM. Now you know whether you are really lucky! It might start!? Good luck!
Posted by Bram de Jager on April 21, 2011