Supportability for SharePoint 2010 SP2 and Windows Server 2012 R2

Before the release of Service Pack 2 (SP2) for Microsoft SharePoint Server 2010, Microsoft did not support SharePoint Server 2010 in a Windows Server 2012 or Windows Server 2012 R2 environment.
However, SharePoint Server 2010 with SP2 has now been released, and this configuration is supported in Windows Server 2012 and Windows Server 2012 R2.

For more information:
http://support.microsoft.com/kb/2724471

As of May 1st, 2014, deployments from the slipstream media available on VLSC and MSDN we only support Setup of SharePoint 2010 SP2 slipstream media (not RTM + SP2) on Windows Server 2012 R2. For this to work, the 2014 Feb CU (or newer) is required.

Please note that only fresh installing of SP2 slipstream + Feb CU (or newer) on Windows Server 2012 R2 is supported.

We don’t support OS in-place upgrade.

SharePoint 2013 and SQL Server 2014 Supportability

We will support SQL Server 2014 with SharePoint Server 2013 but we need April 2014 CU and also SP1 installed.

RTM of SQL Server 2014 and when SharePoint 2013 will be supported: http://blogs.technet.com/b/wbaer/archive/2014/03/21/sql-server-2014-and-sharepoint-server-2013.aspx

Using SQL Server 2014 Reporting Server (SSRS) features together with SharePoint 2013? Check more here: http://technet.microsoft.com/en-us/library/gg492257(v=sql.120).aspx

Without an April 2014 full-server package for SharePoint Server 2013 we cannot say yet that it will be supported with all available features. We also need updated information in our TechNet that we now support SQL Server 2014, but it should be available as soon all information are collected.

Resources:
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

SharePoint 2013 and April CU 2014 issues.

Due to the problem identified in SP1, the  global installation package has not been released yet an. If your business has some urgency to have this issue fixed you can install the single package without any impact in your supportability.

Our full-server packages (SharePoint Server and Foundation) are not yet available and therefore you could install only “sub-packages”. From support perspective we are always suggesting to install full-server packages, but in case you need an important April 2014 CU hotfix, just for your info.

SharePoint contains not only SharePoint components and therefore the following list may not exhaustive.

General information you can find here: http://support.microsoft.com/kb/2953733

Access Server Download Link
Contains fixes when SQL Server 2014 will be used.

OWAS 2013 has an own kb article:
2863899    Description of the Office Web Apps Server 2013 hotfix package (Wacserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863899
For this package you need to have a SlipStream installation of OWAS2013 including SP1 or you can install it on top of any other former CU.

SharePoint Server 2013 Oserver package
2760265    Description of the SharePoint Server 2013 hotfix package (Oserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2760265

SharePoint 2013 / Word Server
2768332    Description of the SharePoint Server 2013 hotfix package (Wdsrv-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2768332

SharePoint Server 2013 Coreserver package
2863887    Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp; Projectserverwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863887

SharePoint Server 2013 Client Components package
2863895    Description of the SharePoint Server 2013 Client Components SDK hotfix package (Spdevsdk-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863895

More Info
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

 

 

SharePoint 2013 Service Pack 1 (SP1) again online

Customers with Service Pack 1 Already Deployed

For customers who have previously deployed Service Pack 1, download the updated Service Pack 1 and install over the existing Service Pack 1 running PSConfig or PSConfigUI immediately following.


Customers without Service Pack 1

For customers without Service Pack 1 deployed, download the updated Service Pack 1 package and deploy as per the KB documentation.

For more Information:
http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx

 

Unable to sync user titles for Welcome name in SharePoint

Hello ,

If you facing this problem you may read my previous post.

Sharepoint 2010 Change your display of wellcome name

In this post i have adding another powershell script that detects and fixes this problems for a workaround.

# THIS CODE-SAMPLE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
# OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR
# FITNESS FOR A PARTICULAR PURPOSE.
<#

#Add SharePoint PowerShell SnapIn if not already added
if ((Get-PSSnapin “Microsoft.SharePoint.PowerShell” -ErrorAction SilentlyContinue) -eq $null) {
Add-PSSnapin “Microsoft.SharePoint.PowerShell”
}

if( $args.Length -eq 0) {
write-host “Usage : Missing ”
exit
}

$MissMatchCount = 0
$NoProfile = 0;
$NoPrefferedName = 0
$TotalUser = 0
$Matched = 0
$Fixed = 0

write-host “Intializing…”
$site = new-object Microsoft.SharePoint.SPSite($args[0]);
$ServiceContext = [Microsoft.SharePoint.SPServiceContext]::GetContext($site);
$ProfileManager = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($ServiceContext);

foreach($siteUser in $site.RootWeb.SiteUsers)
{
write-host “Checking -> AccountName: ” $siteUser.LoginName ” ID:” $siteUser.ID
try
{
$profile = $ProfileManager.GetUserProfile($siteUser.LoginName);
}
catch
{
write-host “Unable to get profile for user” $siteUser.LoginName -foregroundcolor red
$NoProfile++
$TotalUser++
Write-host “————-”
continue;
}

$AccountName= $profile[[Microsoft.Office.Server.UserProfiles.PropertyConstants]::AccountName].Value
$PreferredName = $profile[[Microsoft.Office.Server.UserProfiles.PropertyConstants]::PreferredName].Value

write-host “Profile Data -> Account: ” $AccountName ” DisplayName:” $siteUser.DisplayName ” PrefferedName:” $PreferredName

if( $accountName -ne $siteUser.LoginName)
{
write-host “Account MissMatch -> LoginName: ” $siteUser.LoginName ” Profile Account:” $AccountName -foregroundcolor red
}

if( $PreferredName -ne “NONE” )
{
if($PreferredName -ne $siteUser.DisplayName)
{
write-host “MissMatch :” $siteUser.LoginName ” DisplayName:” $siteUser.DisplayName ” PrefferedName:” $PreferredName -foregroundcolor yellow
$MissMatchCount++

#Set-SPUser -identity $siteUser.LoginName -Displayname $PreferredName -web $args[0]
#$Fixed++
}
else
{
Write-host “OK”
$Matched++
}
}
else
{
$NoPrefferedName++
}
Write-host “————-”
$TotalUser++
}

Write-host “Results”
write-host “Total User : ” $TotalUser
write-host “Total Matched User Count : ” $Matched
write-host “Total Fixed User Count : ” $Fixed
Write-host “Total Missmatch User Count : ” $MissMatchCount
Write-host “Total Missing Profile User Count : ” $NoProfile
write-host “Total Empty Preffered Name user Count : ” $NoPrefferedName

For fixing option just activate the line by deleting “#” charecter.

#Set-SPUser -identity $siteUser.LoginName -Displayname $PreferredName -web $args[0]
#$Fixed++

Usage is simple:
Save the script in your drive as ps1 file.

C:\> .\syncuser.ps1 <SiteUrl>
Exp
C:\> .\syncuser.ps1 http://blog.bugrapostaci.com

PS: To get output in a text file is a little tricky but you can do it like this.
Start a Command Prompt ( Not Powershell! )
Type following command
C:\> powershell .\syncuser.ps1 http://blog.bugrapostaci.com > .\results.txt