Some AD binding questions

Scotty
Contributor

Hello,

New to Jamf and I am tryin to wrap my head around a lot of things very fast haha. unfortunately faster than I am able to schedule my 200-400 admin classes. I hve done some searching but im not finding exactly what im looking for.

First off, yes for now, we still need to AD bind, but were looking to move away form it with Nomad in the near future, but for our initial rollout of Jamf, we need NEW machines to be bound. Existing machines are already bound.

So, what is the best approach to getting newly provision machines bound to AD? We are utilizing Apple Business Manager (DEP) and a single preStage config for machines enrolled. We have a few profiles that go down upon enrollment and they work fine, but the AD binding isn't working.

I see I can have it done in preStage config or as a profile (both would actually be profiles no?). I also see binding under "Settings > Computer Management > Directory Binding", not sure who that coms into play.

Also, why does the profiles for binding ask for the DC name, but not the domain itself? maybe thats why it wont bind for me.

1 REPLY 1

Scotty
Contributor

ok I figured out that the "Settings > Computer Management > Directory Binding" is used with a policy. I coupled that with a script to rename the machines to m$Serial (all 3 locations). the Policy runs one time at logon, pointed a smart group for DEP enrolled machines.

However when it binds the computer name is left blank. If I unbind, the m$Serial shows up here. any ideas there?