Quantcast
Channel: Adobe Community : All Content - Enterprise Deployment (Acrobat and Reader)
Viewing all articles
Browse latest Browse all 2437

Installing/activating Adobe std/pro on a MS Terminal Server, Process

$
0
0

I'm looking going to deploy Adobe Std/Pro for a new Terminal Server deployment (Windows 2012R2).

 

I'm not entirely sure what to expect when activating and what type of licensing I should get.

 

What do I need to install the software to the terminal server and activate it?  I believe I read something about a deployment tool?

 

When I got a quote for Adobe software, I was told I would get 10 separate licenses as this TS will have 10 users.  How does this work with licensing and the deployment tool?  Do I just pick one of the license keys to include in the deployment tool or will I get a special key that is for 10 users?  Just hold on to the licensing keys as proof of purchase?

 

If I go with a subscription model, does each user need an adobe login?  Will this break the application in some way by going with a subscription model on a TS?

 

What I'm expecting during the install/activation process is I will get 10 indevidual license keys.

 

  1. Download the Adobe setup and deployment tool.
  2. Input any one of the license keys into the deployment tool and complete this process.
  3. Install Adobe using the config file output from the deployment tool, this will activate the product as the key is embedded.
  4. If I need more licenses, I just purchase from my vender as needed and keep the license on hand for additional users as proof of ownership.

 

Please clarify, thank you.


Viewing all articles
Browse latest Browse all 2437

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>