APP Configuration

Steps:

- Create Forward Lookup Zone- Domain Name and Cnamne in DNS for app domain
- Verify Domain name and ping in netwrok.
-  Enable Microsoft SharePoint Foundation Subscription setting services, App management services
- Navigate to App settings & configure app URL

Refer:
http://www.enjoysharepoint.com/Articles/Details/configure-app-environment-and-create-a-app-in-sharepoint-server-2013-21894.aspx

Office 365 Business Plans

Microsoft Offering -SaaS- Office365 comes up with different subscription associated with each subscription set of features.

Naming few are E1,E3,O365 Proplus, E5 plan deatiled of this subscription can be referred in below link provided.

https://products.office.com/en-in/business/compare-more-office-365-for-business-plans

SharePoint Online Limits

Below SharePoint Online limits apply to all plans:

Items & Files : List-> 30 millions items & Library-> 30 millions files\Folders  Views can have upto 12 lookup columns, file name character should be less than 400 character

Sub-Site:  2 thousand per site collection

File Size: 15 GB per file, 250 MB attachment for list item

Managed Metadata Term Store (database): 200000 terms, 1000 global term sets, 1000 groups

Users: 2 million per site collection

SharePoint groups: A user can belong to 5,000 groups, and each group can have up to 5,000 users. You can have up to 10,000 groups per site collection

Versions: 5,000 major versions and 511 minor versions

Sync: For optimum performance no more than 100,000 files in a single OneDrive or team site library. If you use the previous OneDrive for Business sync client (Groove.exe), the sync limit per library is 5,000 items

SharePoint 2013 H\W & S\W Requirements

Below are the minimum H\W & S\W Requirements for SharePoint 2013 environment along with per-requisites.

Software Requirement
Component	Minimum Version Required
Operating system	64-bit Windows Server 2008 R2 with SP1 64-bit Windows Server 2012 Std or Data Edi
SQL Server	64-bit SQL Server 2008 R2 with SP1 64-bit SQL Server 2012 64-bit SQL Server 2014/SP2013 SP1CU May 14

Hardware Requirement
Processor	64-bit, four cores for small deployments           (fewer than 1,000 users) 64-bit, eight cores for medium deployments (between 1,000 to 10,000 users)
Ram	16 GB for small deployments                               (fewer than 1,000 users) 32 GB for medium deployments                         (between 1,000 to 10,000 users)
HD for Web server and application Server	80 Gb should remain free for system drive. Rest drive and space depends on requirement.
HD Sql Server	Separate Data (mdf file) and log (ldf file) file drive each with minimum 50 gb free in real time.

http://blog.blksthl.com/2012/11/19/hardware-requirements-for-all-sharepoint-2013-components-summarized/

https://docs.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements-0

Pre-requisites

    Web Server (IIS) role

    Application Server role

    Microsoft .NET Framework version 4.5

    SQL Server 2008 R2 SP1 Native Client

    Microsoft WCF Data Services 5.0

    Microsoft Information Protection and Control Client (MSIPC)

    Microsoft Sync Framework Runtime v1.0 SP1 (x64)

    Windows Management Framework 3.0 which includes Windows PowerShell 3.0

   Windows Identity Foundation (WIF) 1.0 and Microsoft Identity Extensions (previously named WIF 1.1)

    Windows Server AppFabric                                            

    Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

Install and Download

http://blogs.technet.com/b/meamcs/archive/2012/12/26/install-and-download-sharepoint-2013-prerequisites-offline-manually.aspx

Note: SP2013 With SP1 is only supported in WS2012 R2
https://support.microsoft.com/en-us/help/2891274/sharepoint-2013-sp1-support-in-windows-server-2012-r2

For SharePoint 2013 Updates
https://docs.microsoft.com/en-us/SharePoint/sharepoint-updates

 

Handling Custom Error Pages

1) Browse to C:\inetpub\custerr\en-US on the Server.

2) Open the folder you want to edit and modify the error pages for 401,403,404 and 500. Bottom section of the page holds the error message. Top section of the page holds the code for portal header.

3) Browse to C:\inetpub\wwwroot\wss\VirtualDirectories\ and open the folder associated to the Sharepoint site you would like to affect.

4) Edit the file web.config and find the keyword customErrors. Replace the complete customErrors code block with:

<customErrors defaultRedirect="404.htm" mode="On">

       <error redirect="401.htm" statusCode="401" />

       <error redirect="403.htm" statusCode="403" />

       <error redirect="404.htm" statusCode="404" />

       <error redirect="500.htm" statusCode="500" />

</customErrors>

5) Now find the keyword <system.webServer>. Inside this block, place the following block code. (If the httpErrors block already exists, replace it completely!)

<httpErrors errorMode="Custom" existingResponse="Auto">

</httpErrors>

6) Save web.config file.

7) Perform the step 4 and 6 in both the virtual directories (internal and external) for the SharePoint site.

8) Run iisreset command if needed

9) Do step 1 to 8 on all the 3 servers (for staging or production environments).

Reference: http://www.ngpixel.com/2010/12/23/sharepoint-2010-custom-error-pages/

Farm Admin Do and dont's

Never delete any site collection without taking a backup

Don’t restore any site collection without checking the database allocated site collection numbers

Restore site collections using Powershell Assigning individual database

Never make any changes to web.config files before keeping a copy of original

Don’t delete a farm solutions using UI, Preferably use the PS commands

Never restart any SP timer service without having latest Image backup in place

Avoid IIS reset during Working hours

Don’t  restart any SP services without going through the reverse stop procedure similar to activating
the service

Never Change user account of FIM service manually, use proper user account change and password change through PowerShell

Additionally never delete and create the user profile service application with same name of the service application created previously. Internal name references clashes could lead to more issues

Never do any registry settings without backup.

Make sure that after registry settings servers are restarted.

How to Add Chart control Web Part if missing, to Web Part Gallery for SharePoint2010 \2013 \0ffice365

Recently I have encountered with issues where i was unable to find chart control web part under Business Data section in web part gallery.Below are the steps to fix the same.

Steps:
Navigate to top level site or root site.

Go to site settings and then Web Part Gallery.
So chart web part is missing


In order to add chart web part to web part gallery
Repeat steps 1 and 2
From top ribbon click new and then locate Chart Web part control as shown in screen below.




Select the check box and click populate container.


After performing above step 6 and 7 ,chart control web part will be available in Miscellanous section in Web Part gallery



Click Ok