11-08-2011 08:13 AM - edited 03-19-2019 03:56 AM
For as long as I've had to support it, our Unity 5.0 server was running in a standalone fashion. The other day I rebooted it because of a license file corruption that I was trying to resolve. The next morning I see it has found 2 other Unity servers in our Corporate IntraNet and has decided to pool its licenses with them. Can anyone explain how to configure it to NOT pool its licenses with the other Unity servers?
Thanks!
11-08-2011 08:44 AM
Hi,
Unity is told to participate in the License Pool in your actual license file that you installed. You'll need to go back to the Licensing team and ask that the feature tag be removed and the license re-cut.
Hope that helps,
Brad
11-08-2011 09:16 AM
Is there a way to configure the Unity so that it does not connect with other Unity servers? What I'd really like is for my Unity server to remain a standalone server instead of communicating with other Unity servers.
11-08-2011 09:26 AM
Once Unity is installed/added into AD, it's going to hear about all other Unity servers within the domain/forest by default through AD replication. If you've got the license pooling flag enabled in any Unity servers, they're going to participate in license pooling until the feature is removed from the license file(s) from the Unity servers.
Brad
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide