@balakumaran_R The first question to ask is do you truly need to bind your Macs to AD? If you're just looking at syncing a Mac's password with AD and providing Kerberos auth support then the Kerberos SSO tool (https://support.apple.com/guide/deployment/kerberos-sso-extension-depe6a1cda64/web) built in to macOS these days is a better choice. If you need to support AD based logins for multiple users in a lab environment where FileVault drive encryption won't be used then binding might be appropriate.
If AD binding is required is there some reason you don't want to use a Policy based AD bind? That does require you configure a Directory Binding under Settings->Computer Management->Directory Bindings in your Jamf Pro console. Using that approach only requires you provide the account name and password for an account with bind permissions in the binding configuration as opposed to needing a mechanism to securely pass it to a script being run on a Mac being bound.
Thank you for your response . All Our mac's are already bind to active directory fromSettings->Computer Management->Directory Bindings . Is it possible to specifically add any other Mac to the Active directory group from my Mac via terminal . With this command "dscl "/Active Directory/domainname/All Domains" -read /Groups/ADgroupName " I'm able to read the group membership . Is it possible to add other computers in the Active directory to be added to this group via terminal from my mac ?
@sdagleyThank you for your response . All Our mac's are already bind to active directory fromSettings->Computer Management->Directory Bindings . Is it possible to specifically add any other Mac to the Active directory group from my Mac via terminal . With this command "dscl "/Active Directory/domainname/All Domains" -read /Groups/ADgroupName " I'm able to read the group membership . Is it possible to add other computers in the Active directory to be added to this group via terminal from my mac ?
