Today, I learned about a PowerShell script that is already part of some of the diagnostic tools I use in my day to day work and I just didn't know it was in there. It's freely available online so I wanted to share.
You can go to http://spsfarmreport.codeplex.com/ and download the package to get a full report on your SharePoint farm.
The ReadMe.txt has important information about what will be needed to successfully run the tool. Because I'm using SharePoint 2013 as a base for my Project Server 2013 installation, I used the PowerShell cmdlet Get-ExecutionPolicy to learn the execution policy was already set to Unrestricted on my test farm.
I downloaded the package, then moved the o15 files to a specially created folder on my Project Server 2013 test server called spsfarmreport. The really neat thing about this tool is you can run it on only 1 server in the farm and it will grab results from all of them.
So, I ran .\2013SPSFarmReport.ps1 from a PowerShell command prompt window and this was the output...
PS C:\spsfarmreport> .\2013SPSFarmReport.ps1o15WriteInitialXMLo15farmConfigo15WriteFarmGenSettingso15enumServerso15writeServerso15enumProdVersionso15writeProdVersions2o15enumFeatureso15writeFeatureso15enumSolutionso15writeSolutionso15enumSvcAppso15enumSPSearchServiceAppso15enumSPSearchServiceo15enumHostControllerso15enumSearchActiveTopologieso15enumSearchConfigAdminComponentso15enumSearchConfigLinkStoreso15enumSearchConfigCrawlDatabaseso15enumSearchConfigCrawlRuleso15enumSearchConfigQuerySiteSettingso15enumSearchConfigContentSourceso15writeServiceAppso15enumSPServiceApplicationPoolso15writeSPServiceApplicationPoolso15enumSPServiceApplicationProxieso15writeSPServiceApplicationProxieso15enumSPServiceApplicationProxyGroupso15writeSPServiceApplicationProxyGroupso15enumWebAppso15writeWebAppso15writeAAMsnAPso15enumContentDBso15writeContentDBso15enumCDConfigo15writeCDConfigo15enumHealthReporto15writeHealthReporto15enumTimerJobso15writeTimerJobso15WriteEndXMLPS C:\spsfarmreport>
So where did the output file actually go? It's not in my special spsfarmreport folder.
The readme file has the answer: Run the "[Environment]::CurrentDirectory" command to know where the output XML is written to.
I did this and found my output was being dropped here in the system32 directory.
PS C:\spsfarmreport> [Environment]::CurrentDirectoryC:\windows\system32
I copied these files to my spsfarmreport folder where the SPSFarmReport.xslt is and was able to open the .xml file using IE.
My report is pretty boring because I only have one SharePoint Server in this farm, but you get the idea.
Here's a screenshot of the output I see.
thank you indeed.SPS Farm Report
Thanks - I suppose it's a good idea to change path to the desired location before running the script. :-)
Thank you for commenting, BlueSky2010! You are correct, of course, about setting the path ahead of time. I did want to demonstrate what happened to me the first time I ran the script - I lost the output! Administrators who may be less experienced might
run the spsfarmreport script and be in the same situation, so I feel it is helpful for me to explain the steps I took.
I am full time SharePoint Admin/Consultant and I also use this great script!
@BlueSky2010 - You can set the path in function o15WriteInitialXML . I have set the first part of the path to $PSScriptRoot . This will generate the xml file in the execution directory. Normally I run the script by going to o15 and there also is located the
Thank you for your comment, Ivan!
The Farm Report SharePoint 2013 doesn't work for me
any idea what is wrong? I have SP2013 with CU March 2015
Justin, if you can provide more detail on what happens or doesn't happen, any errors you receive, and possibly a screenshot, I might be able to help.