...without Administrator privileges. Right-Click the Adobe Captivate icon, and then choose Run as Administrator to launch Adobe Captivate in Administrator mode."
We have a policy against granting "admin rights" to end-users. What is the solution?
there is no possibility to get rid of this message in Captivate except getting admin rights.
At least in older versions of Captivate I remember that there was this issue. But when I worked with Captivate 5 at my old workspace I had no problems with the tools. I made a lot of screen captures. For audio recording I worked with Audition so I do not know if that influenced the audio.
This is dependent more on the version of Windows under which you are running Captivate. It only became a problem once Windows Vista and later OS versions introduced User Access Control (UAC) that limited the user's access to core OS capabilities. Captivate is designed in such a way that it needs to access those deeper levels of the OS in order to perform screen capture and many other key functions.
Just granting Admin Rights to the user is not enough. The user must also set Captivate to be launched using Run As Administrator privilege as well.
I've heard IT people TALK about there being some way to set up Group Policies in Windows so that users can be granted Admin Rights ONLY to Captivate but not other programs. But I've never met any IT person who was able to document how they did it, or even prove that they successfully pulled this off.
In the long run, if you're going to be using Captivate, the better route is to secure permission from whichever pointy-headed-boss has the power to grant giving your developers the security clearance they need. All the IT Support people have Admin Clearance. Just add your developers to that group. They NEED it too.
2 Replies
Hi Lois,
there is no possibility to get rid of this message in Captivate except getting admin rights.
At least in older versions of Captivate I remember that there was this issue. But when I worked with Captivate 5 at my old workspace I had no problems with the tools. I made a lot of screen captures. For audio recording I worked with Audition so I do not know if that influenced the audio.
So it could be worth trying it in a little test.
This is dependent more on the version of Windows under which you are running Captivate. It only became a problem once Windows Vista and later OS versions introduced User Access Control (UAC) that limited the user's access to core OS capabilities. Captivate is designed in such a way that it needs to access those deeper levels of the OS in order to perform screen capture and many other key functions.
Just granting Admin Rights to the user is not enough. The user must also set Captivate to be launched using Run As Administrator privilege as well.
I've heard IT people TALK about there being some way to set up Group Policies in Windows so that users can be granted Admin Rights ONLY to Captivate but not other programs. But I've never met any IT person who was able to document how they did it, or even prove that they successfully pulled this off.
In the long run, if you're going to be using Captivate, the better route is to secure permission from whichever pointy-headed-boss has the power to grant giving your developers the security clearance they need. All the IT Support people have Admin Clearance. Just add your developers to that group. They NEED it too.
This discussion is closed. You can start a new discussion or contact Articulate Support.