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.

Advertisements

February 2014 CU for SharePoint 2010 has been released

The product group released the February 2014 Cumulative Update for the SharePoint 2010 product family.

Be aware that the February Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix. It is recommended to have SP2 installed before installing the February CU

More details please check;
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/12/february-2014-cu-for-sharepoint-2010-has-been-released.aspx
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/02/12/sharepoint-2010-and-february-2014-cu.aspx

 

Get SID by Powershell for SharePoint

You can use following powershell to check SID from AD.

$NTAccount = new-object System.Security.Principal.NTAccount(‘SamAccountName’)
$TranslatedToSidObject = $NTAccount.Translate( [System.Security.Principal.SecurityIdentifier])
$SID = New-Object System.Security.Principal.SecurityIdentifier($TranslatedToSidObject.Value)
$TranslatedToNTAccount = $SID.Translate([System.Security.Principal.NTAccount])
Write-host $TranslatedToSidObject.Value `t`t $TranslatedToNTAccount.Value

You can use following powershell to check SID in SharePoint

$site = get-spsite http://blog.bugrapostaci.com
$web = $site.OpenWeb()
$user = $web.EnsureUser(“BLOG\bugra”)
$user.Sid

 

Publishing Field encoding extra “?” questionmark charecters (actually acsii 8203 zero width space )

Assume that you have created a new article page then Typed some string in Page Content.
After Selected this content and make it bold.
Then clicked the
HTML Source.-> In html source we see following looks no unusual charecter in it .
<p><strong>sharepoint</strong></p>

But if we copy this string tsource to another program for example notepad++ We can see “?” <p><strong>sharepoint</strong>?</p> …. or if you run following powershell:

$site = get-spsite http://contoso
$web = $site.OpenWeb()
$list = $web.Lists[“Pages”]
$page = $list.GetItemById(<ItemId>)
$page[“Page Content”]

Result is same :<p><strong>sharepoint</strong>?</p>

+It is happen only when the first page created and saved.
+Issue happen when we reach data with OM or copy paste outside of the SharePoint to another advanced text editor program.

Similar :http://social.msdn.microsoft.com/Forums/sharepoint/en-US/23804eed-8f00-4b07-bc63-7662311a35a4/why-does-sharepoint-put-in-character-code-8203-in-a-richtext-field?forum=sharepointdevelopment

You may face this issue Both SharePoint 2010 and Sharepoint 2013

Unfortunately this is by design . The “Page Content” field or Publishing HTML Fields uses RTE (Rich text editor). RTE sometimes adds zero width space (&#8203) as a workaround to ensure cursor range selection is correct in some browsers. When viewing “HTML Source”, browser HTML doesn’t render zero width space character. But after copying the string out,like notepad++ and powershell renders it as an unknown character (?). It is rare condition and not happen always and depends many various factors But if you have facing this
For a resolution, you may need use some custom codes for remove that charecter in related string.
String.Replace(  ((char)8203).ToString(), “” );

Content Type Publishing does not publish SPD reusable workflow along with Content Type for SharePoint 2010

Content type Publishing will include workflow associations, but not the workflow themselves. It is by design , In SharePoint 2010, Content Type Publishing will include the workflow association, however the actual workflow is not published. To work around this behavior, workflows should be manually created or transferred to the site before the Content Type and workflow association are published.

Does SharePoint Server 2010 SP2 has also contains SharePoint Foundation 2010 SP2 updates ?

The answer is  YES

Unlikely the previous SP1s of the SharePoint If you have a SharePoint Server 2010 installation , just installing SharePoint Server 2010 SP2 is enough,
You dont need to install SharePoint Foundation 2010 SP2 first.

For more information about SP2 please check my previous article.
http://blog.bugrapostaci.com/2013/07/23/sharepoint-2010-sp2-has-been-released/

 

How to remove “Open this webpart page in maintenance view” message

Assume following scenario

1. Add wiki page in wiki page library
2. edit properties of this page, there is an message

“Open this web part page in maintenance view to delete the problem web parts and remove the personal settings.”

at the bottom of the editing property page.

wmm0

this message is usually a false alarm but it can make users annoying. You can remove this message by using JQuery easily.

  1. Integrate the Jquery with your master page.
    http://blogs.msdn.com/b/yojoshi/archive/2010/06/17/using-jquery-with-sharepoint-2010.aspx
  2.  Go to the related Library Settings -> Advanced Settings.
  3. And select “Launch forms in a dialog” option to “no” and click ok.That would provide to open dialog boxes as a page and you can use the ribbon to change edit mode of the editform.aspx page.

    wmm1

  4. Find the item in the library and Click edit Properties
    wmm2
  5. Click Site Actions -> Edit Page while EditForm.aspx in browsing.
    wmm3
  6. Add a “Content Editor” web part to related Document Libraries’ EditForm.aspx
    wmm4
  7. Click HTML-> Edit HTML Source
    wmm5
  8. Type following Script inside of the HTML Source Windows.

    <script type=”text/javascript”>
    $(document).ready(function() {
    $(“a:contains(‘Open Web Part Page’)”).parent().css(‘display’,’none’);
    });
    </script>

    wmm6

  9. Click OK and Save the page. IF everyhing is ok you shouldn’t able to see the WebPartMaintenace Message like below.

    wmm7

  10.  Go to the related Library Settings -> Advanced Settings.
  11.  And select “Launch forms in a dialog” option to “YES” for revert back and click ok