Best Practice On Test Vs Production License Server? 追蹤
I know, I've asked a lot of questions lately :)
I have a decent sized production enterprise automation environment with its own license server on the same server as the Bartender suite.
I have a smaller test/staging enterprise automation environment also with its own license server on the same server as the Bartender suite.
When I create labels, I set their license server to "automatic", this way if they are on test they use test's license server, if they are on production they use production's.
I like the idea of keeping these separate because if I do something very stupid on test, like somehow print to a ton of different printer instances, the worst case is I mess up test for a week until the print count resets. However, in truth, that's never happened. As such, I'm wondering if I should simply kill this test license server off and increase the production by the same count?
- if I merge, I'll have to explicitly identify license server on existing and future labels, so that as they move from test environment to production they keep using the proper single licensing server
- I partly want to do this because I want to create a license-only server that has no other Bartender components except the license server (because I need a BT 2016 license server but don't want to upgrade the rest of my 10.1 stuff right now)
What is the best practice here? Is insulating the license server in its own test instance overkill?