MS20331 Core Solutions of Microsoft SharePoint Server 2013 Training – Day 3

Documents in libraries an elements in lists.

Libraries and Lists.

Child sites.

Site Collection. Defines web path and creates Root Site. Has own DB (could be separate)

Web Application. SQL DB – one per web app.

Path Based and Host Named site collections (russian):

Block file upload by extension (check extensions only) – CA > Manage Web Applications > Select Application > Click “Blocked File Types” on Ribbon

Big files upload settings. CA > Manage Web Applications > Select Application >  General Settings button on the ribbon > Maximum Upload Size (default 250 MB). For list items web.config

Both of aforementioned settings go to web config?

To create test files fsutil can be used:

fsutil file create new <filename> <lenght>

SP cold start issue. Warm up scripts.

Fiddler to test difference with and without warm up scripts

SP can be configured for anonymous access:

1. Enable anonymous access on Web App level. CA > Manage Web Applications > Authentication Providers button on the ribbon (verify in IIS)

SP Site Permissions Management.

1. Site Permissions.

Around 50 individual permissions for certain actions

Permission levels (groups of individual permissions) – Visitors, Participants, Owners etc. New levels can be created.

Permissins can be assigned to AD user account (or other user account) or AD groups or alternatively SP groups can be created (valod on site collection leve;)

Whichever method, or methods, you use to authorize user access to SharePoint objects in your environment, it is independent of the userauthentication mechanism you use because SharePoint 2013 converts all authenticated users into a SharePoint User object (SPUser).

Permissions inheritance/level: Site Collections, Sub Site, Libraries, Elements

Best practice – move on site collection level all content which should be accessible for all

In case you forgot how to create sites/subsites:

Revoke/deny access for particular user – Policy for Web Application

SP cache to alleviate load on SQL, network and SP app servers. Caching removes/minimizes queries to SQL.

If misconfigured caching can lead to perfrormance degradation. Mostly cach is disabled by default.

4 types of cache:

1. Blob cache (stores JS, CSS and pictures on WFE). Each WFE has its own BLOB cache. Cache penalty – 1st query is slower when using cache. If file accessible anonymously it speed things up as there is no neeed to check permissions. BLOB cache optimized for sites anonymous. Extra RAM consumption – extra 800 bytes per file (for index)

BLOB cache configuration: change web.config, BlobCache settings – location, file types, max size in GB

2. Output cache. Requires activation of SP Publishing Feature. Only Publishing pages go into this cache. Being stored in RAM. If disabled constant stream of F5 page refresh request may lead to significant load on SP server. Cache handling: TTL OR Cache being discarded if content changed on site. Each page takes 2x page size + 32 KB in RAM.

You can create cache profiles. E.g. for static content (like final version of article) set TTL, for changing change check.

Create Publishing site and enable SIte Output cache in Site Settings.

3. Object cache. Enabled by default and can not be disabled (navigation, search query box), but has to be configured (you may see warning event about this upon each IIS startup – event ID 7363). Configured after starting “Share Point Publishing Feature”

\n\nOpen a shell

Execute the following commands:\n\n[code language=”powershell”] \n#1\n$wcm = Get-SPWebApplication -Identity http://[webappurl/] \n#2\n$wcm.Properties["portalsuperuseraccount"] = “DOMAINsp_superuser”\n#3\n$wcm.Properties["portalsuperreaderaccount"] = “DOMAINsp_superreader”\n[/code]\n\n

\n\n[code language=”powershell”]\n#Check distibuted cache status on node:\nUse-CacheCluster</div>\nGet-CacheHost\n#Check cache host config:\nGet-CacheHostConfig SERVERNAME 22233</div>\n[/code]\n\n