Friday, November 29, 2013

What are the accounts used in SharePoint for a least privileged configuration

 What are the accounts used in SharePoint  for a least privileged configuration.



In Many Organizations while Implementing SharePoint. The first question which may arise is What are the account we need to create and what are the permission levels it should have. I have tried my best to collate the things together and text it in my Blog as per my experience.Theese accouns are minimal accounts that required but it varies as per the requirements.


The setup account: This is the account with which the user is logged that runs the setup. This account must be a local administrator on all systems where SharePoint is run.

Post-Setup Configuration Run-As user: This is the user that runs the PSC tool.
This user must also be a local administrator
PSC runs a prerequisites check.
In addition to being a local administrator on all computers running Office Server, this account also has the following requirements on a remote server running SQL Server to be used as part of a SharePoint Foundation 2010 Services farm

Must be a SQL login
Must be a member of the SQL Server Database Creators Role
Must be a member of the SQL Server Security Administrators Role
This account need not be a local administrator on the server running SQL Server

This is the only account given explicit rights on SQL. It will give the database access account the SQL privileges it needs because it has the rights to do so.

The database access account: This is the account that is specified to the PSC tool when creating or connecting to a Configuration Database.
This account need not be the same as the PSC Run-As user and it need notbe a local administrator on any computer running Office Server.
It should also not be a local administrator on the SQL server, and doesnot require any SQL permissions in advance of creating a configuration database. Many of us refer to this as the “farm admin” account, but thisis misleading. The user that accesses the Central Admin Web pages to perform farm administrative activities is the farm admin account.

Central Admin App Pool ID:This account is “automatically” configured by the PSC tool to be the same account as the database access account that is stipulated to the PSC tool when creating a configuration database. This account and the SPTimer account constitute one exception to separate accounts being usedfor all account types.

The SPTimer account: As with the Central Admin App Pool ID, this account is “automatically” configured by the PSC tool to be the same account as the database accessaccount that is stipulated to the PSC tool when creating a configuration database.

The Farm Admin account: As mentioned earlier, this is the user that accesses the Central Admin Web pages to perform farm administrative functions.
This account can create Web applications, site collections, SSPs, configure Search, IFSS, Profile Imports, assigning permissions, and so on.


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SharePoint 2013 Server - Components Installed

SharePoint 2013 Server - Components Installed:

   


Everyone must be interested to know whether what all changes were made to  machine after installing SharePoint 2013 Server. Well, I observed very keenly what changes does made. below mentioned are some of the basic changes that occur while installing SharePoint 2013 Server.I post this simple topic because,I many times Think what happend behind installation of Sharepoint 2013.

1) Global Assembly Cache (GAC) Updated: All the SharePoint DLL will be deployed to GAC which makes the SharePoint framework available to the applications on OS.

2) SharePoint Root (15 Hive) Created: The 15 Hive is a special folder which is located at c:\program files\common files\Microsoft shared\web server extensions\15. It consists of a folder structure that holds all the important DLLs, images, config files, templates, etc for developing rich SharePoint applications.

3) Internet Infromation Services (IIS) Updated: Virtual directories and Application pools are created in IIS that hold numerous ASP.NET 2.0 web sites, with configuration files that turn them into SharePoint 2013 sites that use .NET 4.0.

4) Central Administration Site Created: This is the default website for SharePoint 2013 Administration which is created in IIS. This site provides a rich interface for managing and monitoring SharePoint sites and applications.

5) Content Database Created: An SQL Server database that stores all site content, including site documents or files in document libraries, list data, and Web Part properties, as well as user names and rights. All the data for a specific site resides in one content database on only one computer.


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SharePoint Tools

   SharePoint Tools

I used to Follow the CODE PLUX from beginning of I entered into the SharePoint . For any New tools\packages for SharePoint. Thought to share who needs the useful tools from code plux.    

·         Free SharePoint 2010 Sites Templates: http://sp2010teamplates.codeplex.com

·         Free Web Parts for SharePoint 2013 and SharePoint 2010: http://webpartgallery.codeplex.com

·         SharePoint 2010 FBA Pack: http://sharepoint2010fba.codeplex.com

·         SharePoint 2010 Send Emails With Attachments - Workflow Activity: http://sharepointstuff.codeplex.com

·         SharePoint 2010/2013 Tabbed Web Part Zone: http://sharepointtabs.codeplex.com

·         AutoSPInstaller: http://autospinstaller.codeplex.com

·         SharePoint Client Browser for SharePoint 2010 and 2013: http://spcb.codeplex.com

·         SharePoint 2010 - Community Projects: http://lifeinsharepoint.codeplex.com

·         SharePoint 2010 Bulk Document Importer: http://spbulkdocumentimport.codeplex.com

·         SharePoint 2010 CSV Bulk Taxonomy TermSet Importer/Exporter: http://termsetimporter.codeplex.com

·         SharePoint 2010 Batch Edit: http://sp2010batchedit.codeplex.com

·         SharePoint 2010 automatic sign-in with mixed authentication: http://spautomaticsignin.codeplex.com

·         SharePoint 2010 HTML5 MasterPage Templates: http://sharepoint2010html5.codeplex.com

·         Nivo Slider Web Part SharePoint 2010: http://nivowebpart.codeplex.com

·         Export Version History Of SharePoint 2010 List Items to Microsoft Excel: http://exportversionhistory.codeplex.com

·         Audit Log For SharePoint 2010: http://auditlogsp.codeplex.com

·         SharePoint 2010 Filtered Lookup Field: http://sp2010filteredlookup.codeplex.com

·         SharePoint CAML Query Helper for 2007, 2010, and 2013: http://spcamlqueryhelper.codeplex.com

·         LDAP/AD Claims Provider For SharePoint 2010: http://ldapcp2010.codeplex.com

·         SharePoint 2010 Fluent Ribbon API: http://spribbon.codeplex.com

·         SharePoint 2010 Print List Ribbon Button: http://spprintlistbutton.codeplex.com

·         SharePoint AJAX Toolkit for SharePoint 2010 and 2013: http://sharepointajax.codeplex.com

·         Responsive SharePoint: http://responsivesharepoint.codeplex.com

·         SharePoint 2010 Google Maps V3 WebPart: http://spgooglemappart.codeplex.com

·         SharePoint 2010 Word Automation: http://sp2010wordautomation.codeplex.com

·         SharePoint 2010 "Hyperlink with Picture" Column Type: http://spimagehyperlink.codeplex.com

·         SharePoint 2010 Timesheet: http://sp2010ts.codeplex.com

·         SP List Kit for SharePoint 2010: http://splistkit.codeplex.com

·         Show or Hide SharePoint 2010 ribbon based on SharePoint Groups: http://spribbonvisibility.codeplex.com


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Wednesday, November 27, 2013

SharePoint Licensing

 SharePoint Licensing:
 I post this simple Article in a very Understandable manner, because, I have Many unclear things on License part of SharePoint before. After I dig in Google and talking with Experts, I have a clear mind about License’s. Sharing this with who still not clear on Licensing part.

                                 

  
   Explanation:

As most know, starting with the 2007 version of SharePoint, the product is available in three editions. In the 2010 version of SharePoint, those three are SharePoint Foundation, Server Standard, and Server Enterprise.  I think most people know that the Foundation edition of SharePoint does not require any additional license purchase other than Windows Server licenses and Windows Server CALs.  

 The Server Standard edition is not free.  It requires one server license for each server in the SharePoint farm.  It also requires SharePoint users to have a Server Standard Client Access License (CAL).  Both of these licenses are sold through Microsoft Volume Licensing and its volume licensing partners.

The Server Enterprise edition requires one server license for each server in the SharePoint farm, and this server license is the same license that is required for a Server Standard farm. There is no distinction between server licenses for a Standard farm vs. an Enterprise farm.  There is a distinction between the two editions for the user CAL.  To use the Enterprise edition your users need BOTH a Server Standard CAL and a Server Enterprise CAL.



Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Tuesday, November 26, 2013

Download this free E-Book to learn more about what's new in SharePoint 2013

Download this free eBook to learn more about what's new in SharePoint 2013

MS Article: http://www.microsoft.com/en-us/download/details.aspx?id=35396



Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

How to Enable the convert License type option Under Upgrade and Migration.

  How to Enable the “Convert License type” option Under Upgrade and Migration.

  Issue: “Convert License type” is grayed out
                        

 Background: Initially ,I installed foundation of sharepoint-2013 in my test lab. As you all know there are so many features not available on Foundation version. After working some days on foundation, thought to migrate version to SharePoint server 2013.When I try to Install server version giving the Error . As per the experts advise trying to make My standard foundation edition to enterprise. When I check the option it should be in disable state. After digging much time, found way to do so.

  How to Over Come: Follow the below steps to overcome and enter License .
·        Get your IE developer tool out, and point it to the disabled input box. You can do that pressing F12 key on the page of convert license type. Point to the html code that disabled input box.Search for Disable.                                 

·        Now you can have the line highlighted.  disabled=”disabled”. Let’s change it to trick the page.

·        I changed the name “disabled” to something as per below.             



·        Note: Once changed Directly go to “convert License page”.dont refresh the page.
·        Now I can input my Enterprise license key to the box.  OK button is still disabled. do the same below Ok like"changed the name “disabled” to something.
               
·        After Ok button is enabled, click on it, the feature for Enterprise CAL now can be unlocked without any problem.
         this is a quick way to have a workaround.
Note: this is not for production use.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, November 25, 2013

Why 14 Hive folder still Exist for SharePoint 2013

   Why 14 Hive folder still Exist for SharePoint 2013 :

After, I installed Sharepoint-2013 on my test lab. When I am playing it with. I am confuse by Seeing 14 Hive Folder in below path. I expect it should only 15 Hive But still showing 14 Hive including 15 Hive.why?
                                    


   Explanation:

·         That, SharePoint 2013 has a SharePoint 2010 mode. meaning, there is a 14 hive that gets installed when the setup and configuration is complete. After installing SP2013 it will create both 14 & 15 hive folders (its normal). 
·         In SharePoint 2013 it’s possible to install both SharePoint 2010 and 2013 solutions, which is supported by having two folders – one for the Sp2010 (“14) hive files and one for the SP 2013 (“15) hive files

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Sunday, November 24, 2013

Why IIS AppPools show V4.0 for SharePoint 2013 running with .net framework V4.5:

  Why IIS AppPools show V4.0 for SharePoint 2013 running with .net framework V4.5:

After, I installed Sharepoint-2013 on my test lab. When I am playing it with. I am confuse by Seeing the IISmanager AppPool Version of SharePoint. I think it should be V 4.5 But still showing V4.0 Like SharePoint 2010.Why?

                                 

  Explanation:

The .NET Framework can version in two ways.

·          Major Version – also called side by side installs
Two different major versions can live together on the same machine.
·         Minor Version – also called “in-place upgrades”

Minor version means the CLR remains the same but new libraries , bug-fixes and/or some other improvements are added to main CLR.
.NET 4.5 is not a major version and so does not add different side-by-side CLR.

·         It will eventually use the same .net framework V4.0CLR and include some additional libraries and Bug fixes/some improvements as well. But it does not add new CLR. I believe new CLR should be the upcoming version.


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SharePoint 2013 The 15 Hive and other important directories

SharePoint 2013 The 15 Hive and other important directories:

After I installed SharePoint 2013 in My test lab, I come to know that there is some change\Extra folders included in the path .Find the Details of the Folders and the function of those. The 15 Hive is a special folder which is created during SharePoint 2013 installation. All the important files for supporting SharePoint framework like web.config, Features, Web Parts, User Controls, Help Files etc are stored in the SharePoint 2013 server file system inside the 15 Hive.I explained a brief what Folder do what function as My experiance.                         
                                             
                               

  The 15 Hive - Folder Location:

            The 15 Hive folder is located at the following path

C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\15


 The 15 Hive - Folder Structure:

The 15 Hive has a definite folder structure which holds the core SharePoint server files.

 ADMISAPI:- It contains soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.

 Bin:- The directory contains all the core binary files, utilities which used by SharePoint Services.  command line tools such as STSADM.EXE also present in this folder.

Client:- This directory contains files that are used for creating office apps. 

Config:- This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application will not function correctly.

HCCab:- This directory has a set of cab files which has content information used by the SharePoint help system.

Help:- The folder contains html help file (.chm) used by the configuration wizard.

ISAPI:- This directory contains all the standard Web Services for SharePoint and resources and configuration files that the web services use.

Logs:- This is the folder where we can have all the SharePoint related logs will see. This is important when any problem or error occur in SharePoint you have to trace the logs files in this folder to get the error messages.

Policy:- This directory contains SharePoint 2013 Server policy files.

Resources:- This directory contains the core.resx file used for creating language packs for SharePoint.   by which different SharePoint sites with different languages and cultures can be create.

Template:- It contains the core web site functionality like the features, templates, configurations, resources of a web site.

UserCode:- This directory contains files used to support sandbox solution.

Web Clients:- This directory contains files related to Client Object Model.

 Web Services:- This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.


  Other  Directories In SharePoint 2013:

1) C:\Inetpub\wwwroot\wss - This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites.

2) C:\ProgramFiles\Microsoft Office Servers\15.0 - This directory is the installation location for SharePoint Server 2013 binaries and data. The directory can be changed during installation.

3) C:\ProgramFiles\Microsoft Office Servers\15.0\WebServices - This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.

4) C:\ProgramFiles\Microsoft Office Servers\15.0\Data - This directory is the root location where local data is stored, including search indexes.

5) C:\ProgramFiles\Microsoft Office Servers\15.0\Logs – This directory is the location where the run-time diagnostic logging is generated.


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

ShareThis

X