The ADUC console requires the user to be logged on with a domain account to do anything useful with it.
A solution that wouldn't require the notebook to be joined to the domain is to install a virtual machine on the notebook, join the virtual machine to the domain, and do the maintenance on the VM (apart from the obvious method of connecting to a domain machine through RDP).

If you can join the computer to the domain it would make things easier.
If for what ever reason you can't then you still can create customized mmc console like the taskpad and use the "run as" and specify a domain user account and password to run it. To be able to run the taskpad, you need to also install the adminpak on the computer assuming your taskpad console is basically running the ADUC gui.

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.

oBdA is correct, the computer must be in the domain to authenticate the account.
RunAs works when the computer is a member of the domain, it work even when you logged on to a domain member computer with a non-domain account. But the computer must be a member of the domain. Thanks for the correction, my bad.

0

rsnellmanAuthor Commented: 2009-05-14

So, I must add the laptop to the domain and make it a passthrough on my wireless network so it can log into that domain account when it boots up.

Hmmmm...just was hoping not to add it but not a big deal.

Thanks to all.

Bob

0

Featured Post

Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why