Home
%3CLINGO-SUB%20id%3D%22lingo-sub-323372%22%20slang%3D%22en-US%22%3EImproved%20SharePoint%20Health%20Analyzer%20(with%20December%202017%20PU)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-323372%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Dec%2012%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F70518i2658481AF0C0C996%22%20%2F%3E%20December%202017%20PUs%20for%20SharePoint%202013%2F2016%20have%20been%20released%20today%20and%20bring%20some%20good%20changes%20to%20the%20SharePoint%20Health%20Analyzer.%20I've%20had%20a%20lot%20of%20discussion%20with%20customers%26nbsp%3Babout%26nbsp%3Bhow%20useful%20some%20Health%20Analyzer%26nbsp%3Brules%20really%20are%2C%26nbsp%3Bfor%20that%20reason%26nbsp%3Bthese%20feature%20fixes%20are%20a%20good%20decision%20from%20the%20Product%20Group.%20SharePoint%20Administrators%20often%20ended%20up%20in%20disabling%20rules%2C%20but%20this%20is%20not%20how%26nbsp%3Bthe%20Health%20Analyzer%26nbsp%3Bwas%26nbsp%3Bmeant%20to%20be%20used.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Good%20to%20know%3A%26nbsp%3BDisabled%20Health%20Rules%26nbsp%3Bgenerate%20findings%20in%20%3CA%20href%3D%22https%3A%2F%2Fservices.premier.microsoft.com%2Fassess%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Microsoft%20Premier%20Risk%20Assessments%20%3C%2FA%3E%20.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Some%20might%20think%3A%20%22Why%20did%20it%20take%20so%20long%20to%20get%20these%20particular%20things%20improved%3F%22.%20Unfortunately%20I%20can't%20answer%20this.%20What%20I%20can%20do%20is%20to%20point%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fsharepoint.uservoice.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Uservoice%20Feedback%20System%20for%20SharePoint%20%3C%2FA%3E%20%2C%20that%20everybody%20can%20use%20to%20vote%20for%20certain%20product%20improvement%20suggestions.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-1675149847%22%20id%3D%22toc-hId-1737023589%22%3E%3CSTRONG%3E%20SharePoint%20Health%20Analyzer%20Changes%20%3C%2FSTRONG%3E%3C%2FH2%3E%3CBR%20%2F%3E%20The%20December%20PU%20brings%20about%20a%20dozen%20feature%20fixes%20to%20SharePoint.%20Let's%20have%20a%20look%20at%20the%20changes%20related%20to%20the%20Health%20Analyzer%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Health%20Analyzer%20rule%20improvements%3A%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3COL%3E%3CBR%20%2F%3E%3CLI%3EMicrosoft%20improved%20the%20list%20of%20services%20shown%20for%20the%20health%20rule%20report%20that%20show%20services%20using%20a%20built-in%20service%20account%2C%20so%20the%20services%20are%20more%20easily%20understood.%20The%20health%20rule%20will%20now%20list%20the%20service%E2%80%99s%20display%20name%20instead%20of%20the%20shorter%20service%20name%20if%20a%20display%20name%20is%20available.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EMicrosoft%20improved%20the%20SharePoint%20Health%20Analyzer%20algorithm%20that%20checks%20the%20free%20space%20in%20drives%20to%20better%20handle%20large%20drives.%20The%20algorithm%20will%20now%20report%20a%20warning%20if%20the%20amount%20of%20drive%20space%20is%20less%20than%2010%20GB%2C%20or%20report%20an%20error%20if%20the%20amount%20of%20drive%20space%20is%20less%20than%204%20GB.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EMicrosoft%26nbsp%3Bimproved%20the%20Health%20Analyzer%20rules%20to%20include%20additional%20international%20languages.%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FOL%3E%3CBR%20%2F%3E%20%3CSTRONG%3ERemoval%20of%20Health%20Analyzer%26nbsp%3Brules%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Following%20health%20rules%20are%20removed%20completely%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3EDatabase%20has%20large%20amounts%20of%20unused%20space%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EAlternate%20access%20URLs%20have%20not%20been%20configured%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EPeople%20search%20relevance%20is%20not%20optimized%20when%20the%20Active%20Directory%20has%20errors%20in%20the%20manage%20reporting%20structure%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EOne%20or%20more%20crawl%20databases%20may%20have%20fragmented%20indices%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EValidate%20the%20My%20Site%20Host%20and%20individual%20My%20Sites%20are%20on%20a%20dedicated%20Web%20application%20and%20separate%20URL%20Domain%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20%3CSTRONG%3E%20Renamed%20Health%20Analyzer%20rules%20(SharePoint%202013%20only)%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3E%22Health%20Analyzer%3A%20Databases%20exist%20on%20servers%20running%20SharePoint%20Foundation%22%20is%20renamed%20to%20%22Health%20Analyzer%3A%20Databases%20exist%20on%20servers%20running%20SharePoint%22%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%22Health%20Analyzer%3A%20Some%20health%20analyzer%20rules%20do%20not%20have%20associated%20timer%20jobs%22%20is%20renamed%20to%20%22Health%20Analyzer%3A%20Some%20Health%20Analyzer%20rules%20are%20enabled%20but%20do%20not%20have%20any%20associated%20timer%20Jobs%22%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--877007114%22%20id%3D%22toc-hId--815133372%22%3EHow%20to%20get%20these%20changes%3F%3C%2FH2%3E%3CBR%20%2F%3E%20Download%20and%20apply%20the%20December%202017%20PU%20for%20SharePoint%202013%26nbsp%3B%2F%20SharePoint%202016.%20Make%20sure%20to%20plan%20any%20changes%20or%20updates%26nbsp%3Bto%20your%20farm%20thoroughly*.%20%3CBR%20%2F%3E%20What%20if%20I%20do%20not%20plan%20to%20install%20the%20December%20PU%3F%20Future%20CUs%26nbsp%3Binclude%20these%26nbsp%3Bchanges%20as%20well.%20%3CBR%20%2F%3E%20*%20Expect%20some%20great%20guidance%20about%20how%20to%20plan%20and%20apply%20Updates%20to%20your%20SharePoint%20Farm%20on%20this%20blog%20soon!%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-865803221%22%20id%3D%22toc-hId-927676963%22%3EDecember%202017%20Public%20Update%3A%20Download%20and%20KB%20links%3C%2FH2%3E%3CBR%20%2F%3E%20SharePoint%202016%20-%20December%202017%20Public%20Update%3A%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3Ffamilyid%3D354954af-be90-40fe-bc5d-b910943ee7ad%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Download%20%3C%2FA%3E%20%2F%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4011578%2Fdecember-12-2017-update-sharepoint-enterprise-server-2016-kb4011578%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Information%20(KB)%20%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20SharePoint%202013%20-%20December%202017%20Public%20Update%3A%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3Ffamilyid%3D369ec0f3-db82-417d-a401-195608339191%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Download%20%3C%2FA%3E%20%2F%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4011596%2Fdecember-12-2017-update-for-sharepoint-foundation-2013-kb4011596%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Information%20(KB)%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--1686353740%22%20id%3D%22toc-hId--1624479998%22%3EFinal%20Note%3C%2FH2%3E%3CBR%20%2F%3E%20Please%20share%20your%20thoughts%20%26amp%3B%20experiences%20in%20the%20comments.%20Any%20feedback%20to%20this%20post%20is%20highly%20welcome.%20%3CBR%20%2F%3E%20Thank%20you%20for%20rating%20this%20article%20if%20you%20liked%20it%20or%20it%20was%20helpful%20for%20you.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-323372%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Dec%2012%2C%202017%20December%202017%20PUs%20for%20SharePoint%202013%2F2016%20have%20been%20released%20today%20and%20bring%20some%20good%20changes%20to%20the%20SharePoint%20Health%20Analyzer.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-323372%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehealth%20analyzer%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpdate%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on TECHNET on Dec 12, 2017
December 2017 PUs for SharePoint 2013/2016 have been released today and bring some good changes to the SharePoint Health Analyzer. I've had a lot of discussion with customers about how useful some Health Analyzer rules really are, for that reason these feature fixes are a good decision from the Product Group. SharePoint Administrators often ended up in disabling rules, but this is not how the Health Analyzer was meant to be used.

Good to know: Disabled Health Rules generate findings in Microsoft Premier Risk Assessments .

Some might think: "Why did it take so long to get these particular things improved?". Unfortunately I can't answer this. What I can do is to point to the Uservoice Feedback System for SharePoint , that everybody can use to vote for certain product improvement suggestions.


SharePoint Health Analyzer Changes


The December PU brings about a dozen feature fixes to SharePoint. Let's have a look at the changes related to the Health Analyzer:

Health Analyzer rule improvements:

  1. Microsoft improved the list of services shown for the health rule report that show services using a built-in service account, so the services are more easily understood. The health rule will now list the service’s display name instead of the shorter service name if a display name is available.

  2. Microsoft improved the SharePoint Health Analyzer algorithm that checks the free space in drives to better handle large drives. The algorithm will now report a warning if the amount of drive space is less than 10 GB, or report an error if the amount of drive space is less than 4 GB.

  3. Microsoft improved the Health Analyzer rules to include additional international languages.


Removal of Health Analyzer rules:

Following health rules are removed completely

  • Database has large amounts of unused space

  • Alternate access URLs have not been configured

  • People search relevance is not optimized when the Active Directory has errors in the manage reporting structure

  • One or more crawl databases may have fragmented indices

  • Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL Domain


Renamed Health Analyzer rules (SharePoint 2013 only):

  • "Health Analyzer: Databases exist on servers running SharePoint Foundation" is renamed to "Health Analyzer: Databases exist on servers running SharePoint"

  • "Health Analyzer: Some health analyzer rules do not have associated timer jobs" is renamed to "Health Analyzer: Some Health Analyzer rules are enabled but do not have any associated timer Jobs"



How to get these changes?


Download and apply the December 2017 PU for SharePoint 2013 / SharePoint 2016. Make sure to plan any changes or updates to your farm thoroughly*.
What if I do not plan to install the December PU? Future CUs include these changes as well.
* Expect some great guidance about how to plan and apply Updates to your SharePoint Farm on this blog soon!

December 2017 Public Update: Download and KB links


SharePoint 2016 - December 2017 Public Update: Download / Information (KB)

SharePoint 2013 - December 2017 Public Update: Download / Information (KB)


Final Note


Please share your thoughts & experiences in the comments. Any feedback to this post is highly welcome.
Thank you for rating this article if you liked it or it was helpful for you.