Cumulative updates for SharePoint Foundation and Server 2013.

June 2014.

Cumulative Update for SharePoint Foundation 2013 package

http://support.microsoft.com/kb/2881061

Cumulative Update for SharePoint Server 2013 package

http://support.microsoft.com/kb/2881061

July 2014.

Cumulative Update for SharePoint Foundation 2013 package

http://support.microsoft.com/kb/2882999

Cumulative Update for SharePoint Server 2013 package

http://support.microsoft.com/kb/2882989

Recent Published Article: the week of June 23, 2014

Published the week of June 23, 2014

New articles

Explore enterprise social scenarios with Yammer and other Microsoft products   Understand common scenarios for enterprise social that can be built with Microsoft products, including Yammer, Office 365, SharePoint Server, Lync, and Microsoft Dynamics CRM.

Top operations and management issues for SharePoint Server 2013 hybrid   Discusses major maintenance areas for a SharePoint hybrid environment, such as SSL certificate renewal, directory synchronization maintenance, search health smoke-testing, and upkeep of user profile applications.

Updated articles

Configure client certificate authentication for SharePoint 2013   Added information about how full sync is required after filter changes.

Plan enterprise search architecture in SharePoint Server 2013   Updated the hardware tables and the guidance for mix of virtual/physical.

PowerShell Portal: SharePoint 2010, SharePoint 2013.

·         Introduction

·         General

·         Tool Releases

·         Several Technologies

·         BizTalk Server

·         Exchange Server

·         Forefront Identity Manager - FIM

·         Office Products

·         SharePoint

·         Windows OS and Complementary Products

·         SQL Server

·         Active Directory

·         References

·         See Also

·         Other Languages

SharePoint:

• SharePoint: Get Set and Copy User Profile Properties using PowerShell
• PowerShell Script to delete items from SharePoint List
• An Example of Using Write-Progress in a Long Running SharePoint PowerShell Script
• SharePoint 2010: Import or Export a Site using PowerShell
• SharePoint 2010: Add a User in a SharePoint Site using PowerShell
• SharePoint 2010: Create a new Web Application and Site Collection with Windows PowerShell
• SharePoint 2010: Get Site Users with Full Control/Owners Permissions with PowerShell Script
• SharePoint 2010: List and Delete List Item Versions using PowerShell
• SharePoint 2010: Interacting with Site Columns using PowerShell
• SharePoint 2010: Updating User Profile Properties with PowerShell
• SharePoint 2010: Search Windows PowerShell cmdlets
• SharePoint 2013: Installation and Product Detection
• SharePoint 2013: Install Prerequisites Offline or Manually on Windows Server 2012 - A Comprehensive Guide
• SharePoint 2013: PowerShell Reference and Resources
• SharePoint 2013 PowerShell: Features and Solutions
• SharePoint 2013: Internet Information Services (IIS)
• SharePoint 2013: PowerShell - Web Applications
• SharePoint 2013 Online: PowerShell Reference and Resources

You receive error 401.1 when you browse a Web site: IIS 6.0 and SharePoint 2007

Coming back the article Troubleshooting Adding server to the farm: SharePoint 2007, tried to browse the content on the one of the server and was having issues. And discussed previous time it was helped by the disabling loop back adapters.

Error message getting registered in System logs:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: Computer_Name
Description: Logon Failure:
Reason: An error occurred during logon
User Name: User_Name
Domain: Domain_Name
Logon Type: 3
Logon Process: Ðùº
Authentication Package: NTLM
Workstation Name: Computer_Name

Followed the steps in the KB To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:

1.    Set the

DisableStrictNameChecking

Registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

281308 Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name.

2.    Click Start, click Run, type regedit, and then click OK.

3.    In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

4.    Right-click MSV1_0, point to New, and then click Multi-String Value.

5.    Type BackConnectionHostNames, and then press ENTER.

6.    Right-click BackConnectionHostNames, and then click Modify.

7.    In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.

8.    Quit Registry Editor, and then restart the IISAdmin service.

Reference: http://support.microsoft.com/kb/896861 and http://support.microsoft.com/kb/926642 and it worked fine.

Applies to:

• SharePoint 2007
• Office 2007
• IIS 6

Troubleshooting Adding server to the farm: SharePoint 2007

Again going to basics, there was need of the adding one server to the farm in one of our SharePoint 2007 environment. Since its being long time touched SharePoint 2007 configuration. I was struggling to add the server back to the farm.

Issue: After installing SharePoint Binaries, running PS Config was failing on the SharePoint server. Getting the below error message.

  

Troubleshooting: Even after checking permissions in the SQL DB, it seems that everything was fine.

Ping to SQL server was successful; connecting to the SQL Server was failing by creating the .UDL file.

Reference to do this: http://blogs.msdn.com/b/farukcelik/archive/2007/12/31/basics-first-udl-test.aspx

http://blogs.msdn.com/b/steverac/archive/2010/12/14/test-remote-sql-connectivity-easily.aspx and

http://blogs.technet.com/b/appv/archive/2010/12/14/how-to-easily-test-your-remote-sql-connectivity.aspx

It seems that some connection issue was there. Have tried to connect to SQL by following ways:

• SQL_Server_Name only.
• SQL_Server_Name\SQL_Instances_Name
• SQL_Server_Name: SQL_default_Port i.e. 1433.

Resolution: None of the above has worked. So it’s time to contact the SQL expert, he suggested to try using the SQL_Server_Name, SQL_dafault_Port i.e.1433.

It’s hard to spot the difference in third option I have tried above and what SQL guys suggested, but can be spotted by give an example.

What I was trying before: SQLSERVER:1433

What SQL guy suggested is: SQLSERVER,1433 , it just a difference or colon and comma used.

Problem again: PS Config ran smoothly and presuming the server was added to the server, I browsed the Central Admin to configure the services on the server, but…! the server was not available in the Central admin.

Did allot of mind joggling about it, re-run the PS config, disconnecting the server couples of times on and again running the PS config, but now luck.

Resolution: Finally, though of running the PS config on Application server where Central Admin was hosted and it did wonder, I could now see the server in the server list of CA.

It also made me thinking how did I forgot this basic steps in adding server back to the farm as this is one of the recommended practice of Microsoft and this is first question in my interview list which I ask most of the candidates. I would only say its work pressure mate…. J nothing else….!

Guidelines for further issue:

Browsing sites on the added server giving issue of login prompt even after adding the site to local Internet. And it got resolved by the Microsoft KB

http://support.microsoft.com/kb/916894.

Failure running on App server where Central Admin was hosted was resolved by http://support.microsoft.com/kb/916894

Applies to:

• SharePoint 2007
• Office 2007
• IIS 6