Tag Archives: SharePoint2016

Slow SharePoint improve performance without upgrading hardware

what you can do if your SharePoint is sometimes very slow.

E.g.: on the first start of a Site
Sometimes during the day a search query will take about a minute until you get results.....

Just look on that article: http://support.microsoft.com/kb/2625048

it will improve "feeled" performance (site response times) massive, if you're going to implement both solutions.

Disabling CRL Check is just necessary if the SP Server does not have internet connectivity, that means proxy settings must be configured for the server itself

http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx, and your proxy must allow traffic from the server of course.

Advertisements
Advertisements
Advertisements

SharePoint shortcut URL and hidden list

Users and Permissions:
People and Groups: _layouts/people.aspx
Site Collection Admins: _layouts/mngsiteadmin.aspx
Advanced Permissions: _layouts/user.aspx
Master Pages: _Layouts/ChangeSiteMasterPage.aspx
Look and Feel:
Quick Launch settings page: /_layouts/quiklnch.aspx
Title, Desc, and Icon: _layouts/prjsetng.aspx
Navigation: _layouts/AreaNavigationSettings.aspx
Page Layout and Ste Templates: _Layouts/AreaTemplateSettings.aspx
Welcome Page: _Layouts/AreaWelcomePage.aspx
Tree View: _layouts/navoptions.aspx
Top Nav Bar: _layouts/topnav.aspx
Site Theme: _layouts/themeweb.aspx
Reset to Site Definition: _layouts/reghost.aspx
Searchable Columns: _Layouts/NoCrawlSettings.aspx
Site Content Types: _layouts/mngctype.aspx
Galleries
Site Columns: _layouts/mngfield.aspx
Site Templates: _catalogs/wt/Forms/Common.aspx
List Templates: _catalogs/lt/Forms/AllItems.aspx
Filter toolbar for Lists and libraries: ?Filter=1
Web Parts: _catalogs/wp/Forms/AllItems.aspx
Workflows: _layouts/wrkmng.aspx
Workflow history hidden list: /lists/Workflow History
Master Pages and Page Layouts: _catalogs/masterpage/Forms/AllItems.aspx
Regoinal Settings: _layouts/regionalsetng.aspx
Site Administration
Recreate default site sp groups: _layouts/15/permsetup.aspx
recycle bin: _layouts/RecycleBin.aspx
Site Libraries and Lists: _layouts/mcontent.aspx
Site Usage Report: _layouts/usageDetails.aspx
User Alerts: _layouts/sitesubs.aspx
RSS: _layouts/siterss.aspx
Search Visibility: _layouts/srchvis.aspx
Sites and Workspaces: _layouts/mngsubwebs.aspx
Site Features: _layouts/ManageFeatures.aspx
Delete This Site: _layouts/deleteweb.aspx
Site Output Cache: _Layouts/areacachesettings.aspx
Content and Structure: _Layouts/sitemanager.aspx
Content and Structure Logs: _Layouts/SiteManager.aspx?lro=all
Search Settings: _layouts/enhancedSearch.aspx
Site Collection Administration
Search Scopes: _layouts/viewscopes.aspx?mode=site
Search Keywords: _layouts/listkeywords.aspx
Recycle Bin: _layouts/AdminRecycleBin.aspx
Site Collection Features: _layouts/ManageFeatures.aspx?Scope=Site
Site Hierachy: _layouts/vsubwebs.aspx
Site hierarchy page (lists of sub sites): /_layouts/1033/vsubwebs.aspx
Portal Site Connection: _layouts/portal.aspx
Site Collection Audit Settings: _layouts/AuditSettings.aspx
Site Collection Policies: _layouts/Policylist.aspx
Site Collection Cache Profiles: Cache%20Profiles/AllItems.aspx
Site Collection Output Cache: _Layouts/sitecachesettings.aspx
Site Collection Object Cache: _Layouts/objectcachesettings.aspx
Variations: _Layouts/VariationSettings.aspx
Variation Labels: _Layouts/VariationLabels.aspx
Translatable Columns: _Layouts/TranslatableSettings.aspx
Variation Logs: _Layouts/VariationLogs.aspx
Site Settings: _layouts/settings.aspx
Delete user from Site collection (on-premises): /_layouts/15/people.aspx?MembershipGroupId=0

Load document tab initial
?InitialTabId=Ribbon.Document

Delete user from Site collection (on-premises):
/_layouts/15/people.aspx?MembershipGroupId=0

Display list in grid view. ‘True’ is case sensitive:
?ShowInGrid=True

Sandboxed Solution Gallery:
/_catalogs/solutions/Forms/AllItems.aspx

Filter toolbar for Lists and libraries:
?Filter=1

Site usage page:
/_layouts/usage.aspx

View all site content page (Site content):
/_layouts/viewlsts.aspx

Get the version of the SharePoint server (Patch level):
/_vti_pvt/Service.cnf

Web Part Maintenance Page:
?Contents=1

Show Page in Dialog View:
?isdlg=1

Application page for registering SharePoint apps
/_layouts/15/appregnew.aspx

Save Site as a template
/_layouts/savetmpl.aspx

Sign in as a different user
/_layouts/closeConnection.aspx?loginasanotheruser=true

Enable SharePoint designer
/_layouts/SharePointDesignerSettings.aspx

Quick Deploy List
Quick%20Deploy%20Items/AllItems.aspx

Open Page in Edit Mode
?ToolPaneView=2

Taxonomy Hidden List (MMS)
Lists/TaxonomyHiddenList/AllItems.aspx

User Information List:
_catalogs/users
_catalogs/users/simple.aspx

Force displaying the user profile in the site collection:
/_layouts/userdisp.aspx?id={UserID}&Force=True

Site hierarchy page (lists of sub sites)
/_layouts/vsubwebs.aspx
/_layouts/1033/vsubwebs.aspx

Add Web Parts Pane: ?ToolPaneView=2 : Add to the end of the page URL; will only work if the page is already checked out
Create: [area]/_layouts/spscreate.aspx
Create: /_layouts/create.aspx

Create list in a different portal area :

/_layouts/new.aspx?NewPageFilename=YourTemplateName.stp&ListTemplate=100&
ListBaseType=0

When you save a template in a portal area and try to create a new list in a different portal area, the template will not show on the Create page. Use this URL to force it to show.

Documents and Lists: /_layouts/viewlsts.aspx

List Template Gallery: /_catalogs/lt

Manage Audiences: /_layouts/Audience_Main.aspx

Manage Cross Site Groups: /_layouts/mygrps.aspx

Manage List Template Gallery: /_catalogs/lt/Forms/AllItems.aspx

Manage My Alerts: /_layouts/MySubs.aspx

Manage People: /_layouts/people.aspx

Manage Site Collection Administrators: /_layouts/mngsiteadmin.aspx

Manage Site Collection Users:
/_layouts/siteusrs.aspx : To access you must be an admin on the server or a site collection admin for the site.

Manage Site Groups: /_layouts/role.aspx

Manage Site Template Gallery: /_catalogs/wt/Forms/AllItems.aspx

Manage Site Template Gallery: /_catalogs/wt/Forms/Common.aspx

Manage Sites and Workspaces: /_layouts/mngsubwebs.aspx

Manage User Alerts: /_layouts/AlertsAdmin.aspx

Manage User Alerts: /_layouts/SiteSubs.aspx

Manage User Permissions: /_layouts/user.aspx

Manage Web Part Gallery: /_catalogs/wp/Forms/AllItems.aspx

Master Page Gallery: /_catalogs/masterpage : Also includes Page Layouts

Modify Navigation: /_layouts/AreaNavigationSettings.aspx

Recycle Bin: /_layouts/AdminRecycleBin.aspx

Save as site template: /_layouts/savetmpl.aspx

Site Column Gallery: /_layouts/mngfield.aspx

Site Content and Structure Manager: /_layouts/sitemanager.aspx

Site Content Types: /_layouts/mngctype.aspx

Site Settings: /_layouts/settings.aspx

Site Settings: /_layouts/default.aspx

Site Template Gallery: /_catalogs/wt

Site Theme: /_layouts/themeweb.aspx

Site usage details: /_layouts/UsageDetails.aspx

Site Usage Summary: /_layouts/SpUsageWeb.aspx

Site Usage Summary: /_layouts/Usage.aspx

Sites Registry: /SiteDirectory/Lists/Sites/Summary.aspx

Top-level Site Administration: /_layouts/webadmin.aspx

User Information: /_layouts/userinfo.aspx

Web Part Gallery: /_catalogs/wp

Web Part Page Maintenance: ?contents=1 : Add to the end of the page URL

Advertisements
Advertisements

Configure diagnostic logging SharePoint 2016

The SharePoint Server 2016 environment might require configuration of the diagnostic logging settings after initial deployment, after upgrade, and if a change is made to the environment, such as adding or removing a server.

The guidelines in the following list can help you form best practices for the specific environment.

* Change the drive to which the server writes logs:

By default, SharePoint Server 2016 writes diagnostic logs to the same drive and partition on which it was installed. Because diagnostic logging can use a large amount of drive space and compromise drive performance, you should configure SharePoint Server 2016 to write to another drive on which SharePoint Server 2016 is not installed.

You should also consider the connection speed to the drive on which SharePoint Server 2016 writes the logs. If verbose-level logging is configured, the server records a large amount of data. Therefore, a slow connection might result in poor log performance.

* Restrict log disk space usage:

By default, the amount of disk space that diagnostic logging can use is unlimited. Therefore, restrict the disk space that logging uses, especially if you configure logging to write verbose-level events. When the disk reaches the restriction, SharePoint Server 2016 removes the oldest logs before it records new logging data.

* Use the Verbose setting sparingly:

You can configure diagnostic logging to record verbose-level events. This means that SharePoint Server 2016 records every action that it takes. Verbose-level logging can quickly use drive space and affect drive and server performance. You can use verbose-level logging to record more detail when you are making critical changes and then reconfigure logging to record only higher-level events after you make the change.

* Regularly back up logs:

Diagnostic logs contain important data. Therefore, back up the logs regularly to ensure that this data is preserved. When you restrict log drive space usage, or if you keep logs for only a few days, SharePoint Server 2016 automatically deletes log files, starting with the oldest files first, when the threshold is met.

* Enable event log flooding protection:

When you enable this setting, SharePoint Server 2016 detects repeating events in the Windows event log, and suppresses them until conditions return to a typical state.

You can set the level of diagnostic logging for the event log and for the trace log. This limits the types and amount of information that are written to each log.

The following tables define the levels of logging that are available for the event log and trace log.

event-log-levels

trace-log-levels

Configure diagnostic logging by using Central Administration :

  1. In Central Administration, on the home page, click Monitoring.
  2. On the Monitoring page, in the Reporting section, click Configure diagnostic logging.
  3. On the Diagnostic Logging page, in the Event Throttling section, configure event throttling as follows:To configure event throttling for all categories:
    1. Select the All Categories check box.
    2. Select the event log level from the Least critical event to report to the event log list.
    3. Select the trace log level from the Least critical event to report to the trace log list.

    To configure event throttling for one or more categories:

    1. Select the check boxes of the categories that you want.
    2. Select the event log level from the Least critical event to report to the event log list.
    3. Select the trace log level from the Least critical event to report to the trace log list.

    To configure event throttling for one or more subcategories (you can expand one or more categories and select any subcategory):

    1. Click the plus (+) next to the category to expand the category.
    2. Select the check box of the subcategory.
    3. Select the event log level from the Least critical event to report to the event log list.
    4. Select the trace log level from the Least critical event to report to the trace log list.

    To return event throttling for all categories to default settings:

    1. Select the All Categories check box.
    2. Select Reset to default from the Least critical event to report to the event log list.
    3. Select Reset to default from the Least critical event to report to the trace log list.
  4. In the Event Log Flood Protection section, select the Enable Event Log Flood Protection check box.
  5. In the Trace Log section, in the Path box, type the path of the folder to which you want logs to be written.
  6. In the Number of days to store log files box, type the number of days (1-366) that you want logs to be kept. After this time, logs will automatically be deleted.
  7. To restrict the disk space that logs can use, select the Restrict Trace Log disk space usage check box, and then type the number gigabytes (GB) you want to restrict log files to. When logs reach this value, older logs will automatically be deleted.
  8. After you have made the changes that you want on the Diagnostic Logging page, click OK.

Configure diagnostic logging by using Windows PowerShell :

  1. Verify that you have the following memberships:
  • securityadmin fixed server role on the SQL Server instance.
  • db_owner fixed database role on all databases that are to be updated.
  • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint Server 2016 cmdlets.

  1. On the Start menu, click All Programs.
  2. Click SharePoint 2016.
  3. Click SharePoint 2016 Management Shell.
  4. To change the drive to which the server writes logs, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -LogLocation D:\DiagnosticLogs

  1. To restrict log disk space usage, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -LogMaxDiskSpaceUsageEnabled

Or assign the maximum disk space for logs:

Set-SPDiagnosticConfig -LogDiskSpaceUsageGB 500

  1. To view the current logging level, at the Windows PowerShell command prompt, type the following command:

Get-SPLogLevel

  1. To change the logging level, at the Windows PowerShell command prompt, type the following command:

Set-SPLogLevel -TraceSeverity Monitorable

To set all categories back to default levels, at the Windows PowerShell command prompt, type the following command, and then press ENTER:

Clear-SPLogLevel

9. To enable event log flooding protection, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -EventLogFloodProtectionEnabled