Jump to content

Recommended Posts

Posted

Does anyone know how to actually deploy this so it is licensed etc?

 

In previous versions (2015) i just run it from the exception deployer folder. Its different now as it doesn't contain any files.

 

The msi just doesn't work despite me building a new package!

 

They make it hard sometimes Adobe!

 

Thanks

Posted
I used the setup. exe created by the Cc Packager. I used SCCM to remove the old version and install the new version. Several programmes if running like outlook etc will prevent it from working.
Posted
We ended up downloading a separate license package that we install after the DC package. Worked OK for several months but have since started getting issues with the licenses expiring!!! To get over this we have created and downloaded a second license package, annoying that nowhere on the Adobe site is there any mention that the license expires every so often (even though its not due for renewal) though it certainly seems to be the case with our installs.
  • 1 year later...
Posted
I think ideally they want you to use named licences. However you need ADFS or Shibboleth setup.

 

Also Azure AD works if you don’t want to setup and ADFS infrastructure

  • 4 weeks later...
Posted
One thing I have noticed it’s SDL Acrobat is that if acrobat hasn’t been opened and a user right clicks a pdf file and selects Edit with Acrobat they get an annoying acrobat not licensed pop up and it doesn’t open. Normal open works and you get prompted to sign in.
Posted
I also noticed the services within Acrobat Reader are disabled where SDL Apps are deployed. As I can't ensure users have a 1:1 device I can't use named licensing for staff.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...