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

Monday, 9 January 2017

Configuring Stand Alone SharePoint Server 2010


In this post I will explain how to configure a Standalone SharePoint Server.

    Run SharePoint Server 2010 Application file, system will extract files and show the below screen, under Install > click Install Software prerequisites.
      
    Click on Next in the wizard.
     
    Complete the installation wizard and System will run for few minutes and display the following error message: 



    Install your prerequisites software that you downloaded one by one (if possible, follow the above order as shown in the error message). Note: If you try to install Hotfixes from your Share Folder system may prompt “error code 0x80070003” please copy your hotfix files to Windows server and click Install. 

    Once you get the above screen “Installation Complete”, click "Install SharePoint Server” link:
    SharePoint 2010 Installation screen prompts for Product Key. Enter the Product key and press ‘Continue’. 

    Read your License terms and click I accept and start Installation: 

    Select Standalone option, if you are installing with SQL Express 2008 server and SharePoint will be hosted from same location. If you are installing SQL Server 2008 and SharePoint 2010 farm servers, then select Server Farm option. First of all we are choosing Standalone installation. 
     
    System will start the Installation process. 
     
    System would take several minutes to complete installation and prompt for Configuration Wizard. 
     
    Run your Configuration wizard and click next: 
     
    In Configuration wizard click “Yes” to start IIS and SharePoint Admin, Timer service. SharePoint will start configuring the SharePoint farm. If You have selected Standalone while installation process then Configuration wizard continue 2 of 10 tasks and if everything is OK, the system will display the following screen. If you selected Server farm then wizard will show like this-  
     
     
     

    Congratulations… you successfully Installed SharePoint 2010. System will launch SharePoint 2010 Central Administration screen like this (As this is a Standalone SharePoint so you will not be able to do farm level settings). Here you can create a new site.
     

    Configuring SharePoint as a Server Farm 2010

    In this post I will explain how to configure a SharePoint Server Farm.

    Run SharePoint Server 2010 Application file, system will extract files and show the below screen, under Install > click Install Software prerequisites.
      
    Click on Next in the wizard.
     
    Complete the installation wizard and System will run for few minutes and display the following error message: 



    Install your prerequisites software that you downloaded one by one (if possible, follow the above order as shown in the error message). Note: If you try to install Hotfixes from your Share Folder system may prompt “error code 0x80070003” please copy your hotfix files to Windows server and click Install. 

    Once you get the above screen “Installation Complete”, click "Install SharePoint Server” link:
    SharePoint 2010 Installation screen prompts for Product Key. Enter the Product key and press ‘Continue’. 

    Read your License terms and click I accept and start Installation: 

    Select Server Farm option and Click on next. Here again we can Server Type Stand-alone or Complete installation here we are selecting Complete Installation. We can also choose installation folder in File location tab here.

    System will start the Installation process. 
     
    System would take several minutes to complete installation and prompt for Configuration Wizard. 
     
    Run your Configuration wizard and click next: 
     
    In Configuration wizard click “Yes” to start IIS and SharePoint Admin, Timer service. SharePoint will start configuring the SharePoint farm. 






    If you selected Server Farm option while installation Wizard will look like this.
    Here again we can Server Type Stand-alone or Complete installation here we are selecting Complete Installation. We can also choose installation folder in File location tab here.

    Select if you want to connect the sharepoint to existing Farm or you want to configure new farm. Here we select to configure a new Sharepoint Farm.


    Here select your SQL server 2008 R2 (Minimum) and provide Configuration Database name and User name and Password for the user. Please make sure to provide a user whose password does not change or expire. User must have Securityadmin, DB_owner,  dbcreator rights on the SQL server for installation as recommended by Microsoft but we suggest to provide user in sysadmin  rights on SQL to install the SharePoint.

    Please provide the Passpharse and click on next, so that you can add other sharepoint in this form by providing this passphrase.

    Provide the port where you want to host the SharePoint on the server and provide the Security Settings here we are selecting NTLM. These security settings can be changed later. Click on next.
     
    Now wizard will show the configuration setting selected by you. Check once and click on next.

    Then Configuration wizard will continue 2 of 10 tasks. 

    If everything is OK, the system will display the following screen. Click on Finish. 

    Congratulations your SharePoint 2010 is now installed. It will be opened in browser like this and will ask you configure the SharePoint Services on the server. Here we are using wizard to configure the services. User can configure the same manually.

    Click on next to complete the configuration of the farm and its services. Select the service and the service account user who will operate the services and click on next the wizard will do the process.

    After process the wizard will ask you to create a site collection.  And will show the below screen. Please provide Site Title, Description and select the Template and click on OK.
     
    After completing the configuration and creating new site collection wizard will show below screen. Click on OK or you can now open you site.

    Now your SharePoint is ready to use. You can see the Central Administration screen as below.

    Configure SharePoint 2013 in Windows Server 2012 R2

    I was recently trying to install SharePoint 2013 on Windows Server 2012 R2. But when I start to install I got many errors in installation. In this blog I am defining the steps and resolutions that I followed to install the SharePoint 2013 in Windows Server 2012 R2.

    The Problem with SharePoint 2013 on Windows 2012 R2

    As we know that SharePoint 2013 came onto the market before Windows 2012 R2 so it is not supported to install Sharepoint 2013 on Windows 2012 R2. Anyhow, I tried to install SharePoint 2013 onto Windows 2012 R2 and then patch up to SharePoint 2013 SP1.
    Reference - https://blogs.technet.microsoft.com/wbaer/2013/09/22/sharepoint-2013-support-for-windows-server-2012-r2/
    Before I start solving the problem and solution, it is important that it is possible to download a Microsoft provided slip-streamed iso of SharePoint 2013 with SP1. For this user should have access to a MSDN Subscription.

    We can also do one change in system32 directory so that you will be able to check pre-requisites status and installing the same using check prerequisiteinstaller.exe wizard.

    1. Go to System drive where windows server 2012 is installed. Normally it is drive C:.
    2. Go to Windows Folder.
    3. Go to System32 Folder.
    4. Look for "ServerManager.exe" file.
    5. Create a copy of this file. (Remember not to remove or change this file)
    6. Now rename the new file with "ServerManagercmd.exe".
    7. Now run the "Prerequisiteinstaller.exe" file now it will work.

    Otherwise you can follow steps to install Pre-requisites manually and correctly in Windows Server 2012 R2 in SharePoint 2013 -

    Here in path the drive ‘D’ is the name of drive where Windows 2012 R2 disk is inserted. Path is – D:\sources\sxs
    1. Enable the Windows-Identity-Foundation feature:

    Get-WindowsFeature Windows-Identity-Foundation|
    Add-WindowsFeature -source:”Path”

    2. Enable the Application-Server role:

    Get-WindowsFeature Application-Server|
    Add-WindowsFeature -source:”Path”

    3. Enable the Web-Server role and management tools:

    Get-WindowsFeatureWeb-Server|
    Add-WindowsFeature -source:”Path” -IncludeManagementTools

    4. Enable the IIS 6 Management Compatibility component:

    Get-WindowsFeature Web-Mgmt-Compat|
    Add-WindowsFeature -source:”Path”

    5. Download and install WCF Data Services (5.0.512) from  http://www.microsoft.com/en-gb/download/details.aspx?id=29306

    6. Download and install Windows Identity Extensions (1.0) from  http://go.microsoft.com/fwlink/?LinkID=252368

    7. Download Windows Server AppFabric (1.1) from 
    and install it through the command line:

    WindowsServerAppFabricSetup_x64.exe /I CacheClient,CachingService,CacheAdmin /gac

    8. Reboot Server.

    9. Download and install AppFabric 1.1 CU1 from 

    10. Download and install Sync Framework Runtime v1.0 SP1 from 
    (extract and execute the synchronization.msi installer from the Microsoft Sync Framework directory).

    11. Download and install Microsoft Information Protection and Control Client from 

    12. Reboot Server.

    13. Download and install the SQL Server 2012 Native Client from http://go.microsoft.com/fwlink/?LinkID=239648 
    (minimum requirement is SQL Server 2008 R2 SP1).

    14. Reboot Server (for good measure).


    After pre-requisite has been installed in the above sequence and start installing SharePoint 2013. Now you will be able to install SharePoint 2013 on Windows Server 2012 R2 easily.

    Post SharePoint 2013 installation do not forget to patch to SharePoint 2013 Service Pack 1.

    Friday, 23 December 2016

    SharePoint Site asking password again and again

    Hi All,

    Today I am going talk about a very wired behavior of SharePoint.

    Issue-
    When you are opening a SharePoint site in  Internet Explorer it is asking for user credentials again and again and mostly it is asking for password 3 times and then shows a blank screen. This issue is coming for all the users even also for Site Collection Admin or Farm Administrators. 

    Here i will like to mention that i was using a Hosted site collection.

    Some trouble shooting i did in my case -

    1. I tried to open this site in Mozila Firefox and Google Chrome and found that site is working fine in both. Sharepoint is simply asking for a user name and password and allowing me to access the site. The difference I noticed here is that, When I am trying to access SharePoint in IE and getting credential prompt at that time it is show that connecting to servername.domain.root.loc while logically it should show site url in that window (as it is doing in Mozila and Chrome). By this step I was sure that we are missing something and it is giving issue with Internet Explorer only.
    2. So I visited different blogs, most of them suggest to add the site in trusted sites, or Local Intranet sites. also suggesting to bypass proxy if we are using but in my case we were not using any proxy. I tried all these stuff but no result. Even I tried to enable Internet Explorer for logging in to site with System credentials but it also did not helped me.
    After doing all the above stuff i was again on same page that my site is not opening in IE or also in SharePoint designer.

    Resolution -
    After doing a lot of research work, I was sure that the issue is coming due to some authentication configuration.
    So below are the steps how i solved the issue-
    1. I go to IIS Manager in the wfe servers of SharePoint.
    2. Expend the sites
    3. Selected the Defective site.
    4. Double clicked on Authentication. and click on "Windows Authentication".
    5. Select Provided in the left hand side tool box.
    6. Here you will see two providers "Negotiate" and "NTLM". Here leave NTLM and remove the other one.
    7. Click on "OK" and restart the IIS services.

    Now open your site in IE or SharePoint designer and it should work.

    Sunday, 23 October 2016

    SharePoint Permission Management

    Hi All,
    In today's blog post I will define the permission management in SharePoint. Most of us knows very well about the permissions on Site/Sub sites/List/Library/Items but there is a lot of confusion in permissions managed on a Farm level or from Central Administration level. Here today I am trying to define these permissions.

    Farm level Permissions

    Farm Account
    Farm Account is the user who have installed SharePoint in a environment. Basically this account is supposed to be a Service account (it is expected that password of this service account  will never be changed)
    For Installing SharePoint, user must be in Local Server Administrator group. This user should have 'Securityadmin' and 'DBCreator' permissions on SQL server.
    When SharePoint has been configured this user will automatically get DBOwner access on the databases. That is required for performing any operation in SharePoint using Powershell.

    Farm Administrators
    Farm Administrators have complete access on SharePoint sites/products/feautres same as Farm Account but they can use GUI on for performing their tasks but they can not do any query with database. They can’t do anything with PowerShell.
    If they need to use power shell or access database they have to get DBOwner rights on all SharePoint Database. 
    This access can be granted using 
    Add-SPshelladmin -username domain\user
    To use powershell (Permission will be granted on Config and CA Content DB)
    Add-SPshelladmin –username domain\user -database Databasename
    To use powershell for a particular Web application

    Service Account
    You can use multiple service accounts. The different between a normal account and a service account is that it is expected that the password of service accounts will not be changed in future. Basically these accounts are used for configuring different type of services and service applications in SharePoint.
    These accounts should not be used for accessing SharePoint sites and by any normal users. Only power user should have access to these accounts.


    Web Application Level Permissions

    Anonymous Access
    If you enabled this access, anyone in the network can access your SharePoint site with logging in to it (like you access google without any login).
    This is required to be enabled on Central Administration Level for a particular web application and once enabled Site collection admins can manage its permissions on the site level.

    Permission Policy
    There are four permission policy by default.
    Full Control – Have full access on complete web application
    Full Read - Have full read on complete web application 
    Deny Write – Can’t write or modify anything in complete web application
    Deny All – Can’t access complete web application
    You can define the custom permission of your choice and choose what are the permissions for the user on web app. This policy is defined on the bases of Zones of the web application.

    User Policy
    A Farm admin can define that, what a user can do with in the web application. Any permission policy can be applied for a user that will impact on complete web application.
    These settings can’t be removed by any site collection admin or any user who have full control. If you have selected Deny All for a particular user then that user cannot access any site collection, Site, Subsite, List, Library, Document even if he/she have full control on the site or he/she is a Site collection admin.

    User Permissions
    Farm admin can choose which permissions will be available for the users inside a site collection. If you removed Manage Permissions from this location any user having full control on the site will not be able to change the permissions of the site. Only Site Collection Admin will be able to do this.

    Site Collection Level Permissions
    Site Collection Administrator
    A Site Collection Administrator has full control on the Site Collection and its sub sites.
    But there are two type of Site Collection Administrators
         1. Managed by Central Administration
    ·         Maximum 2 users can have this access. Groups are not allowed.
    ·         When we create a Site collection we have to provide 2 Site collection Administrator (Primary and Secondary). Primary is mandatory.
    ·         Have full access on complete site collection and its sub sites
    ·         Receives Alerts related to issues with Quota Limit and Site Access requests and other issues that are coming due to settings in the site.
    ·         Can’t be managed by Site Settings. Only Farm admins can remove these users.

         2. Managed by the site it self
    ·         Any number of users or groups can have these permissions.
    ·         Managed by Site Settings. Any user having Site collection admin right can remove these users.
    ·         Does not get any alert of any issue in the site.



    Scope of Users and Groups
    ·         SharePoint Group – Site Collection
    ·         Permission Level – Site Collection
    ·         Permissions - Site/Subsite/List/Library/Items
    ·         Users – Active directory
    ·         Domain Group – Active Directory (Domain groups can’t be granted any permission on SharePoint.
    ·         Security Group – Active Directory (Domain groups must be converted to security groups if you need to give permission to AD groups) 




    Friday, 29 July 2016

    SharePoint Architecture

    Today I am defining the normal Architecture of SharePoint -

    Architecture of SharePoint –

    1-Tier: all above layers can only run in one computer. In order to achieve 1-Tier, we need to use the embedded database system, which cannot run in an individual process. Otherwise, there will be at least 2-Tier because non-embedded databases usually can run in an individual computer (tier).   

    2-Tier: Either presentation layer and application layer can only run in one computer, or application layer and data layer can only run in one computer. The whole application cannot run in more than 2 computers. 

    3-Tier: the simplest case of N-Tier architecture; all above three layers are able to run in three separate computers. Practically, these three layers can also be deployed in one computer (3-Tier architecture, but deployed as 1-Tier). 

    N-Tier: 3 or more tiers architecture. Diagram 2 below depicts a typical N-Tier architecture. Some layers in 3-Tier can be broken further into more layers. These broken layers may be able to run in more tiers. For example, application layer can be broken into business layer, persistence layer or more. Presentation layer can be broken into client layer and client presenter layer. In diagram 2, in order to claim a complete N-Tier architecture, client presenter layer, business layer and data layer should be able to run in three separate computers (tiers). Practically, all these layers can also be deployed in one computer (tier). 
    Usage of Different Tier Architectures of SharePoint -

    1-Tier: Normally this architecture is used in development environment.  This is a standalone SharePoint installation that contains all the services, web applications, SQL server, Central Administration in one machine. We can also install a complete farm SharePoint but we will not add any other server in this farm otherwise it will become 2 or more tier architecture.
    2-Tier: Normally this architecture is used in development/preprod environment. There are two machine that are sharing the load from SharePoint. This can be used where we have SQL server installed on different machine. In this mode we can use both standalone installation or farm installation but if we install a farm then we will not add any other server in this farm otherwise it will become 3 or more tier architecture.
     
    3-Tier/N-Tier: This is a complete SharePoint farm installation, where we a have a Database server, Application server and Web Front End (WFE) servers. This architecture is used in Preprod or Prod Environment.

    In a typical 3-tier architecture there is -
     
    One Database server – This server contains the SQL server database, that hosts the SharePoint and its databases. 
    One Application server – Normally this server hosts Central Administration, and SharePoint services and service applications. 
    Two Web Front End servers – This server hosts all web custom applications in the SharePoint farm, most of custom SharePoint features, wsp solutions are installed on these servers only. 


    A WFE can be identified by "Microsoft SharePoint Foundation Web Application" service. This service is not started on a application server.