Kasutusjuhend Tühista

Shared Device Licensing | Deployment guide

Otsi

Viimati uuendatud 28. juuni 2023 | Kehtib samuti Packager

Enterprise

Admin Console

Adobe ettevõtetele ja meeskondadele: administreerimisjuhend
Juurutamise planeerimine
1. Põhimõisted
2. Juurutamisjuhised
3. Creative Cloud haridusasutustele – juurutamine
Oma organisatsiooni seadistamine
1. Identiteeditüübid | Ülevaade
2. Identiteedi seadistamine | Ülevaade
3. Organisatsiooni seadistamine Enterprise ID-ga
4. Azure AD föderatsiooni ja sünkroonimise seadistamine
5. Google'i föderatsiooni ja sünkroonimise seadistamine
6. Organisatsiooni seadistamine Microsoft ADFS-iga
7. Organisatsiooni seadistamine piirkonna portaalide ja LMS-i jaoks
8. Organisatsiooni seadistamine koos teiste identiteedi pakkujatega
9. SSO levinud küsimused ja tõrkeotsing
Teie organisatsiooni seadistamise haldamine
Kasutajate haldamine
1. Ülevaade
2. Administratiivsed rollid
3. Kasutajate haldamise strateegiad
4. Litsentside määramine Teamsi kasutajale
5. Rakendusesisene kasutajate haldamine meeskondade jaoks
  1. Meeskonna haldamine Adobe Expressis
  2. Meeskonna haldamine Adobe Acrobatis
6. Ühtivate e-posti domeenidega kasutajate lisamine
7. Kasutaja identiteedi tüübi muutmine
8. Kasutajarühmade haldamine
9. Kataloogi kasutajate haldamine
10. Arendajate haldamine
11. Olemasolevate kasutajate migreerimine Adobe Admin Console'i
12. Kasutajate haldamise migreerimine Adobe Admin Console'i
Toodete ja õiguste haldamine
1. Toodete ja tooteprofiilide haldamine
2. Jagatud seadmete litsentside haldamine
Global Admin Console'iga alustamine
Salvestusruumi ja varade haldamine
1. Salvestusruum
2. Varade migratsioon
3. Varade tagasinõudmine kasutajalt
4. Üliõpilaste varade migratsioon | ainult EDU
  1. Automaatne üliõpilaste varade migratsioon
  2. Teie varade migratsioon
Teenuste haldamine
1. Adobe Stock
2. Kohandatud fondid
3. Adobe Asset Link
4. Adobe Acrobat Sign
5. Creative Cloud ettevõtetele – tasuta liikmesus
  1. Ülevaade
Rakenduste ja uuenduste juurutamine
1. Ülevaade
2. Pakettide loomine
  1. Rakenduste pakendamine Admin Console'i kaudu
  2. Nimeliste kasutajate litsentsipakettide loomine
  3. Eelgenereeritud pakettide haldamine
    1. Adobe mallide haldamine
    2. Üksikrakenduse pakettide haldamine
  4. Pakettide haldamine
  5. Seadmete litsentside haldamine
  6. Seerianumbrite litsentsimine
3. Pakettide kohandamine
  1. Creative Cloudi töölauarakenduse kohandamine
  2. Laienduste kaasamine teie paketti
4. Pakettide juurutamine
5. Uuenduste haldamine
  1. Adobe ettevõtte ja meeskondade klientide muutuste haldamine
  2. Uuenduste juurutamine
6. Adobe Update Server Setup Tool (AUSST)
7. Adobe Remote Update Manager (RUM)
  1. Väljalaskemärkmed
  2. Adobe Remote Update Manageri kasutamine
8. Tõrkeotsing
  1. Creative Cloudi rakenduste installimise ja deinstalleerimise vigade tõrkeotsing
  2. Klientide masinate päring, et kontrollida, kas pakett on kasutusele võetud
Meeskonnakonto haldamine
Uuendamised
1. Meeskonnaplaanide liikmesus: uuendamine
2. Ettevõtte VIP: uuendamised ja nõuetele vastavus
Lepingute haldamine
Aruanded ja logid
Abi saamine

What is Shared Device Licensing

Manage Shared Device licenses in the Adobe Admin Console | YouTube video

Shared Device Licensing is a licensing model to deploy and manage Adobe applications in labs and shared device setups, where multiple users use the devices and applications. The software license is assigned to a device or computer instead of an individual. Shared Device Licensing is ideal for computers in your labs or classrooms. Shared Device Licensing is not designed for use on machines used by dedicated users. For dedicated users, we recommend you deploy named-user licenses.

Shared Device Licensing versus Named User Licensing

While Named User Licensing associates the license with the user, Shared Device Licensing associates the machine. So, when you launch a named user licensed app, the license is validated against the user name and password. When you launch a shared device licensed app, the license is validated against the machine on which the app is license is installed. This implies that a named user licensed app can be activated on any machine as long as the user name and password are validated. While shared device licensed apps will only activate on a machine on which the license is installed.

Read more about Adobe's licensing methods.

End-user experience

When users launch an app on a shared device, they’re prompted to sign in with their credentials. Apps only launch after a successful sign-in. The required credentials depend on how you have set up identity in your institution.

The sign-in screen warns users to sign out of Creative Cloud after they're done. Also, users should not store any assets on this shared device.

A shared device license does not directly entitle a user to access any services such as storage, libraries, fonts, or Adobe Stock, among others. However, if the user account has these entitlements, these services are available.

Märkus.

While shared device licenses do not have specific system requirements, ensure that your end-user machines meet the system requirements of the installed Creative Cloud applications. See the Creative Cloud system requirements. Also, for details on any installation errors, see Product Installation Error/Exit Codes.

Granular access to apps

IT admins can create packages and deploy the apps to computers. Shared Device Licensing provides several tools that allow you to control user access to apps: Identity, Access Policy, Egress IP addresses, and Associated Machines. You can use a combination of these options to prevent unauthorized usage of the apps and protect your student accounts and the assets created by them.

Identity

Enterprise ID or Federated IDs are owned by the organization or school and the organization legally owns all data. K-12 schools are required to use Enterprise or Federated IDs. You can also use these IDs if you want to exercise tighter control on who can access the apps. To use Enterprise or Federated IDs, if you haven’t already done so, you must set up identity.
Adobe IDs are owned by the users, and the user or the organization legally owns any data depending on the account profile. K-12 schools are required to use Enterprise ID or Federated ID. However, higher-education institutes may use Adobe ID, Enterprise ID, or Federated ID.

For more information, see the identity Types supported on the Admin Console.

Access policy

You can choose Open Access to enable anyone to access the apps on a shared device. All users need is a valid account of any of the types described above, a personal account (Adobe ID) or an enterprise account. Users can even sign up for a free Adobe ID and access the apps. Use Open Access for open labs where the general public, visiting students and staff, and our students access the labs and the apps. For example, shared machines in your public, on-campus library or if you use the lab to provide continued education after hours.
Choose Organization user only to limit access to users you have added to the Admin Console. These users could be of any type of ID which is supported on the admin console. This option is useful if you want to provide limited access to approved students and staff only. For example, a lab at a higher education institution, where users may have any supported identity type.
Choose Enterprise/Federated users only, to restrict access to Enterprise users only. Signing in with personal Adobe IDs does not enable access to the apps. This option is useful to restrict access to Enterprise users only. For example, in a K-12 lab use this option to authorize minor students to access the apps and services.

Egress IPs

Egress IP addresses or ranges prevent access to apps if users connect from outside your approved computer networks. This is especially useful, if you use portable computers and can restrict the apps to run only when they’re connected to a lab or school network. Using the apps from outside your labs or school network is not allowed.

Use this option to specify external IP address ranges. This is the Internet-facing IP address behind which the workstations are connected. You can use this to prevent access to applications if these workstations are used from a different network. You may have to modify the setting periodically if your Internet connection does not have a static IP address.

Associated Machines

You can use the Associated Machines section to define how to segment groups of machines into different product profiles.

Choose By Microsoft Active Directory organizational units to ensure all machines that belong to a listed organizational unit are associated with a product profile. If for example, your institution has created organizational units based on department, you can create product profiles for each department. Machines that belong to a department will be associated to a specific product profile.
Choose By LAN IP address range to ensure that all machines within the listed LAN IP address ranges are associated with a product profile. For example, choose this option if your computer labs or shared computers in a library are organized by defined LAN IP ranges.
Choose By installed package to ensure that all machines with the selected packages are associated with a product profile.

Märkus.

The associated machine options are applied in the listed order of priority.

Say profile A is configured with Active Directory OU = Library and profile B is configured with Package = Video apps. A machine in the Library OU and with the Video apps package, will be associated with profile A and not with profile B.

Migrate to Shared Device Licensing

Märkus.

If you're a new customer, you can skip this section.

Migrate from device licenses

If you’re an existing Device Licensing customer, Adobe provides you a complimentary upgrade to Shared Device Licensing. The older Device Licensing program does not provide access to the latest version of Creative Cloud apps. For access to the latest version of Creative Cloud apps, you can migrate your older device licenses to the new shared device licenses. Post migration, your older apps will continue to work for 30 days, within which you can set up and deploy the latest apps using shared device licenses.

Migrate from serial number licenses

If you’re using the legacy Serial Number Licensing to manage your lab computers, you can continue to use the older apps until the serial numbers become invalid. If you deploy a shared device license package alongside a serial number package, both will continue to work. You can continue to use the older apps until the serial number licenses expire, or you can uninstall the serial number licensed apps and deploy a new shared device license package.

Märkus.

The above migrations are one way. So, once you complete the migration process from device or serial licenses to shared device licenses, you cannot then go back to either device or serial licenses.

Begin your Deployment

Once you’ve determined the machines to deploy the Creative Cloud apps, you can start your deployment. Depending on your access requirements and current setup, you may perform some of the following actions. We recommend that you read this document completely before starting the deployment to have all the required information ahead of time.

1. Set up Identity

If you haven’t already done so, you’ll start with setting up identity to enable Enterprise or Federated IDs.
You’ll need to demonstrate ownership of the domain (for example: @school.edu) to complete this step.
You may need to contact the person who manages your institution’s website or emails to complete this activity.

Adobe recommends that you use Enterprise or Federated IDs to provide access to regular students or lab users. These identity types provide your organization better control and monitoring.

For step-by-step instructions, see Set Up Identity.

Before you proceed, we recommend that you see the following videos on setting up identity for Shared Device Licensing:

Note: The content and voice-over for this video is currently available in English only.

2. Manage admins

The primary admin for your institution on the Admin Console is a System admin. The system admin has the rights to perform all tasks on the Admin Console. However, it's always a good idea to delegate tasks to other admins. This decentralizes the admin tasks and specialized tasks are then performed by the roles that most fit those tasks.

Create Product admins to create product profiles and add users to the organization.
Create Product profile admins to manage product profiles and add users to the organization.

See how to manage admin roles on the Admin Console.

3. Add users to the Admin Console

If you plan to configure your shared devices to be accessible by Organization users only, you must add these users to the Admin Console.

You can manually add users, bulk upload users using a CSV file, or set up the User Sync Tool (for large organizations).

For more details, see Manage users.

Note: The content and voice-over for this video is currently available in English only.

4. Create packages

In the Admin Console, navigate to the Packages tab to create shared device license packages.

For step-by-step instructions, see Create shared device license packages.

Märkus.

As a user in a Named User Licensing education lab, you may encounter the error: Unable to verify subscription/Trial error after updating your Adobe XD application to version 50 or above. You will need to create and install a new Shared Device Licensing package from the Admin Console to resolve this issue. This is applicable on both Windows and macOS.

Note: The content and voice-over for this video is currently available in English only.

5. Create product profiles

If you plan to deploy shared device licenses in multiple labs to your institution, you can map each lab to a different product profile on the Admin Console.

For example, you can create a product profile for labs to be unrestricted, so that anyone can use Adobe apps, even users without a school account. Also, you can create product profiles for other labs where access to the installed applications must be restricted to users with a school account. And, you can restrict access to the applications installed in these labs based on the access policies defined on the corresponding product profiles.

For details, see how to manage shared device license profiles.

Note: The content and voice-over for this video is currently available in English only.

6. Define access policy

Shared device configurations provide three options to control user access to apps: Access Policy, Egress IP addresses, Associated Machines. You can use a combination of these options to prevent unauthorized usage of the apps and protect your student accounts and the assets created by them.

For more details, see Shared device configuration.

7. Deploy packages

After you create the shared device license package, set up the devices in your lab with the license.

Choose from the following methods to deploy the package:

Use the following third-party tools:
Install by double-clicking the package file. Learn more.
Deploy using command line on Windows computers. Learn more.
Deploy using Info.plist file on macOS computers. Learn more.

For details on troubleshoot Creative Cloud apps installation and uninstallation errors, see this document.

What's next

Add products and licenses

If you are a VIP (Value Incentive Plan) customer, you can purchase products or additional shared device licenses from the Admin console directly.

In the upper-right corner of the Overview page of the Admin Console, click Buy More.

In the Add Products screen, add products or add licenses to your existing products.

Recover unused licenses

If you deploy shared device licenses to machines and those machines are no longer in use, the licenses are still consumed and you can't use them on other machines. The machines used status is displayed on the product card in the Products tab.

To recover licenses on unused machines, go to the Admin Console and reset the product profile that is mapped to the unused machines. See this document for details on how to recover shared device licenses.

Frequently asked questions

To recover a license from an inoperable machine, you'll need to reset the licenses of all machines of that product profile.

However, to recover the license from machine to which you have access, you can deactivate the license on that machine itself.

No. Shared device license packages cannot be installed on virtual machines.

No. Currently, Adobe's SSO setup doesn't support passthrough authentication. Even if you have set up Federated identity, students have to sign in to the machine and then reenter their credentials when signing in to Creative Cloud.

Your IT department determines if the users are allowed to do so on the lab machines, by setting the appropriate user access policy.

If the user access policy is set to Open Access, the users can use any Adobe ID to sign in. If they have more than one account, each account's storage is unique.

If your question is not answered here, see the complete Shared Device Licensing FAQ.

And if you have more questions, ask them on our community.

Saage abi kiiremini ja hõlpsamalt

Uus kasutaja?

Shared Device Licensing | Deployment guide

What is Shared Device Licensing

Shared Device Licensing versus Named User Licensing

End-user experience

Granular access to apps

Identity

Access policy

Egress IPs

Associated Machines

Migrate to Shared Device Licensing

Migrate from device licenses

Migrate from serial number licenses

Begin your Deployment

1. Set up Identity

2. Manage admins

3. Add users to the Admin Console

4. Create packages

5. Create product profiles

6. Define access policy

7. Deploy packages

What's next

Add products and licenses

Recover unused licenses

Frequently asked questions

Saage abi kiiremini ja hõlpsamalt

Küsige kogukonnalt

Võtke meiega ühendust