Showing posts with label SharePoint basics. Show all posts
Showing posts with label SharePoint basics. Show all posts

Saturday, August 30, 2014

SharePoint – Back to basics - Are sure you are SharePoint Farm Administrator?

How can I’ll be SharePoint farm Administrator? By Adding Farm Admin group from SharePoint Central Admin site as shown the below I’ll become Farm Administrator?

But as we have expected by completing all the steps, these will not grant Farm Admin privileges on the server. These steps will add user to farm admin group in SharePoint and WSS_ADMIN_WPG group in SharePoint farm. By updating user to this farm admin, users get access to web site and access to SharePoint resources as logs and web services.

If user not added in SharePoint local Admin group, user is not fully-fledged SharePoint farm administrator. When user runs SharePoint management he will see "The local farm is not accessible. Cmdlets with feature dependency ID is not registered."

To execute PowerShell commands, users need SharePoint_Shell_Access in SQL server SharePoint configuration database and other databases where we need to manage the data.

Therefore, to make a user as SharePoint farm admin, he need to have following permissions,

·      Local Administrator security group for each server in the farm
·      Farm Administration SharePoint Group
·      SQL Server SharePoint_Shell_Access database role for the SharePoint configuration database and all content databases.

Saturday, April 26, 2014

SharePoint – Back to basics- Creating lists using excel by using Import spread sheet template

We can create SharePoint list using Excel sheet using Import Spreadsheet Template. As a Developer\Administrator we can have knowledge on how to create the lists and libraries. But End users will not aware of this. For this purpose we have an option to create the list by using excel sheet having data.

To create using Excel sheet we have an option “Import Spreadsheet” as shown the image below.

While creating the list, Select “Import Spreadsheet” option. By selecting the option we’ll be navigated to details form page as below. Enter Name and description for new list and browse the Excel sheet in File location. Click on Import Button to update the data to select the data from the list.

Once user importing the data, list will be created with all the existing columns in sheet. Sometime SharePoint will not identify the type column. That’s only disadvantage with this option
Hope this helps.

Friday, September 27, 2013

SharePoint – Back to basics - Quotas and locks in SharePoint

In SharePoint, as an administrator, I can control the storage limits for a site. Quota specifies the amount of data that stored in a site collection. Quota settings will send emails when quota limit is exceeded.

We can change the quota settings in SharePoint central Administration By Navigating to Application Management and Selecting Specify Quota Templates link.

We can the Quota template page with maximum size and personal site template. We can change the separate template also. Template name will edit the existing quota templates. We can create new templates in the template name section. Storage limits values will specify the whether to limit the amount of the storage available on the Site Collection. “Sand boxed Solutions with Code Limits” specifies the sand boxed code allowed in the site collection.

If warning limits exceeds, Quota template will send an email. Any change in the template will be affected all the sites in this template. To change the specific site collection quota without changing the quota template we need to follow the steps below,
Navigate to Application Management in Configure Quotas and Locks link Site Collections section.

In Quotas page, in the Current quota template, we have to choose the template quota and specify the Limit site storage and send warning details and Sand boxed Solutions Resource Quota.

Locks will specify administrators to disallow users to view, add, edit, and delete the items from a site. This will be useful while taking backup or migrating activities. We have four lock types are available in SharePoint.

Not Locked is the default scenario users can view or edit the contents. Adding Content Prevented option will add new content that blocked but edit/delete will allowed here. Through Read only option users can only view the content. Adding/editing/Deleting will not be allowed. Through No access users cannot allow to access the site.

We can configure locks by navigating to Application management and select configure quotas and locks. In the quotas and locks page, we need to specify the lock status in “Lock status for this site” option.

Monday, June 3, 2013

SharePoint - Back to basics - Evaluation of SharePoint

Back to the day that I have started learning SharePoint, It was Thursday in January month and SharePoint 2010 came out recently at that time. Few of my colleagues are started working on SharePoint 2010 and few more working on SharePoint 2007.
MOSS 2007 was launched with greater things. There were lot of changes between SharePoint 2003 and SharePoint 2007. We have to check that we are going to inherit from System.Web.UI.Webcontrols.Webpart or SP WebPart class.  Here are few differences between ASP.NET web part and SharePoint webparts.
  •       We don’t have cross page connections
  •       Data caching allows caching in content DB
  •       Client side connection and connections between two webparts.

In SharePoint 2007, we need to use CKS tools to create WSP package or else we need to create our own package. Here are the simple steps,
  •       Create a dwp file for the web part
  •       Create feature.xml file and manifest.xml file
  •      Create a DDF to cab and use it to create a cabinet file using makecab command.

For Moss 2007, project server and and info path form services also released.
SharePoint 2010 was come out as the next release to the SharePoint 2007 with few add-ins (Office web apps, FAST search server.) Web parts can be created also using silverlight packages and we can use them in SharePoint for more beautiful UI. We can use Silverlight in SP 2007, but we have to write our own code to it by using web services or using Object model. REST came in to the picture with Client side Object model and Silverlight Object model in SharePoint 2010. This helped to get the SharePoint object and use them on client machine.  Sand boxed solutions are helped to deploy the solutions at site collection level instead of farm. All these are created that In previous versions all code was running under server side, so to escape the burden from the server. So that the impact on web front end machine performance was impacted.
In SharePoint 2013, we can see that CSOM has expanded with extra functionality and APPS was working more of replacement of Sand boxed solutions. Here we have more feasibility to use client side things like JavaScript, JQuery, Silverlight, and HTML.
These are few basics on the SharePoint evolution and it is helpful to know the things as a SharePoint developer. 

Wednesday, May 22, 2013

SharePoint - Back to Basics - Are you SharePoint Developer? What Kind of Developer you are?

As per my knowledge, I have divided SharePoint Developers into three categories. Each of them in three groups knows SharePoint very well.
Managing complex custom list and creating custom workflows are both come under Application maintenance. As per the knowledge on custom application development I have assumed the developers into three groups,

End User SharePoint Developer: End user SharePoint developer can have owner or contributor permissions on a site. He can able to create or modify list views (personal or Shared). He is able to change the complex list view to his needs by filtering and sorting the list data. User can add web parts and change the settings of the web part if he has owner permissions to page.
End User SharePoint Developer can use Internet explorer or any other web browsers.

Power User SharePoint Developer: Power User SharePoint Developer will have permissions for site owners or site collection Administrator. He can able to develop complex applications, site pages, and designer workflows. He can have knowledge to modify the web part pages, connecting external data sources and show the data in SharePoint site dashboards. He can have knowledge on JavaScript. He can develop the applications by using SharePoint Out of box features, so that we can see the results in a quick manner.
This user mainly uses Internet Explorer and SharePoint designer to build the applications.

Advanced SharePoint Developer: Advanced SharePoint Developer will have knowledge on SharePoint out of Box features, SharePoint Designer and Custom development using Visual Studio. He can able to build features, Solutions and workflows using Visual Studio. He will have command on everything in SharePoint as well as .net concepts.
This user uses Internet explorer, SharePoint designer and Visual Studio to do his work.

Here is the simple image differentiating the SharePoint Developers.