This is a comprehensive Environment scanning tool (OEAT) for use in deploying Microsoft Office 2010. This tool (along with documentation) assists a customer in the assessment phase of deployment. It identifies:
- Currently installed applications and installation environment
- Add-ins currently in use by Office clients
- Programs that are not registered as add-ins but still interact with Office programs
- Provides a report on the Environmental assessment (potential upgrade issues)
- Also reports the Add-ins assessment–list of third party programs and information about the compatibility of those programs with Microsoft Office 2010
You can download this Assesment Tool (OEAT) here!!!
When you execute the downloaded exe, it wil show a dialog to extract the files. (Select a folder, where the application has permission to write the files into)
Once extracted, there will be 2 files in the folder (OEAT.exe and Readme). On executing the OEAT.exe, you will see the Assesment Tool,
Use the option 1, if you are running it for an individual machine. Administrators can choose Option 2, to run a Wizard for advanced configuration like passive scan, UNC Path, Hidden execution options. Invoking this button, will first scan your machine and create a XML file report and create it in the same location of the executable. Check a sample xml file below.
Once the scan is complete (either by Option 1 or 2)., you can compile the report. This will compress the collected data, compile them into readable format and gives the output in a excel file. On clicking the button “Compile Results”
You can Review the excel sheet (which is present in the same folder of the OEAT.exe), to analyze the follow different parameters,
- Machine Summary Report
- All Installed Addin
- Installed Addins which were not shipped with Office
- Disk Space
- 32bit vs. 64bit
- Antivirus State
I would also recommend you download and use the Office 2010 Compatibility Inspector to check the Code Compatibility for Office 2010.
The key features of the Office Code Compatibility Inspector include the following:
- It consists of four add-ins that load, one add-in per application, in Excel 2010, PowerPoint 2010, Word 2010, and Visual Studio 2008.
- It runs on a per-user or a per-document basis. For VBA, users open a document and run the tool from the Developer tab. For Visual Studio projects, the developer runs the tool from the Tools menu.
- It adds comments in the code where it finds other potential issues.
- It displays a summary and a detailed report of its findings after it completes its inspection.
About Author: Vijay is a passionate Technology Evangelist & a Photographer at iclickd. He was also a former Microsoft MVP from India. Contact Me.