Copy link to clipboard
Copied
We use Federated ID's at my work. I was asked to assign a license for Adobe Acrobat Pro DC for a user. When we went to install it, she had already signed onto using her personal Adobe account and downloaded & installed the software.
Is there a way to prevent that from happening in the future?
david_lutz wrote
We use Federated ID's at my work. I was asked to assign a license for Adobe Acrobat Pro DC for a user. When we went to install it, she had already signed onto using her personal Adobe account and downloaded & installed the software.
Is there a way to prevent that from happening in the future?
We can't install software on our computers. Is a question of rights. That's all...
I do not think that you can block people using personal accounts (from a technical point of view), but you ca
...Copy link to clipboard
Copied
Unplug the computer from the Internet is the only way I know of to prevent someone from going to the Internet
If you have a written policy in place, sanction the employee and remind others of the policy
Copy link to clipboard
Copied
david_lutz wrote
We use Federated ID's at my work. I was asked to assign a license for Adobe Acrobat Pro DC for a user. When we went to install it, she had already signed onto using her personal Adobe account and downloaded & installed the software.
Is there a way to prevent that from happening in the future?
We can't install software on our computers. Is a question of rights. That's all...
I do not think that you can block people using personal accounts (from a technical point of view), but you can submit a company policy to do so.
Copy link to clipboard
Copied
If you are trying to control user access completely you might consider whether the user should have been able to get administrative privilege.
Copy link to clipboard
Copied
My thought too.
Where I work, downloading cannot be stopped but installing requires admin privileges.
Copy link to clipboard
Copied
Yeah - sadly the user requires Admin privileges for some of the development work she does so I was trying to figure out another way.
OK thanks guys!
Copy link to clipboard
Copied
Censure letter from head of department
Copy link to clipboard
Copied
Development on a virtual machine. Works fine... For the rest: Policy, the one on paper! Works also fine if enforced.
Copy link to clipboard
Copied
I'm having a similar issue but on a terminal server. I had a user log in with their personal account and I could not block it now everyone else 40 people that use the server get a messge stating they are not logged in and to sign in. But the other 39 people do not have adobe accounts. There has to be a way to remove the sign in button. nobody had rights on the server except for me and I did not sign in.
Copy link to clipboard
Copied
Have that user sign OUT of their account, and then you MAY need to use the cleaner to remove whatever that user did
https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html to remove programs
Copy link to clipboard
Copied
this is not an option I have 150 users who do not listen to policies and they sign in. Once they sign in all the other user are affected. I want Adobe Reader only without them to be able to log in. I clean wipe the server either as other use it. I also do not know who logged in as I have to ask 150 users who did it. They will not be honest,
Copy link to clipboard
Copied
For anyone else facing this issue- you control the computer and the network. Install a proxy server and a self-signed root cert so you can monitor traffic. The proxy logs will show who signed in where.
Copy link to clipboard
Copied
You can not assume we control the proxy servers. That's not a valid option.
A simple button removal would be ideal
Copy link to clipboard
Copied
We can assume, you control the proxy servers. You are the system administrators.
Copy link to clipboard
Copied
you know what happens when you assume. We have seperation of duties on purpose. They do not want to handle it this way which agree with. Besides the packets are encypted so the login will not show the username.
Remove the button and boom issue resolved.
Copy link to clipboard
Copied
Remove the button and boom issue resolved.
By @Johnny T
https://www.adobe.com/products/wishform.html
Copy link to clipboard
Copied
The button is not going to be removed because you demand it. As for encrypted traffic, any competent admin would understand why I specified installing a root certificate.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now