Do you need to
- Detect if the current site is SharePoint or not?
- Detect the current SharePoint Version?
- Detect the Build Number.
- Detect the latest Cumulative Update that already installed on your farm or other SharePoint farms without having to log in to the site?
- Detect the Current Site Template, language …etc.
- Detect manually the corresponding Cumulative update for a specific patch level.
If you want to detect this information at the push of a button, you have to try the free google extension SharePoint Detector!
SharePoint Detector Features
Detect the SharePoint Version.
SharePoint Detector checks first if the current site is SharePoint or not?
- If the current site is SharePoint site, it detects the SharePoint Version.
- If the current site is not SharePoint Site, it will report that. It also provides you to find the SharePoint Version & Cumulative Update for a specific Build number.
Find the latest Cumulative Update that already installed on the farm
Besides detecting the SharePoint Version, the SharePoint Detector detects the build number and the corresponding build name to can easily find the latest CU that already installed on your farm or other farms.
Manually find the corresponding CU for a specific build number
The SharePoint Detector provides you to manually find the corresponding CU based on the Build Number.
Detect the current SharePoint Site Template
SharePoint Detector is used to detect the current SharePoint Site Template
- Team Site.
- Publishing Site.
- PWA Site.
- Wiki Site ….etc.
Support 2010 – 2013 – 2016 & soon 2019
SharePoint Detector is tested in
- SharePoint 2010.
- SharePoint 2013.
- SharePoint 2016.
- Designed to support 2019.
No need for Administrative Tasks
- No need to login to the site in most cases.
- No need to access Central Admin or to run PowerShell cmdlets to detect the SharePoint version, build number, build Name, Site templet …etc.
Install SharePoint Detector
- Click on SharePoint Detector.
- Click on ‘Add To Chrome’ button.
- Wait a moment until the extension installation is finished.
Keep in mind
In some rare cases, the build number can’t be determined properly because the patch level is not matched the build number. for these cases, I build a bit algorithm to find the nearest patch level for the current build number!
Eg: the corresponding patch level for March 2017 CU SharePoint 2016 is 16.0.4510.1001 but the build number is 16.0.4507.1000 so we detect the nearest number for the patch level to can detect the correct build name.
- SharePoint Server 2016.
- SharePoint Server 2013.
- SharePoint Server 2010.
Please, if you face any issue to use SharePoint Detector or you have any suggestions. Please, don’t hesitate to report this by filling the below form! I fully appreciated your feedback 🙂
Project Center Totalize! Google extension