You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-stack/azure-stack-validation-report.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ ms.reviewer:
21
21
22
22
23
23
# Azure Stack validation report
24
-
The Azure Stack Readiness Checker tool runs validations that support deployment and servicing of an Azure Stack environment. The tool writes validation results to a .json report file. The report displays detailed and summarized data on the state of prerequisites for deployment of Azure Stack and on Secrets Rotation for existing Azure Stack Deployments.
24
+
Use the Azure Stack Readiness Checker tool to run validations that support deployment and servicing of an Azure Stack environment. The tool writes results to a .json report file. The report displays detailed and summarized data about the state of prerequisites for deployment of Azure Stack. The report also displays information about Secrets Rotation for existing Azure Stack Deployments.
25
25
26
26
## Where to find the report
27
27
When the tool runs, it logs results to **AzsReadinessCheckerReport.json**. The tool also creates a log named **AzsReadinessChecker.log**. The location of these files displays with the validation results in PowerShell.
@@ -35,7 +35,7 @@ By default, both files are written to *C:\Users\<username>\AppData\Local\Temp\Az
35
35
- Use the **-CleanReport** parameter at the end of the run command to clear information from *AzsReadinessCheckerReport.json*. about previous runs of the tool.
36
36
37
37
## View the report
38
-
To view the report in PowerShell, supply the path to the report as a value for **-ReportPath**. This command displays the contents of the report and also identifies validations that do not yet have results.
38
+
To view the report in PowerShell, supply the path to the report as a value for **-ReportPath**. This command displays the contents of the report and identifies validations that do not yet have results.
39
39
40
40
For example, to view the report from a PowerShell prompt that is open to the location where the report is located, run:
@@ -54,7 +54,7 @@ The summary shows validations that don't have results and indicates pass or fail
54
54
55
55
56
56
## View a filtered report
57
-
To view a report filtered on a single type of validation, use the **-ReportSections** parameter and specify one of the following values that correspond to the validation type you want to view:
57
+
To view a report that is filtered on a single type of validation, use the **-ReportSections** parameter with one of the following values:
0 commit comments