As the title suggests, I'm reaching out to others in the community managing large environments (several hundred to thousands of users/endpoints) to understand how they are (or have been) handling the transition from volume license/volume serialization keys to named user licensing or deployments (NUD).
Our organization is federated with Adobe, licenses have been allocated and all that works well.
But for the corporate environment the NUD process isn't silent. In fact, it's intrusive since a corporate user has to do something on a corporate machine in order to be allocated a license:
- User launches Acrobat
- Splash screen displayed
- Acrobat launches behind splash screen
- Acrobat closes
- Adobe Sign-in window
- User enters their user principal name (UPN)
- As soon as they press TAB or click into the password field they're redirected to the identity provider
- There are 1-2 more redirections
- Eventually the user is allocated a license and they click a button to complete it.
- Acrobat launches
I'm struggling to come to terms that all of our corporate users on corporate machines are going to have to do this.
It would be nice if Acrobat behaved similarly to Office 365: The UPN is silently retrieved and the application 'figures it out' (aka steps 7 through 9) behind the scenes without requiring user intervention, unless something went wrong at which point the user would be prompted.
How are you doing it?
AdChoices