Skip to main content
T
TomCoyle
Participant
April 23, 2021
Answered

Removing a Single Shared Device License to be reallocated

  • April 23, 2021
  • 1 reply
  • 990 views

Hi All,

We've recently migrated our Adobe device licenses to the new shared license platform.

Does anybody know a way that a single shared license can be recovered from within a profile instead of recovering all licensees that are tied to a profile?

The only option available within the Admin panel is to recover all licenses from a profile, resulting in a wait of 7 days for the license to be released.

 

Example Scenario:

- All shared device licenses are currently in use

- I have 1 device that has a hardware failure and a replacement machine needs to be put in place

- All machines are associated to a "shared device license profile" for that lab.  The only option I can see is to "recover" all licenses from within this profile which then takes 7 days to become available again. 

 

This results in an entire labs worth of computers losing their shared license with no means to re-instate them for 7 Days just because 1 machine is affected and I'm unable to pull that individual license back and end up with an entire lab needing to be relicensed and waiting a week for the licenses to be usable again.

 

Surely there a better solution?

Does anybody know a way to revoke 1 license from 1 machine from within a shared device profile?
Many Thanks,

Tom

This topic has been closed for replies.
Correct answer SuJoshi

"you would need just as many licenses in surplus" I don't see it that way. I'd have some spare licenses, and just assign them as needed to replace broken kit. Holding spare licenses against hardware failure is a common requirement, to avoid the downtime of applying for a license transfer, both at the desktop and the server end.


Hello,

The recover license option will just reset the license count to 0. The users can still access the apps after signing in and there is no need to wait for 7 days to use the applications. The "recover license" option only will be available after 7 days.

Once you recover the license, it admin console will register only those machines on which the users will log in. In this way, you can replace the device/hardware of the affected machine and re-install the shared device license package and when the user will sign in, it will be active and ready to use.

1 reply

T
Test Screen Name
Legend
April 23, 2021

I don't have any inside knowledge but I'm going to share my thoughts

(1) it seems Adobe have decided to put serious obstacles in the way of companies who want to move around their shared device licenses rather than dedicate them permanently. It may be that 7 days is needed to catch old machines trying to use their revoked licenses. This is catching out your failure case.

(2) you will certainly need some spares in your licenses to cope with hardware failures. Perhaps the maximum per lab to allow seamless recovery. Or plan to regain lost spares out of term time.

    T
    TomCoyleAuthor
    Participant
    April 23, 2021

    Fully aware that point (1) is true and it is their intention for device licenses to become a thing of the past.

    However, as a school, our budget is quite restrictive with regards to purchasing additional licenses + the ability to be able to license a lab for multi-use by students is a must.

    Subscription modelling aside, there really needs to be a better way to control a shared license that doesn't involve having to revoke all licenses on mass. Even with a surplus of licenses, if a lab has 25 computers in it you would need just as many licenses in surplus just to get around the need to replace 1 hardware failure/license revoktion without waiting 7 days. It seems completely illogical/ results in what would probably equate to hours of work to get the lab working properly again.

     

    T
    Test Screen Name
    Legend
    April 23, 2021

    "you would need just as many licenses in surplus" I don't see it that way. I'd have some spare licenses, and just assign them as needed to replace broken kit. Holding spare licenses against hardware failure is a common requirement, to avoid the downtime of applying for a license transfer, both at the desktop and the server end.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices