- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi,
Can someone please assist me with the steps/commands that need to be performed when pointing existing Splunk components (Deployment Server, Search Heads, Heavy Forwarder, Indexer) to a different existing License Server?
We currently have two separate environments with their own License Servers, now this is all being merged into one license. So, one of the environments needs to point to the other existing License Server where the new license will be installed.
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


For each Splunk instance you have, change the manager_uri setting in the [license] stanza of server.conf and restart the instance. For a SHC, this is done via the SHC Deployer. For an indexer cluster, use the Cluster Manager.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


For each Splunk instance you have, change the manager_uri setting in the [license] stanza of server.conf and restart the instance. For a SHC, this is done via the SHC Deployer. For an indexer cluster, use the Cluster Manager.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Thanks for the response. I have tried the following, but it times out. I assume its a port issue.
[license]
manager_uri = https://servername:8089
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


Make sure the LM is running. Confirm 8089 is the LM's management port (it's the default). Verify your firewalls allow connections to that port.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

I tried a different server in the same IP range now to test and the method you mentioned worked just fine.
So was the port being blocked.
Thanks for the help.
