The IT Crownd

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 f

Nothing is every easy. Last week I installed the SCOM agent on our shiny new TMG array.  I followed the instructions from Microsoft and everything went smoothly.  Until I attempted to approve the last member of the array within SCOM Management Console.  An error occured which ditched my console.  I didn't worry too much and I thought nothing of it till the next day when the last server wasn't appearing in SCOM. The console however no longer showed the server as pending - infact the console didn't show the server at all. I found some powershell lying around on the internet which allowed me to approve/reject and list computers in "pending management" there was my server!  I duely approved the pending operation and bingo back in business. Gotta love Powershell.  Just a shame that they don't use powershell to populate to console! To list pending agents...(oh yeah you need to run the Operation Manager Shell - not just Powershell you knew that right?) ge