Here I am tinkering with Sharepoint 2013 trying to illustrate to my manager how awesome it is and why we need to upgrade. Unfortunately, I can't get Sharepoint 2013 to work in Windows 2012 and probably because I've just missed a step. So with the risk of getting a "tick this box idiot!" reply I'm asking here:
On a fresh Sharepoint 2013 install on Windows 2012 server, straight of out the box after using prerequisiteinstaller, installed if normally, run configuration wizard normally and then the built in wizard in central admin to set up my farm and a standard application / site collection and after it completes I browse to the new site and get the "sorry something went wrong" message with a correlation ID. When checking my logs for that id I see alot of errors there and it looks like claims is the culprit:
02/18/2013 09:39:32.63 w3wp.exe (0x1158) 0x1328 SharePoint Foundation Claims Authentication ad5swUnexpectedFailed to create instance of cookie value handler type 'Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue'.21eaff9b-9780-5081-d116-9a34b618c5e702/18/2013 09:39:32.63 w3wp.exe (0x1158) 0x1328 SharePoint Foundation Claims Authentication ad5suUnexpectedToken Cache: Could not get cookie value handler.21eaff9b-9780-5081-d116-9a34b618c5e7
But this only happens on a Windows 2012 server. When running on a Windows 2008 R2 server with these exact steps it works as expected. It's the same SQL engine behind it (local SQL2012 install), it's in the same AD OU, the "only" thing that's different is the OS.
As I said, this is just a lab installation out of the box and I've reinstalled from start several times, even the OS, same result every time.
I'm fairly sure I'm missing something here, I just don't know what. Some service? ...