使用 Microsoft 365 應用程式整備工具組評估應用程式相容性Use the Readiness Toolkit to assess application compatibility for Microsoft 365 Apps
Readiness Toolkit for Office add-ins and VBA 可協助您識別與您用於 Office 的 Microsoft Visual Basic for Applications (VBA) 巨集和增益集的相容性問題。The Readiness Toolkit for Office add-ins and VBA can help you identify compatibility issues with your Microsoft Visual Basic for Applications (VBA) macros and add-ins that you use with Office. Readiness Toolkit 包含 Readiness Report Creator，它會建立 Excel 報表，其中具有 VBA 巨集相容性和增益集整備資訊，可協助貴組織評估其移至 Microsoft 365 應用程式的整備程度。The Readiness Toolkit includes the Readiness Report Creator, which creates an Excel report with VBA macro compatibility and add-in readiness information to help your organization assess its readiness to move to Microsoft 365 Apps.
您可以從 Microsoft 下載中心免費下載整備工具組。我們建議您一律下載及使用最新版本。當您執行報告時，整備工具組會檢查是否您正在使用的最新版本，並會提示您下載最新的版本。在安裝最新版本前，您不必解除安裝舊版的整備工具組。You can download the Readiness Toolkit for free from the Microsoft Download Center. We recommend that you always download and use the most current version. The Readiness Toolkit checks if you're using the most current version when you run a report and will prompt you to download the most current version. You don't have to uninstall the older version of the Readiness Toolkit before installing the most current version.
重要
整備工具組無法修復或修正您的 VBA 巨集中的程式碼。如果您建立進階報告，報告會在可行時提供修復 VBA 巨集程式碼的指引。The Readiness Toolkit doesn't repair or fix the code in your VBA macros. If you create an advanced report, the report does provide guidance, when available, for remediating your VBA macro code.
整備報告建立工具可以掃描 Word、Excel、PowerPoint、Outlook、Access、Project、Visio 及 Publisher 檔案中的 VBA 巨集，即使是 Office 2003 這麼舊的 Office 版本。它也可以掃描與 Office 搭配使用的特定類型增益集。可以識別所有 Office 應用程式的增益集，但是不包括 Web 增益集。如需詳細資訊，請參閱針對 VBA 巨集分析的副檔名和整備報告建立工具會收集其資料的增益集類型。The Readiness Report Creator can scan for VBA macros in Word, Excel, PowerPoint, Outlook, Access, Project, Visio, and Publisher files, for Office versions as far back as Office 2003. It can also scan for certain types of add-ins used with Office. Add-ins for all Office applications are identified, but it doesn't include web add-ins. For more information, see File extensions analyzed for VBA macros and Types of add-ins for which the Readiness Report Creator collects data.
下載項目是 MSI 檔案，您可以用來在使用者的電腦上安裝整備工具組。安裝之後，當您執行整備報告建立工具時，UI 精靈會逐步引導您進行建立整備報告的程序。另外也有可以從命令列執行或透過指令碼來使用的獨立可執行檔。如果您需要以更加自動化的方式收集整個企業中使用者的整備資訊，則獨立可執行檔很有用。如需詳細資訊，請參閱取得企業中多位使用者的整備資訊。The download is an MSI file that you can use to install the Readiness Toolkit on a user's computer. After it's installed, when you run the Readiness Report Creator, a UI wizard steps you through the process of creating a readiness report. There is also a standalone executable that can be run from the command line or used with scripts. This is useful if you need to collect readiness information from users throughout your enterprise in a more automated manner. For more information, see Getting readiness information for multiple users in an enterprise.
下列資訊可協助您使用整備報告建立工具：The following information is provided to help you use the Readiness Report Creator:
建立整備報告，包括需求和限制，選擇作為基礎來建立報告的資訊，以及基本與進階報告之間的差異。Creating a readiness report, including requirements and limitations, choosing the information to base your report on, and the difference between a basic and an advanced report.
整備報告中的資訊，適用於 VBA 巨集和增益集整備。Interpreting the information in the readiness report, for both VBA macros and add-in readiness.
取得企業中多位使用者的整備資訊，並且使用命令列版本的整備報告建立工具來掃描多部電腦。Getting readiness information for multiple users in an enterprise, and using a command-line version of the Readiness Report Creator to scan multiple computers.
使用SQL Server 儲存報告結果並使用 Power BI 分析報告結果，以克服使用 Excel 的一些限制，尤其是對於包含大量資料的報告。Use SQL Server to store report results and use Power BI to analyze report results to overcome some of the limitations of using Excel, especially for reports with large quantities of data.
使用標籤來分類及篩選報告中的資料可協助您分析您的組織的整備程度並且進行決策。Use labels to categorize and filter data in reports to help you analyze and make decisions about your organization's readiness.
管理報表中所收集資料的隱私權可讓您知道如何隱藏檔案路徑和名稱的機密資訊。Manage the privacy of data collected in reports to show you how to conceal sensitive information about file paths and names.
收集並顯示在報告中的增益集使用資訊 可以更了解您的組織中最常使用哪些增益集以及是誰使用這些了增益集。Collect and show add-in usage information in reports to get better insights into which add-ins are used most often within your organization and by whom.
其他資訊，包括整備報告建立工具分析的副檔名、整備報告建立工具會收集其資料的增益集類型，以及當建立進階報告時傳送給 Microsoft 的資訊範例。Additional information, including file extensions that are analyzed by the Readiness Report Creator, the types of add-ins the Readiness Report Creator collects data on, and examples of the information sent to Microsoft when creating an advanced report.
注意
- 許多企業在執行 Readiness Toolkit 後，發現相容性問題比之前的預計要少。以企業版所提供的資料為基礎來執行 Readiness Toolkit ，平均 6% 的掃描檔案有巨集，而這些檔案中的 3.3% 有巨集問題。所以這代表僅有 0.2% 的檔案有巨集相容性問題。在 Office 增益集中，已找到的 75% 被分類為採用或支援。After running the Readiness Toolkit, many enterprises find that they have fewer compatibility issues than first expected. Based on data provided by enterprises running the Readiness Toolkit, on average 6% of scanned files have macros, and of those files, 3.3% have macro issues. So that's only 0.2% files with macro compatibility issues. For Office add-ins, 75% of add-ins found are already categorized as adopted or supported.
- 如果您有關於整備工具組的意見反應或問題，請傳送電子郵件到 ReadyForOffice@microsoft.com 與我們連絡。If you have feedback or questions about the Readiness Toolkit, please email us at ReadyForOffice@microsoft.com.
建立整備報告Creating a readiness report
使用整備工具組的需求和限制Requirements and limitations for using the Readiness Toolkit
在安裝及使用整備工具組之前，您應該注意下列需求：Before installing and using the Readiness Toolkit, you should be aware of the following requirements:
Windows 7 Service Pack 1 (SP1) 或更新版本Windows 7 Service Pack 1 (SP1) or later
Microsoft .NET Framework 4.5.1 或更新版本Microsoft .NET Framework 4.5.1 or later
Excel 2010 或更新版本Excel 2010 or later
Microsoft Access Database Engine 2010 可轉散發套件 (只有在您是使用隨選即用版本的 Access 時才適用)Microsoft Access Database Engine 2010 Redistributable (only if you're using a Click-to-Run version of Access)
注意
我們建議使用 64 位元版本的 Excel，特別是當您預期在整備報告中有超過 400,000 筆結果時。We recommend using the 64-bit version of Excel, especially if you expect more than 400,000 results to appear in the readiness report.
此外，您還應該了解整備報告建立工具的一些限制：Also, there a few limitations about the Readiness Report Creator that you should know about:
整備報告建立工具無法掃描受密碼保護的檔案，如果您嘗試掃描此類檔案，檔案會在報告中顯示為「受密碼保護」。The Readiness Report Creator can't scan password protected files. If you try to scan one of these files, the file shows up as "Password protected" in the report.
預設情況下，整備報告建立者無法掃描儲存在 SharePoint 文件庫、OneDrive 或一些其他類型的雲端儲存位置的檔案。如果您嘗試掃描此類檔案，檔案會在報告中顯示為「雲端式」。如需可能的因應措施，請參閱如何掃描雲端式的檔案。By default, the Readiness Report Creator can't scan files that are saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location. If you try to scan one of these files, the file shows up as "Cloud-based" in the report. For a possible workaround, see How to scan cloud-based files.
整備報告建立工具會在 Excel 工作表的個別資料列中列出 Office 文件的每個問題。因此，整備報告建立工具只能傳回 1,046,575 筆結果。如果您預期會超過這個限制，我們建議您將報告的範圍縮小，例如縮小為特定部門。The Readiness Report Creator lists each issue with an Office document in a separate row in an Excel worksheet. Therefore, the Readiness Report Creator can only return 1,046,575 results. If you expect to exceed these limits, we recommend that you narrow the scope of your report, such as to a specific department.
選擇要用來建立報告的資訊Choosing the information to use to create your report
若要建立整備報告，首先您需要選擇用來建立報告的資訊。下表列出可能的選項和每個選項的說明。它也會指定各個選項會建立哪種類型的整備報告。To create a readiness report, you first need to select what information to use to create the report. The following table lists the possible options and an explanation of each option. It also specifies which type of readiness report is created with each option.
| 選項Option | 說明Explanation | 建立的報告Report created |
|---|---|---|
| 這部電腦上最近使用的 Office 文件和已安裝增益集Most recently used Office documents and installed add-ins on this computer |
整備報告建立工具只會掃描使用者最近使用檔案清單中的 Office 文件。這樣可以讓您將掃描焦點縮小到使用者定期存取的文件上。The Readiness Report Creator only scans Office documents that are in the user's list of most recently used files. This allows you to narrow the focus of the scan to documents that a user accesses on a regular basis. 此外，整備報告建立工具會尋找在整備報告建立工具執行所在的電腦上安裝的任何 Office 增益集。In addition, the Readiness Report Creator looks for any add-ins for Office that are installed on the computer on which the Readiness Report Creator is run. |
VBA 和增益集VBA and Add-in |
| 本機資料夾或網路共用中的 Office 文件。Office documents in a local folder or network share. |
整備報告建立工具會掃描您指定的資料夾或網路共用中的 Office 文件。整備報告建立工具會自動掃描指定位置及該位置中的所有子資料夾。The Readiness Report Creator scans the Office documents in the folder or network share that you specify. The Readiness Report Creator automatically scans the specified location, and all the subfolders in that location. 附註： 使用此選項，整備報告建立工具就不會尋找安裝在整備報告建立工具執行所在電腦上的增益集。Note: With this option, the Readiness Report Creator doesn't look for add-ins installed on the computer on which the Readiness Report Creator is run. |
僅限 VBAVBA only |
| 先前的整備結果會一起儲存在本機資料夾或網路共用。Previous readiness results saved together in a local folder or network share. |
此選項可讓您建立由多部獨立電腦的個別整備結果所組成的彙總報告。This option allows you to create a consolidated report comprised of individual readiness results from multiple standalone computers. 例如，您可能會在「財務」部門的所有電腦上執行整備報告建立工具，將每個掃描的結果儲存至網路共用。然後，您可以使用此選項來建立「財務」部門的彙總報告。For example, you might want to run the Readiness Report Creator on all the computers in the Finance department, saving the results of each scan to a network share. Then, you can use this option to create a consolidated report for the Finance department. 如需詳細資訊，請參閱取得企業中多位使用者的整備資訊。For more information, see Getting readiness information for multiple users in an enterprise. |
僅限 VBA 或 VBA 和增益集，取決於使用哪個整備結果。VBA only, or VBA and Add-in, depending on what readiness results are being used. |
| 來自 Office 遙測儀表板的增益集資料。Add-in data from Office Telemetry Dashboard. |
如果您使用 Office 遙測儀表板評估增益集相容性，您可以使用您收集的資訊來建立整備報告。您只需要將用來存取 Office 遙測儀表板資料庫的適當資訊提供給整備報告建立工具。If you're already using Office Telemetry Dashboard to assess add-in compatibility, you can use that information which you've already collected to create a readiness report. You just need to provide the Readiness Report Creator with the appropriate information to access the database for Office Telemetry Dashboard. 附註： 使用此選項，整備報告建立工具就不會尋找 VBA 巨集。要執行此選項的使用者需要有資料庫上的 GRANT SELECT 存取權。Note: With this option, the Readiness Report Creator doesn't look for VBA macros. GRANT SELECT access on the database is required for the user to run this option. |
僅限增益集Add-in only |
在基本與進階報告之間選擇Choosing between a basic and an advanced report
在您選取要用什麼資訊來建立報告並且指定儲存報告的位置之後，您必須選擇要建立基本報告或進階報告。After you select what information to use to create your report and specify a location to save your report, you need to choose whether to create a basic report or an advanced report.
我們強烈建議您建立進階報告，因為進階報告提供額外的資訊，可以協助您評估您的 VBA 巨集和增益集與 Microsoft 365 應用程式的相容性。We strongly recommend that you create an advanced report because an advanced report provides additional information to help you assess the compatibility of your VBA macros and add-ins with Microsoft 365 Apps. 例如，您會在進階報告中取得下列額外資訊：For example, in an advanced report, you get the following additional information:
針對在您的 VBA 巨集中找到的問題的修復建議 (如果有的話)。Remediation advice, when available, for issues found in your VBA macros. 此資訊會顯示在報告的個別工作表中。This information is shown in a separate worksheet in the report.
增益集的整備狀態。例如，報告可能會顯示軟體提供者有 Microsoft 365 應用程式增益集的支援版本。Readiness status for add-ins. For example, the report might show that the software provider has a supported version of the add-in for Microsoft 365 Apps.
增益集的整備狀態是從以遙測為基礎的計算衍生而來，並且明確支援來自 ISV 的陳述式。The readiness status for add-ins is derived from telemetry-based computations as well as explicit support statements from ISVs.
為了向您提供最新的修復建議和整備狀態，整備報告建立工具會在建立報告時與 Microsoft 連絡。您的 VBA 巨集和增益集的某些相關資訊會傳送給 Microsoft。如需會傳送哪些項目的詳細資訊，請參閱建立進階報告時傳送給 Microsoft 的資訊範例。To provide you with the most up-to-date remediation advice and readiness status, the Readiness Report Creator contacts Microsoft when it creates the report. Some information about your VBA macros and add-ins is sent to Microsoft. For more information about what is sent, see Examples of the information sent to Microsoft when creating an advanced report.
重要： 如果您要建立進階報告，請確保執行整備工具組的電腦有網際網路存取權。Important: If you're creating an advanced report, make sure the computer on which you're running the Readiness Toolkit has access to the internet. 整備工具組會呼叫公開可用的 Web 服務，因此必須在防火牆內將下列 URL 列入白名單：The Readiness Toolkit calls a publicly available web-service, so the following URLs need to be whitelisted in your firewall:
解譯整備報告中的資訊Interpreting the information in the readiness report
整備報告建立工具會以 Excel 檔案格式建立整備報告。報告中可用的整備資訊取決於您的報告是以哪些資訊為基礎，以及您選擇要建立基本或進階報告。The Readiness Report Creator creates a readiness report as an Excel file. The readiness information available in the report depends on what information you based your report on, as well as whether you chose to create a basic or advanced report.
每份報告都是以 [概觀] 頁面開始，該頁面提供結果的高階資訊，以及可用報告的連結 - VBA 或增益集或者兩者。Each report starts with an Overview page, which provides high-level information about the results, and links to the reports available - VBA or Add-in or both.
VBA 整備報告VBA readiness reports
下表提供 VBA 整備報告中顯示的不同索引標籤 (工作表) 的清單。The following table provides a list of the different tabs (worksheets) that are shown in a VBA readiness report.
| 工作表名稱Worksheet name | 內容Contents |
|---|---|
| VBA 概觀VBA Overview |
顯示三個圓形圖以提供掃描結果的高階概觀。Displays three pie charts to provide a high-level overview of the results of the scan. 每個圓形圖顯示不同的資訊：已掃描檔案的狀態、掃描期間找到的唯一巨集的整備狀態，以及已掃描唯一檔案的整備狀態。請參閱本節稍後的表格，以取得有關檔案狀態與這些圓形圖中顯示的整備狀態值的詳細資訊。Each pie charts shows different information: the status of the files scanned, the readiness status for the unique macros found during the scan, and readiness status of the unique files scanned. See the tables later in this section for more information about the file status and readiness status values that appear in these pie charts. 整備工具組會建立 VBA 巨集程式碼的唯一雜湊，以找出在多個檔案中重複使用的巨集。整備工具組會執行類似的操作以找出重複的檔案。整備工具組會執行這個操作，以便為您提供必須評估多少唯一 VBA 巨集和唯一檔案的更實際評估。The Readiness Toolkit creates a unique hash of the VBA macro code to identify macros that are reused in multiple files. The Readiness Toolkit does something similar to identify duplicate files. The Readiness Toolkit does this to provide you with a more realistic assessment of how many unique VBA macros and unique files need to be evaluated. 附註： 如果您打算部署 64 位元版本的 Microsoft 365 應用程式，請確定已勾選 [包含 64 位元整備資料] 核取方塊，並且已重新整理報告。Note: If you plan to deploy the 64-bit version of Microsoft 365 Apps, be sure that the "Include 64-bit readiness data" check box is selected and that you've refreshed the report. |
| VBA 摘要VBA Summary |
提供一些預先定義的樞紐分析表，讓您分析從掃描擷取的資料。Provides some pre-defined PivotTables to allow you to analyze the data captured from the scan. 如果這些樞紐分析表不符合您的特定需求，您可以根據 VBA 結果工作表上的資料自行建立。If these PivotTables don't meet your specific needs, you can create your own based on the data on the VBA Results worksheet. |
| VBA 結果VBA Results |
提供整備報告建立工具掃描的每個檔案的資訊。如果在掃描的檔案中找到多個問題，每個問題都有個別資料列。Provides information on each file scanned by the Readiness Report Creator. If multiple issues are found in a scanned file, there is a separate row for each issue. 請參閱本節結尾「詳細 VBA 資訊」標題底下的表格，以取得每個欄位中顯示資訊的說明。See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column. |
| VBA 修復VBA Remediation |
提供掃描期間找到的 VBA 巨集程式碼的建議變更。Provides proposed changes to VBA macro code found during the scan. 請參閱本節結尾「詳細 VBA 資訊」標題底下的表格，以取得每個欄位中顯示資訊的說明。See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column. |
| VBA 參考VBA References |
列出在程式碼和 VBA 專案中識別的參考。這些參考通常會用於呼叫外部 DLL、連結檔案及 VBA 程式碼所使用的 ODBC 連線。List references identified in code and in the VBA project. These references are generally used to call external DLLs, linked files, and ODBC connections for use by the VBA code. 請參閱本節結尾「詳細 VBA 資訊」標題底下的表格，以取得每個欄位中顯示資訊的說明。See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column. |
檔案狀態： 報告也會依據檔案狀態對掃描的檔案進行分類。下表列出整備報告中顯示的可能檔案狀態，以及檔案狀態的說明。File status: The report also categorizes, by a file status, the files that were scanned. The following table lists the possible file statuses that can appear in a readiness report, and an explanation of the file status.
| 檔案狀態File status | 說明Explanation |
|---|---|
| 沒有 VBANo VBA |
已掃描檔案，找不到任何 VBA 巨集程式碼。The file was scanned and no VBA macro code was found. |
| 具有 VBAHas VBA |
已掃描檔案，找到 VBA 巨集程式碼。The file was scanned and VBA macro code was found. |
| 雲端式Cloud-based |
無法掃描檔案，因為它儲存在 SharePoint 文件庫、OneDrive 或某些其他類型的雲端式儲存位置。The file couldn't be scanned because it is saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location. |
| 受密碼保護Password protected |
檔案受密碼保護，所以它不會針對 VBA 巨集進行掃描。The file is password protected so it couldn't be scanned for VBA macros. |
| 無法存取Inaccessible |
因為某些原因而無法掃描檔案，例如整備報告建立工具沒有足夠權限可以存取檔案、檔案已損毀，或者檔案使用很舊的 Office 檔案格式。The file couldn't be scanned for some reason, such as the Readiness Report Creator had insufficient permission to access the file, the file is corrupted, or the file uses a very old Office file format. |
| 無法存取 - 需要驅動程式Inaccessible - Driver required |
無法掃描檔案，因為在執行掃描的電腦上未安裝必要的 Microsoft Access Database Engine 2010。The file couldn't be scanned because the required Microsoft Access Database Engine 2010 isn't installed on the computer performing the scan. |
| 鎖定Locked |
執行掃描時檔案已鎖定或在使用中。The file was locked or in use when the scan was performed. |
| 錯誤Error |
掃描期間嘗試讀取的 VBA 程式碼串流不是有效格式。有時候開啟然後儲存支援 Office 版本的檔案，可讓整備報告建立工具掃描檔案。The VBA code stream trying to be read during the scan wasn't in a valid format. Sometimes opening, and then saving, the file in a supported Office version will allow the Readiness Report Creator to scan the file. |
嚴重性等級： 報告會依據嚴重性等級對 VBA 巨集中找到的問題進行分類，協助您估計解決所找到的問題需要多少努力。如果找到多個 VBA 巨集的問題，報告會在圓形圖中顯示最高的嚴重性等級。Severity level: The report categorizes, by a severity level, the issues found with the VBA macros to help you estimate how much effort it will take to address the issues found. If multiple issues are found with a VBA macro, the report displays the highest severity level in the pie chart.
下表列出整備報告中顯示的可能嚴重性，以及嚴重性等級的說明。The following table lists the possible severities that can appear in a readiness report, and an explanation of the severity level.
| 嚴重性Severity | 說明Explanation |
|---|---|
| 準備升級Ready to upgrade |
在此檔案中找不到問題，且該檔案與 Microsoft 365 應用程式相容。No issues were found in this file and it's compatible with Microsoft 365 Apps. |
| 程式碼設計認知Code design awareness |
程式碼將會如預期般運作，而且使用者不太會發現任何變更、功能、屬性或方法的運作方式與先前版本不同，或者可能在較新版本中已遭到取代。While the code will function as expected and the user isn't likely to notice any change, the feature, property, or method works differently than previously or might be deprecated in favor of a newer version. |
| 建議的基本驗證Minimal validation recommended |
預期不會出現執行階段或編譯時間錯誤，但 API 功能可能會以某種方式變更。No runtime or compile time errors are expected, but the API functionality may have changed in some way. 建議使用者使用 Microsoft 365 應用程式對檔案執行快速檢查，以確保持續如預期運作。It's recommended that the user runs a spot check on the file with Microsoft 365 Apps to ensure it continues to function as expected. 為了最小化環境問題，建議您在巨集通常執行的電腦上執行快速檢查。To minimize environmental issues, ideally run the spot check on the computer that the macro usually runs. |
| 需要有限修復Limited remediation required |
需要某些程序碼重構。但是會有一個清楚的取代動作，因此預期修正巨集所需的工作會大量減少。Some refactoring of code will be required. But, there is a clear replacement and so the expectation is that the work required to fix the macro is significantly reduced. |
| 需要大量修復Significant remediation required |
需要大量程式碼重構，讓程式碼繼續如舊版 Office 版本一樣運作。例如，API 已遭到取代，但是未提供取代的功能。在此情況下，唯一的可用選項是重新建立功能。Significant code refactoring will be required to enable the code to continue to function as it did in the legacy Office version. For example, an API that has been deprecated, but no replacement function has been provided. In this case, the only option available is to recreate the functionality. |
詳細 VBA 資訊： VBA 整備報告中的 [VBA 結果]、[VBA 修復] 和 [VBA 參考] 索引標籤都包含類似的資訊資料行。下表提供這些資料行的清單，以及這些資料行所包含資訊的說明。Detailed VBA information: The VBA Results, VBA Remediation, and VBA References tabs in the VBA readiness report each contain similar columns of information. The following table provides a list of those columns, along with an explanation of what information is contained those columns.
| 資料行名稱Column name | 說明Explanation | 範例Example |
|---|---|---|
| 指導方針Guideline |
掃描文件時識別的指導方針 (規則)。The guideline (rule) identified when document has been scanned. |
Access 2013 中不再有程式工具列和功能表列。Program Toolbars and Menu Bars will no longer be visible in Access 2013. |
| 嚴重性Severity |
所識別問題的嚴重性。Severity of issue identified. |
需要大量修復Significant remediation required |
| 來源位置Source Location |
已掃描檔案的位置。Location of the file that was scanned. |
D:\我的文件\我的檔案D:\My Documents\My Files\ |
| 來源檔案Source File |
已掃描檔案的名稱。Name of the file that was scanned. |
MyFileName.xlsxMyFileName.xlsx |
| 來源檔案雜湊Source File Hash |
檔案的唯一產生雜湊。Uniquely generated hash for the file. |
36426A0DCFC06F6425E205F107A5CA5836426A0DCFC06F6425E205F107A5CA58 |
| 來源檔案副檔名Source File Extension |
已掃描檔案的副檔名。Extension of the file that was scanned. |
.docm.docm |
| 模組Module |
在其中識別程式碼問題的模組名稱。Name of the module where the code issue was identified. |
mDJSCommandBarsmDJSCommandBars |
| 行號Line # |
在其中識別程式碼問題的行號。Line number where the code issue was identified. |
112112 |
| 類型Type |
已識別的問題類型。Type of issue that has been identified. |
VBAVBA |
| 成員Member |
在其中識別問題的 VBA 模組區段名稱 (亦即功能)。VBA Module section name where the issue was identified (i.e. function). |
CommandBarsCommandBars |
| 陳述式Statement |
在其中識別問題的程式碼區段。The section of the code where the issue was identified. |
Dim ctlName As CommandBarControlDim ctlName As CommandBarControl |
| VBA 雜湊VBA Hash |
VBA 程式碼的唯一產生雜湊。Uniquely generated hash for the VBA code. |
CC-D2-F3-9C-58-48-04-E4-16-5B-B6-44-B3-EB-EB-FECC-D2-F3-9C-58-48-04-E4-16-5B-B6-44-B3-EB-EB-FE |
| 參考Reference |
問題描述和說明內容的連結 (如果有的話)。Link to description of issue and help content (where applicable). |
https://technet.microsoft.com/library/cc178954.aspx |
| FileStatusFileStatus |
已處理的檔案狀態的分類。Classification of the status of the file that was processed. |
受密碼保護Password protected |
| 64 位元64Bit |
指定識別的問題是否為 64 位元特定。Specifies if the issues identified is 64-bit specific. |
是Yes |
| UserHashUserHash |
檔案的使用者。User of the file. |
Katharine CruzKatharine Cruz |
| DeviceNameDeviceName |
在其中執行掃描的電腦名稱。Name of the computer where the scan was performed. |
Laptop01Laptop01 |
| 原始程式碼Original code |
移至 64 位元版本 Office 時，在可能會造成問題的巨集中找到的 VBA 程式碼。VBA code found in the macro which may cause issues when moving to a 64-bit version of Office. |
Private Declare Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPrivate Declare Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As Long |
| 建議變更Proposed changes |
對於巨集中的 VBA 程式碼如何更新才能正確地與 64 位元版本的 Office 搭配運作的建議。1, 2Suggestions on how the VBA code in the macro can be updated to work correctly with a 64-bit version of Office.1, 2 |
Private Declare PtrSafe Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtrPrivate Declare PtrSafe Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtr |
| 標籤1Label1 |
如已設定，則為自訂標籤的值。Value of custom label, if configured. 如需詳細資訊，請參閱使用標籤來分類及篩選報告中的資料。For more information, see Use labels to categorize and filter data in reports. |
北美North America |
| 標籤2Label2 |
如已設定，則為自訂標籤的值。Value of custom label, if configured. 如需詳細資訊，請參閱使用標籤來分類及篩選報告中的資料。For more information, see Use labels to categorize and filter data in reports. |
舊金山San Francisco |
| 標籤3Label3 |
如已設定，則為自訂標籤的值。Value of custom label, if configured. 如需詳細資訊，請參閱使用標籤來分類及篩選報告中的資料。For more information, see Use labels to categorize and filter data in reports. |
財務Finance |
| 標籤4Label4 |
如果已設定，則為自訂標籤的值。如需詳細資訊，請參閱使用標籤來分類及篩選報告中的資料。Value of custom label, if configured. For more information, see Use labels to categorize and filter data in reports. |
控制項Controller |
| 來源檔案參考Source file reference | 進行掃描隱藏檔案名稱的時候，在檔案名稱 .log 檔裡用來識別檔案名稱的唯一值。如需詳細資訊，請參閱 管理報表中所收集的資料穩私權。Unique value used to identify the file name in the file-names.log file when concealing file names when doing a scan. For more information, see Manage the privacy of data collected in reports. | 9FE4E090A33CDA8F4502E7E5672464C8F40E79E353DC98FF8CA84846C7D998229FE4E090A33CDA8F4502E7E5672464C8F40E79E353DC98FF8CA84846C7D99822 |
| RT 版本RT Version | 執行此掃描的電腦上安裝整備工具組版本Version of the Readiness Toolkit installed on the computer running the scan | 1.0.0.01.0.0.0 |
1 如需針對 64 位元版本的 Office 撰寫 VBA 程式碼的詳細資訊，請參閱 64 位元 Visual Basic for Applications 概觀。1 For more information about writing VBA code for 64-bit versions of Office, see 64-Bit Visual Basic for Applications Overview.
2 重要事項： 所有建議變更都是以現狀提供，不含保固或保證。當您更新 VBA 巨集程式碼時，驗證所有變更都如預期般運作相當重要。2 Important: All proposed changes are provided as is, with no warranty or guarantee. It's important to validate that all changes work as expected when you update your VBA macro code.
增益集報告Add-in report
下表提供增益集報告中顯示的不同索引標籤 (工作表) 的清單。The following table provides a list of the different tabs (worksheets) that are shown in an add-in report.
| 工作表名稱Worksheet name | 內容Contents |
|---|---|
| 增益集摘要Add-in Summary |
提供整備報告建立工具找到的增益集的高階概觀。Provides a high-level overview of the add-ins found by the Readiness Report Creator. 工作表頂端的資料是要讓您快速評估有多少增益集與 Microsoft 365 應用程式相容，以及有多少增益集還需要您進行更多研究。The data at the top of the worksheet is intended to give you a quick assessment of how many add-ins will likely be compatible with Microsoft 365 Apps and how many add-ins you'll need to do more research on. |
| 增益集詳細資料Add-in Details |
提供所找到的增益集的相關中繼資料資訊 (例如，發行者和版本編號)、每個增益集的安裝總數，以及 (如果是進階報告) 整備狀態 (例如，「支援的版本可用」)。Provides metadata information about the add-ins found (for example, publisher and version number), the total number of installs of each add-in, and, if an advanced report, the readiness status (for example, "Supported version available"). |
| 依據電腦名稱By computer name |
提供增益集詳細資料工作表上的類似資訊，但是會列出增益集安裝所在的每一部電腦，而不只是增益集的安裝總數。Provides similar information to what's on the Add-in Details worksheet, but lists every computer that the add-in is installed on, instead of just a total number of installs for the add-in. |
您可以調整增益集報告中顯示的資訊，方法是從 [增益集摘要] 索引標籤上的下拉式清單選取選項，然後重新整理報告。例如，您可以調整報告只顯示 Access 和 Excel 增益集的相關資訊。You can adjust what information is shown in the add-in report by selecting choices from the drop-down lists on the Add-in Summary tab, and then refreshing the report. For example, you can adjust the report to only show information about Access and Excel add-ins.
根據預設，不會顯示 Office 隨附的增益集。如果您想要查看這些增益集的資訊，請從下拉式清單選取 [是]，然後重新整理報告。但是，大部分企業不需要擔心 Office 隨附增益集的應用程式相容性。By default, add-ins that are shipped by Office aren't shown. If you want to see information about those add-ins, select "Yes" from the drop-down list and refresh the report. But, most enterprises won't need to worry about application compatibility of add-ins which are shipped with Office.
如果您正在 收集增益集使用狀況資訊 並只想看到使用中的增益集相關資訊，您可以從下拉式清單中選取「是的」並重新整理報表。If you're collecting add-in usage information and only want to see information about add-ins that are being used, you can select "Yes" from the drop-down list and refresh the report.
如果您計劃部署 64 位元版本的 Microsoft 365 應用程式，請務必選取下拉式清單中的 [64 位元]，然後重新整理報告。If you plan to deploy the 64-bit version of Microsoft 365 Apps, be sure to select "64-bit" from the drop-down list and refresh the report. 這提供增益集的 64 位元特定整備資訊。報告的預設選取項目為 32 位元。This provides 64-bit specific readiness information about the add-ins. The default selection for reports is 32-bit.
下表列出您可以在增益集報告中看到的可能整備狀態，以及每個狀態代表什麼的說明。The following table lists the possible readiness statuses that you can see in the add-in report and an explanation of what each status means.
| 整備狀態Readiness status | 說明Explanation |
|---|---|
| 高度採用Highly adopted |
這個增益集在其他組織中廣泛用於 Microsoft 365 應用程式，並已準備好搭配 Microsoft 365 應用程式使用。This add-in is being widely used on Microsoft 365 Apps in other organizations, and is ready for use with Microsoft 365 Apps. 但是軟體提供者未正式在 Microsoft 365 應用程式上支援增益集。But, the software provider doesn't officially support the add-in on Microsoft 365 Apps. |
| 採用Adopted |
這個增益集在其他組織中用於 Microsoft 365 應用程式，但是軟體提供者未正式在 Microsoft 365 應用程式上支援增益集。This add-in is being used on Microsoft 365 Apps in other organizations, but the software provider doesn't officially support the add-in on Microsoft 365 Apps. |
| 採用版本可用Adopted version available |
這個增益集的不同版本在 Microsoft 365 應用程式上是「採用」或「高度採用」。A different version of this add-in is either “Adopted” or “Highly Adopted” on Microsoft 365 Apps. |
| 請連絡軟體提供者Contact software provider |
這個增益集可能會在 Microsoft 365 應用程式中發生問題。This add-in might have issues with Microsoft 365 Apps. 您需要決定這個增益集是否為商務關鍵性，然後與軟體提供者連絡以取得指導方針。You need to decide if this add-in is business critical and then contact the software provider for guidance. |
| 支援的版本可用Supported version available |
軟體提供者現在提供適用於 Microsoft 365 應用程式的此增益集支援版本。A supported version of this add-in for Microsoft 365 Apps is available from the software provider. |
| 未知1,2Unknown1,2 |
這個增益集對於 Microsoft 是未知。例如，它可能是您的內部應用程式開發小組建立的企業營運增益集。This add-in is unknown to Microsoft. For example, it could be a line-of-business add-in that your in-house application development team created. 如果您建立基本報告，所有增益集的整備狀態會列為「未知」。只有當您建立進階報告時，整備報告建立工具才會連絡 Microsoft 以嘗試取得增益集的整備狀態。If you create a basic report, the readiness status for all add-ins is listed as Unknown. It's only when you create an advanced report that the Readiness Report Creator contacts Microsoft to try to get readiness status of add-ins. |
| 資料不足2Insufficient data2 |
Microsoft 已經發現這個增益集，但是未收集足夠資訊以提供此增益集的整備狀態。Microsoft has seen this add-in but not enough information has been collected to provide a readiness status for this add-in. |
1 預設隨附於 Office 的部分增益集目前在增益集整備報告中標示為「未知」。這些增益集實際上是「高度採用」且受到 Microsoft 支援。以下是這些增益集的名稱：增益集的 ActionsPane 結構描述、分析工具箱、分析工具箱 - VBA、日期 (XML)、適用於 Microsoft Office 2016 的交談歷程記錄增益集、歐元工具、即時訊息連絡人 (英文)、度量轉換程式 (Measurement Converter)、Microsoft 執行窗格 3、適用於 Microsoft Office 2016 的 Skype 會議增益集、規劃求解增益集、電話號碼 (XML) 及時間 (XML)。1 Some of the add-ins that ship by default with Office are currently flagged as Unknown in an add-in readiness report. These add-ins are actually Highly Adopted and are supported by Microsoft. Here are the names of those add-ins: ActionsPane Schema for Add-Ins, Analysis ToolPak, Analysis ToolPak - VBA, Date (XML), Conversation History Add-in for Microsoft Office 2016, Euro Currency Tools, Instant Messaging Contacts (English), Measurement Converter (Measurement Converter), Microsoft Actions Pane 3, Skype Meeting Add-in for Microsoft Office 2016, Solver Add-in, Telephone Number (XML), and Time (XML).
2 如需詳細資訊，請參閱針對分類為「未知」或「資料不足」的增益集所採取的可能步驟。2 For more information, see Possible steps to take for add-ins classified as "Unknown" or "Insufficient data".
詳細增益集資訊： 增益集報告中的 [增益集詳細資料] 和 [依據電腦名稱] 索引標籤都包含類似的資訊資料行。下表提供這些資料行的清單，以及這些資料行所包含資訊的說明。Detailed add-in information: The "Add-in Details" and "By computer name" tabs in the add-in report each contain similar columns of information. The following table provides a list of those columns, along with an explanation of what information is contained in those columns.
| 資料行名稱Column name | 說明Explanation |
|---|---|
| 電腦名稱Machine name |
安裝增益集所在的電腦名稱。The name of the computer on which the add-in is installed. 此資料行只會顯示在 [依據電腦名稱] 索引標籤上。This column only appears on the "By computer name" tab. |
| 增益集名稱Add-in Name |
增益集的名稱。The name of the add-in. |
| 增益集發行者Add-in Publisher |
增益集發行者的名稱。The name of the add-in's publisher. |
| 增益集版本Add-in Version |
增益集的版本。The version of the add-in. |
| 應用程式App |
增益集在其中使用的 Office 應用程式。例如，Word 或 Excel。The Office application that the add-in is used in. For example, Word or Excel. |
| 安裝總計Total Installs |
增益集的安裝總數。The total numbers of installs of the add-in. 此資料行只會顯示在 [增益集詳細資料] 索引標籤上。This column only appears on the "Add-in Details" tab. |
| 整備狀態 (32 位元)Readiness status (32-bit) |
增益集的整備狀態。僅限進階報告。The readiness status for the add-in. Advanced reports only. 請參閱上方表格以取得可能整備狀態的清單。See the table above for a list of possible readiness statuses. 附註：如果您從 [增益集摘要] 索引標籤上的下拉式清單選擇 [64 位元]，此資料行名稱會改為顯示 [(64 位元)]。Note: If you chose "64-bit" from the drop-down list on the "Add-in Summary" tab, this column name displays as "(64-bit)" instead. |
| 註解Remarks |
增益集整備狀態相關的其他資訊 (如果有的話)。僅限進階報告。Additional information, if available, about the readiness status of the add-in. Advanced reports only. |
| 詳細資訊More information |
增益集相關其他整備資訊的連結。僅限進階報告。Link to additional readiness information about the add-in. Advanced reports only. |
| 總裝置安裝Total Device Installs | 增益集安裝所在的裝置數目。Number of devices on which the add-in is installed. 收集增益集使用狀況資訊時才可用。Available when collecting add-in usage information. 如需詳細資訊，請參閱 收集並顯示報告中的增益集使用狀況資訊。For more information, see Collect and show add-in usage information in reports. |
| 使用增益集的裝置總數Total devices add-in used | 從您開始收集增益集使用狀況資訊起已經使用的增益集裝置數目。Number of devices on which the add-in has been used since you started collecting add-in usage information. 收集增益集使用狀況資訊時才可用。Available when collecting add-in usage information. 如需詳細資訊，請參閱 收集並顯示報告中的增益集使用狀況資訊。For more information, see Collect and show add-in usage information in reports. |
| 自從 {日期} 開始使用的增益集Add-in used since {date} | 自從您開始收集增益集使用狀況資訊起，增益集是否已被使用的指示。Indication of whether the add-in has been used since you started collecting add-in usage information. 收集增益集使用狀況資訊時才可用。如需詳細資訊，請參閱 收集並顯示報告中的增益集使用狀況資訊。Available when collecting add-in usage information. For more information, see Collect and show add-in usage information in reports. |
取得企業中多位使用者的整備資訊Getting readiness information for multiple users in an enterprise
在單一使用者的電腦上安裝及執行整備報告建立工具來建立整備報告很容易。但是如果您是在大型組織中，而且需要為整個部門或分公司建立整備報告呢？It's easy enough to install and run the Readiness Report Creator on a single user's computer to create a readiness report. But what if you're in a large organization and need to create readiness reports for an entire department or branch office?
除了 UI 精靈版本的整備報告建立工具以外，還有可以從命令列執行或搭配指令碼使用的獨立可執行檔。它的名稱是 ReadinessReportCreator.exe 且位於整備工具組安裝所在的資料夾中。Along with the UI wizard version of the Readiness Report Creator, there is also a standalone executable that can be run from the command line or used with scripts. It's named ReadinessReportCreator.exe and is located in the folder where the Readiness Toolkit is installed.
如果您讓您的使用者執行 UI 精靈版本的整備報告建立工具，您最終會有個別 Excel 檔案，每個使用者一個檔案。如此一來就會難以從部門或整個辦公室的觀點查看整備程度。您還必須依賴使用者執行整備報告建立工具並且正確遵循指示。If you have your users run the UI wizard version of the Readiness Report Creator, you end up with separate Excel files, one for each user. That makes it difficult to see readiness from a departmental or office-wide perspective. You also have to rely on the users to run the Readiness Report Creator and follow the instructions correctly.
更好的替代方式是使用整備報告建立工具的命令列功能，並且使用指令碼來執行整備報告建立工具以代表使用者收集資訊。您可以將整備報告建立工具建立的檔案儲存到網路共用。如果您這麼做，請確定已將適當的寫入權限授與共用。The better alternative might be to use the command line capabilities of the Readiness Report Creator and use a script to run the Readiness Report Creator to collect the information on behalf of the user. You can save the files created by the Readiness Report Creator to a network share. If you do this, make sure that the appropriate write permissions are given to the share.
注意
如果您使用 Microsoft Endpoint Configuration Manager 或類似企業軟體部署工具來執行整備工具組，請務必部署使用使用者內容 (而非系統內容) 的套件。否則，整備工具組將無法在電腦上的目前使用者的登錄 hive 中讀取最近使用 (MRU) 資訊。If you're running the Readiness Toolkit by using Microsoft Endpoint Configuration Manager, or similar enterprise software deployment tools, be sure to deploy the package using the user context, instead of the system context. Otherwise, the Readiness Toolkit won't be able to read the most recently used (MRU) information in the current user's registry hive on the computer.
您可以藉由開啟命令提示字元、瀏覽到您安裝整備工具組所在的資料夾，然後輸入下列命令，看到可用命令列選項的清單：You can see a list of the available command line options by opening a command prompt, navigating to the folder where you installed the Readiness Toolkit, and then typing the following command:
ReadinessReportCreator.exe -help
命令列版本的整備報告建立工具沒有與 UI 精靈版本相同的所有功能。您可以使用命令列版本來掃描最近使用的 Office 文件和電腦上的已安裝增益集，或者本機資料夾或網路共用中的 Office 文件。The command line version of the Readiness Report Creator doesn't have the all the same capabilities as the UI wizard version. You can use the command line version to scan the most recently used Office documents and installed add-ins on a computer, or Office documents in a local folder or network share.
以下是您可以執行以掃描 VBA 巨集和增益集，並且將結果儲存到「財務」部門網路共用的命令列範例。請注意，您必須在命令列中包含 addinscan 選項，增益集掃描才會發生。The following is an example of a command line that you can run to scan for both VBA macros and add-ins, and save the results to a network share for the Finance department. Note that you have to include addinscan option as part of the command line for the add-in scan to occur.
ReadinessReportCreator.exe -mru -addinscan -output \\server01\finance -silent
以下是您可以執行以掃描使用者最近使用的 Office 文件，並且將結果儲存到「財務」部門網路共用的命令列範例。這個選項只會掃描 VBA 巨集。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.
ReadinessReportCreator.exe -mru -output \\server01\finance -silent
以下是您可以執行以掃描資料夾及其所有子資料夾，並且將結果儲存到「財務」部門網路共用的命令列範例。這個選項只會掃描 VBA 巨集。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. This only scans for VBA macros.
ReadinessReportCreator.exe -p c:\officefiles\ -r -output \\server01\finance -silent
請務必注意，當您從命令列執行整備報告建立工具時，整備報告建立工具不會建立 Excel 檔案。整備報告建立工具會改為建立 JSON 檔案，其中包含來自掃描的 VBA 巨集和增益集資訊。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. Instead the Readiness Report Creator creates JSON files containing VBA macro and add-in information from the scan.
若要從這些不同的命令列掃描建立彙總 Excel 報告，您必須執行 UI 精靈版本的整備報告建立工具。針對資訊來源，請選取 [先前整備結果一起儲存在本機資料夾或網路共用]，然後選取您儲存所有掃描檔案的位置。然後整備報告建立工具會從 JSON 檔案將資訊合併至單一 Excel 檔案中的整備報告。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. The Readiness Report Creator then consolidates the information from the JSON files into a readiness report in a single Excel file.
請注意，整備報告建立者會在 Excel 工作表的個別資料列中列出每個 Office 文件的問題。Keep in mind that the Readiness Report Creator lists each issue with an Office document in a separate row in the Excel worksheet. 因此，整備報告建立者只能傳回 1,046,575 個結果。Therefore, the Readiness Report Creator can only return 1,046,575 results. 如果您希望超過這些限制，建議您縮小報告的範圍，比方說限制在特定部門。If you expect to exceed these limits, we recommend that you narrow the scope of your report, such as to a specific department. 或者，SQL 的匯出選項對於可容納的結果數目沒有限制，如果您希望有大量結果，則這可能是合適的選擇。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.
根據預設，整備 Toolkit 所需掃描檔案逾時而並將移至另一個檔案之前的 2 分鐘。您可以使用-t 選項從命令列來允許整備 Toolkit 超過 2 分鐘来掃描的檔案。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.
使用 SQL Server 來儲存報告結果Use SQL Server to store report results
從版本 1.2.19098 (2019 年 4 月 9 日版本) 開始，您可以將報告資料匯出到任何受支援的 SQL Server 或 SQL Server Express 版本。Starting with Version 1.2.19098 (which was released on April 9, 2019), you can export report data to any supported version of SQL Server or SQL Server Express. 此功能為許多客戶的意見反應的回應結果，這些客戶在執行整備工具組報告時需要更大的規模和更大的彈性。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. 如果您使用的是 [整備報告建立工具]，請選取 [本機資料夾中的 Office 文件]**** 或 [將之前的整備結果一起儲存在本機資料夾或網路共用] **** 選項。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. 然後，在 [報告設定]**** 頁面上，選取 [SQL Server 報告]****。Then, on the Report settings page, select SQL Server report. 提供必要的認證，以及您想要使用的資料庫名稱。Provide the necessary credentials and the name of the database you want to use. 如果資料庫不存在，則會建立資料庫。If the database doesn't exist, it will be created.
會建立具有相同資訊的 Power BI 報告，而不是建立 Excel 文件，以便您檢閱結果。Instead of creating an Excel file, a Power BI report, with the same information, is created for you to review the results. 可展開或視需要變更此 PowerBI 報告。This PowerBI report can be expanded on or changed as desired. 它的文件副檔名為 .pbit，並會儲存到安裝整備工具組的資料夾中，通常會是 C:\Program Files (x86)\Microsoft Readiness Toolkit for Office。It has a file extension of .pbit and is saved to the folder where the Readiness Toolkit is installed, which is usually C:\Program Files (x86)\Microsoft Readiness Toolkit for Office. 如果在 Power BI 中出現提示，請選取 [直接查詢]**** 資料存取模式。If prompted in Power BI, select Direct Query data access mode.
如果您使用的是整備報告建立工具的命令列版本，請鍵入 ReadinessReportCreator.exe -help 以查看使用 SQL Server 資料庫的相應命令。If you're using the command line version of the Readiness Report Creator, type ReadinessReportCreator.exe -help to see the appropriate commands for using a SQL Server database. 例如，您可以使用以下命令，使用名為整備的本機 SQL 資料庫，並使用 SQL Server 驗證而不是 Windows 驗證從財務部門的前一個整備結果建立報告。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.
ReadinessReportCreator.exe -sqlimport “C:\Reports\Finance” -server localhost/SQLEXPRESS -database Readiness -username Officeadmin -password seCRet123$%^
使用標籤來分類及篩選報告中的資料Use labels to categorize and filter data in reports
您可以指定最多四個自訂標籤，來分類及篩選整備工具組所建立報告中的資料。報告中可用的標籤是根據最近使用 Office 文件和使用者電腦上已安裝增益集的掃描。You can specify up to four custom labels to categorize and filter data in reports created by the Readiness Toolkit. Labels are available in reports that are based on scans of the most recently used Office documents and installed add-ins on the user’s computer.
您可以為自訂標籤指定任何字串。例如，您可以使用標籤來表示使用者的部門、職銜或地理位置。當整備工具組在使用者的電腦上執行時，系統會收集自訂標籤並且讓標籤可用於所建立的報告中。例如，您可以篩選報告，只顯示來自「財務部門」的資料或只顯示來自非洲辦公室的資料。以一致的方式指派標籤，例如針對部門一律使用「標籤 1」。You can specify any string for the custom labels. For example, you can use a label to indicate the user’s department, title, or geographic location. When the Readiness Toolkit runs on the user’s computer, the custom labels are collected and are made available in the reports that are created. 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.You can specify these labels by using the Specify custom labels to use with the Readiness Toolkit Group Policy setting. You can find this policy setting under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Readiness Toolkit.You can find this policy setting under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Readiness Toolkit. Be sure to download the latest Administrative Template files (ADMX/ADML) for Office.Be sure to download the latest Administrative Template files (ADMX/ADML) for Office.
注意
如果您是使用 Office 遙測儀表板並且已經設定標記 (標籤)，整備工具組會在它掃描使用者電腦期間自動收集這些標籤，並且使其可用於報告中。但是，您為整備工具組指定的標籤不會出現在 Office 遙測儀表板中。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. But, labels you specify for the Readiness Toolkit won't appear in the Office Telemetry Dashboard.
管理報告中收集資料的隱私權Manage the privacy of data collected in reports
對使用者來說在一個組織裡使用含有敏感或機資訊的檔案名稱來儲存 Office 檔案十分常見。若要保護使用者隱私權並協助防止揭示敏感資訊，整備工具組可讓您建立一份報告，此報告可隱藏檔案路徑並且隱藏在掃描期間所識別的文件名稱。您可以從 UI 精靈或從命令列中藉由執行整備報告建立者來建立隱藏這項資訊的報表。It’s common for users in an organization to save Office files using file names that contain sensitive or confidential information. 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.
如果您正在使用 UI 精靈，首先請在「 最近使用的 Office 文件和這部電腦上安裝的增益集 」或「在本機資料夾或網路共用的 Office 文件」中選擇其中一個作為您要建立的報表類型。然後，在繼續下一步之前，請在精靈的 [下一步] 頁面上選取 [隱藏檔案名稱和路徑] 的核取方塊。****。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.
ReadinessReportCreator.exe -mru -addinscan -output \\server01\finance -silent -concealnames
當您建立一份隱藏檔案路徑和文件名稱的報告時，只有剩餘的字元是磁碟機代號、檔案名稱及副檔名的前兩個字元。其他檔案路徑的字元最多到8 字元，並且檔案名稱已取代為星號 (* )。例如：「c:\mergersinfo\Q4\companyx.docx 」 會顯示為「c:\********\co******.docx」。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. The other characters of the file path, up to 8 characters, and of the file name are replaced with asterisks (*). For example, "c:\mergersinfo\Q4\companyx.docx" will appear as "c:\********\co******.docx."
當建立報表時，執行掃描的電腦上會建立檔案名稱 .log 的檔案。這個檔案包含一個已掃描完且沒有任何隱藏資訊的完整清單的檔案路徑和名稱。記錄檔也包含列出每個檔案的參照代碼。此參照代碼出現在所建立報表中的一個欄位裡。這可讓您在報告中識別特定的檔案，以防報表中辨識需要進一步調查的 VBA 巨集或增益集問題。儲存檔案名稱 .log 的檔案至使用者的 AppData 資料夾中的暫存資料夾。例如，針對 user01、儲存此檔案至 C:\Users\user01\AppData\Local\Readiness Toolkit Temp\ 資料夾。When the report is created, a file named file-names.log is created on the computer that ran the scan. 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.log file is saved to a temp folder in the user's AppData folder. For example, for user01, the file is saved to the C:\Users\user01\AppData\Local\Readiness Toolkit Temp\ folder.
在報告中收集並顯示增益集的使用狀況資訊Collect and show add-in usage information in reports
如果您想深入了解組織最常使用哪些增益集或哪些人經常使用相關的增益集，您可以使用整備工具組收集增益集的使用情況資訊並將其納入整備報表。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 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.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. This policy setting is available in the most current version of the Administrative Template files (ADMX/ADML) for Office that are available on the Microsoft Download Center.This policy setting is available in the most current version of the Administrative Template files (ADMX/ADML) for Office that are available on the Microsoft Download Center. This policy setting is found under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Readiness Toolkit.This policy setting is found under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Readiness Toolkit.
其所生成和收集的資料包括增益集載入和使用的時間，以及增益集的故障情況。此資訊將儲存在執行使用代理程式的電腦登錄檔中。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.
我們建議您讓使用代理程式執行至少30天的時間，以確保您清楚掌握使用者及其使用行為。監視期間結束後，建立一份整備報表，以收集資訊並將其顯示在報表中。在您取得所需資訊後，即可變更群組原則設定，並關閉使用代理程式。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.
注意
在此版本的整備工具集中，執行 Office 2016 的電腦並未收集增益集的使用情況資訊。In this release of the Readiness Toolkit, no add-in usage information is collected on computers that are running Office 2016.
偵測 Silverlight 或 Flash 控制項Detect Silverlight or Flash controls
Microsoft 365 應用程式將停用並封鎖 Silverlight、 Shockwave Flash 及 Macromedia Flash 控制項。Silverlight, Shockwave Flash, and Macromedia Flash controls are blocked from activating in Microsoft 365 Apps. 如需詳細資訊，請閱讀此技術社群貼文。For more information about this, read this Tech Community post.
若要識別涵蓋各該控制項的 Office 檔案，您可以選擇在您建立一份整備報表時掃描所有的 Office 文件。這將掃描所有的 Office 檔案，即便這些檔案並不包含巨集。由於一次需要掃描多個檔案，因此建立報表將耗費更長的時間。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.
如何將掃描雲端架構檔案How to scan cloud-based files
預設情況下，整備報告建立者無法掃描儲存在 SharePoint 文件庫、OneDrive 或一些其他類型的雲端儲存位置的檔案。如果您嘗試掃描其中一個檔案，檔案會在報告中顯示為 「 雲端式 」。By default, the Readiness Report Creator can't scan files that are saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location. If you try to scan one of these files, the file shows up as "Cloud-based" in the report.
其中一項可行的因應措施是掃描這些雲端架構檔案在使用者電腦上的本機快取。如果檔案只儲存在雲端位置，您可以建立一個與 OneDrive 或 SharePoint 共用位置相互對應的網路磁碟機。然後，您就可以讓整備報告建立者掃描該磁碟機。但是，掃描此位置時，您必須把檔案下載到記憶體中，以便執行掃描。根據相關檔案的數量和大小，掃描相關檔案可能耗費大量時間，並用盡網路頻寬。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.
其他資訊Additional information
針對 VBA 巨集分析的檔案副檔名File extensions analyzed for VBA macros
下表依據應用程式列出當整備報告建立工具在 Office 文件中尋找 VBA 巨集時，所分析的檔案副檔名。The following table lists, by application, the file extensions that are analyzed when the Readiness Report Creator looks for VBA macros in Office documents.
| ApplicationApplication | 檔案副檔名File extension |
|---|---|
| AccessAccess |
accdb、accdt、mdbaccdb, accdt, mdb |
| ExcelExcel |
xla、xlam、xls、xlsm、xlsx、xlt、xltm、xltxxla, xlam, xls, xlsm, xlsx, xlt, xltm, xltx |
| OutlookOutlook |
otmotm |
| PowerPointPowerPoint |
pot、potm、potx、ppa、ppam、pps、ppsm、ppt、pptm、pptx、sldx、sldmpot, potm, potx, ppa, ppam, pps, ppsm, ppt, pptm, pptx, sldx, sldm |
| ProjectProject |
mpp、mptmpp, mpt |
| PublisherPublisher |
pubpub |
| VisioVisio |
vsd、vsdx、vsdmvsd, vsdx, vsdm |
| WordWord |
doc、docm、docx、dot、dotm、dotxdoc, docm, docx, dot, dotm, dotx |
整備報告建立工具會收集其資料的增益集類型Types of add-ins for which the Readiness Report Creator collects data
下表列出整備報告建立工具會收集其資料的增益集類型。The following table lists the types of add-ins that the Readiness Report Creator collects data on. 系統會識別所有 Office 應用程式的增益集，但是不包含 Web 增益集。對於我們看到在 Microsoft 365 應用程式中執行的 COM 增益集，也會提供整備資訊。Add-ins for all Office applications are identified, but it doesn't include web add-ins. Readiness information is provided for COM add-ins that we have seen running in Microsoft 365 Apps.
| 增益集類型Add-in type | Office 應用程式Office applications | 描述Description |
|---|---|---|
| 自動化Automation |
ExcelExcel |
支援 Excel 的自動化增益集是依據 COM 增益集所建置。可以從 Excel 工作表中的公式呼叫自動化增益集中的函數。Excel-supported automation add-ins are built upon COM add-ins. Functions in Automation add-ins can be called from formulas in Excel worksheets. |
| COMCOM |
Excel、Outlook、PowerPoint 及 WordExcel, Outlook, PowerPoint, and Word |
COM 增益集包含通常是以 C++ 和使用受控程式碼開發的 Visual Studio Tools for Office (VSTO) 撰寫的增益集。COM add-ins include add-ins usually written in C++ and Visual Studio Tools for Office (VSTO) developed using managed code. |
| VBAVBA |
Excel、PowerPoint 和 WordExcel, PowerPoint, and Word |
VBA 增益集是包含 VBA 程式碼之應用程式專用的檔案，包括啟用巨集的 Word 範本 (.dotm)、Excel 增益集 (.xla、.xlam) 及 PowerPoint 增益集 (.ppa、.ppam)。VBA add-ins are application-specific files that contain VBA code. These include macro-enabled Word templates (.dotm), Excel add-ins (.xla, .xlam), and PowerPoint add-ins (.ppa, .ppam). |
| WLLWLL |
WordWord |
WLL (.wll) 增益集為 Word 所特有，且使用任何支援建立 DLL 的編譯器而建立。WLL (.wll) add-ins are specific to Word and built with any compiler that supports building DLLs. |
| XLLXLL |
ExcelExcel |
XLL 增益集 (.xll) 為 Excel 所特有，且使用任何支援建立 DLL (動態連結程式庫) 的編譯器而建立，無須進行安裝或註冊。XLL 增益集亦包括含有使用者定義之命令及函數的 DLL。XLL add-ins (.xll) are specific to Excel and are built with any compiler that supports building DLLs (dynamic-link libraries). They do not have to be installed or registered. XLL add-ins also include DLLs that contain user-defined commands and functions. |
| XLS RTDXLS RTD |
ExcelExcel |
XLS 即時資料 (RTD) 增益集是使用 RealTimeData 工作表函數來呼叫 Automation 伺服程式即時擷取資料的 Excel 工作表。XLS real-time data (RTD) add-ins are Excel worksheets that use the RealTimeData worksheet function to call an Automation server to retrieve data in real-time. |
建立進階報告時，傳送給 Microsoft 的資訊範例Examples of the information sent to Microsoft when creating an advanced report
當您選擇建立進階報告時，某些資訊會傳送給 Microsoft。When you choose to create an advanced report, some information is sent to Microsoft.
下表提供傳送給 Microsoft，關於在掃描期間找到的 VBA 巨集的資訊清單，以及範例。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.
| 資料Data | 描述Description | 範例Example |
|---|---|---|
| DevicesScannedDevicesScanned |
已掃描的電腦數目。Number of computers that were scanned. |
DevicesScanned：23DevicesScanned: 23 |
| UniqueUsersUniqueUsers |
掃描中包含的使用者計數。Count of users included in scan. |
UniqueUsers：14UniqueUsers: 14 |
| 規則Rule |
特定規則套用到已掃描 VBA 巨集的次數。使用 GUID 以唯一識別規則。Count of how many times a specific rule was found to apply to the VBA macros scanned. A GUID is used to uniquely identify the rule. |
48f05b1d-c8ad-4d0c-9453-1abdf007b2db：2348f05b1d-c8ad-4d0c-9453-1abdf007b2db: 23 74db65ab-76f3-43fb-997d-0d9750efb527：274db65ab-76f3-43fb-997d-0d9750efb527: 2 |
| FilesWithIssuesFilesWithIssues |
具有相容性問題的唯一檔案計數。Count of unique files with compatibility issues. |
FilesWithIssues: 320FilesWithIssues: 320 |
| FilesWithDuplicateVBAFilesWithDuplicateVBA |
包含重複巨集的唯一檔案計數。Count of unique files containing duplicate macros. |
FilesWithDuplicateVBA：233FilesWithDuplicateVBA: 233 |
| FilesWithNoIssuesFoundFilesWithNoIssuesFound |
沒有問題的唯一檔案計數。Count of unique files with no issues. |
FilesWithNoIssuesFound：12FilesWithNoIssuesFound: 12 |
| InaccessibleFilesInaccessibleFiles |
無法存取的唯一檔案計數。Count of unique inaccessible files. |
InaccessibleFiles：4InaccessibleFiles: 4 |
| FilesPasswordProtectedFilesPasswordProtected |
受密碼保護的唯一檔案計數。Count of unique files that were password protected. |
FilesPasswordProtected：123FilesPasswordProtected: 123 |
| FilesLockedFilesLocked |
已鎖定的唯一檔案計數。Count of unique locked files. |
FIlesLocked：0FIlesLocked: 0 |
| FilesWithVBAFilesWithVBA |
具有 VBA 的唯一檔案計數。Count of unique files with VBA. |
FilesWithVBA：122FilesWithVBA: 122 |
| FilesWithoutVBAFilesWithoutVBA |
沒有 VBA 的唯一檔案計數。Count of unique files without VBA. |
FilesWithoutVBA：11FilesWithoutVBA: 11 |
| SignificantremediationrequiredSignificantremediationrequired |
需要大量修復的唯一檔案計數。Count of unique files that require significant remediation. |
Significantremediationrequired：12Significantremediationrequired: 12 |
| LimitedremediationrequiredLimitedremediationrequired |
需要有限修復的唯一檔案計數Count of unique files that require limited remediation |
Limitedremediationrequired：12Limitedremediationrequired: 12 |
| MinimalvalidationrequiredMinimalvalidationrequired |
需要基本驗證的唯一檔案計數。Count of unique files that require minimal validation. |
Minimalvalidationrequired：22Minimalvalidationrequired: 22 |
| CodeDesignChangesCodeDesignChanges |
包含使用我們建議變更的功能的唯一檔案計數。Count of unique files that contain use of features that we would recommend changes. |
CodeDesignChanges：1CodeDesignChanges: 1 |
| DevicesWithNoMacrosDevicesWithNoMacros | 未啟用巨集的裝置數目。Number of devices that didn't have macro enabled files. | DevicesWithNoMacros: 12DevicesWithNoMacros: 12 |
| DevicesWithDeclaresDevicesWithDeclares | 巨集包含 Declare 陳述式的裝置數目。Number of devices scanned that included macros that used Declare statements. | DevicesWithDeclares: 12DevicesWithDeclares: 12 |
| DevicesWhichRequireSignificantRemediationDevicesWhichRequireSignificantRemediation | 包含巨集檔案須作重大修復的裝置數目。Number of devices that contain macro files that require significant remediation. | DevicesWhichRequireSignificantRemediation: 12DevicesWhichRequireSignificantRemediation: 12 |
| DevicesBlockedFromUpgradeDevicesBlockedFromUpgrade | 包含巨集須作修復以解除封鎖並升級至 Microsoft 365 應用程式的裝置數目。Number of devices that contain macros that require remediation to be unblocked from upgrading to Microsoft 365 Apps. | DevicesBlockedFromUpgrade: 1DevicesBlockedFromUpgrade: 1 |
| DevicesWithMacrosWithIssuesDevicesWithMacrosWithIssues | 包含巨集出現相容性問題的裝置數目。Number of devices that contain compatibility issues with macros. | DevicesWithMacrosWithIssues: 2DevicesWithMacrosWithIssues: 2 |
| DevicesWhichRequireLimitedRemediationDevicesWhichRequireLimitedRemediation | 包含巨集檔案須作重大修復的裝置數目。Number of devices that contain macro files that require limited remediation. | DevicesWhichRequireLimitedRemediation: 12DevicesWhichRequireLimitedRemediation: 12 |
| DevicesWhichRequireMinimalValidationDevicesWhichRequireMinimalValidation | 包含巨集檔案須作最小驗證的裝置數目。Number of devices that contain macro files that require minimal validation. | DevicesWhichRequireMinimalValidation: 12DevicesWhichRequireMinimalValidation: 12 |
| DevicesWithMacrosWithoutIssuesDevicesWithMacrosWithoutIssues | 包含巨集但無任何相容性問題的裝置數目。Number of devices that contain macros, but don’t have any compatibility issues. | DevicesWithMacrosWithoutIssues: 12DevicesWithMacrosWithoutIssues: 12 |
| DevicesWithMacrosDevicesWithMacros | 包含巨集檔案的裝置數目。Number of devices that contain macro files. | DevicesWithMacros: 12DevicesWithMacros: 12 |
| DevicesSafeToUpgradeDevicesSafeToUpgrade | 可升級至 Microsoft 365 應用程式的裝置數目。Number of devices are ready to upgrade to Microsoft 365 Apps. | DevicesSafeToUpgrade: 12DevicesSafeToUpgrade: 12 |
| DevicesWithOlderToolVersionDevicesWithOlderToolVersion | 使用舊版整備工具組的裝置數目。Number of devices that are using an older version of the Readiness Toolkit. | DevicesWithOlderToolVersion: 12DevicesWithOlderToolVersion: 12 |
下表提供傳送給 Microsoft，關於在掃描期間找到的增益集的資訊清單，以及範例。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.
| 資料Data | 範例Example |
|---|---|
| 增益集程式識別碼Add-in Pro ID |
UCAddin.LyncAddin.1UCAddin.LyncAddin.1 |
| 易記名稱Friendly Name |
適用於 Microsoft Office 2016 的 Skype 會議增益集 (Outlook)Skype Meeting Add-in for Microsoft Office 2016(Outlook) |
| 描述Description |
適用於 Microsoft Office 2016 的 Skype 會議增益集Skype Meeting Add-in for Microsoft Office 2016 |
| 檔案名稱File Name |
UCADDIN.DLLUCADDIN.DLL |
| 增益集 CLSIDAdd-in CLSID |
{A6A2383F-AD50-4D52-8110-3508275E77F7}{A6A2383F-AD50-4D52-8110-3508275E77F7} |
| 提供者Provider |
Microsoft CorporationMicrosoft Corporation |
| 檔案戳記File Timestamp |
14999408321499940832 |
| 檔案版本File Version |
16.0.8326.204416.0.8326.2044 |
| Office 應用程式Office App |
OutlookOutlook |
| 裝置數量Number of Devices |
3535 |
變更巨集設定，以檢視整備報告中的資訊Change macro settings to view information in the readiness report
整備報告建立工具建立的報告會使用巨集和主動式內容，以在報告中顯示資訊。因此，若要在報告中查看 VBA 巨集相容性和增益集整備資訊，您必須在 Excel 中允許巨集和主動式內容。如果未在 Excel 中啟用巨集和主動式內容，您會在開啟報告時，於 [概觀]**** 工作表上看到 [開始使用]**** 訊息。該頁面上有如何啟用巨集和主動式內容的指示。這與在訊息列中按一下 [啟用內容]**** 一樣簡單。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.
在某些情況下，您可能不會看到訊息列和 [啟用內容]**** 選項。這種情形最有可能發生，因為 Excel 是設定為停用所有巨集且沒有通知。您可以藉由移至 [檔案]**** > [選項]**** > [信任中心]**** > [信任中心設定…]**** > [巨集設定]**** 來檢查此設定。在 [信任中心]**** 對話方塊中，您可以將設定變更為 [停用所有巨集並且通知]****。在您這麼做之後，選擇 [確定]**** 以儲存變更並且關閉 [信任中心]**** 對話方塊，然後選擇 [確定]**** 以關閉 [Excel 選項]**** 對話方塊，然後關閉報告檔案。當您再次開啟報告檔案時，您應該會看到訊息列和 [啟用內容]**** 選項。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. You can check this setting by going to File > Options > Trust Center > Trust Center Settings… > Macro Settings. 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.
如果 [信任中心]**** 對話方塊中的巨集設定選項呈現灰色，則是系統管理員已經使用群組原則進行設定，且設定無法手動變更。在這種情況下，最簡單的解決方案是在與執行 Excel 巨集設定不同的電腦上開啟報告檔案，讓您藉由選取訊息列中的 [啟用內容]**** 選項來啟用巨集。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.
如需巨集設定選項的詳細資訊，請參閱在 Office 檔案中啟用或停用巨集。For more information about macro setting choices, see Enable or disable macros in Office files.
針對分類為「未知」或「資料不足」的增益集所採取的可能步驟Possible steps to take for add-ins classified as "Unknown" or "Insufficient data"
如果增益集分類為「未知」或「資料不足」，則表示 Microsoft 尚未有與增益集相關的足夠資訊可以提供整備狀態。如果這是組織的商務關鍵性增益集，您可以執行下列動作：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:
請與開發此增益集的軟體提供者聯繫，確認此增益集是否支援 Microsoft 365 應用程式。Contact the software provider who developed this add-in to see if the add-in is supported for Microsoft 365 Apps. 此外，您也可以要求您的軟體提供者在準備好使用 Windows 網站中列出對 Microsoft 365 應用程式的增益集支援。Also, you can request that your software provider list the add-in's support for Microsoft 365 Apps on the Ready for Windows site. 透過列出增益集，軟體提供者可將增益集對 Microsoft 365 應用程式的支援狀態提供給其他企業。By listing the add-in, the software provider can make the add-in's support status for Microsoft 365 Apps available to other enterprises.
請透過 ReadyForOffice@microsoft.com 與我們連絡。我們會竭盡所能將增益集的整備狀態新增至我們的資料庫。請盡可能提供增益集的相關資訊，包括但不限於下列項目：Contact us at ReadyForOffice@microsoft.com. 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:
易記名稱Friendly name
檔案版本File version
軟體提供者Software provider
下載連結，或有關如何下載及安裝增益集的任何詳細資料。Download link, or any details on how to download and install the add-in.
其他詳細資料，例如增益集的類型、增益集與哪個 Office 應用程式搭配使用、程式識別碼或 CLSID。Other details, such as the type of add-in, which Office app the add-in is used with, the Prog ID, or the CLSID.
傳送給 Microsoft 的錯誤報告資訊Information sent in an error report to Microsoft
如果顯示整備報告時發生問題，您會收到訊息，詢問您是否想要傳送錯誤報告給 Microsoft。例如，如果在報告中建立圖表時或查詢收集的資料時發生問題。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.
藉由傳送錯誤報告給 Microsoft，您可以協助我們改善整備工具組。傳送給 Microsoft 的錯誤報告不會包含任何可識別個人的資訊。下表提供傳送給 Microsoft 的錯誤報告中包含哪些資訊的清單。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.
| 傳送的資料Data sent | 描述Description |
|---|---|
| 模組Module | 發生錯誤的 VBA 模組。The VBA module where the error occurred. |
| 子/函數名稱Sub/Function name | 發生錯誤的子程序或函數的名稱。The name of the sub procedure or function that the error occurred in. |
| 行識別碼Line identifier | 最後成功執行的程式碼行開頭的識別碼。The identifier placed at the beginning of the last successfully executed line of code. |
| 錯誤訊息Error message | 使用者訊息通常會依據錯誤輸出。可能會針對某些錯誤當地語系化。The user message normally output by the error. May be localized for some errors. |
| 錯誤編號Error number | 識別錯誤的編號。The number identifying the error. |
| 來源名稱Source name | 引發錯誤的物件名稱。這不是變數名稱。The name of the object that raised the error. This is not the variable name. |
| 工具版本Tool version | 所使用的整備工具組版本。The version of the Readiness Toolkit that was being used. |
| 報告 GUIDReport GUID | 針對每個報告產生的 GUID 有助於篩選出重複的錯誤。A GUID generated for each report to help filter out repeated errors. |
| 工作階段識別碼Session ID | 當建立報告來讓它與整備工具組所記錄的任何錯誤相互關聯時的工作階段識別碼。The Session ID when the report was created to help correlate it with any errors logged by the Readiness Toolkit. |
| Excel 版本Excel version | 用來檢視整備報告的 Excel 版本。The version of Excel used to view the readiness reports. |