Configuring Diagnostic Logging

1. Central Administration

2. PowerShell
The Best practice is reduce the level of logging and then re-enable it to be higher based on the specific
issue.

Configuring Diagnostic logging

We can do this through PowerShell command

To set a log location:

Set-SPDiagnosticConfig -loglocation ‘Directory:\\Folder’

To restrict the log disk space

Set-SPDiagnosticConfig –logDiskSpaceUsageGB 500

To set the log level

Set-SPloglevel -TraceSeverity – Monitorable –EventSeverity –None – Identity

Enable the Event log flood protection

Set-SPDiagnosticconfig –EventlogFloodProtectionEnabled
Using Powershell

Configure Usage Health and Data Collection

Enable usage Data logging

Set-SPUsageService –LoggingEnabled 1

Set the number of days to store page request usage data

Set-SPUsageDefinition –Identity ‘Page Requests’ –DaysRetained 31

Get-SPUsageDefinition

Sharepoint Monitoring Tools

1. Health Analyser
2. Timer jobs
3. Reporting
4. Powershell
5. Event viewer
6. Developer dashboard
 Monitoring Tools:

1. System Center -> It is a third party component, it is a Microsoft one. It can be connected directly
into the SharePoint and then monitor what’s going on.
2. SQL Reporting services-> that can be connected to give us the report we need.
3. Windows Management Instrumentation (WMI) kind of PowerShell to get the information.
As a best practice if you are building a SharePoint environment from scratch (no data, nothing), as soon
as you built it, run this command ,it will identify if there are any issues that you need to have fixed.

Viewing Reports and Logs

Two Types

1. Health Report
2. Usage Report

To View Health Reports

To View Usage Reports

To View Search Usage Reports

 Patching and Updating SharePoint 2019 farm

Understand Software update

1. Public Update

This is an update that contains all previous critical on demand hotfixes to date.

Additionally a public updates contains fixes for issues that meet specific hotfix
acceptance criteria. This criteria may include the availability of a workaround, effect for
specific customer.

2. Patch

This is a compiled executable installer that contains update to one or more products.

Examples of packages are the executable files that you would download to install a
service pack, public updates or hot fixes. Often these packages are known as MSI files.

3. Software update

It is an update of service pack, a feature pack, a critical update, a security update or a

hot fix that is used to improve or fix a software version or a product.

4. Upgrade

This is a process by which you change an environment to use a newer version of the
software. You can upgrade to a minor release such as an update or Patch or to a Major release.

Upgrade to a minor release is called a build to build upgrade whereas upgrade to a major release is
called a version to version upgrade.

SharePoint server 2019 has features that facilitate the end to end software update
experience.

This core features that can help us are - > backward compatibility between an updated
services farm and a non-updated content farm, it means is ,if we have the farm that providing
the shared services as in the service applications and then a farm for content which ever one of
this updated ,it is backward compatible.
Update Deployment phase

Deployment phase is broken into two.

1. Patch phase

a. This involves doing the updates on each SharePoint server in the farm. May
be one or two patches that are required to be run. The Language dependent
update and language independent update depending on what you have.
b. The patch phase has two steps, the Patch deployment steps and the
binaries deployment step.
c. During the patch deployment step new binary files are copied to the server
running SharePoint server 2019. Services that use the files that the patch
must replies are temporarily stopped. Stopping the services reduces the
requirement to restart the server to replace files that are being used.
However in some instances you must restart the server.

2. Build to Build Upgrade Phase

This requires the administrator to run the configuration wizard or PSconfig from
the SharePoint management shell. After you finish the Patch phase you must
complete the update installation by starting the build to build upgrade Phase.
It is task intensive and therefore takes the most amount of time to finish. The
First action of this is to upgrade all the SharePoint processes that are running.
After you upgrade the processes the databases are then crawled and upgraded
After you complete the farm upgrade on one server you must complete the
process on all other servers to maintain compatibility.
Update Deployment Cycle