I found a way around this. On the client machines, I was able to log in and tun the adjoin command with the folloing syntax and I was able to join the machine into AD:

adjoin -w mydomain.com -u najeebd --verbose

Once the machine is joined to the domain, I am able to use Kerberos for authentication into other machines. Now the issues is that I don't want to be running this command manually on all my hosts when I want to join them to the domain. Can someone please sed some light on this issue? Thanks.

Re: Deployment Error: Adding computer object into Windows AD

It appears as though you have used install.sh to install our DirectControl express, for DirectControl Express installation please run install-express.sh for installation and respond to installation/join questions as follows:

How do you want to proceed? (S|X|C|Q) [X]:

Do you want to run adcheck to verify your AD environment? (Q|Y|N) [Y]:

Re: Deployment Error: Adding computer object into Windows AD

Was there any resolution to this? I'm getting the same messages trying to join the domain -- both during installation using install-express.sh and also if I run the adjoin command manually. I can't seem to figure out exactly what the problem is, and I can join windows machines to the domain. I see this in the logs if I turn on debugging:

The adcheck stuff comes back with only a warning about using a domain ending in .local (but that's not something I can change), otherwise all the tests pass. Also, running adinfo --diag as the error message suggests turns up all passing tests.

Re: Deployment Error: Adding computer object into Windows AD

The server appears in the list but you can't click on the + and expand it out to see what it contains.

Check in your server list that can actually see the server. Also keep in mind that this software needs access to the admin port, not the normal web one, although it looks like your tunnel is correct for that.

You also need to turn on remote administration and set up the username and password etc. Try pointing a web browser to your localhost 6122 and check you can log in to the admin panel if that does not work try the blog of