Planning to deploy
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage products and entitlements
- Manage users
- Administrative roles
- User management techniques
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Manage products and product profiles
- Manage products
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage users
- Manage storage and assets
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
- About Creative Cloud Packager
- Creative Cloud Packager release notes
- Application packaging
- Create packages using Creative Cloud Packager
- Create named license packages
- Create packages with device licenses
- Create a license package
- Create packages with serial number licenses
- Packager automation
- Package non-Creative Cloud products
- Edit and save configurations
- Set locale at system level
- Manage your account
- Manage your Teams account
- Assign licenses to a Teams user
- Add products and licenses
- Automated expiration stages for ETLA contracts
- Switching contract types within an existing Adobe Admin Console
- Purchase Request compliance
- Value Incentive Plan (VIP) in China
- VIP Select help
- Reports & logs
- Get help
Before you create packages, you need to do a good deal of thinking and planning. This article gives you all the information you need for that planning. There are several steps to your planning process:
- Identifying your user groups and their application needs.
- Identifying the packages you need to create to install those applications for those users, and deciding how you will deploy the packages.
The sections in this article address each one of these planning steps.
Identifying user groups and their needs
You will need one or more deployment packages for every unique user group in your enterprise. Your first planning step is to identify each user group that needs a particular application or set of applications to do their job. If you or someone else at your company has already purchased the Creative Cloud for teams subscription, this step has undoubtedly already been done, but it may or may not be written down in a form useful to you at this stage in planning.
At this point, you want to identify the following:
- Group name: Identify each user group that will use the software subscription. The labels you choose to identify your user groups are for your own use only; they are not included anywhere in the deployment package, and so there are no restrictions on how you name them.
- Primary applications needed: For each user group, create a list of applications people in that group need to do their jobs.
- Product: Identify the product(s) that provide the applications you have listed. This list should consist of point product and/or suite product names.
- Platform: Identify the platform for each product (Windows or Mac OS, or both).
Making your package list
After you have a complete list of user groups and the applications each one needs to do their jobs, you are ready to determine how many packages you need to deploy those applications for those users. To determine your package count and what each one should contain, you need to understand a few concepts about Adobe product and package design.
Calculate your package count
If you have chosen only one platform, your package count is 1. If you have chosen both platforms, your package count is 2. You can record these numbers in the package count column of the example planning sheet shown later in the article.
Name each package
You are now ready to name your packages. Choose a brief but descriptive name for each package on your list. If you have Mac OS and Windows versions of the same package, you may want to choose a common package name and append “Win” or “Mac” to the name. Whatever name you choose, it should allow you to easily identify that package with its intended user group and usage.
Since the package name is used to name the folder on your system that will contain the package files, the same operating system constraints that apply to folder names also apply to the package names you choose.
An example planning sheet
To list all the information at one place, you can create an example planning sheet as shown below.
Primary applications needed
Photoshop, Illustrator, InDesign
Dreamweaver, Flash, Fireworks
Влезте във вашия акаунт