Service Now Agent Client Collector for macOS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2025 08:13 AM
Hi, not sure if this is the correct forum location or not, but any help would be greatly appreciated.
I am trying to install the ServiceNow Agent Client Collector for macOS on our test devices, but the command to install the collector is not working. I am not able to locate any logs or installation folder after running the command.
This is the command I am using to install the connector. (Hiding the API key and URL)
ACC_API_KEY=xxxxxxx="wss://10.90.23.236:443/ws/events" bash -c "$(curl -L https://xxxxxxx/api/sn_agent/agents/install_agent)”
Can anyone help me with this.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2025 08:31 AM
Check the Command Syntax. Below is the syntax to install ACC on macOS
ACC_API_KEY=<your_api_key> ACC_WS_URL=wss://<your_instance_or_ip>:443/ws/events bash -c "$(curl -fsSL https://<your_instance>/api/sn_agent/agents/install_agent)
1. I think you are missing a space between the API key and the WS_URL
2. Also, ACC_WS_URL should be its own environment variable
3. use -fsSL for better curl handling
Example :
ACC_API_KEY=your_key_here ACC_WS_URL=wss://10.90.23.236:443/ws/events bash -c "$(curl -fsSL https://your_instance/api/sn_agent/agents/install_agent)
Also check some pre-requisites :
1. You are using macOS 10.15+
2. The device has curl and bash available
3. You are connected to the internet or network where the ServiceNow MID Server or instance is reachable
Please mark as correct answer if it helps you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2025 07:09 AM
Hi, thanks for replying.
For your first point, there is a space between API key and WS_URL, I think while pasting the syntax, it deleted the space.
Also, I want to highlight that the same command was working, and the devices were registered to the dashboard, however, it stopped working after some time. We have confirmed that nothing changed from the ServiceNow side regarding the URL or IP.