Kasutusjuhend Tühista

Create Shared Device Licensing packages

  1. Adobe ettevõtelele ja meeskondadele: administreerimisjuhend
  2. Juurutamise planeerimine
    1. Põhimõisted
      1. Litsentsimine
      2. Identiteet
      3. Kasutajate haldamine
      4. Rakenduste juurutamine
      5. Admin Console'i ülevaade
      6. Administraatori rollid
    2. Juurutamisjuhised
      1. Nimeliste kasutajate juurutamisjuhend
      2. SDL juurutamisjuhend
      3. Adobe Acrobati juurutamine 
    3. Creative Cloud haridusasutustele – juurutamine
      1. Juurutamisjuhend
      2. Adobe rakenduste kinnitamine Google Admin Console'is
      3. Adobe Expressi lubamine Google Classroomis
      4. Integratsioon Canvas LMS-iga
      5. Integratsioon Blackboard Learniga
      6. SSO konfigureerimine piirkonna portaalide ja LMS-ide jaoks
      7. Adobe Expressi juurutamine läbi Google'i rakenduste litsentsimise
      8. Kasutajate lisamine nimekirja sünkroonimise kaudu
      9. Kivuto KKK
      10. Esmaste ja teiseste asutuste õiguste suunised
  3. 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
      1. SSO seadistamine Microsoftiga Azure OIDC kaudu
      2. Azure'i sünkroonimise lisamine oma kataloogi
      3. Hariduse rollide sünkroonimine
      4. Azure Connectori KKK
    5. Google'i föderatsiooni ja sünkroonimise seadistamine
      1. SSO seadistamine Google'i föderatsiooniga
      2. Google Synci lisamine teie kataloogile
      3. Google'i föderatsiooni KKK
    6. Organisatsiooni seadistamine Microsoft ADFS-iga
    7. Organisatsiooni seadistamine piirkonna portaalide ja LMS-i jaoks
    8. Organisatsiooni seadistamine koos teiste identiteedi pakkujatega
      1. Kataloogi loomine
      2. Domeeni omandiõiguse kontrollimine
      3. Domeenide lisamine kataloogidele
    9. SSO levinud küsimused ja tõrkeotsing
      1. SSO levinud küsimused
      2. SSO tõrkeotsing
      3. Hariduse levinud küsimused
  4. Teie organisatsiooni seadistamise haldamine
    1. Olemasolevate domeenide ja kataloogide haldamine
    2. Automaatse konto loomise lubamine
    3. Organisatsiooni seadistamine kataloogi usalduse kaudu
    4. Üleminek uuele autentimise pakkujale 
    5. Varade sätted
    6. Autentimise sätted
    7. Privaatsuse ja turvalisuse kontaktid
    8. Konsooli sätted
    9. Krüpteerimise haldamine  
  5. Kasutajate haldamine
    1. Ülevaade
    2. Administratiivsed rollid
    3. Kasutajate haldamise meetodid
      1. Kasutajate individuaalne haldamine   
      2. Mitme kasutaja haldamine (hulgi CSV)
      3. Kasutajate sünkroonimisvahend (UST)
      4. Microsoft Azure'iga sünkroonimine
      5. Google'i föderatsiooniga sünkroonimine
    4. Kasutaja identiteedi tüübi muutmine
    5. Kasutajarühmade haldamine
    6. Kataloogi kasutajate haldamine
    7. Arendajate haldamine
    8. Olemasolevate kasutajate migreerimine Adobe Admin Console'i
    9. Kasutajate haldamise migreerimine Adobe Admin Console'i
  6. Toodete ja õiguste haldamine
    1. Toodete ja tooteprofiilide haldamine
      1. Toodete haldamine
      2. Ettevõtte kasutajate tooteprofiilide haldamine
      3. Automaatse määramise reeglite haldamine
      4. Tootetaotluste läbivaatamine
      5. Iseteeninduse poliitikate haldamine
      6. Rakenduste integratsioonide haldamine
      7. Toodete õiguste haldamine Admin Console'is  
      8. Teenuste lubamine/keelamine tooteprofiili jaoks
      9. Üks rakendus | Creative Cloud ettevõtetele
      10. Valikulised teenused
    2. Jagatud seadmete litsentside haldamine
      1. Mis on uut
      2. Juurutamisjuhend
      3. Pakettide loomine
      4. Litsentside taastamine
      5. Profiilide haldamine
      6. Litsentsimise tööriistakomplekt
      7. Jagatud seadmete litsentsimise KKK
  7. Salvestusruumi ja varade haldamine
    1. Salvestusruum
      1. Ettevõtte salvestusruumi haldamine
      2. Adobe Creative Cloud: salvestusruumi uuendamine
      3. Adobe salvestusruumi haldamine
    2. Varade migratsioon
      1. Automatiseeritud varade migratsioon
      2. Automatiseeritud varade migratsiooni KKK  
      3. Ülekantud varade haldamine
    3. Varade tagasinõudmine kasutajalt
    4. Üliõpilaste varade migratsioon | ainult EDU
      1. Automaatne üliõpilaste varade migratsioon
      2. Teie varade migratsioon
  8. Teenuste haldamine
    1. Adobe Stock
      1. Adobe Stocki krediidipaketid meeskondadele
      2. Adobe Stock ettevõtetele
      3. Adobe Stock ettevõtetele kasutamine
      4. Adobe Stocki litsentside heakskiitmine
    2. Kohandatud fondid
    3. Adobe Asset Link
      1. Ülevaade
      2. Kasutajarühma loomine
      3. Adobe Experience Manageri varade konfigureerimine
      4. Adobe Asset Linki konfigureerimine ja installimine
      5. Varade haldamine
      6. Adobe Asset Link XD jaoks
    4. Adobe Acrobat Sign
      1. Adobe Acrobat Signi seadistamine ettevõtte või meeskondade jaoks
      2. Adobe Acrobat Sign – meeskonna funktsiooni administraator
      3. Adobe Acrobat Signi haldamine Admin Console'is
    5. Creative Cloud ettevõtetele – tasuta liikmesus
      1. Ülevaade
  9. Rakenduste ja uuenduste juurutamine
    1. Ülevaade
      1. Rakenduste ja uuenduste juurutamine ja tarnimine
      2. Juurutamise planeerimine
      3. Juurutamise ettevalmistus
    2. Pakettide loomine
      1. Rakenduste pakendamine Admin Console'i kaudu
      2. Nimeliste kasutajate litsentsipakettide loomine
      3. Adobe pakettide mallid
      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 
      1. Pakettide juurutamine
      2. Adobe pakettide juurutamine Microsoft Intune'i abil
      3. Adobe pakettide juurutamine SCCM-iga
      4. Adobe pakettide juurutamine ARD-ga
      5. Toodete installimine erandite kausta
      6. Creative Cloudi toodete desinstallimine
      7. Adobe provisioning toolkit enterprise editioni kasutamine
      8. Adobe Creative Cloudi litsentsimistunnused
    5. Uuenduste haldamine
      1. Adobe ettevõtte ja meeskondade klientide muutuste haldamine
      2. Uuenduste juurutamine
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST ülevaade
      2. Sisemise uuenduste serveri seadistamine
      3. Sisemise uuenduste serveri haldamine
      4. AUSST tavalised kasutusjuhud   
      5. Sisemise värskenduste serveri tõrkeotsing
    7. Adobe Remote Update Manager (RUM)
      1. Adobe Remote Update Manageri kasutamine
      2. Kanalitunnused Adobe Remote Update Manageriga kasutamiseks
      3. RUM-i vigade lahendamine
    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
      3. Creative Cloudi paketi veateade „Installimine ebaõnnestus”
    9. Pakettide loomine Creative Cloud Packageriga (CC 2018 või varasemad rakendused)
      1. Teave Creative Cloud Packageri kohta
      2. Creative Cloud Packageri väljalaskemärkused
      3. Rakenduste pakendamine
      4. Pakettide loomine Creative Cloud Packageri abil
      5. Nimeliste litsentsipakettide loomine
      6. Pakettide loomine seadme litsentsidega
      7. Litsentsipaketi loomine
      8. Pakeetide loomine seerianumbri litsentsidega
      9. Pakendaja automatiseerimine
      10. Mitte-Creative Cloudi toodete pakendamine
      11. Konfiguratsioonide muutmine ja salvestamine
      12. Süsteemi tasandil lokaadi määramine
  10. Teie konto haldamine
    1. Meeskonnakonto haldamine
      1. Ülevaade
      2. Makseandmete uuendamine
      3. Arvete haldamine
      4. Lepinguomaniku muutmine
      5. Edasimüüja muutmine
    2. Litsentside määramine Teamsi kasutajale
    3. Toodete ja litsentside lisamine
    4. Uuendamised
      1. Meeskonnaplaanide liikmesus: uuendamine
      2. Ettevõtte VIP: uuendamised ja nõuetele vastavus
    5. ETLA lepingute automatiseeritud aegumise etapid
    6. Lepingutüüpide vahetamine olemasolevas Adobe Admin Console'is
    7. Ostutaotluse nõuetele vastavus
    8. Value Incentive Plan (VIP) Hiinas
    9. VIP Select abi
  11. Aruanded ja logid
    1. Auditilogi
    2. Määramise aruanded
    3. Sisulogid
  12. Abi saamine
    1. Ühenduse võtmine Adobe klienditeenindusega
    2. Meeskonnakontode tugivõimalused
    3. Ettevõtluskontode tugivõimalused
    4. Experience Cloudi tugivõimalused

Introduction

Shared Device License is a licensing method targeted at educational institutions where software is assigned to a device instead of an individual. Anyone who logs on to the device will have access to Adobe's products and services. This method of licensing is ideal for desktop computer labs and classrooms.

For more details, see Licensing overview.

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

How to create Shared Device Licensing 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.

To learn how to create packages for Shared Device Licensing, follow the instructions:

  1. Log in to the Admin Console and navigate to Packages > Packages. The history of all packages created by all admins in your organization is displayed.

    If you have not created any packages as yet, you are presented with the following screen to help you get started.

  2. Click Create a Package.

  3. Select Shared Device Licensing from the given licensing options that are displayed on your screen, and click Next.

    Choose licensing method

  4. On the Entitlements screen, choose the required entitlement and click Next.

  5. On the Configure screen, select the required options and then click Next.

    • Choose a Platform: Choose the operating system and the processor support from the following:
      • macOS (Universal)
      • macOS (Intel)
      • macOS (Apple Silicon)
      • Windows (64-bit)
      • Windows (32-bit)
      • Windows (ARM)
    Märkus.

    A package made for one operating system and architecture type, cannot be deployed on another.

    • It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
    • It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.

     

    • Language: Select the language in which you want to create the package.
    • Use OS Locale: Enables you to create a package that deploys in the OS language of client machine. When not available, the OS language is the default fallback language in which the package is deployed.
  6. On the Choose Apps screen, click the plus icons next to the applications to include them in the package.

    Choose applications

    Märkus.

    If you add a product that has dependent products, the dependent products are added automatically. For example, if you add Photoshop, the dependent products Camera Raw and Adobe Preview are added automatically.

    Optionally, you can filter down the list of Available Applications to choose from.

    Latest versions: Display the latest version of all available applications.

    Long-term supported versions: Display Adobe's long-term supported versions. To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy

    Beta apps: Display available beta apps. Learn more.

    Older versions: Display a list of previous versions of the apps. View versions that don't receive security or feature updates.

    Filter available applications

    App Add-ons: Certain Adobe apps come with Add-ons. So, when you add an app that includes one or more Add-ons, you have the option to include the add-ons in the package you're creating. By default, Add-ons are not included in the package.

    App Add-ons

    After you're done with your selections, click Next.

  7. (Not currently available for Windows ARM devices) On the Choose Plugins screen, search and select plug-ins to include in the package, and click Next.

    You can select the Show Compatible Plugins Only check box to display the plug-ins that are compatible with the apps in the package. This filter doesn't appear if you only have the Creative Cloud desktop app in your package.

    To view the list of selected plug-ins, click Selected Plugins.

    Märkus.

    The plug-ins that you include in the package do not necessarily need the supporting application to be part of the same package. You can include plug-ins and extensions for apps that are previously installed on your users' computers. Also, if a computer does not have the targeted application for a plug-in, the plug-in is not installed on the computer.

    Choose plugins

  8. On the Options screen, select or enable the required options and then click Next.

    Märkus.

    Starting December 11, 2023, new users and organizations will not be entitled to Creative Cloud Synced files. Starting February 1, 2024, Creative Cloud Synced files will be discontinued for personal accounts that existed before December 11, 2023 (learn more here). Starting October 1, 2024, Creative Cloud Synced files will be discontinued for business accounts associated with organizations that existed before December 11, 2023 (learn more here).

    Creative Cloud Desktop Options:

    • Enable self-service install: Allow users to install and update applications from App panel on the Creative Cloud desktop app.
    • Allow non-admin to update and install apps: Enables the self-service end users, who do not have Administrative privileges, to install and manage their applications and updates.
    • Disable auto-update for end users: Ensure that end users will not be able to automatically update their applications via the Creative Cloud Desktop app. Learn more.
    • Disable file syncing: Suppress the automatic syncing of files to client systems. Useful when you are installing packages in a test environment where you want to suppress file syncing. Available only to educational institutions.
    Hoiatus.

    Certain Creative Cloud desktop apps require you to keep file syncing enabled.

    If you disable file syncing:

    • All apps load.
    • Creative Cloud files are not synced. It also applies, for example, to media files in Adobe Premiere Rush projects.
    • Adobe Fonts are available.
    • Adobe Stock search is available (however, Federated IDs are unable to download previews)

    • Enable browser-based login: By default, users must sign in using the Creative Cloud desktop app. However, you can choose to redirect users to sign in via the browser. Choose this option to ensure users sign-in via the browser. For details, see Enable browser-based login.
    • Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop application. This means that end users can then go to the Creative Cloud Desktop application and install or update these apps. Learn more.

    Management Options:

    • Enable Remote Update Manager: Enables the use of Remote Update Manager. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. For more information, see Use Adobe Remote Update Manager.
    • Redirect to internal update server: Enables you to redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
    • (Not currently available for Windows ARM devices) Create a folder for extensions and include the UPIA command-line tool: Enables you to create a subfolder in your package folder that you can use to include extensions that you want to install with the package. For more, see Manage Extensions in packages.
    • Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. For more, see the Preferences section of thePackaging apps via the Admin Console article.
  9. On the Finalize screen, enter the name of the package, and then click Create package.

    You can also review the included applications and configuration for this package before building the package.

    Build a package

    It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.

    Building Package Message

    Märkus.

    To check the remaining time for the existing packages in the details pane, click  for the package.

  10. The build status of the package is displayed in the Status column on the Packages page.

    If the package is built successfully, it displays the Download link in the Actions column.

    Packages Status

    Märkus.

    A package is available in the Admin Console for up to three days. To check the time remaining to download the package, click  to the right of the package name. It displays the package details.

Caution

If the package that you've created, contains one or more apps that have been rolled back owing to a bug or issue which needs to be fixed, this package displays as Revoked. You will be unable to download this package.

Also, if you have previously downloaded a package that contains a revoked app, you should not deploy it. You should create and deploy a new package with a non-revoked version of the app. 

Revoked package

The downloaded package file is a .zip file format.

If you double-click to unzip the package file, you may encounter the following, Unable to expand error on macOS 10.14 and prior versions.

This is because the macOS Archive Utility does not support the unzipping of large files that are zipped using the Zip64 mode.

Error 1 - Operation not permitted

To unzip the file, open the terminal in the folder where you've downloaded the file and run the unzip command:

unzip <file name>.zip

Märkus.

If you are creating macOS packages, the Adobe Package Downloader is downloaded to your computer. Open and run to complete download of package. For further details, see here.

Packageinfo.txt

The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:

  • Package Name
  • Package Type - Self Service or Managed
  • Platform
  • Locale
  • Creative Cloud Desktop application version
  • Package Configurations
    • Remote update manager - Enabled or Disabled 
    • App Panel - Enabled or Disabled
    • Beta App Download - Enabled or Disabled
    • Browser Based Auth - Enabled or Disabled
    • Files Panel - Enabled or Disabled
    • Use OS Locale - Enabled or Disabled

The PackageInfo.txt file is for informational purposes only.

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:

  • Deploy using Info.plist file on macOS computers. See this document for details.

Deploy updates

Adobe regularly ships updates and new release to its Creative Cloud apps. This way, your students, and staff can access the latest features of apps that you deployed to the shared devices in your labs and classrooms. To get the latest Creative Cloud updates, choose one of the following methods:

  • You can create an update package and deploy it manually on the client machines.
  • Or, you can use Remote Update Manager, which uses the Adobe Update Server. Alternatively, use an internal update server and deploy the latest updates available on update server to each device on which it is run. You don't have to manually push updates to the individual devices.

Uninstall products and licenses

While you create and deploy packages to client machines, you might also require to remove previously installed products and licenses. For example, if your organization migrated from Shared Device Licensing to Named User Licensing, uninstall all the products and licenses previously installed on the machine. Also, there's often the case when client machines may contain multiple versions of apps. Or, may be using conflicting licenses. Client machines, may be consuming extra licenses, which are not returned to the deployment pool.

In all these scenarios, we recommend that you use one of these procedures to uninstall the products and / or licenses on the client machines:

 Adobe

Saage abi kiiremini ja hõlpsamalt

Uus kasutaja?