Skip to main content

Posts

SIGN IN As a Different User in SharePoint 2013 Server

In SharePoint Server 2013, noticed  that the Sign in as Different User menu option is missing. This was a great tool for developers and IT pro who wanted to test their solutions or customizations. Missing this option in the new version of SharePoint. May be There can be multiple reasons like 1. Caching Problems 2. Documents opened in external applications are saved with an unexpected user account . 3. Page content shows information from the previous user due to cached information. 4. Session variables contain information from previous user as the cookies are not cleared. The Sign in as Different User functionality is not meant to be used as a security feature! This feature allows users which have more than one AD account to quickly login with a different account to SharePoint - but it does not guarantee that no artefacts from the previous user remain! If you have to guarantee that one user cannot see data from a different user you have to logoff / logon in Windows...

The Ultimate SharePoint 2013 Certification Guide.

First version of The ultimate SharePoint 2013 Certification Guide.This guide is aimed at anyone who is considering studying for SharePoint Certifications either to improve their knowledge or to validate existing knowledge about SharePoint. This guide covers both certification options for all roles on both the Business and Technical side. To achieve technical certifications Microsoft offers several exams and certification options More information.... Please click here to download the   The ultimate SharePoint 2013 Certification Guide .

Define Managed Path in SharePoint

A Managed path is a location within a web application to use for site collections,You can specify that one or more site collections exist at a specified path. As an example, sites is the managed path in http://<site>/sites/madison . Managed paths cannot be limited for use by specific security groups, nor can they be targeted directly with audiences. They are simply a way to organize a large quantity of site collections. SharePoint uses the managed path to determine which content database the URL a user entered is in. Every URL request that comes into your server actually looks at the URL structure, looks up the managed paths listed in Central Admin, then routes the request to the proper database to retrieve the content. Knowing this, the more managed paths you add, the slower the performance so try to keep the number at a minimum (>20). Another reason to use managed paths is to keep structure and organization in where you place your site collections. For example, if your...

How to Install SQL Server BI Features with SharePoint 2013

SQL Server 2012 Service Pack 1 (SP1) supports Microsoft SharePoint 2013 Excel Services usage of Excel workbooks which containing data models and Reporting Services Power View reports. Excel Services in SharePoint 2013 includes data model functionality to enable interaction with a PowerPivot workbook in the browser. You do not need to deploy the PowerPivot solutions  for SharePoint 2013 add-in into the farm. You only need to install an Analysis Services server in SharePoint mode and register the server within the Excel Services Data Model settings. Deploying the PowerPivot for SharePoint 2013 add-in enables additional functionality and features in your SharePoint farm. The additional features include PowerPivot Gallery, Schedule Data Refresh, and the PowerPivot Management Dashboard. The basic steps to deploy the PowerPivot for SharePoint 2013 add-in are the following: 1. Verify Excel Services is configured to use an in SharePoint mode. For more information, see Manage E...

Workflow Manager 4.0 in SharePoint 2013 Workflows

SharePoint 2013 does not include the Workflow system as SharePoint 2010. To use SharePoint 2013 workflow, you have to get the Workflow Manager 4.0 on Microsoft Product download and create a new Workflow manager farm.  This system permits to host different SharePoint services in Cloud like Windows Azure. You can just have your SharePoint 2013 farm in your company and deploy Office Web Apps and Workflow Manager for example in Windows Azure Cloud infrastructure. You can use SharePoint 2010 Workflows too! In fact, SharePoint 2013 kept SharePoint 2010 Workflow service integrated.  If you want to configure the new SharePoint 2013 service, following this steps: Step 1 Install on your farm workflow manager 1.0 on Microsoft Web Platform Installer. Step 2 You should create new Services Bus Farm required by Workflow Farm. If you have already a Service Bus farm you can just attach it with " Join an existing Farm  " option. If you want to create ...

SharePoint 2013 Architecture

The new Microsoft template of SharePoint 2013 architecture includes new services. The design of SharePoint 2013 infrastructure has always 3 servers’ roles:  Web server,  Application server  and Database server.   Microsoft had published different SharePoint 2013 farm topology. In this example, a Six-Server virtualized farm. Example of Office Web Apps 2013 & SharePoint 2013 Architecture Example of SharePoint 2013 with Distributed Cache Service

STSADM Vs Powershell Commands in SharePoint 2013

The SharePoint PowerShell management console replaced STSADM since SharePoint 2010 release. In SharePoint 2013, the PowerShell management console is always here and do not purpose new functionalities. If you have some difficulties to use PowerShell management console as STSADM console, you can get equivalent STSADM commands in PowerShell in this table: STSADM Commands Sharepoint Management PowerShell Commands Activatefeature Enable-SPFeature Activateformtemplate Enable-SPInfoPathFormTemplate Addalternatedomain New-SPAlternateUrl Addcontentdb Mount-SPContentDatabase New-SPContentDatabase Adddataconnectionfile Install-SPDataConnectionFile Add-ecsfiletrustedlocation New-SPExcelFileLocation Add-ecssafedataprovider New-SPExcelDataProvider Add-ecstrusteddataconnectionlibrary New-SPExcelDataConnectionLibrar...