Tag Archives: SharePoint 2016

SharePoint Server 2016

new features outgoing email 1920x1080

New features in outgoing email settings SharePoint 2016

New features in outgoing email settings SharePoint 2016

Introduction of New features in outgoing email settings like non-default port can be set in the field “SMTP Server port”. which means SMTP server can use non-default ports.

SharePoint Server 2016 supports sending email to SMTP servers that use STARTTLS connection encryption.STARTTLS is an extension to plain text communication protocols, which offers a way to upgrade a plain text connection to an encrypted (TLS or SSL) connection instead of using a separate port for encrypted communication.

This Outgoing Email Settings supports sending mail to SMTP servers using STARTTLS connection encryption, therefore SMTP can use non-default ports. It does not support unencrypted connections.

The following list shows the SharePoint 2016 requirements that are needed to negotiate connection encryption with an SMTP server:

  • STARTTLS must be enabled on the SMTP server.
  • The SMTP server must support the TLS 1.0, TSL 1.1, or TLS 1.2 protocol.
  • The SMTP server must have a server certificate installed.
  • The server certificate must be valid. Typically, this means that the name of the server certificate must match the name of the SMTP server provided to SharePoint. The server certificate must also be issued by a certificate authority that is trusted by the SharePoint server.
  • SharePoint must be configured to use SMTP connection encryption.
Advertisements
Advertisements

Secure Sockets Layer (SSL) with SMTP Connection Encryption

To configure SharePoint to always use SMTP connection encryption, In SharePoint Central Administration website and under System Settings , Configure outgoing e-mail settings and set the Use Secure Sockets Layer (SSL) drop-down menu to Yes. To configure SharePoint to always use SMTP connection encryption in Windows PowerShell, use the Set-SPWebApplication cmdlet without the -DisableSMTPEncryption parameter.

For example:
$WebApp = Get-SPWebApplication -IncludeCentralAdministration | ? {
$_.IsAdministrationWebApplication -eq $true }
Set-SPWebApplication -Identity $WebApp -SMTPServer smtp.internal.contoso.com -OutgoingEmailAddress sharepoint@domain.com -ReplyToEmailAddress sharepoint@domain.com
Advertisements
Advertisements

Secure Sockets Layer (SSL) with No SMTP Connection Encryption

To configure SharePoint to never use SMTP connection encryption in SharePoint Central Administration, browse to System Settings > Configure outgoing email settings and set the Use Secure Sockets Layer (SSL) drop-down menu to No.

To configure SharePoint to never use SMTP connection encryption in Windows PowerShell, use the Set-SPWebApplication cmdlet with the -DisableSMTPEncryption parameter.

For example:
$WebApp = Get-SPWebApplication -IncludeCentralAdministration | ? {
$_.IsAdministrationWebApplication -eq $true }
Set-SPWebApplication -Identity $WebApp -SMTPServer smtp.internal.contoso.com -DisableSMTPEncryption -OutgoingEmailAddress sharepoint@domain.com -ReplyToEmailAddress sharepoint@domain.com
Advertisements
Improved list view threshold sharepoint 2016

Improved list view threshold sharepoint 2016

Advertisements

Advertisements

Improved list view threshold sharepoint 2016

So as to increase the performance of large lists, new timer job is introduced which can be associated with particular WebApp. In particular list if threshold is increased to more than 2500 list items & auto indexing is enabled for the list then it creates auto index based on List view filter column.

It works as shown in following flow diagram.

Large list column index management Timer Job

This PowerShell script helps to start this timer job.

  • $webapp= Get-WebApplication -Name “Web Application Name”
  • Get-SPTimerJob -WebApplication $webapp -Identity job-list-automatic-index-management
  • Start-SPTimerJob -Identity job-list-automatic-index-management

Enable Auto Indexing for SharePoint List or Library

Auto indexing can be enabled from the list settings or with Powershell as below.

This is the script for enabling the automatic indexing with PowerShell.

  • $web = Get-SPWeb http://webUrl
  • $list = $web.Lists["List Name"]
  • $list.EnableManagedIndexes = $false
  • $list.Update()
  • $list.Fields | Select Title, Indexable
Advertisements

Advertisements

SharePoint search crawl properties storage locations

SharePoint search crawl properties storage locations

Advertisements

Advertisements

SharePoint search crawl properties storage locations

Here we will discuss about SharePoint search crawl properties storage locations. When gathering files from a content source, the SharePoint 2013 Crawl Component can be very I/O intensive process – locally writing all of the files it gathers from content repositories to its to temporary file paths and having them read by the Content Processing Component during document parsing. This post can help you understand where the Crawl Components write temporary files, which can help in planning and performance troubleshooting (e.g. Why does disk performance of my C:\ drive get so bad – or worse, fill up – when I start a large crawl?)

By default, all Search data files will be written within the Installation Path

  • The Data Directory (by default, a sub-directory of the Installation Path) specifies the path for all Search data files including those used by I/O intensive components (Crawl, Analytics, and Index Components)
    • The Data Directory can only be configured at the time of Installation (e.g. it can only be changed if uninstalling/re-installing SharePoint on the given server)
      • From the Installation Wizard, choose the “File Location” tab as seen below
      • IMPORTANT: Before uninstalling SharePoint, first modify your Search topology by removing any Search components from the applicable server. Once SharePoint is re-installed, you can once again deploy the components back to this server.
    • The defined path can be viewed in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Setup\DataDirectory

    • Advanced Note: The Index files (by default, written to the Data Directory) path can be configured separately when provisioning an Index Component via PowerShell using the “RootDirectory” parameter

3175.installAndDataPath
(As a side note: the graphic is only intended to display the default locations specified at install time. It is recommended to change these to a file path other than C:\ drive)

For the Crawl Component:

  • When crawling [gathering] an item, the filter daemon (mssdmn.exe – a child process of the Crawl Component that actually interfaces with an end content repository using a Search Connector/Protocol Handler) will download any applicable file blobs to the SSA’s “TempPath” (e.g. an HTML file, a Word document, a PowerPoint presentation, etc)
    • In the graphic below, this is step 2a
    • The defined path can be viewed either:
      • In the registry (of a Crawl server)

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager\TempPath

      • Or as a property of the SSA:

        $SSA = Get-SPEnterpriseSearchServiceApplication

        $SSA.TempPath

  • When the filter daemon completes the gathering of an item, it is returned to the Gathering Manager (mssearch.exe – responsible for orchestrating a crawl of a given item) and the applicable blob is moved to the “GathererDataPath“, which is a path relative to the DataDirectory mentioned above.
    • In the graphic below, this occurs in step 2b
    • The defined path can be viewed in the registry (of a Crawl server):

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataPath

  • The GathererDataPath is mapped as a network share (used by the Content Processing Components)
    • The shared path can be viewed in the registry (of a Crawl server):

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataShare

8233.crawlFlow
Usage by the Content Processing Components:

  • When the item is fed from the Crawler to the Content Processing Component (step 3 above), the item is only logically submitted to the CPC in a serialized payload of properties that represent that particular item – any related blob would remain on the Crawler and retrieved by a later stage in the processing flow
    • For SharePoint list items, there would typically not be a blob (unless the list item had an attachment)
    • For a document in a SharePoint library, the blob would represent the item’s associated file (such as a Word document)
  • During the Document Parsing stage in the processing flow (e.g. during step 4 above), the item’s blob will be retrieved from the Crawl Component via the GathererDataShare
  • When the Crawl Component receives a callback (success or failure) from the CPC (e.g. in step 6b above after an item has been processed), the temporary blob is then deleted from the GathererDataPath

1373.gathererDataShare
An example path to an item with DocID 933112 would look like the following:

file://crawlSrv/gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0//f8/0xe3cf8_1.aspx   

#0xe3cf8 hex = 933112 decimal

Where:

  • crawlerSrv is a server running a crawl component
  • gthrsvc_-GUID-of-theSearchAdminWebServiceApp--crawl-0 is the name of the crawl component
    • This GUID can be identified using the following PowerShell:

      $SSA = Get-SPEnterpriseSearchServiceApplication

      $searchAdminWeb = Get-SPServiceApplication –Name $SSA.id

      $searchAdminWeb.id

      7ecdbb10-3c86-4298-ab09-04f61aaeb636

  • And the file name is actually re-named to the hex value of the docID
    • For example: 0xe3cf8 hex = 933112 decimal
    • Which we can see in ULS, such as:
      • From the Crawl Component (in this case, running on server “faceman”):

        mssearch.exe     SharePoint Server Search Crawler:Content Plugin      af7zf VerboseEx

        CTSDocument: FeedingDocument: properties : strDocID = ssic://933112 key = path values =\\FACEMAN\gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0\\f8\0xe3cf8.aspx 

      • From the Content Processing Component:

        NodeRunnerContent2-834ebb1f-009    Search    Document Parsing      ai3ef VerboseEx

        AttachDocParser – Parsing: ‘file://faceman/gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0//f8/0xe3cf8.aspx’

Advertisements

Advertisements

16 Hive directories default location SharePoint 2016

16 Hive directories default location SharePoint 2016

16 Hive directories default location SharePoint 2016:

16 Hive directories default location SharePoint 2016 path is as below

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

16 Hive and other important directories location SharePoint2016

16 Hive and other important directories location SharePoint 2016

Folder Structure :

The 16 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.

GAC:- This folder contains Microsoft.SharePoint.Client.Runtime.Portable.Resources.dll and Microsoft.SharePoint.Client.Runtime.Resources.DLL.

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 2016 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 2016 :

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.

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

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

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

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

Advertisements

Advertisements

SharePoint logging change default location of log file 1920x1080

SharePoint logging change default location of log file

Advertisements

Advertisements

SharePoint logging change default location of log file

By default SharePoint logging is stored it’s usage logs in " C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS "

but if a server doesn’t have a large C drive then it is easy to change the location to a larger drive.  Here is how:

  1. Log in to Central Administration.
  2. In the Monitoring section click on Configure usage and health data collection.
  3. Change the path for the logs and the maximum size and then click OK

SharePoint logging

The change takes immediate effect, no services need to be restarted.

Note: the specified location must exist on all servers in the farm

Advertisements

Advertisements

Modify number of backup threads 1920x1080

Modify number of backup threads SharePoint

Advertisements

Advertisements

Modify number of backup threads SharePoint

By default SharePoint is configured to use 3 backup threads.  This can be increased to improve performance and reduce the amount of time taken to backup large farms.  However, the log files can become more difficult to read.

These are the steps required to modify the number of backup threads used by SharePoint:

1. Log in to Central Administration

2. In the Backup and Restore section click Configure Backup Settings

3. Enter a new value for the number of desired threads (between 1-10) and click OK

Modify number of backup threads sharepoint2010

Modify number of backup threads sharepoint2010

Advertisements

Advertisements