Copy link to clipboard
Copied
Hi,
We have just federated against Adobe and tried to migrate our existing device license to the Creative Cloud All Apps for HED - Shared Device section of the new CC admin console. We generated the deployment package in the admin console and then deployed this to the machine with the old device license.
All installed but when started the program gives the error dialog: Sorry, Your account is not valid on this device. Please Try again with a School ID.
I thought that this being a device license it wouldn't need to login. The CC Admin console on the adobe site doesn't show the device as having checked out or activated the license, it just says 0/5 (in our case we only have 5 device licenses).
It sounds to me like something is wrong with our federated setup but not sure what
Is there something we can check to determine what may be wrong?
Many thanks for any replies,
Martin Searle
University of Kent, UK
Just to be clear, you've deployed the CC 2019 apps and are getting an error when users sign in? I'd start with checking the Shared device configuration : user access policy. For example, if you're using Org user only, you'll need to add users to the Admin Console. try toggling this setting and see if the issue is here.
Copy link to clipboard
Copied
Hi Martin,
Shared device licensing requires students to login in using any of the following: Adobe ID, Enterprise ID or Federated ID. K-12 users must login with Enterprise or Federated ID.
Currently, Adobe's SSO setup doesn't support passthrough authentication. Even if you have set up Federated identity, users will have to login to the computer and then re-enter their credentials when logging in to Creative Cloud.
For more details please read the following: Shared device license FAQ.
Let us know if you have any more queries.
Copy link to clipboard
Copied
Just to be clear, you've deployed the CC 2019 apps and are getting an error when users sign in? I'd start with checking the Shared device configuration : user access policy. For example, if you're using Org user only, you'll need to add users to the Admin Console. try toggling this setting and see if the issue is here.