Trimble Business Center

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

I'll second this request for being able to assign a list of potential Trimble IDs to a TBC license. We have multiple TBC users that aren't in TBC all day every day, and pressure from on high to reduce overhead cost. We need to be able to move fast and let individual users check licenses in and out without handing out account admin rights to every user and without having to have an admin manually switch licenses around at random times throughout the day. Actual individual user license selection could easily happen within the existing license manager in TBC...

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

I asked this question at the December power hour, and Trimble's response was they might have something in the works about making this better but they could not say anything specific at that time.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hello,

I was not aware perpetual licenses were no longer an option.  I don't want to shift the discussion.  We use the perpetual license system and if that is being removed, i would be disappointed and looking to move on.  I agree the network license can be buggy, and beyond that very complicated if you don't want to have all equal seats of all functionality.  We need four copies of the advanced scanning TBC options, we don't need four licenses for mobile mapping, UAV mapping, etc.  The option to get this is to build another license server, or have something called a ghost server or something.  This seems like low hanging fruit to make work on a single server.  Two cents.

I asked this question at the December power hour, and Trimble's response was they might have something in the works about making this better but they could not say anything specific at that time.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

We are in the same boat. We have been using the perpetual network licenses for a long time and plan to run them until they are ripped away from us.

I'd welcome being proven wrong, but I don't see how this could be a beneficial change for companies with many, albeit infrequent, users.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.

We have not been told that perpetual licenses would be removed.  What we did experience was a few directed sales leading us to subscription and if we weren't paying attention we would have been sold that.  I think it is unfortunate and disrespectful of the investment we have made into a very large closet of depreciated Trimble assets, and many, many years of software license maintenance.  There is also other hardware that was purchased and built to support network license server.

I have found that many of the Trimble (and other company) subscription services do a very poor job tracking the reality of a company.  The subscriptions get assigned to an email or login, and if you use a staff member you risk dealing with a headache when there is turnover, or if you come up with some fake email alias, then you have issues with people changing stuff when other users aren't aware.  There isn't a way to assign the subscription to the company, like you do with a perpetual floating server license.

Boo Trimble if it is true that perpetual licenses are being sunset.  This is a money grab, for a company that has a pretty captive audience and forces captive audiences within their own Geography.  I don't know many other businesses that have such a lock up market share as Trimble in California.  One authorized vendor of surveying hardware.  Isn't that enough advantage and low cost risk.  Now the value we have invested each year in maintaining our perpetual licenses is going to be ripped away.  Bummer.

We are in the same boat. We have been using the perpetual network licenses for a long time and plan to run them until they are ripped away from us.

I'd welcome being proven wrong, but I don't see how this could be a beneficial change for companies with many, albeit infrequent, users.

Hi brains trust. 

Hoping for a little help here. Long time perpetual network license user which we share across the team with people jumping in and out during the day as needs require. 

We have recently added an additional license to improve our capacity but have been pushed onto the new subscription service which does not seem to have the same functionality and the license has to be allocated to a seat/user? We were hoping that the system would be straightforward enough and operate like a network license and if a "named user" was on the list and logged in when opening TBC they could pull the subscription license for use and then when closing TBC the license was returned to the pool for the next user but it does not seem to have this functionality. The license could be allocated to a single shared user but this creates issues around staff departures and movements and unauthorised license usage. 

Once again the move to subscription licensing for "improved user experience" and "flexibility" is far from the case and certainly has us looking in other directions for software usage as our TBC requirement is minimal. 

Very happy to be proven wrong and shown a workable solution for us but not seeing it at present.