Office 365 deployment readiness tool download

Note that you have to include addinscan option as part of the command line for the add-in scan to occur. The following is an example of a command line that you can run to scan a user's most recently used Office documents and save the results to a network share for the Finance department.

This only scans for VBA macros. The following is an example of a command line that you can run to scan a folder, and all its subfolders, and save the results to a network share for the Finance department. It's important to note that when you run the Readiness Report Creator from the command line, the Readiness Report Creator doesn't create an Excel file. To create a consolidated Excel report from these various command line scans, you need to run the UI wizard version of the Readiness Report Creator.

For the information source, select "Previous readiness results saved together in a local folder or network share," and then specify the location where you saved all the files for the scans. Keep in mind that the Readiness Report Creator lists each issue with an Office document in a separate row in the Excel worksheet. Alternatively, the SQL export option doesn't have a limit on the number of results that it can accommodate, so this may be a suitable choice if you expect a large number of results.

By default, the Readiness Toolkit will spend 2 minutes scanning a file before timing out and moving on to another file. You can use the -t option from the command line to allow the Readiness Toolkit more than 2 minutes to scan a file. Starting with Version 1. This capability is in response to feedback from many customers who want greater scale and more flexibility when running Readiness Toolkit reports.

You can use either the Readiness Report Creator wizard or the command line. If you're using the Readiness Report Creator, select either Office documents in a local folder or network share or Previous readiness results saved together in a local folder or network share option.

Provide the necessary credentials and the name of the database you want to use. If the database doesn't exist, it will be created. Instead of creating an Excel file, a Power BI report, with the same information, is created for you to review the results.

This Power BI report can be expanded on or changed as desired. It has a file extension of. For example, you can use the following command to create a report from previous readiness results for the Finance department, using a local SQL database named Readiness, and using SQL Server authentication, instead of Windows authentication. You can specify up to four custom labels to categorize and filter data in reports created by the Readiness Toolkit.

You can specify any string for the custom labels. For example, you can filter the report to show only data from the Finance Department or only data from offices in Africa. Assign labels in a consistent manner, such as always using Label 1 for department. You can specify these labels by using the Specify custom labels to use with the Readiness Toolkit Group Policy setting. If you're using the Office Telemetry Dashboard and have already configured tags labels , the Readiness Toolkit automatically collects those labels during its scan of the user's computer and will make them available in its reports.

To protect the privacy of users and to help prevent revealing sensitive information, the Readiness Toolkit allows you to create a report that conceals the file paths and names of documents identified during a scan. You can create a report that conceals this information either by running the Readiness Report Creator from the UI wizard or from the command line. If you're using the UI wizard, begin by selecting either "Most recently used Office documents and installed add-ins on this computer" or "Office documents in a local folder or network share" as the type of report that you want to create.

Then, on the next page of the wizard, select the Conceal file names and paths check box, before continuing on. If you are using the command line to create a report, use the -ConcealNames option, as shown in the following example. When you create a report that conceals the file paths and names of documents, the only characters that remain are the drive letter, the first two characters of the file name, and the file extension.

When the report is created, a file named file-names. This file contains a complete list of the file paths and names that were scanned, without any of the information concealed. The log file also includes a reference code for each file listed. This reference code appears in a column of the report that's created. This allows you to identify the specific file in the report, in case a VBA macro or add-in issue that needs further investigation is identified in the report.

The file-names. If you want to get better insights into which add-ins are used most often within your organization and by whom, you can use the Readiness Toolkit to gather add-in usage information and include it in a readiness report. To collect add-in usage information, install the most current version of the Readiness Toolkit on each computer that you want to capture add-in usage information from.

To enable the agent that generates and collects the add-in usage information, you need to enable the "Allow add-in usage data to be generated and collected by the Readiness Toolkit" Group Policy setting. The data generated and collected includes when the add-in is loaded and used, and if the add-in crashes.

This information is stored in the registry of the computer on which the usage agent runs. We recommend that you allow the usage agent to run for at least 30 days, to ensure you have good coverage of your users and their usage behavior. Once the monitoring period is complete, create a readiness report to collect the information and display it in a report. After you have the information you need, turn off the usage agent by changing the Group Policy setting.

In this release of the Readiness Toolkit, no add-in usage information is collected on computers that are running Office For more information about this, read this Tech Community post.

To identify Office files that contain these controls, you can choose to scan all Office documents when you create a readiness report. This will scan all Office files, even if those files don't contain macros. Because more files are scanned, report creation will take longer. One possible workaround is to scan the local cache of these cloud-based files on the user's computer.

If the files are only stored in a cloud-based location, you can create a mapped network drive to a OneDrive or SharePoint share. Then, you can have Readiness Report Creator scan that drive. But, when this location is scanned, the files must be downloaded in memory to perform the scan. Depending on the number and size of those files, this could result in the scan taking significantly longer and using up a considerable amount of network bandwidth.

We recommend that organizations apply the V3 signature to all macros to eliminate the risk of tampering. You can use the Readiness Toolkit to find existing signed VBA files in your organization that you should upgrade to use the V3 signature. To find these files, run the Readiness Report Creator from an elevated command prompt and use the sigscan option. To view the results in Excel, run the Readiness Toolkit and on the Create a readiness report page, select Previous readiness results saved together in a local folder or network share.

Then, specify the JSON file you created using sigscan at the command line, and finish the steps in the Readiness Toolkit wizard. To use sigscan, you must be using at least version 1. For more information, including how to upgrade those files to use the V3 signature, see Upgrade signed Office VBA macro projects to V3 signature.

The following table lists, by application, the file extensions that are analyzed when the Readiness Report Creator looks for VBA macros in Office documents. The following table lists the types of add-ins that the Readiness Report Creator collects data on.

When you choose to create an advanced report , some information is sent to Microsoft. The following table provides a list of the information that is sent to Microsoft about the VBA macros that are found during a scan, along with examples. The following table provides a list of the information that is sent to Microsoft about the add-ins that are found during a scan, along with examples.

The report created by the Readiness Report Creator uses macros and active content to display the information in the report.

Therefore, to see the VBA macro compatibility and the add-in readiness information in the report, you need to allow macros and active content in Excel.

If macros and active content aren't enabled in Excel, you see a Getting started message on the Overview worksheet when you open the report. On that page are instructions on how to enable macros and active content. This can be as simple as clicking Enable Content in the Message Bar. In some cases, you might not see the Message Bar and the Enable Content choice. This is most likely because Excel is configured to disable all macros without notification.

There, in the Trust Center dialog box, you can change the setting to Disable all macros with notification. After you do that, choose OK to save the change and close the Trust Center dialog box, then choose OK to close the Excel Options dialog box, and then close the report file. When you open the report file again, you should see the Message Bar and the Enable Content choice. If the macro settings choices are grayed out in the Trust Center dialog box, an administrator has configured these settings by using Group Policy and the settings can't be changed manually.

In this case, the simplest solution is to open the report file on a different computer where the macro settings for Excel allow you to enable macros by selecting the Enable Content choice in the Message Bar. For more information about macro setting choices, see Enable or disable macros in Office files. If an add-in is classified as "Unknown" or "Insufficient data" this means that Microsoft doesn't yet have sufficient information regarding the add-in to provide a readiness status.

If this is an add-in that is business critical for your organization, you can do the following:. Contact the software provider who developed this add-in to see if the add-in is supported for Microsoft Apps.

Contact us at ReadyForOffice microsoft. We'll do our best to add the readiness status of the add-in to our database. Please provide as much information about the add-in as possible including, but not limited to, the following:. If there is a problem showing the readiness reports, you will receive a message asking if you want to send an error report to Microsoft. For example, if there is a problem creating a graph in the report or querying the data collected.

By sending an error report to Microsoft, you can help us improve the Readiness Toolkit. The error report sent to Microsoft doesn't contain any personally identifiable information. The following table provides a list of what information is sent to Microsoft in the error report.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note After running the Readiness Toolkit, many enterprises find that they have fewer compatibility issues than first expected.

What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange. All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! Hello all, I am upgrading the Exchange to Office I am looking for this tool and go to below webpage but I do not see any download link in there.

Could you please provide my some hint how to download it? Most Points The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics. Join our community to see this answer! You can run the Readiness Toolkit on client devices across your entire organization. For more information, see Use the Readiness Toolkit to assess application compatibility for Microsoft Apps.

Use the reports to identify the readiness status of your add-ins and get recommendations about how to fix any VBA macro issues that were identified. Working with your business groups, define a pilot group of representative users and client devices from across the organization. Those client devices should include the architectures in your organization bit and bit and all the critical line-of-business applications, add-ins, and macros that you want to test with Microsoft Apps.

If you use the current version of Configuration Manager, you can use the Office ProPlus Pilot and Health Dashboard to help you plan, pilot, and perform your Microsoft Apps deployment. As part of your Office deployment, you'll deploy Office first to the targeted group from step 3, and then do an additional round of testing to ensure compatibility between Microsoft Apps and the add-ins and client devices in that group. After you have verified compatibility, you can deploy to the rest of your organization.

That first group will then continue to be a pilot for testing future updates from Office ahead of the rest of your organization. For more information, see Plan your enterprise deployment of Microsoft Apps.

Before planning your deployment, make sure you've completed all the steps for assessing your environment and requirements. Plan your deployment of Microsoft Apps. Skip to main content. This browser is no longer supported.