Agent Client Collector Installation Fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2024 01:30 PM
We are currently piloting the Agent Client Collector for Visibility so far has been relatively successful. We attempted to install the agent on 2 different Windows Servers that are not AD Domain Joined (Workgroup) and were met with an agent installation failed message noting there was a problem creating the default "servicenow" user. On our domain joined servers this has not been a problem. Oddly, it does create the ServiceNow group, just not the user account.
We also tried to create a local account and use that in place of the default servicenow account and the installer would not allow us to proceed stating it was not a valid account.
We attempted to use LocalService and the installation was able to complete successfully.
Has anyone else come across this problem before and what did you do to resolve?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2024 10:03 PM
the error for user account is generally because it is not having required permisssions. what is the error during failure?
how are the agents being deployed- manually or via third party tool?
you can use the LocalService option if there is no requirement to run it under any service account and it will also help in bringing 'assigned to' value of the systems being discovered.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-08-2024 06:37 AM
Thank you for the reply. We see the installer will end and note that the installation was terminated and to review the install log for further details. I have attached the install log.
Right now, we are installing manually. The account logged in during the install was a local administrator.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2024 06:56 AM
from the log its stating "Error setting user info. This can occur due to mismatch in installed user and configured service user."
1. while running the installer for the first time, did you provide the default user name? And was that already created? Because there is a pre requisite mentioned in the document to create the group and user and assign the permissions.
2. And you mentioned that while trying to use a service account it doesnt take it. This could be due to incomplete installation tried first. So my advice would be to remove the installer and try it again from the start.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-11-2024 07:30 AM
The first installation attempt we chose to have installer create the default service account (servicenow user). We had not created a service account prior to running the installation. On the other servers that we have successfully completed the installation, we had the installer create the servicenow user and necessary group and assign the permissions as needed.
We ran the uninstaller after each failed attempt to make sure we were starting with a clean slate. You noted that if we opt to use a service account that we created, that we need to create the group and assign the permissions manually. I will see if I can find that documentation. IF you are able to include a link to that documentation that would be greatly appreciated.
