SharePoint DevOps

https://github.com/SharePoint/PnP-JS-Core/wiki/Developer-Guide

https://github.com/SharePoint/PnP-JS-Core/wiki/Basic--Operations

Before discussing the Integration, we will discuss the architecture of SharePoint at the architecture level. The diagram represents the architecture of SharePoint and split into two halves. The Left-half is administrator world and the right-half is the end-user world. Everything in right half resides in SharePoint content database. Let's continue with some terminologies before goes into deep dive.  Farm A farm is a logical architecture or logical grouping of SharePoint servers that share common resources of SharePoint. It can be a single machine or more than one machine. The farm is differentiated on their tier levels. Might be possible Farm can be 1to N-tier. Installation can either be done at 1 machine to N. Most of the cases in production you have to choose at least 5-tier architecture for application Server, front-end  Server , SQL, AD+DNS, Office Web App Server and Exchange; you can add more than one application server, Front-End etc at any level. Configuration Da

http://www.petenetlive.com/KB/Article/0000730  

Error 1603 is a known Microsoft/environmental issue. This error message is displayed by the Microsoft Windows Installer Engine and is a general error code that indicates a problem occurred during the installation. The following is a non-exhaustive list of known causes for this error. Short file name creation is disabled on the affected machine. An Install Script custom action is prototyped incorrectly. A file is locked and cannot be overwritten. The Microsoft Windows Installer Service is not installed correctly. The Windows Temp folders are full. The setup was corrupted after installation and therefore fails with this error during un-installation. An older version of Install Shield Developer is being used. A general error occurred during the installation. Print and File sharing is not installed or enabled when installing MSDE 2000. For more information please visit -  http://support.microsoft.com/kb/834484/en-us Resolution To resolve this issue, complete the fo

https://www.kapilarya.com/fix-startup-type-options-greyed-out-for-services https://prajwaldesai.com/windows-installer-service-not-accessed/

http://serverfault.com/questions/229651/iis6-virtual-smtp-server-isnt-coming-back-up-automatically-after-a-system-resta

https://sharepointobservations.wordpress.com/2013/07/16/error-you-do-not-have-an-email-address/

Mine was a known bug with SP2013 SP1 and SQL server 2014.You need to install any of the CU after April 2014 to fix this issue After installing latest CU,I was able to start the user profile synchronization service without any issue http://sharepoint.stackexchange.com/questions/190126/sharepoint-user-profile-synchronization-service-not-starting

https://czerwsup.wordpress.com/2014/11/05/allow-log-on-locally-add-new-user-greyed-out-fix-via-domain-controller-policy-settings/

https://sharepointadam.com/2010/07/20/add-backconnectionhostnames-to-the-registry-via-powershell/ https://blog.blksthl.com/2013/05/07/a-quick-guide-to-configuring-the-loopback-check/ https://blogs.technet.microsoft.com/scottstewart/2014/09/15/disableloopbackcheck-when-routing-through-a-load-balancer-powershell-sample-included/

http://www.guidingtech.com/25191/remote-desktop-rdp-vmware/