<div>
Agreed with John.<br />
<br />
The users most likely need to be local admins on their PCs in order to run those programs. OR you can reach out to the vendor of those programs and see if they have a least priv. model for how to provide access to the programs to standard user accounts. <br />
<br />
E.g. some vendors will give you a list of folders and reg keys that the user must have Full Control on but can remain a standard user account.. and this allows them to run the program without making them a local admin.
</div>


<div>
OK, I will look into these suggestions. Thanks for the quick input.
</div>


<div>
Let's analyze before we recommend.<br />
If your users weren't admins before they joined the domain, but they were able to run all those programs, then we can surely enable them also domain joined.<br />
Was that the case? or were they local admins before joining the domain?
</div>


<div>
I see.<br />
Than the method of choice is indeed the tool that John links. But be aware that it will cause administrative overhead and costs. it would be better to eliminate the need for admin privileges by using compatible software.
</div>


<div>
The software is for banking purposes. After speaking with the IT department they informed me that the user will have to be an admin. So that is what I will do.
</div>


<div>
John Hurst said &quot;You either have to provide administrative credentials to these users or...&quot;<br />
<br />
This is what the clients Bank IT department told me to do.
</div>


<div>
@jbcbussoft &nbsp;- Thanks for the update and I was happy to help.
</div>


<div>
You are giving all of them admin status? Very bad advice by your bank, security wise.<br />
At least look at the software that was linked and also ask if that's all the bank's developers have to offer. It's less than poor.
</div>


<div>
The two users are the CEO and CFO these are the only two that have the software and/or the problem. They have had admin status for years on their pc's with no problems. If problems arise we will address them.
</div>


<div>
One of the most common errors is to give important people admin status just to avoid quarrels (of any kind) with them. They are the most likely ones picked for direct attacks - and being admin really improves the attackers' chance to infect them.
</div>


<div>
If you have to give them admin status, I would advise ensuring you are using layers of security on their boxes. Since giving them admin status is a risk, consider the controls you could put in place to minimize the risk level. <br />
<br />
For example, you could consider the software from Beyond Trust that allows you to give admin rights to your users but still control what they do... suchas you could prevent the CFO and CEO from installing other software. <br />
<br />
Ensure you have active and quality AV protection on their computers. Consider DLP if you do not already have it. In addition, take a look at perimeter security and ensure you have good IPS/AV/web filtering etc. All of these items combined help to reduce the overall risk of granting those two users admin access.
</div>


<div>
<div class="content wysiwyg-content">
We have a server that was a stand alone file server. The need arose to convert it to convert it to an Active Directory Domain controller. After this was done and the existing users were joined to it there have been a few programs on a few workstations that have required the domain server user/pass to run. How do I give these end users permission to run their needed programs without elevating them?
</div>
</div>


We have a server that was a stand alone file server. The need arose to convert it to convert it to an Active Directory Domain controller. After this was done and the existing users were joined to it there have been a few programs on a few workstations that have required the domain server user/pass to run. How do I give these end users permission to run their needed programs without elevating them?

Security requires end users to user the domain admins user/pass to run programs on their workstations

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows 7 is an operating system from Microsoft. Features include multi-touch support, a redesigned Windows Shell with a new taskbar, referred to as the Superbar, a home networking system called HomeGroup, and performance improvements.

Windows 7

Operating system security (OS security) is the process of ensuring OS integrity, confidentiality and availability. OS security refers to specified steps or measures used to protect the OS from threats, viruses, worms, malware or remote hacker intrusions. OS security encompasses all preventive-control techniques, which safeguard any computer assets capable of being stolen, edited or deleted if OS security is compromised, including authentication, passwords and threats to systems and programs.