URL Rewrite with SharePoint 2007/2010/2013

17/02/2014 Leave a comment

Redirection is the use of HTTP status codes 301 or 302 to redirect the client to a different location, which involves an additional client round trip.

Rewriting is actually changing both incoming and/or outgoing URLs. Any implementation of such rewrites is unsupported with SharePoint unless the path is symmetrical.

For example, you can modify the path of a request, such as http://www.contoso.com/sharepoint/default.aspx, which is forwarded to the SharePoint server as http://sharepoint.perimeter.example.com/default.aspx. This is referred to as an asymmetrical path.

SharePoint Server 2007/2010/2013 do NOT support asymmetrical paths. The path of the URL must be symmetrical between the public URL and the internal URL. In the above example, this means that the /SharePoint/default.aspx portion of the URL must not be modified by any external tool.

For More Information :
http://support.microsoft.com/kb/2818415

Filed under Sharepoint Tagged with ,

February 2014 CU for SharePoint 2010 has been released

17/02/2014 Leave a comment

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

 

Filed under Sharepoint 2010 Tagged with , , , , ,

Get SID by Powershell for SharePoint

05/02/2014 Leave a comment

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

 

Filed under Sharepoint 2010, SharePoint 2013 Tagged with , , ,

Keynotes for Distributed Cache on SharePoint 2013

05/02/2014 Leave a comment

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

Filed under SharePoint 2013 Tagged with , , , , ,

SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

03/02/2014 Leave a comment

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

 

Filed under SharePoint 2013 Tagged with , , , , ,

← Older posts

Newer posts →