UAC and ktpass.exe9 July 2007
User Account Control (UAC) is a feature new to Windows Vista and Windows Server 2008 that is designed to help protect Windows-based systems against processes running with administrative permissions. It’s a great idea, but the implementation is, in my humble opinion, a bit flawed.
Here’s a great example. In working on interoperability and integration documentation for Windows Server 2008, I came across a problem that prevents you from using Samba to join Linux or UNIX systems to Active Directory for the purpose of centralizing authentication to those systems (more information available in this article). OK, no big deal; we’ve done it before with ktpass.exe, right? We’ll just drop back to using ktpass.exe and do it “old school”.
Here’s the output from ktpass.exe when running on a Windows Server 2008-based server with UAC enabled:
This is running as an account that is not the built-in Administrator account, but is a member of Domain Admins, Schema Admins, Enterprise Admins, and the built-in Administrators group.
Take that same command and run it on the same server after disabling UAC, and it runs just fine. No errors, no warnings, no problems. Clearly, UAC is interfering with ktpass.exe.
If you have a need to integrate Linux and/or UNIX systems into Active Directory for authentication, keep this in mind: you’ll need to disable UAC (and reboot the server) before you can use ktpass.exe to map service principals onto accounts.Tags: ActiveDirectory · Microsoft · Security · Windows Previous Post: Linux-AD Integration with Windows Server 2008 Next Post: ESX Server-AD Integration