Kerberos, MOSS and IIS 7

-
I recently found out why our MOSS 2007 FEW which was hosted on a Windows 2008 R2 server was unable to provide MOSS sites.

Whilst this was not a service impacting issue, we have plenty of other SharePoint 2007 FEWs so one less didn't matter plus this one was really just doing the Report Service bit in any case.

However after a couple of weeks of getting annoyed at this I decided to look for a solution.  A quick trawl of Google later and I found this site which explains things nicely.

http://sharepointspot.blogspot.co.uk/2008/12/sharepoint-kerberos-on-windows-2008.html

Basically this is due to Windows 2008 R2 doing kerberos in the kernal and as such it ignore any SPN you may have in place and uses the computer object.  In principle this is a great thing, no more SPNs needed!  However poor old MOSS needs SPNs as all the website applicaiton pool MUST run using identities if you are using kerberos.

Quick change to the C:\Windows\System32\inetsrv\config\applicationHost.config file, look for the line

<windowsAuthentication enabled="true" />

and make it look like the following...

<windowsAuthentication enabled="true" useKernelMode="true" useAppPoolCredentials="true" />

and IISReset (as admin!) and you are back in business.

Comments

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine
Read more

Intune installation requires a wire...or does it?

-
If you are using Intune (great!) it assumes you have a wired connection (not great) - this is more of an issue as some machine now no longer have built in ethernet ports. It is possible to connect to your wireless - albeit in a slightly awkward way.....here's how During the OOBE hit SHIFT+F10 to get a command window and type either; start ms-settings: To get the settings window or start ms-availablenetworks: To see the network fly outs. Thanks to  Using a wireless network connection with Windows Autopilot white glove – Out of Office Hours (oofhours.com)
Read more

Security Policy 1001

-
We had an annoying warning showing every 5 minutes on our Read Only Domain Controllers.  This didn't affect service but meant we were losing our logs of important events (should the have occurred) "Security policy cannot be propagated. Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation." Source: SceCli Event: ID 101 We tracked this down to a GPO which was populating the local Administrators group. Obviously a Domain Controller has no local users or groups so this was causing the issue. Ensuring that the GPO did not apply to the Domain Controllers - yes the GPO was linked at the root! fixed the issue. It is strange that we did not see the warnings on our main Domain Controllers only on the Read Only DC's as this would have affected all DCs the same (I would have thought)
Read more