Update file-sync-troubleshoot-installation.md

Author: jeffpatt24

articles/storage/file-sync/file-sync-troubleshoot-installation.md

@@ -15,22 +15,42 @@ After deploying the Storage Sync Service, the next steps in deploying Azure File
 
 ## Agent installation
 <a id="agent-installation-failures"></a>**Troubleshoot agent installation failures**  
-If the Azure File Sync agent installation fails, at an elevated command prompt, run the following command to turn on logging during agent installation:
+If the Azure File Sync agent installation fails, locate the installation log file which is located in the agent installation directory. If the Azure File Sync agent is installed on the C: volume, the installation log file is located under C:\Program Files\Azure\StorageSyncAgent\InstallerLog. 
 
+> [!Note]  
+> If the Azure File Sync agent is installed from the command line and the /l\*v switch is used, the log file will be located in the path where the agent installation was executed. 
+
+The log file name for agent installations using the MSI package is AfsAgentInstall. The log file name for agent installations using the MSP package (update package) is AfsUpdater.
+
+Once you have located the agent installation log file, open the file and search for the failure code at the end of the log. If you search for **error code 1603** or **sandbox**, you should be able to locate the error code. 
+
+Here is a snippet from an agent installation that failed:
 ```
-StorageSyncAgent.msi /l*v AFSInstaller.log
+CAQuietExec64:      + CategoryInfo          : SecurityError: (:) , PSSecurityException  
+CAQuietExec64:      + FullyQualifiedErrorId : UnauthorizedAccess  
+CAQuietExec64:  Error 0x80070001: Command line returned an error.  
+CAQuietExec64:  Error 0x80070001: QuietExec64 Failed  
+CAQuietExec64:  Error 0x80070001: Failed in ExecCommon64 method  
+CustomAction SetRegPIIAclSettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)  
+Action ended 12:23:40: InstallExecute. Return value 3.  
+MSI (s) (0C:C8) [12:23:40:994]: Note: 1: 2265 2:  3: -2147287035
 ```
 
-Review installer.log to determine the cause of the installation failure.
+For this example, the agent installation failed with error code -2147287035 (ERROR_ACCESS_DENIED). 
 
 <a id="agent-installation-gpo"></a>**Agent installation fails with error: Storage Sync Agent Setup Wizard ended prematurely because of an error**
 
 In the agent installation log, the following error is logged:
 
 ```
-CAQuietExec64:  + CategoryInfo          : SecurityError: (:) , PSSecurityException
-CAQuietExec64:  + FullyQualifiedErrorId : UnauthorizedAccess
-CAQuietExec64:  Error 0x80070001: Command line returned an error.
+CAQuietExec64:      + CategoryInfo          : SecurityError: (:) , PSSecurityException  
+CAQuietExec64:      + FullyQualifiedErrorId : UnauthorizedAccess  
+CAQuietExec64:  Error 0x80070001: Command line returned an error.  
+CAQuietExec64:  Error 0x80070001: QuietExec64 Failed  
+CAQuietExec64:  Error 0x80070001: Failed in ExecCommon64 method  
+CustomAction SetRegPIIAclSettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)  
+Action ended 12:23:40: InstallExecute. Return value 3.  
+MSI (s) (0C:C8) [12:23:40:994]: Note: 1: 2265 2:  3: -2147287035 
 ```
 
 This issue occurs if the [PowerShell execution policy](/powershell/module/microsoft.powershell.core/about/about_execution_policies#use-group-policy-to-manage-execution-policy) is configured using group policy and the policy setting is "Allow only signed scripts." All scripts included with the Azure File Sync agent are signed. The Azure File Sync agent installation fails because the installer is performing the script execution using the Bypass execution policy setting.