Thursday, August 15, 2013

Content Deployment


If you ever run into issues with content deployment stuck in “Importing” state for long time and not moving forward even after manually running the destination timer job, recycling the timer service only on destination server and then re-running the CD timer job on destination fixes the issue. Make sure the timer job is recycled when there is no current CD jobs executing.

Saturday, January 19, 2013

SharePoint No Downtime based deployments

Deploying solutions to a SharePoint farm with zero or no downtime. It is possible by using the local switch to deploy the files only to the local server hence individual servers can be taken out of rotation and then this operation can be performed.

stsadm -o addsolution -filename "WSPName.wsp" (Does not cause IIS pool recycle)
stsadm -o deploysolution -allowgac -local -name "WSPName.wsp"
stsadm -o retractsolution -local -name "WSPName.wsp"
stsadm -o deletesolution -filename "WSPName.wsp" (Does not cause IIS pool recycle)
stsadm -o upgradesolution -filename "WSPName.wsp" -name "WSPName.wsp" -allowgac -local

Sunday, January 13, 2013

SP2010 Web Analytics

If you are using a Hardware Load Balancer (HLB) in front of your SharePoint 2010 FE servers to offload SSL and have web analytics configured on the farm, you may see incorrect (less) traffic values in the site collection web analytics reports. 
Make sure HLB sends client IP address to the FE servers, you can easily find that out by checking the IIS Logs to ensure actual client-ip's are getting logged and not the HLB ip address. 
If you see HLB ip address getting logged, you need to find out a way to add the cip(client ip) to the package sent by HLB to SP FE as a custom header and the FE should have IIS AARHelper module to reassign the custom header to client-ip. Once this is done Web analytics reports should start reporting actual traffic data.

The root cause of the problem is, when HLB sends all traffic stamped with its IP address, Web analytics reporting logic treats all incoming requests as SPAM and deletes them from the reporting database. The rule of thumb what we discovered was if there were more than 1000 requests from a specific client requesting any url within a span of  then the deletion logic would kick in.


SQL 2012 - HA/DR Offering

Friday, September 28, 2012

Delete FAST index content

 
This command can be used to delete content from FAST SSA in SharePoint. This command needs to be executed on FAST admin server,
 

Sunday, September 2, 2012

SP2013/SP15 Overview

Key Highlights:
1. Shredded storage
2. SQL Improvement - SQL 2012 support
3. Cache Services: Win AppFabric, Farm Level Cache
4. Request Management: Redirection between farm servers based on request parameters
5. Themes
6. Sharing

* Office Webs and Web Analytics no longer available

ECM:
1. Site level retention
2. Discovery Center: Record center. Easy connect to Exchange, file shares etc

Web Content Management:
1. HTML tools for web design
2. Variation: Machine translation using cloud based service to translate individual sites or pages
3. SEO: Url handling (clean urls), metadata setting, site hirerarchy available for individual site pages.
3. Cross Site Collection Publishing
4. Video Embedding: native html 5 video rendering capability
5. Image renditions: resize images on server side by storing new versions
6. Clean urls: Drive navigation using specific term set/metadata navigation. No longer depended on physical site hirearchy but with metadata navigation
7. Metadata navigation:

Social:
1. Microblogging
2. Activity Feeds
3. Communities
4. Discussions
5. Blogs

Search:
1. Personalization
2. Contextual Previews (check with edition has it)

BI
1. Excel BI
2. Excel Services
3. PerformancePoint Services: Using Analysis Services Effective User eliminates Kerb delegation
4. Vision Services: More number of data sources (Use BCS or SQL Azure)

Mobile:
1. Automative Mobile Browser Redirection -> Part of publishing infrastructure

Evolution of customizations in SP15
1. Customization that involve gathering information from external sources are kept seperate from SharePoint and are managed seperately (patched, executed) from SharePoint.
2. This code is outside SharePoint execution context.

Reference:
http://technet.microsoft.com/en-us/sharepoint/fp123606.aspx