某些 Creative Cloud 应用程序、服务和功能在中国不可用。
InDesign Server supports creating packages using Online activation method. Online activation method is the simplest licensing method to deploy for versions 15.1.1 and above.
Your license is valid till the contract end date. Information transmitted from Adobe servers: Signed license specific to machine ID.
Learn the steps to create Online activation InDesign Server packages and deploy them. After deploying, you can learn how to remove the licenses, for example, machines that are no longer in use or if you must redeploy the license.
You must have access to the Adobe Admin Console and the new FRL SKUs. If you do not have the FRL SKUs, contact your account manager for assistance.
- Log in to the Admin Console. From the upper-right corner, search and apply the organization that has InDesign Server.
- Navigate to Packages > Packages. The history of all packages created by all admins in your organization is displayed.
3. Click Create a Package.
4. In the screen that appears, select your activation method as Online, and click Next. For more information, see Feature Restricted Licensing - Online.
6. In the System step, select the required options and click Next.
- Choose a Platform: Choose Mac OS or Windows 64-bit operating system.
- 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. In which case, the OS language is the default fallback language in which the package is deployed.
7. In the Choose Apps step, you can choose whether to build a License-only package or a package that also includes the InDesign Server application.
| Type of package | Description | How to... |
|---|---|---|
| License-only package | Create this package if the client machines already have InDesign Server installed. Later, you can simply license the installed application. | From Available Applications, add only the License File to Selected Applications. |
| Apps-only package |
Create this package if the client machine is already licensed with a Feature Restricted Licensing - Online license. Then, install InDesign Server on the machine. | From Available Applications, add InDesign Server to Selected Applications. Don't add the License File. |
| Package containing apps and license |
Create this package to install and license InDesign Server. |
From Available Applications, add InDesign Server and the License File to Selected Applications. |
Select Show older versions to display a list of previous versions of the apps. Enterprise admins can view more versions that don't receive security or feature updates by selecting Available application versions in package preferences (Admin Console > Packages > Preferences). For more information, see Packaging apps using Admin Console.
To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy.
Note| License activation options |
|---|
Choose how clients will send information to Adobe’s licensing servers Authorize Adobe License server by DNS name(default): Allow traffic to pass through your firewall to https://lcs-cops.adobe.io. Authorize Adobe License server by fixed IP address: Allow traffic to pass through your firewall to https://lcs-cops-proxy.adobe.com and the fixed IPs listed in the License activation options screen. The default domain has a non-static IP behind it, while the new domain will point to one among the list of static IPs in the License activation options screen. The second option provides more control to the customer in managing outgoing network traffic. |
| Management options |
|---|
|
9. In the Finalize step, in the Package Name box, enter the name for the package.
Review the included applications and configuration for this package before building the package.
10. Click Build Package.
Watch the build status of the package in the Status column on the Packages pane.
If the package is built successfully, it displays the Download link in the Availability column.
A package is available in the Admin Console for up to three days. To check the time remaining to download the package, click the row item for the package to display the package details.
After you create the Feature Restricted Licensing - Online package, you must set up the end-user machines with the license. To learn more about deploying packages, update or remove licenses and a list of FAQs, see the FRL Deployment Guide.
Note:
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.
After you create a license-only package in the Admin Console, follow these steps to install this license to end-user computers (for Online, Offline, Isolated, or LAN Activation packages):
1. Download the package from the Admin Console.
2. Extract the contents of the package.
The license-only package contains a .json file (that contains the licensing information) and the Licensing Toolkit utility:
- For Windows: adobe-licensing-toolkit.exe
- For macOS: adobe-licensing-toolkit
3. To install the license, run the following commands with admin privileges:
For Windows:
adobe-licensing-toolkit.exe --precondition --install --filePath <absolute path of the .json file>
Short form:
adobe-licensing-toolkit.exe -p -i -f <absolute path of the .json file>
For macOS:
sudo adobe-licensing-toolkit --precondition --install --filePath <absolute path of the .json file>
Short form:
sudo adobe-licensing-toolkit -p -i -f <absolute path of the .json file>
After you create the feature restricted license package, you can install it on your server.
- Install by double-clicking the package file. See this document for details.
- Use third-party tools such as Microsoft System Center Configuration Manager (SCCM), Apple Remote Desktop, or JAMF Casper Suite. See this document for details.
- Deploy using command line on Windows computers. See this document for details.
- Deploy using Info.plist file on macOS computers. See this document for details.
Want to quickly find solutions to install or uninstallation errors? Read the Fix errors installing Adobe apps article.
If you have installed multiple feature restricted licenses to an end-user computer, follow these steps to uninstall all these licenses from that computer.
Follow these steps to remove a license from a computer in the following scenarios:
- If the package is a license-only package.
OR - If the package includes the license and InDesign Server, use the OS specific uninstall procedures such as Add-Remove Programs on Windows.
Follow these steps to update the license usage on the Admin Console.
Note:
To enable connection to the Adobe server, you are required to whitelist the following URL via https:
https://daco.adobe.io/device/registration/sdl/v1
If you remove a feature restricted license for a Online Activation package, the license usage displayed on the Overview tab of the Admin Console is decremented. However, the update on the Admin Console requires an Internet connection to the Adobe licensing server. If you removed the license while unconnected or if an error occurred connecting to the Adobe servers, the updated license usage may not be reflected on the Admin Console.
Online activation is designed to meet the high security requirements of our customers. No PII (User identifiable information) is provided to Adobe. After package installation and upon product launch the client will establish a secure https channel with lcs-cops.adobe.io. The client will send the following information to Adobe as part of the https call:
"npdId": "ID of NGL Preconditioning Data",
"npdPrecedence": "Precedence of NGL preconditioning data",
"asnpTemplateId" : "ASNP Template ID",
"deviceDetails": {
"deviceId": "Device ID",
"osName": "OS Name",
"osVersion": "OS Version",
"currentDate": 1510649774873
},
"appDetails": {
"nglAppId": "NGL App ID",
"nglAppVersion": "NGL App version",
"nglLibVersion": "NGL Lib version",
"currentAsnpId": "Current ASNP Id",
"locale": "en_US"
}
It is important to note that the NPDID is the unique entitlement identifier and also that the Device ID is not the same as machine name. The Device ID is a SHA 256 hash that is created and cannot be reversed.
Yes. There are various services included in the Adobe products. These services will attempt to reach out to the Adobe servers, however, if a connection is not possible then the calls will fail silently. For the purpose of licensing only the above endpoints are required. For a list of all network endpoints please consult this document.
The client will attempt to reach the designated endpoint at random intervals to validate the license however if the endpoint cannot be reached then it will rely on the cached license on the client machine. This means that after the initial activation, if the client is moved to a remote or secure location, then the license will persist on the machine without additional contact to Adobe.
You can also use the licensing toolkit to remove a license from the client. The licensing toolkit can be downloaded on the Adobe Admin Console.
To remove a license with the licensing toolkit you can use the command:
adobe-licensing-toolkit.exe –deactivate
If you want to remove the license of InDesign Server, you can specify the NPID.
Use the licenseInformation command to get the NPID.
For Windows:
adobe-licensing-toolkit.exe --licenseInformation.
Short form: adobe-licensing-toolkit.exe -l
For macOS:
sudo adobe-licensing-toolkit --licenseInformation
Short form: sudo adobe-licensing-toolkit -l
Sample output:
Adobe Licensing Toolkit (1.1.0.83)
License Details
NpdId : NDgyYTYzZGMtNjAwOC00MjNjLTg2NWMtZjUzMGUzZDYwYjQ0
AppId : InDesignServer1
DeploymentMode : FRL_CONNECTED
Operation Successfully Completed.
Use the NPID to remove the license:
adobe-licensing-toolkit.exe --deactivate --npdId <Unique ID of Preconditioning Data described above>
For example:
adobe-licensing-toolkit.exe --deactivate --npdId NDgyYTYzZGMtNjAwOC00MjNjLTg2NWMtZjUzMGUzZDYwYjQ0
License activation for InDesign Server installations on virtual platforms will work assuming the platform is Connected. There may be issues if the virtual machine is rebooted causing a change in the underlying machine ID. For more information, see Known issues in licensing.