Use the information in this section to troubleshoot your Workspace ONE Access connector installation. Accessing Workspace ONE Access Connector Log FilesTo debug and troubleshoot problems, you can view the Workspace ONE Access connector log files, which are stored on the connector server. The Directory Sync, User Auth, and Kerberos Auth services each have their own log files. Creating a Workspace ONE Access Connector Log BundleYou can create a log bundle of Workspace ONE Access connector logs, which can be easily transferred to another machine or sent to support. Increasing the Size and Number of Workspace ONE Access Connector Log FilesThe Directory Sync, User Auth, and Kerberos Auth services each create log files that you can use to troubleshoot problems. If you want to save more logs than are saved by default, you can increase the size of the files as well as the number of files that are created before logs are rotated. Updating the Workspace ONE Access Connector Host NameIf you change the Workspace ONE Access connector server host name after installing the connector, you must also update the Directory Sync service, User Auth service, and Kerberos Auth service installed on the connector to use the new host name. Updating Workspace ONE Access Service FQDN in Enterprise Services application.properties FilesIn an on-premises Workspace ONE Access service installation, if you change the fully-qualified domain name (FQDN) of the Workspace ONE Access service, you also need to update the FQDN entry in the Directory Sync, User Auth, and Kerberos Auth services' application.properties files if you deployed these services before the FQDN change. Kerberos Auth Service Installation Fails Installation of the Kerberos Auth service, a component of the Workspace ONE Access connector, fails with the error message Failed to run KerberosAuthService as DOMAIN\username if the domain user account password contains unsupported characters. Use this information to resolve the issue.