AD Appears to bind, but computer objects not created?

[mlinde]

Ok so this is messed up. I’m configuring a complex AD/OD environment – complex only because there are 6 remote locations, some have an AD and an OD replica, some do not, and some are in one AD Domain, others are in another (but all are in the same forest).

The issue we are experiencing is that in one site (no OD replica, no AD replica) when attempting to bind a Mac (10.4.9-10.4.11) it appears to bind (Directory Access thinks it bound) but the computer object isn’t created in AD, and upon reboot the bind doesn’t work (obviously). DA doesn’t report any errors when binding, but I haven’t run the debug yet to see if something is throwing an error anyway.

I read the suggestion to pre-create the computer object in AD, but what often happens then is that the plugin requests to join an existing object, but fails to actually bind/join the computer object.

Before I run the debug and peruse the log, does this sound familiar, and if so, what was your solution?

Thanks!

update – and a difficult piece for me is I am connecting via ARD to do this from Denver to L.A. – so there’s a bit of lag in the connnection when setting up.

[mlinde]

Well, I found my own resolution/answer, so I thought I’d share.

AD has a replication cycle, up to (in our environment) 30 minutes. If a new machine is bound in a different location (like an office in a different state), it could take up to 30 minutes for that replication cycle to get into the primary DC and back to the local DC, which would potentially also prevent the computer object from showing up right away.

That’s for anyone else who runs into this.

[Author]

Posts