Monitoring Read/Write Latency


https://sqlperformance.com/2015/03/io-subsystem/monitoring-read-write-latency

Advertisements
Posted in SQL server | Leave a comment

CRM 2011 and SharePoint 2010 / 2013 Integration – Part 1


https://blogs.technet.microsoft.com/anand_nigam/2011/12/03/crm-2011-and-sharepoint-2010-2013-integration-part-1/

https://blogs.technet.microsoft.com/anand_nigam/

Posted in CRM | Leave a comment

SHAREPOINT – Keep your environment running tip-top- Application Pool


SharePoint 2010 IIS Application Pool Recycle???

Do you still need to recycle the application pool/ResetIIS in SharePoint 2010?  Yep. This is actually setup for you by default, out of the box when you create a new web application in central administration.  You can see this for yourself by doing the following:

Create a new web application
Be sure to create a new application pool:
Open IIS Manager
Select Application Pools:
Select the “SharePoint – 200” application pool
Right-click it, select “Advanced Settings”:


In the “recycle” category, notice the “Specific Times” property:

Don’t want it to recycle?  Just remove the TimeSpan value and it will stay up forever, but be forewarned, out of the box memory leaks will eventually exhaust your SharePoint/web server memory!
Click the Ellipsis, click “Remove” for the timespan values
Click “OK”, now your SharePoint Application Pool won’t recycle!

You still need those handy warm up scripts running every 30 minutes to keep your environment running tip-top!

Orgnial Post :http://blogs.architectingconnectedsystems.com/2010/11/22/sharepoint-2010-iis-application-pool-recycle/

 

Posted in SHAREPOINT ADMIN | Leave a comment

INFORMATION ARCHITECTURE DIAGRAM USING POWER SHELL AND VISIO


Posted by ieDaddy or Ref :http://iedaddy.com/2011/11/sharepoint-information-architecture-diagram-using-powershell-and-visio/

Get-SPWebApplication http://sharepoint| Get-SPSite -Limit All | Get-SPWeb -Limit All | Select Title, URL, ID, ParentWebID, AssociatedOwnerGroup, @{Name=’SiteAdministrators’;Expression={[string]::join(“;”, ($_.SiteAdministrators))}} | Export-CSV C:\InfoArch.csv -NoTypeInformation

 

As SharePoint consultants, we don’t always have the luxury of building our farms and the site structures from the ground up.  Sometimes we walk into a situation where the farm and sites have already been up for several years.  However, having a well-planned Information Architecture is critical for any successful SharePoint implementation.  As SharePoint gains in popularity and use, sites are created as one-offs, and after a while our environments start to run wild.  Sites are created without our knowledge or placed as sub-sites of other sites where they don’t really belong.  The power of SharePoint to make web technology accessible to the average information worker is also one of the biggest elephants in the room when it comes to proper and successful implementations.

At some point, whether you are designing the information architecture for the first time or you are going through a regular audit and review of your site structures, you’ll need to get the big picture.  What sites are where?  How do you start the conversation with management that site sprawl is affecting the usability of the system?  When dealing with management, the one thing I’ve learned is that they don’t want to see code or lengthy documents.  If you can’t get your point across in 2 minutes they’ll tune out.  So you have to start the conversation with a visual tool.  A graphical representation of the sites and subsites in a web application would be the perfect tool to give the 50,000 foot view of your sites.  Unfortunately we don’t get that out of the box with SharePoint.  However, this sort of diagram is easy to create with a little bit of PowerShell know how and some Visio diagramming wizards.

We’re looking to create a Visio diagram that makes it easy to visualize site and subsite structures.  The diagram should have relevant and important data about each site.  The layout should show how wide or deep our web application goes and allow us to find the sites that are buried deep inside out information architecture that should be brought up closer to the root.  If our information architecture is too wide we should be able to identify sites that can be pruned or moved under other sites in order to properly categorize them and make them more visible to the end user.

GATHER SHAREPOINT DATA WITH POWERSHELL

Nobody would want to create this diagram by hand.  First off, imagine how long it would take if you had hundreds of sites.  Second, unless you have extremely tight governance controls already in place, the document would be outdated even before it was finished.The fist step is that we need to create a method of extracting the site hierarchy from the SharePoint farm that is easy and repeatable.  This is where PowerShell is a huge help for us.

  1. Remote to one of your SharePoint farm servers and open PowerShell
  2. Run the following PS command:

Get-SPWebApplication http://sharepoint| Get-SPSite -Limit All | Get-SPWeb -Limit All | Select Title, URL, ID, ParentWebID | Export-CSV C:\InfoArch.csv -NoTypeInformation
And what we get now is a nice set of records showing the following properties for each SPweb:

We could also choose to select additional properties of the SPWeb, it really depends on what other information you want to have available to you in the final Visio diagram.

CONVERT THE CSV IN EXCEL

Once we’ve created the CSV file with the elements we need for our Visio diagram, we need to go in and tweak a few things so that the final product formats correctly and shows a nice high level architecture.  In this case, we may find that there will be certain site collections with a ParentWebID GUID of “00000000-0000-0000-0000-000000000000″.  For our purposes, only the actual root of the web application should have this.  All the other site collections should be linked to the root by replacing their ParentWebID with the ID from the root site collection.  In order to do this:

  1. Open the CSV file in Excel (Note: You’ll probably copy the CSV to your desktop, because MS Office should not be running on a SharePoint server)

image

  1. To link all of the Site Collections to the root Site Collection, replace all ParentWebID’s that are “00000000-0000-0000-0000-000000000000″ (minus the Root’s) with the ID from the root Site Collection. So, in our example, all of the sites after the first record with a ParentWebID of “00000000-0000-0000-0000-000000000000″ would be replaced by the ID of the Root Site Collection “5b8bbd9b-1cb4-4c8f-a624-b464d08cd32c″ (except as noted where the first record is concerned).

image

  1. Now that we have our data structured properly, save the file as XLSX so Visio can properly consume it as a data source.

image

USE VISIO TO CREATE THE INFORMATION ARCHITECTURE DIAGRAM

  1. Launch Visio 2010, and under the New selection, under the template categories you’ll want Business.  Select the Organization Chart Wizard

Visio 2010

Visio 2013 (Updated)

clip_image005 image

 

  1. The wizard will start, choose ”Information that’s already stored in a file or database” and click Next

image

(I would update to show Visio 2013, but hey, they are the same dialog boxes!)

  1. Choose “A text, Org Plus (*.txt) or Excel file, click Next.

image

  1. Browse to where you saved the XLSX file and click Next.

image

  1. Here is where the magic happens, instead of using the Employee/Manager relationships, we use ID for the Name, and ParentWebId for the Reports To fields.

image

  1. This screen will be different, depending on what properties of the SPWeb you selected in your PowerShell script.  To keep it simple, I’ll just use the Title so that it will be the only label displayed on the diagram.

image

  1. For shape data fields, it generally makes sense to leave all the columns in there.  This allows the Visio drill-down to be able to display all the relevant data about the SPWeb that you selected in your PowerShell scripts.  So for instance, if I had included the site owner property in my properties select, I would be able to click on a website shape and see who the site owner of the web was.

image

EDIT for Visio 2013: Don’t include pictures in my organization chart.

image

  1. Select “I want to specify how much of my organization to display on each page” and click Next

image

  1. For now, just keep the one page with your root Site Collection as the Employee at Top of Page and click Finish.

image

Once the Visio Organizational Chart Wizard completes its processing, you should have a single page diagram with the root Site Collection at the top of the page, and all the various sites and subsites under it (just like an org chart!).  Depending on how big your site is and your own computer processing power, this may take a few minutes to finish, so grab a cup of coffee and congratulate yourself on creating a great visual tool of your Information Architecture.

EXPLORE THE VISIO DIAGRAM OF YOUR SHAREPOINT INFORMATION ARCHITECTURE

Once the process completes, you should have a single page Visio diagram with the Root at the top and Site Collections and subsites connected underneath.

EDIT: Visio 2013 diagram

image

 

Of course, when you select a particular site’s shape data, you can see all the additional information we chose to include from the SPWeb.

imageimage

NOTE: Article edited to update to Visio 2013.

Posted in SHAREPOINT ADMIN | Leave a comment

SharePoint 2010 build level and version numbers


Original post: https://blogs.technet.microsoft.com/sharepointjoe/2011/01/31/sp2010-sharepoint-2010-build-level-and-version-numbers/

SharePoint Foundation Server 2010 

Release Version KB Article Download
RTM 14.0.4762.1000 N/A
June 2010 CU 14.0.5114.5003 N/A
Aug 2010 CU 14.0.5123.5000 2352346 Download
Oct 2010 CU 14.0.5128.5000 2394323 Download
Dec 2010 CU 14.0.5130.5002 2459125 Download
Feb 2011 CU 14.0.5136.5002 2475880 Download
April 2011 CU 14.0.5138.5001 2472804 Download
Service Pack 1 14.0.6029.1000 2460058 Download
June 2011 CU 14.0.6106.5000 2536601
Recalled
June 2011 CU 14.0.6106.5002 2536601 Download
Aug 2011 CU 14.0.6109.5002 2553117 Download
Oct 2011 CU 14.0.6112.5000 2596508 Download
Dec 2011 CU 14.0.6114.5000 2596998 Download
Feb 2012 CU 14.0.6117.5002 2597132 Download
April 2012 CU 14.0.6120.5000 2536601
Recalled
April 2012 CU 14.0.6120.5006 2598321 Download
June 2012 CU 14.0.6123.5002 2598373 Download
Aug 2012 CU 14.0.6126.5000 2687355 Download
Oct 2012 CU 14.0.6129.5000 2687566 Download
Dec 2012 CU 14.0.6131.5001 2596957 Download
Feb 2013 CU 14.0.6134.5000 2760791 Download
Apr 2013 CU 14.0.6137.5000 2794728 Download
June 2013 CU 14.0.7102.5000 2817392
Recalled
June 2013 CU 14.0.7102.5004 2817552 Download
Service Pack 2 * 14.0.7015.1000 2687464 Download
Aug 2013 CU 14.0.7106.5000 2817594
Recalled
Aug 2013 CU 14.0.7106.5000 2825990 Download
Oct 2013 CU 14.0.7110.5000 2825824 Download
Dec 2013 CU 14.0.7113.5000 2849990 Download
Feb 2014 CU 14.0.7116.5000 2863938 Download
Apr 2014 CU 14.0.7121.5000 2878270 Download
June 2014 CU 14.0.7125.5002 2880975 Download
July 2014 CU 14.0.7128.5001 2883026 Download

* All the public updates that were released through May 2013, and all the cumulative updates that were released through April 2013 are included in Service Pack 2.  However, even though the June 2013 Cu was released prior to Service Pack 2, the service pack does NOT contain the fixes included in the June CU.  In order to get the fixes included in June 2013 CU you must install both the June 2013 CU AND Service Pack 2.

SharePoint Server Server 2010

Release Version KB Article Download
RTM 14.0.4762.1000 N/A
June 2010 CU 14.0.5114.5003 N/A
Aug 2010 CU 14.0.5123.5000 2352342 Download
Oct 2010 CU 14.0.5128.5000 2394320 Download
Dec 2010 CU 14.0.5130.5002 2459257 Download
Feb 2011 CU 14.0.5136.5002 2475878 Download
April 2011 CU 14.0.5138.5001 2512800 Download
Service Pack 1 14.0.6029.1000 2460045 Download
June 2011 CU 14.0.6106.5000 2536599
Recalled
June 2011 CU 14.0.6106.5000 2536599 Download
Aug 2011 CU 14.0.6109.5002 2553048 Download
Oct 2011 CU 14.0.6112.5000 2596505 Download
Dec 2011 CU 14.0.6114.5000 2597014 Download
Feb 2012 CU 14.0.6117.5002 2597150 Download
April 2012 CU 14.0.6120.5000 2598151
Recalled
April 2012 CU 14.0.6120.5006 2598151 Download
June 2012 CU 14.0.6123.5002 2598354 Download
Aug 2012 CU 14.0.6126.5000 2687353 Download
Oct 2012 CU 14.0.6129.5000 2687564 Download
Dec 2012 CU 14.0.6131.5001 2596955 Download
Feb 2013 CU 14.0.6134.5000 2767793 Download
Apr 2013 CU 14.0.6137.5000 2775353 Download
June 2013 CU 14.0.7102.5000 2817363
Recalled
June 2013 CU 14.0.7102.5004 2817527 Download
Service Pack 2 * 14.0.7015.1000 2687453 Download
Aug 2013 CU 14.0.7106.5000 2817570
Recalled
Aug 2013 CU 14.0.7106.5000 2825949 Download
Oct 2013 CU 14.0.7110.5000 2825786 Download
Dec 2013 CU 14.0.7113.5000 2849971 Download
Feb 2014 CU 14.0.7116.5000 2863913 Download
Apr 2014 CU 14.0.7121.5004 2878250 Download
June 2014 CU 14.0.7125.5002 2880972 Download
July 2014 CU 14.0.7128.5001 2883005 Download

All the public updates that were released through May 2013, and all the cumulative updates that were released through April 2013 are included in Service Pack 2.  However, even though the June 2013 Cu was released prior to Service Pack 2, the service pack does NOT contain the fixes included in the June CU.  In order to get the fixes included in June 2013 CU you must install both the June 2013 CU AND Service Pack 2.

Posted in SHAREPOINT ADMIN | Leave a comment

HOW To – Check Versions of SharePoint 2010/2013/2016


Here Power Shell snippet to verify the installed updates:

#Create empty array of installed SharePoint binaries
$spInstallations = @()

#Get registry keys for all installed applications and updates
$UninstallKey=”SOFTWAREMicrosoftWindowsCurrentVersionUninstall”
$reg=[microsoft.win32.registrykey]::OpenRemoteBaseKey(‘LocalMachine’,$env:COMPUTERNAME)
$regkey=$reg.OpenSubKey($UninstallKey)
$regkey.GetSubKeyNames() | %{
$thiskey=$UninstallKey+””+$_
$thisSubKey=$reg.OpenSubKey($thiskey)
$DisplayName=$thisSubKey.GetValue(“DisplayName”)

#Add any relevant to SharePoint to the array
if ($DisplayName -like ‘*SharePoint*’){
$spInstallations+=$DisplayName}
}

$spInstallations | sort | Get-Unique | %{Write-Host $_ -ForegroundColor Green}

 

Note :Obviously you use this at your own risk and discretion.But i tested in multiple servers and it works.

Ref: https://blogs.technet.microsoft.com/stefan_gossner/2015/04/20/powershell-script-to-display-version-info-for-installed-sharepoint-product-and-language-packs/

Posted in SHAREPOINT ADMIN | Leave a comment

Migrate metadata Sharepoint


Step 1:Export Metadata

 $mmsApplication = Get-SPServiceApplication | ? {$_.TypeName -eq “Managed Metadata Service”}
$mmsProxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq “Managed Metadata Service Connection”}
Export-SPMetadataWebServicePartitionData $mmsApplication.Id -ServiceProxy $mmsProxy -Path “\\server\share\mmsdata.cab”

or

#Export

$mmsApp = “MMS ID”; #this sets the exporting MMS ID

$mmsproxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq “ExportTaxonomyProxyName”};

Export-SPMetadataWebServicePartitionData -Identity $mmsApp -ServiceProxy $mmsproxy -Path \\location\exportfile.bak;

Step 2: Import Metadata

$mmsApplication = Get-SPServiceApplication | ? {$_.TypeName -eq “Managed Metadata Service”}
$mmsProxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq “Managed Metadata Service Connection”}
Import-SPMetadataWebServicePartitionData $mmsApplication.Id -ServiceProxy $mmsProxy -Path “\\server\share\mmsdata.cab” -OverwriteExisting

or

#Import

$mms2 = “MMS ID here” #this sets the importing MMS ID

$mms2proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq “ImportTaxonomyProxyName”};

Import-SPMetadataWebServicePartitionData -Identity $mms2 -ServiceProxy $mms2proxy -path \\location\exportfile.bak -OverwriteExisting;

Posted in SHAREPOINT ADMIN | Leave a comment

Min Role in SharePoint Server 2016


Please read this post by Vignesh.

https://vigneshsharepointthoughts.com/tag/sharepointsharepoint-server-2016/

Posted in Share Point 2016 | Leave a comment

certificate mismatches Setting-There is a problem with this website’s security certificate” Message


IE problem with website security certificate

Fix 1 – Name Mismatches Setting

If you receive a message that says “The security certificate presented by this website was issued for a different website’s address” with your version of security certificate error, it might mean that the certificate has a name mismatch. You might not want to mess with this setting as you want it enabled to prevent security issues, but if you insist, use these steps:

  1. Open Internet Explorer.
  2. Select the options gear, then select “Internet Options“.
  3. Select the “Advanced” tab.
  4. Scroll down to the “Security” section, and uncheck the “Warn about certficate address mismatch” option.
  5. Select “OK“.
  6. Restart the compute
Posted in SHAREPOINT ADMIN | Leave a comment

SharePoint Server CPU is maxed out at 100%


There must be something wrong?

Issue : CPU utilization 100% on SharePoint server

Root cause : This is causing because of the search crawl is running at backend. That’s why Task manager showing that mssearch and mssdmn process are taking maximum CPU utilization.

Resolution : Folders that may have to be excluded from antivirus scanning in SharePoint

Note In the following sections, the placeholder Drive represents the letter of the drive on which you have your SharePoint application installed. Typically, this drive letter is C.
1.  %PROGRAM FILES%\Common Files\Microsoft Shared\web server extensions\12\14\15
2.  %WINNT%\temp
3.  %PROGRAM FILES%\Microsoft Office Server
4.  %WINNT%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
5.  Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\     (the config cache)
6.  %WINNT%\Temp\WebTempDir

SharePoint Server 2016

You may have to configure your antivirus software to exclude the following folders and subfolders from antivirus scanning:

  • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions

    If you do not want to exclude the whole Web Server Extensions folder from antivirus scanning, you can exclude only the following folders:

    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16
    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\Logs
  • Drive:\Program Files\Microsoft Office Servers\16.0\Data\Office Server\Applications
  • Drive:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
  • Drive:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
  • Drive: \Users\ServiceAccount\AppData\Local\Temp\WebTempDir

    Note The WebTempDir folder is a replacement for the FrontPageTempDir folder.

  • Drive:\ProgramData\Microsoft\SharePoint
  • Drive:\Users\account that the search service is running as\AppData\Local\Temp

    Note The search account creates a folder in the Gthrsvc_spsearch4 Temp folder to which it periodically must write.

  • Drive:\WINDOWS\System32\LogFiles
  • Drive:\Windows\Syswow64\LogFiles

    Note If you use a specific account for SharePoint services or application pools identities, you may also have to exclude the following folders:

    • Drive:\Users\ServiceAccount\AppData\Local\Temp
    • Drive:\Users\Default\AppData\Local\Temp

You should also exclude all the virtual directory folders under Drive:\inetpub\wwwroot\wss\VirtualDirectories and all the folders under Drive:\inetpub\temp\IIS Temporary Compressed Files.

SharePoint Server 2013

You may have to configure the antivirus software to exclude the Drive:\Program Files\Microsoft Office Servers folder from antivirus scanning for SharePoint Server 2013. If you do not want to exclude the whole Microsoft Office Servers folder from antivirus scanning, you can exclude only the following folders:

  • Drive:\Program Files\Microsoft Office Servers\15.0\Data

    (This folder is used for the indexing process. If the index files are configured to be located in a different folder, you also have to exclude that location.)

  • Drive:\Program Files\Microsoft Office Servers\15.0\Logs
  • Drive:\Program Files\Microsoft Office Servers\15.0\Bin
  • Drive:\Program Files\Microsoft Office Servers\15.0\Synchronization Service
  • Any location in which you decided to store the disk-based binary large object (BLOB) cache (for example, C:\Blobcache).

Note If you have SharePoint Server 2013, these folders should be excluded in addition to the folders that are listed in the “SharePoint Foundation 2013” section.

SharePoint Foundation 2013

You may have to configure your antivirus software to exclude the following folders and subfolders from antivirus scanning:

  • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions

    If you do not want to exclude the whole Web Server Extensions folder from antivirus scanning, you can exclude only the following two folders:

    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Logs
    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Data\Applications

      Note The Applications folder must be excluded only if the computer is running the SharePoint Foundation Search service. If the folder that contains the index file is located elsewhere, you must also exclude that folder.

  • Drive:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
  • Drive:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
  • Drive: \Users\ServiceAccount\AppData\Local\Temp\WebTempDir

    Note The WebTempDir folder is a replacement for the FrontPageTempDir folder.

  • Drive:\ProgramData\Microsoft\SharePoint
  • Drive:\Users\account that the search service is running as\AppData\Local\Temp

    Note The search account creates a folder in the Gthrsvc_spsearch4 Temp folder to which it periodically has to write.

  • Drive:\WINDOWS\System32\LogFiles
  • Drive:\Windows\Syswow64\LogFiles

    Note If you use a specific account for SharePoint services or application pools identities, you may also have to exclude the following folders:

    • Drive:\Users\ServiceAccount\AppData\Local\Temp
    • Drive:\Users\Default\AppData\Local\Temp

    You should also exclude all the virtual directory folders under Drive:\inetpub\wwwroot\wss\VirtualDirectories\ and all the folders under Drive:\inetpub\temp\IIS Temporary Compressed Files\.

SharePoint Foundation 2010

You may have to configure your antivirus software to exclude the following folders and subfolders from antivirus scanning:

  • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions

    If you do not want to exclude the whole Web Server Extensions folder from antivirus scanning, you can exclude only the following two folders:

    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs
    • Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Data\Applications

      Note The Applications folder must be excluded only if the computer is running the SharePoint Foundation Search service. If the folder that contains the index file is located elsewhere, you must also exclude that folder.

  • Drive:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files
  • Drive:\Windows\Microsoft.NET\Framework64\v2.0.50727\Config
  • Drive: \Users\ServiceAccount\AppData\Local\Temp\WebTempDir

    Note The WebTempDir folder is a replacement for the FrontPageTempDir folder.

  • Drive:\ProgramData\Microsoft\SharePoint
  • Drive:\Users\account that the search service is running as\AppData\Local\Temp

    Note The search account creates a folder in the Gthrsvc_spsearch4 Temp folder to which it periodically has to write.

  • Drive:\WINDOWS\system32\LogFiles
  • Drive:\Windows\Syswow64\LogFiles

    Note If you use a specific account for SharePoint services or application pools identities, you may also have to exclude the following folders:

    • Drive:\Users\ServiceAccount\AppData\Local\Temp
    • Drive:\Users\Default\AppData\Local\Temp

    You should also exclude all the virtual directory folders under Drive:\inetpub\wwwroot\wss\VirtualDirectories\ and all the folders under Drive:\inetpub\temp\IIS Temporary Compressed Files\.

SharePoint Server 2010

You may have to configure your antivirus software to exclude the Drive:\Program Files\Microsoft Office Servers folder from antivirus scanning for SharePoint Server 2010. If you do not want to exclude the whole Microsoft Office Servers folder from antivirus scanning, you can exclude only the following folders:

  • Drive:\Program Files\Microsoft Office Servers\14.0\Data

    (This folder is used for the indexing process. If the Index files are configured to be located in a different folder, you also have to exclude that location.)

  • Drive:\Program Files\Microsoft Office Servers\14.0\Logs
  • Drive:\Program Files\Microsoft Office Servers\14.0\Bin
  • Drive:\Program Files\Microsoft Office Servers\14.0\Synchronization Service
  • Any location in which you decided to store the disk-based binary large object (BLOB) cache (for example, C:\Blobcache)

    For more information about the binary large object cache, go to the following Microsoft website:

Note If you have SharePoint Server 2010, these folders should be excluded in addition to the folders that are listed in the “SharePoint Foundation 2010” section.

Ref : https://support.microsoft.com/en-us/help/952167/certain-folders-may-have-to-be-excluded-from-antivirus-scanning-when-y

Posted in SHAREPOINT ADMIN | Leave a comment