Noticed something on a recent 2013 farm build where Central Administration site opened correctly from the server it was running on, but when you tried to open it from another server in the farm or a workstation you were prompted for authentication three times and it never succeeded.
This seemed like a behavior I have seen in the past when working with Kerberos based web applications that did not have the SPN's configured correctly. I checked the authentication provider on Central Admin and found it was set to Kerberos instead of NTLM. Since the client is not utilizing Kerberos I changed to NTLM, saved changes, and after this could access CA from other servers in the farm.
I looked again at my script and realized that I had not set the authentication provider switch correctly so this is why it had been set to Kerberos
SharePoint 2010/2013 Tech Notes
Tuesday, May 14, 2013
Monday, May 13, 2013
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
Ran across this site and it has all the needed SP build numbers for multiple versions of the product. Also has some other helpful links on how to get build numbers, etc.
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
http://sqlserverbuilds.blogspot.com/
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
http://sqlserverbuilds.blogspot.com/
March and April CU for 2013
It seems that the CU's for 2013 are coming quicker than they did for 2010. The March CU was launched and now has to be installed in order to apply any future updates.
April 2013 CU also released and looking through the details for SP Server it appears that most of the issues are around sites and service applications that were migrated from 2010.
March CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx
April CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/04/27/april-2013-cu-for-sharepoint-2013-has-been-released.aspx
Hopefully we don't see the same issues that we did with 2010 where CU's are released, pulled, and then released again.
April 2013 CU also released and looking through the details for SP Server it appears that most of the issues are around sites and service applications that were migrated from 2010.
March CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx
April CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/04/27/april-2013-cu-for-sharepoint-2013-has-been-released.aspx
Hopefully we don't see the same issues that we did with 2010 where CU's are released, pulled, and then released again.
Subscribe to:
Posts (Atom)