[THIN] Re: MPS 3.0 licensing issue

  • From: Dogers <dogers@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Fri, 17 Sep 2004 20:39:18 +0100

You need to have A server which has the licenses stored on it, so
either way, if an office "goes down" (I'm assuming you're talking
about the net link??) then the other office cant get to the licenses

Although if you're talking about the server, then the only way round
that, would be to either replicate a sql db datastore between the two
sites, or somehow keep the access db current between the two.

Thats the only way I can see it :)


----- Original Message -----
From: Jonathan Kadoo <jkadoo@xxxxxxxxxxxxxx>
Date: Fri, 17 Sep 2004 15:28:44 -0400 (EDT)
Subject: [THIN] MPS 3.0 licensing issue
To: Thinlist <thin@xxxxxxxxxxxxx>

I am working on an issue with our upgrade to mps 3.0.  We have two
offices with a dedicated link between them. We are debating on how to
setup our licensing.  What we want to accomplish is to have our
licenses shared between both offices.  So if one office goes down the
other will still have the use of all the licenses.
I have been doing a lot of reading about how the new licensing works
and I don't really see a way of accomplishing this.  The only options
I can see is to have one server in one office and have everyone in
both offices share the licenses from that server.  Or have two servers
one in each office and split our total licenses between both offices. 
Am I missing something here?  Is there no way we can share the
licenses without having just one server in one office?
This Weeks Sponsor triCerat:
Have you had your fill of printing support calls, unauthorized apps running on 
unsecured Terminal Servers, profile headaches, and application performance 
problems? Join us and learn how you can have a less demanding on-demand 
Useful Thin Client Computing Links are available at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts: