Jump to content

Recommended Posts

Posted
asks for sign in

Did you uncheck the Creative Cloud Desktop Application when creating the package?

 

VXEARB.png

 

I normally create separate applications in SCCM for each Adobe CC app rather than one big application containing everything.

Posted

Yes I did. I have managed to find a work around to allow packages to run (reapplied license) however Adobe InDesign won't work due to a permissions (preferences issue).

Unfortunately not a qualified network administrator (Head of Computer Science Teacher). Trying to fix things as best as I can with some support from my technician (we have RM as our network manager).

Deployed the package (some deployed, others did not). Managed to fix license issues by applying a patch on each individual machine, but now have permissions issue for student / non-admin accounts.

Posted
Not at the moment. It just says can't load preferences as permissions issue. I thought it my be the user roaming profile, but staff and students can read/write there (on another server).
Posted
I am working with a technician who, to be frank, isn't very helpful and has pretty much locked everything down (wasn't given the post of network manager, so you can imagine the politics). He will be unwilling to provide C: drive access without a signed document, triple checked and verified by senior management through pain of death.
Posted
I thought it my be the user roaming profile, but staff and students can read/write there (on another server).

Does the AppData folder get redirected to the network? Adobe applications often don't like that.

Posted
We're in the exact same situation as you, Dreamweaver and InDesign not working due to this permissions issue. Adobe support forums not helpful so far!
Posted (edited)

Are these the 2018 releases?

The packager tool should allow serial licence. If you get a permissions issue when testing as a standard user. You can use procmon to see what's causing it.

Edited by free780
Posted

Yes, 2018 releases, I built them last week. I've noticed that running procmon yields very little, but it does crash the program on load ... and then magically it works! I'm not entirely sure how this is happening, but two machines now I've opened DW and ID (the two broken programs) a few times using Proc monitor, let it crash the program and open it again... and it runs.

 

How very strange!

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...