Troubleshooting the Windows Servicing Suite (WSS) Installer
The WSS Installer writes to a log file (Application.log) under
%APPDATA%\1E\Windows Servicing Suite Installer and records all the installer activities as it copies and executes the individual product installers to the specified servers. As each installer is executed, its log file is collected and saved to
%APPDATA%\1E\Windows Servicing Suite Installer on the machine where the WSS Installer is executed to simplify troubleshooting. A full reference of all the log files generated is provided in Log files.
The settings selected when the wizard UI is completed are written to
%APPDATA%\1E\Windows Servicing Suite Installer\AnswerFile.xml. If you need to contact 1E support to assist with troubleshooting installation issues, please provide
AnswerFile.log and any product installer logs from
%APPDATA%\1E\Windows Servicing Suite Installer\Installation Logs.
Troubleshooting Windows Servicing Suite components
When troubleshooting problems with any of the Windows Servicing Suite components, you should first check that you have completed all of the steps listed under preparation and the system meets the prerequisites.
To troubleshoot individual components of the 1E Windows Servicing Suite, see the following:
- Troubleshooting Nomad
- Troubleshooting PXE Everywhere
- Troubleshooting NightWatchman WakeUp
- Troubleshooting Shopping self-service
Preserving Tachyon Agent and WSA log files in a Wipe-and-load scenario
The TachyonAgent.log and WSA.log files provide diagnostic information when the Windows Servicing Assistant is used to perform a deployment. In the In-place Upgrade and Replace scenarios, these log files remain on the PC in their original location (C:\ProgramData\1E\Tachyon). However, in a Refresh (Wipe-and-load) scenario, these log files are wiped and cannot be viewed after the new OS has been installed. To capture and restore these log files using USMT in he Task Sequence, refer to Preserving Tachyon Agent and WSA log files in a Wipe-and-load scenario