SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

Blog

Change the Oil – SharePoint Windows O/S

SharePoint runs best with regular health checks and preventative maintenance.   Often we overlook the Windows Server O/S as a key component.   Applications only run as fast as the host operating system.   A well tuned Windows Server O/S gives SharePoint the best opportunity to perform for end users.    Change the oil regularly and users will have the best experience possible.

Cheers! 

shades_smile

 

image
Image result for oil change driveway

 

CLEANMGR.EXE

Native to Windows, this utility is part of the “Desktop Experience” category and can remove Windows Update, Recycle Bin, and temp files which may not be needed.  Convenient and good start point to release storage.

 

Image result for cleanmgr

CCLEANER

Will do all of the above and more by removing temp files specific to certain applications.   Registry keys can also be scanned fro issues and auto repaired to improve lookups.   Windows Start Up, Browser plug-ins, Schedule Tasks, and many other settings give an overall O/S performance boost.   No other utility offers more benefit from one download.

 

Image result for ccleaner

SPCACHECLEANER

The local XML file cache for SharePoint server can become out of sync with Config DB.   Purging this folder occasionally for a new re-population can help all servers in the farm stay in sync.    This procedure also confirms health of the SPTimerV4 service and database connectivity.

 

Image result for spcachecleaner

DEFRAG

Local drive read/writes can slow over time as files become fragmented.   The modern usage with Virtual Machines (VM) and Solid State Drives (SSD) can vary but often a “Quick” defrag or SSD “Optimize” can yield disk I/O performance gains.

 

Image result for defraggler

CHKDSK

When machines suddenly halt (power off, VM failure, etc.) drives and file sectors can become corrupted.  Occasionally running CHKDSK can help scan for any issues to provide assurance there are none and attempt to repair before future disk writes make repair less available.  Running “CHKDSK C: /F’ can help mitigate risk after and ensure a healthy drive.

 

Image result for chkdsk

SYSTEM FILE CHECK

SFC allows admins to scan for and restore corrupt Windows system files.   Similar to the above, this ensure the O/S has current and working files for all needed features.   Recent forced power off or system power halts can corrupt drive data.   Running “SFC / SCANNOW’ can help mitigate risk after and ensure a healthy O/S.

 

Image result for sfc scannow

A/V UPDATE

Current definition and engine binary ensure your system is well protected against common attacks.   Secure systems experience less downtime, data loss, and performance reduced by malware and attacks.   Keep bad users out and provide more resources for good users.

A/V EXCLUSION

SharePoint Server has certain folders with frequent disk I/O (i.e.  search index) where excluding the AV checker can significantly improve performance.   Not scanning these temp files allows the product to quickly move through items, catalog, and index for users.    NOTE – There are subtle differences based on product version (SP 2010/2013/2016) which need to be adjusted to match your farm.

VIDEO – code JS todo CRUD on Breeze & SQL Express (part 2 of 2)

Our next step in this series is cloud hosting.  Each of the local source components has a Microsoft cloud destination equivalent.   Here is the mapping:

  • SQL Express > SQL Azure
  • WebAPI > Azure Web App
  • Angular SPA > Office 365 SharePoint Content Editor

In the video below I walk through all of these steps to migrate the local “todo” CRUD application created earlier to be fully hosted in Microsoft’s cloud.    From there, we have a fully operational business application running on Office 365 with all custom code hosted in Azure.

Enjoy!

shades_smile

 

 

Video

VIDEO – code JS todo CRUD on Breeze & SQL Express (part 2 of 2) from Jeff Jones on Vimeo.

Enable NPM behind corporate proxy

Running “npm install” on an enterprise workstation can often trigger an avalanche of errors.   Running the below commands helps point NPM at the corporate proxy server to resolve the issue. 

Cheers!   

shades_smile

 

 

Commands

npm config set strict-ssl false
npm config set registry "http://registry.npmjs.org"
npm config set proxy=http://proxy.company.com:8080
npm config set https-proxy=http://proxy.company.com:8080

 

Screenshot

image

 

Reference

Feb 2017 CU Download – SharePoint 2016

Quick post with download links for WSS and STS EXE files for SharePoint Server 2016.

 

SPPatchify has also been updated.

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲