For the past few months we've been using getcomputername.exe as a Pre-Install Task, and setcomputername.exe as a Mid-Level Install Task, to name our machines. We've been happy with it as our naming convention is varied, e.g. it doesn't work off machine hardware like a serial number, and we like having a prompt.

We're now working on binding the machine to Active Directory but have had little success. So far we've tried using the join_domain.vbs that's already loaded onto the K2000. I've edited the Command Line options to input our domain, username, password and DNS server. For some reason the scripted installs run as normal but there's no binding occuring. I've checked obvious things like is the machine in AD etc. Am i meant to be editing this join_domain.vbs file at all? Any ideas?

Thanks for your help!

0 Comments   [ + ] Show Comments


Please log in to comment



We use the Scripted install and have it join the computer to the domain in the scripted install, and then have it name the machine as a post-install task.

Answered 06/24/2013 by: WGM_Jeff
Fourth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja