text: SharePoint 2010 · Mike F. Robbins
  You've followed the instructions in my other three blogs and built a SharePoint 2010 farm (not a stand-alone installation) with one or more web front-end servers. Per one of the notes in a TechNet article I found: "As a best practice, we recommend the operating system on the new server should be at the same service pack level and have the same security updates and other hotfixes as the existing farm servers.
  You're attempting to add an additional web front-end server to your SharePoint 2010 farm and find out the passphrase you've documented is incorrect or it isn't documented. Resetting the passphrase is a fairly simple process. Open PowerShell and execute the following script. Enter the new passphrase when prompted: Add-PSSnapin Microsoft.SharePoint.PowerShell $Passphrase = Read-Host -assecurestring "SP PassPhrase" Set-SPPassPhrase -PassPhrase $Passphrase –Confirm Most other blogs on this subject use the code shown in the image below, but why would you want the password to be shown in clear text when it's typed into the textbox?
  PDF's that have been uploaded to your SharePoint 2010 document libraries do not show the correct icon and only give you the option of saving instead of opening them: The following PowerShell script downloads a 17×17 GIF image from Adobe.com named pdficon_small.gif, places it in the images folder under the 14 hive, associates it in the DOCICON.XML file, sets Browser File Handling to Permissive, and then runs IISReset: $14 = "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14" $src = "https://www.
  Configure the outgoing email settings in a SharePoint 2010 Farm with PowerShell. Launch the PowerShell ISE. Import the SharePoint PowerShell Snap-in, modify the script below using your specific email server settings and then run the script. Add-PSSnapin Microsoft.SharePoint.PowerShell $SMTPSvr = 'mail.mikefrobbins.com' $FromAddr = 'noreply@mikefrobbins.com' $ReplyAddr = 'noreply@mikefrobbins.com' $Charset = 65001 $CAWebApp = Get-SPWebApplication -IncludeCentralAdministration | Where { $_.IsAdministrationWebApplication } $CAWebApp.UpdateMailSettings($SMTPSvr, $FromAddr, $ReplyAddr, $Charset) The outgoing email settings are now configured.
  This blog article will guide you through the process of slipstreaming SP1 into Microsoft SharePoint Foundation 2010. The process for the non-foundation edition is identical with the exception of the file names and the actual service pack file. You've downloaded SharePoint Foundation 2010 and SP1 for that specific version to D:tmp. You've created a folder (D:\sp2010) to house the installation files once they're slipstreamed. Extract the SharePoint installation files into the D:\sp2010 folder::
  This blog is a continuation from last weeks blog (Part 2). We'll jump right in where we left off. Verify you are logged into the server that you want to install SharePoint on as the sp_Name_Install account. Right click the PowerShell ISE and select "Run as administrator": Load the SharePoint PowerShell Snap-in: Add-PSSnapin Microsoft.SharePoint.PowerShell You will receive "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered." This is normal since we have not configured the farm yet.
  This blog is a continuation from last weeks blog (Part 1). We'll jump right in where we left off. Verify you are logged into the server that you want to install SharePoint on as the sp_Name_Install account. Run the SharePoint executable (SharePointFoundation.exe) that you previously downloaded. Select "Install software prerequisites": With SharePoint 2010, there's no need to manually install any of the prerequisites as in previous versions of SharePoint. It installs all of them for you:
  You're ready to introduce SharePoint 2010 into your [SMB])https://en.wikipedia.org/wiki/Small_and_medium_businesses) and you've chosen to install the free with Windows Server version called "Foundation". Details about this version can be found on the SharePoint Foundation 2010 Production Information webpage. You'll need a minimum of two servers, virtual or physical with the specifications listed below to get started. While it is possible to run SharePoint 2010 on a single server, it's definitely not recommended for a production environment.