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/virtual-desktop/troubleshoot-vm-configuration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,10 +76,10 @@ The recommended way to provision VMs is using the Azure Resource Manager **Creat
76
76
Follow these instructions to confirm the components are installed and to check for error messages.
77
77
78
78
1. Confirm that the two components are installed by checking in **Control Panel** > **Programs** > **Programs and Features**. If **Windows Virtual Desktop Agent** and **Windows Virtual Desktop Agent Boot Loader** are not visible, they aren't installed on the VM.
79
-
2. Open **File Explorer** and navigate to **C:\Windows\Temp\scriptlogs.log**. If the file is missing, it indicates that the PowerShell DSC that installed the two components was not able to run in the security context provided.
80
-
3. If the file **C:\Windows\Temp\scriptlogs.log** is present, open it and check for error messages.
79
+
2. Open **File Explorer** and navigate to **C:\Windows\Temp\ScriptLog.log**. If the file is missing, it indicates that the PowerShell DSC that installed the two components was not able to run in the security context provided.
80
+
3. If the file **C:\Windows\Temp\ScriptLog.log** is present, open it and check for error messages.
81
81
82
-
### Error: Windows Virtual Desktop Agent and Windows Virtual Desktop Agent Boot Loader are missing. C:\Windows\Temp\scriptlogs.log is also missing
82
+
### Error: Windows Virtual Desktop Agent and Windows Virtual Desktop Agent Boot Loader are missing. C:\Windows\Temp\ScriptLog.log is also missing
83
83
84
84
**Cause 1:** Credentials provided during input for the Azure Resource Manager template were incorrect or permissions were insufficient.
85
85
@@ -93,7 +93,7 @@ Follow these instructions to confirm the components are installed and to check f
93
93
- Confirm that the tenant name is accurate and the tenant exists in Windows Virtual Desktop.
94
94
- Confirm the account has at least RDS Contributor permissions.
95
95
96
-
### Error: Authentication failed, error in C:\Windows\Temp\scriptlogs.log
96
+
### Error: Authentication failed, error in C:\Windows\Temp\ScriptLog.log
97
97
98
98
**Cause:** PowerShell DSC was able to execute but couldn't connect to Windows Virtual Desktop.
0 commit comments