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.

Anybody who is running on the new subscription license, can you send a static t02 or t04 file for an RTX solution?  We made the move at the start of the year and cannot use that function and get a license out of warranty error. Our sales rep escalated the issue into Trimble's tech support but so far we have no fix. 

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.

I was recently told this is an issue they are working on and the solution is to use the RTX option online instead of through TBC.

Anybody who is running on the new subscription license, can you send a static t02 or t04 file for an RTX solution?  We made the move at the start of the year and cannot use that function and get a license out of warranty error. Our sales rep escalated the issue into Trimble's tech support but so far we have no fix. 

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.

Hi Sean and all,

The RTX issue has been repaired in the recent release of TBC v2025.21.  It's available for download in the usual places, suggest here to start - TBC Geospatial Download

I was recently told this is an issue they are working on and the solution is to use the RTX option online instead of through TBC.

Anybody who is running on the new subscription license, can you send a static t02 or t04 file for an RTX solution?  We made the move at the start of the year and cannot use that function and get a license out of warranty error. Our sales rep escalated the issue into Trimble's tech support but so far we have no fix. 

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.

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.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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 agree 100%. Trimble eliminating new maintenance options and then forcing a person to shuffle names around in and out of subscription licenses is like not making any more horse drawn carriages but not having any mechanism to keep the wheel on new automobiles! Poor planning by Trimble. All a big push to increase profits, but it will push smaller surveying companies away, and possible away from Trimble altogether.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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 Juan,

It isn't the "subscription" that is the problem.  As noted by me, Autodesk does subscription model with network available seats.  They don't make us assign those seat to arbitrary email addresses.

We have the same situation you have, on a smaller scale.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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 Juan,

It isn't the "subscription" that is the problem.  As noted by me, Autodesk does subscription model with network available seats.  They don't make us assign those seat to arbitrary email addresses.

We have the same situation you have, on a smaller scale.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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.

You can add multiple users as admins - then they can claim the seat when they need it.

Then you can switch accounts and use the admin privilege you have been delegated to claim the seat.

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 Nick,

True the subscription model is named user (one person should have one Trimble Identity for one TBC edition license), which is different from the first-come, first-served network license model.  Trimble's focus on making the licensing personal is a part of a broader strategy that TBC is on forefront.  We are working on more transparent license management tools.

We recognize this is a change from the perpetual options and, through our distribution partners, incentivize the change through subscription pricing incentives and functionality.  Engage with your Trimble reseller for pricing info (there's an attractive trade-in and multi-seat pricing discount) and review the TBC subscription website.  We've positioned more functionality at lower price levels, bundled Trimble Connect Business Premium with each seat, and have some exciting new functionality for subscription licenses in the works.

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.

Someone correct me if I'm wrong, but I think we are actually talking about a numbers problem here above anything else. The numbers vary depending on the subscription, but I think what people are saying is if 40 TBC users shared 10 network licenses at $2500 per license per year, the annual cost was $25000. The only convenient way to utilize subscription licensing is for each user to have a license, so at even a reduced rate of $2000 per license per year for 40 licenses, it's still $80,000 per year, or a difference of $55,000 per year. Or choose the cost of major inconvenience or the cost of poor admin account security. Does that add some measureable perspective to this issue?

Hi Nick,

True the subscription model is named user (one person should have one Trimble Identity for one TBC edition license), which is different from the first-come, first-served network license model.  Trimble's focus on making the licensing personal is a part of a broader strategy that TBC is on forefront.  We are working on more transparent license management tools.

We recognize this is a change from the perpetual options and, through our distribution partners, incentivize the change through subscription pricing incentives and functionality.  Engage with your Trimble reseller for pricing info (there's an attractive trade-in and multi-seat pricing discount) and review the TBC subscription website.  We've positioned more functionality at lower price levels, bundled Trimble Connect Business Premium with each seat, and have some exciting new functionality for subscription licenses in the works.

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.

m hufford. 

personally i agree with what you are saying. i have not actually tried the subscription, so not 100%. but i would say your scenario is compounded by the fact that you used to be able to let your perpetual license laps and still be able to use it. not sure what happens with the subscription but i assume you can not use it once the year is up without paying. so the old perpetual network or other keys would be good forever but stuck at the last maintenance payment date. when i used to do the math, if you left it for 3 years you would start to come out ahead after that. if you paid for maintenance before 3 years are up, you might as well have kept up to date the whole time. 

with your numbers, after year 1 the out of maintenance user was paying 0$, but now are forced to pay minimum 20k or for full convenience 80 000$ !!!!!!

our dealer prompted us to purchase more perpetual seats prior to christmas. we did not do it because we pretty much have enough.

my real frustration here is this: you want us to pay big money then provide big service. i have been at this for 15 years or so and the changes to tbc are minimal. we used to pay up only to see the colors and ribbon change so that we could not find things any more. when ever i say this i don't want to blame the software engineers that i know are working as best as they can. but this is a huge budget and there are so many little things with tbc that are not fixed and so many improvements that could be made. if it was top notch i would pay up right away and be happy about it. but as is, there are too many frustrations. a simple command line that worked better and activated for every function and imbedded function prompt, with better escape functionality would go a long way, no separate command line for some cad, this is weird. there is way too much clicking in tbc that slows it down. people have been asking for better snaps for so so long. 3d point cloud snap could be cool...

anyways, i don't want to get too deep into frustrations. 

Someone correct me if I'm wrong, but I think we are actually talking about a numbers problem here above anything else. The numbers vary depending on the subscription, but I think what people are saying is if 40 TBC users shared 10 network licenses at $2500 per license per year, the annual cost was $25000. The only convenient way to utilize subscription licensing is for each user to have a license, so at even a reduced rate of $2000 per license per year for 40 licenses, it's still $80,000 per year, or a difference of $55,000 per year. Or choose the cost of major inconvenience or the cost of poor admin account security. Does that add some measureable perspective to this issue?

Hi Nick,

True the subscription model is named user (one person should have one Trimble Identity for one TBC edition license), which is different from the first-come, first-served network license model.  Trimble's focus on making the licensing personal is a part of a broader strategy that TBC is on forefront.  We are working on more transparent license management tools.

We recognize this is a change from the perpetual options and, through our distribution partners, incentivize the change through subscription pricing incentives and functionality.  Engage with your Trimble reseller for pricing info (there's an attractive trade-in and multi-seat pricing discount) and review the TBC subscription website.  We've positioned more functionality at lower price levels, bundled Trimble Connect Business Premium with each seat, and have some exciting new functionality for subscription licenses in the works.

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.

For what it's worth, I use TBC everyday often 6-8 hrs a day and every new version release has improvements I appreciate and start using. I'm using point cloud/scanning features, GIS, construction, control network adjustments, etc.  Often when I see people on here complaining about the "lack" of improvements it's clear they're not heavy users. Or, I recognize the features they're asking for are things from Autodesk. Trimble, please, please, please for the love of the Lord don't make my TBC anymore like AutoCAD.

------------------------------
Andrew Haukaas

Original Message:
Sent: 01-20-2026 21:12
From: Nick McKelvey
Subject: TBC Subscription License for multiple 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.

------------------------------
Nick McKelvey
------------------------------

For what it's worth, I use TBC everyday often 6-8 hrs a day and every new version release has improvements I appreciate and start using. I'm using point cloud/scanning features, GIS, construction, control network adjustments, etc.  Often when I see people on here complaining about the "lack" of improvements it's clear they're not heavy users. Or, I recognize the features they're asking for are things from Autodesk. Trimble, please, please, please for the love of the Lord don't make my TBC anymore like AutoCAD.

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.

------------------------------
Nick McKelvey
------------------------------

Ngā mihi,

John.

------------------------------
John Longson

Original Message:
Sent: 01-20-2026 21:12
From: Nick McKelvey
Subject: TBC Subscription License for multiple 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.

------------------------------
Nick McKelvey
------------------------------