Faq's about ADUC+

Security
 
Q. Why does my local computer have to be in a Windows Domain?
A. For reasons of security ADUC+, and it's spin off tools, uses the security context of your Windows Domain. Not only is it impossible to supply credentials to the application itself, it actively checks whether your local computer resides in a Windows Domain. ADUC+ can therefore only be misused if someone has already hacked into one or more of your Domain computers.

Q. Do I have to supply credentials to use ADUC+?
A. No. ADUC+ uses the security context of your local computer, or you can run it via 'run as' and supply different, remote administrator credentials. When you do so, the credentials are handled by the OS, not by ADUC+ (to put it in another way, ADUC+ doesn't start up until after you've supplied those credentials to your OS).

Q. Why do I have to run ADUC+ from a local drive?
A. Well, you don't have to. But if you want to run it from a network drive, you'll have to reconfigure your .net Security Policy so that it trusts applications to be run from remote resources. This is not recommended though. It's safer to copy the executable to a local drive and run it from there.
 

Prerequisites
 
Q. Do I need to install any server side client software before I can use ADUC+?
A. No, no client software needs to be installed. You can just unzip the executable and run it on the spot.

Q. So, what needs to be installed before I can use ADUC+?
A. For the Network functions within ADUC+, both on the local and remote computer DotNet Framework needs to be installed. Also, the WMI and RPC services need to be activated locally and remotely. That's it!
 

Risks
 
Q. How does ADUC+ affect the processor load?
A. WMI queries can take up quite a bit of resources (memory and processor wise). The threads that handle your ADUC+ queries run under normal priority, so jobs with higher priority should not be affected.