What can't I do without Administrator Privileges? And Why can't Adobe install a workaround?

Report · Feb 03, 2017

OK - I know Lieve and Rod had been tilting at this particular windmill for several years now, but I just want to get the conversation boiling again.

My new organization is locked down tight and there is no way in heck we're getting full admin rights to Captivate or any other Adobe product. (obviously we would use our powers to conduct nefarious activities through the product updaters...) That being said, I do have the ear of the IT folks regarding the possible loss of functionality in my Adobe Suite due to this situation. Since we bought these tools to leverage all of their capabilities, I need to be able to list the things I can't do and how it affects our production in order to give them the ammunition they need to overwhelm legal and the security team objections (money does talk).

Can anybody give me a full list of the capabilities that I am losing due to this situation and what those limitation impose on my ability to unleash all Captivate is capable of? Also, I've seen some tech-speak about elevated user accounts/power users/group limited admin right set ups, but nothing from Adobe and nothing that I can take to the IT folks and ask them to try.

If I can get one or both of these pieces of information together - I can systematically annoy the proper contacts with logical and fact based pleas until they do what I need just to get rid of me. Little help, please?

Report · Feb 03, 2017

Really cannot help you with a full list, because it looks like it depends on many factors. Latest version seems even to be more sensitive. Capturing (for software simulations) is certainly one of the crippled functionalities when you cannot run Captivate as Administrator (which is not at all the same as having full Administrator rights). Another problem I remember is when trying to save customisation (themes to be one of them). Cleaning Preferences (which often has to be done) same thing.

Report · Feb 03, 2017

It's going to crash unexpectedly and at very inconvenient times, causing you to lose any unsaved and backed up work. It won't be predictable in most cases. But the general rule is that it will happen when the app is trying to access low-level system stuff, which includes video capture, screen capture, audio recording, and publishing/rendering out to files.

Tell IT that you will be yelling at them personally each time it does this and requiring them to be publicly flogged each time you lose work.

Report · Feb 06, 2017

Thanks - I think the idea that the project will be unstable and the system will crash when we are providing time sensitive projects for the executive team will probably be enough motivation - although public flogging does have its merits.