Agent Client Collector Service User Password Handling<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The ACC Windows service fails to start (or stops unexpectedly) after the password for the local "servicenow" user account has been changed. Cause During installation, the ACC MSI installer creates a local Windows user named servicenow and generates a random password for it. That password is used both to create the account and to configure the Windows service to run under that account. The generated password is not recorded or retrievable anywhere and it exists only in the installer's runtime memory at install time. When the password for a Windows user account is changed, that same password must also be updated in the service configuration wherever that account is mapped to run the service. If only the account password is changed and the service configuration is left pointing to the old (now outdated) credentials, Windows can no longer authenticate the service to run as that user and so the service fails to start. Because the original password was never recorded, there is no way to "recover" or "look up" the installer-generated password. This is expected behavior. Resolution There will be no issues to change the servicenow user's password (or changing the service to run under a different user entirely), provided the following are done consistently: Update the service to use the new password Open services.msc, locate the ACC service, go to the Log On tab, and re-enter the new password so it matches the account. If changing the service's user account (not just the password): Ensure all file and folder permissions used by ACC are updated to grant the new account the required access.Ensure the new account has the required local security policy user rights: Log on as a service — required for ACC-F and ACC-VDebug Programs — additionally required for ACC-M Restart the service and confirm it starts successfully under the new credentials.