Licensing Endpoints for Teams

[unku]

Can anyone provide precise network endpoints (hostnames or IPs) for keeping Adobe CC for Teams licensed?

We can't open up to the whole web and we can't open up for file sharing and syncing. We can *only* open up for licensing if absolutely necessary.

Until now, we've been able to get by by connecting to the web once every 90 days on each machine and launching a single app in a single user account. As of CC 2019 is would seem that this no longer works. On Macs, this now requires us to launch EVERY CC app in EVERY user to stay licensed. And on the PCs, the CC Apps just crash after 1 minute if not connected to the internet full time.

[unku]

Unfortunately, this is not the correct answer. We've been provided this page and have reviewed this page many times. Even if we whitelist every endpoint on this entire page (not advised or practical), we still can't keep CC Teams licensed without opening up further internet access.

Can you please provide the precise endpoints that are used to license CC Teams?

[alisterblack]

Hi,

The information in the document Adobe Creative Cloud Network Endpoints ​ is complete, we don't list specific IP addresses as these are hosted by AWS, are dynamic and constantly changing. The behavior you describe goes beyond what I would expect to see for blocked endpoints. Endpoints for 2019 apps have not changed, what has changed is that licensing information is stored in the OS keychain. Do you have any local restrictions to that?

Other elements that can cause you issues when trying to connect online are proxy servers, host files, certificates.

Resolve connection errors with Adobe Creative Cloud and Creative Suite applications

Proxy support in Adobe Creative Cloud Products

[unku]

Oh man... does that mean that the licensing info is stored separately in each users keychain now? And we shouldn't hope to be able to license the software system-wide anymore?

Can you provide any other documentation about this as it related to Mac AND Windows?

[unku]

I'll use this opportunity while I have your attention to try and get more information about what might be happening here.

- All 2018 apps are running fine, on or offline, licensed as before, on Windows 10 & Mac

- On Windows 10, AE 2019, Photoshop 2019, Illustrator 2019 will all shut down with no information (just quit) after about 1 minute of opening if the user is a) not an administrator and b) the machine has no internet access.

- If the user is an admin OR there is internet access the above apps stay open.

- On macOS 10.13, all apps will stay open and licensed but will lose that license within 24 hours, if not connected to the internet and not an admin. Keychain access errors are presented at that time.

- Further, as mentioned before, we are unable to license the users system-wide. We are required to launch 2019 and license each individual app in each individual users on macOS 10.13.

[alisterblack]

Hi,

I'm adding below our documentation relating to licensing changes for CC 2019 in relation to Mac OS Keychain and Windows credential manager.

User and license information issues | CC 2019

Apps display the licensing dialog box while accessing the Keychain | macOS

Adobe license certificates installed in the Keychain or Certificate Store are shown as not trusted

If you don't have any progress on the basis of this it would be useful to have more information about the keychain errors you are seeing.

[unku]

Thanks you for these resources. We will investigate in get back to you. In the mean time I have some pointed questions that I hope to have answered:

1) From what I'm reading in the documentation you sent, based on the fact that the authentication data is being stored in the Login Keychain on a Mac, the 2019 apps are now being licensed at the user level and can no longer be licensed system-wide. Can you confirm that?

     If Yes, do you have any documentation regarding alternative workflows that allow for system-wide licensing?

2) On Windows 10, the 2019 apps will all shut down with no information (just quit) after about 1 minute of opening if the user is a) not an administrator and b) the machine has no internet access. Can you confirm that this is likely related to the new licensing model of 2019, or do you suspect that this is an unrelated issue?

[alisterblack · Accepted solution]

Hi,

1) Yes this is the expected behaviour. In the previous method licenses were applied system wide. This was not the desired behaviour as it allowed running of applications by users without the correct entitlement and many customers asked us to fix this so that they did not inadvertently become out of compliance from a licensing perspective.  Named user licensing ties the license to the user. Each user has to sign in individually to pick up their own entitlement. A CC license cannot be shared between multiple users on a machine.

2) We would need to gather more information. I would recommend using the Log Collector Tool to get logs following a crash, open a case with support via your Admin Console and share the logs. They will be able to either assist immediately or check with our engineering teams. You should also let support know the exact versions of the OS, the applications launched and any relevant non-standard permissions or group policies that could be impacting this issue.

[unku]

Thank you for your help and answering my questions. It's a feat to get questions answered by Adobe support these days! So it is much appreciated in that regard.

BUT WOW, I can't (but really can) believe that Adobe is continuing to make licensing and deployment even harder on the sysadmins. It's a shame that this continues to get worse.

[HarleyTDavis]

No, no more system wide login.  That means each person has their own cloud.  However, if you wish to link machines rather than people for a system-wide look and feel, you can finnagle it a bit, but it takes a little more work.  Let's say you're on a network where the users never move desks... ...Then you mark their desk, and give the DESK an email or Alias email account to use for an Adobe ID.  A person can purchase as many Adobe ID's or create as many as they want, provided they all have a separate spelling of an email account.  This means that if you create ALIAS accounts attached to a single email server account, they will still APPEAR as separate user accounts to adobe servers that have no access to your internal email structures.  This means you can now "own" multiple adobe id's under a single email account, but multiple email aliases.  This used to be just an old way of making sure your old email addresses could be used to fill your new inbox, without paying for the space on the old inbox, even if you still have to pay for the domain names.  It was common enough when the domain service's pricing changed.  It's still practiced by people who want to access emails from multiple businesses through a single account, but want the address the clients see to be associated with the business they are contacting instead of the individual.  It allows sorting algorithms to separate the mail into folder headers easier.  Now it also allows you to cultivate multiple ID's and Licenses for products.

And what if the people move between machines and have to work the same apps at the same time on many desks?  Same idea.  Make Aliases for each person in your email system for each machine they will use, and then use the aliases to license the software.  If they will only use 2 machines for some things and 2 machines for other, then 2 licenses are necessary, 2ID's  and 2 aliases, since you can log in on 2 devices with each license, you can use different apps on 2 computers, just mark the machines with red and blue tape that notes that one red and one blue can collaborate or something of the like.  Then they will always be aware of their capability and how much they can work on at a time, and you will be able to use less licensing for more work.