Keynotes for Distributed Cache on SharePoint 2013

My colleague Hector has created a very good article by compiling different issues with Distributed Cache.
You can read the orginal article below link:
http://blogs.msdn.com/b/calvarro/archive/2013/08/29/points-to-consider-with-distributed-cache-on-sharepoint-2013.aspx

Here is the key notes:

  • NEVER admin the distributed cache from the admin console
  • Maximum capacity of memory is 16 GB per host cache
  • Dynamic memory is not supported in SharePoint 2013 environments nor APP fabric servers
  • The prodcuct after being installed allocates 10% of the physical RAM memory available at the sever. It can be configured following the next point.
  • It’s recommended to allocate 2 GB for other services.
  • It’s not supported to develop code against the Distributed Cache of SharePoint 2013.
    “If you are using custom applications in SharePoint Server 2013 which use the AppFabric client APIs, or are creating custom caches, you should create a separate AppFabric cache cluster to support your custom applications. Do not use the AppFabric cache cluster supporting your SharePoint Server 2013 farm. Run your separate AppFabric cache cluster for your custom applications on separate servers from the servers dedicated to your SharePoint Server 2013 farm.
    http://blogs.msdn.com/b/calvarro/archive/2013/06/05/supportability-of-custom-developments-in-sps-2013-and-appfabric-cache.aspx
  • Install the latest APP Fabric CU if possible. Right now we are in CU 4

SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

The following change was made to the December 2013 Cumulative Update from the previous SharePoint Server 2013 rollup updates. Previously, SharePoint 2013 Cumulative Updates included both the executable and the .CAB file in the same self-extracting executable download. Due to the file size, the SharePoint Server 2013 package has been divided into two separate downloads in December 2013. One package contains the executable file (identified as ubersrv2013kb2850024fullfilex64glb), while the other contains the .CAB file (identified as ubersrv_1). Both are necessary and must be extracted to the same folder to successfully install the update. Both are available via the same Hotfix Download Available link in the KB article for the December 2013 SharePoint Server Cumulative Update release.

For more information:
http://blogs.technet.com/b/office_sustained_engineering/archive/2013/12/20/change-sharepoint-2013-rollup-update-for-the-december-2013-cumulative-update-packaging.aspx

 

Office 365 new Partner Admin Center feature

The new Office 365 Partner admin center provides Partners new and enhanced tools to manage their Office 365 customers.  The new Office 365 Partner admin center is rolling out to partners worldwide over the next few weeks.  Previously, with Partner tools in the Office 365 admin center, you could perform delegated administration tasks on behalf of customers and create trial invitations, purchase offers, and offers for delegated administration. With the tools in the new Partner admin center, you are now also able to:

  • View the customers for which you have delegated admin privileges—all in one place.
  • Easily find, select, and perform administrative tasks on behalf of your customers.
  • View your customers’ Office 365 service health status and details.
  • Create, edit, and view service requests on behalf of your customers

For more info:
http://blogs.office.com/2014/01/28/introducing-the-new-office-365-partner-admin-center/

 

Microsoft is retiring InfoPath and investing in new forms technology across SharePoint

Here is some headlines from official article:

In an effort to streamline our investments and deliver a more integrated Office forms user experience, we’re retiring InfoPath and investing in new forms technology across SharePoint, Access, and Word. This means that InfoPath 2013 is the last release of the desktop client, and InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services. The InfoPath Forms Services technology within Office 365 will be maintained and it will function until further notice.

If you’re an InfoPath customer, we want to reassure you that we’re working on migration guidance in parallel as we’re building our next generation of forms technology. Until we have more detailed technology roadmap and guidance to share with you, we encourage you to continue using InfoPath tools. We also want to remind you that the InfoPath 2013 desktop client and InfoPath Forms Services for SharePoint Server 2013 will continue to be supported through 2023 as part of our Lifecycle support policy.

1.  Will Microsoft be shipping another version of InfoPath? No, there will not be another version of the InfoPath desktop client or InfoPath Forms Services. We are focusing all of our investments on new intelligent, integrated forms experiences across Office technology.

2.  How long will InfoPath be supported?

  • The InfoPath 2013 client will be supported through April 2023.
  • InfoPath Forms Services for SharePoint Server 2013 will be supported until April 2023.
  • InfoPath Forms Services in Office 365 will be supported until further notice.

For more information on InfoPath Forms Services support in Office 365, please review our Online Services Support Lifecycle Policy.

http://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/

 

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(), “” );