Inventory AD status as "Not Bound" when it is.

What happens when you run jamf recon -verbose? Is it checking to see if a computer is bound?

sudo jamf recon -verbose

My rather weak guess is, your workflow has not ran recon successfully in order to ascertain whether a machine is bound or not.

Here is the front end of my recon scan...

*Retrieving inventory preferences from https://jss.math.osu.edu:8443/...
Finding extension attributes...
 verbose: Running script for the extension attribute com.apple.metadata.mds running
 verbose: Running script for the extension attribute Computer Name Validation
 verbose: Running script for the extension attribute CrashPlan
 verbose: Running script for the extension attribute EFI Password Mode
 verbose: Running script for the extension attribute Firewall
 verbose: Running script for the extension attribute JAMF vs AD name
 verbose: Running script for the extension attribute JSS Certificate Validation
 verbose: Running script for the extension attribute Network Time Server
 verbose: Running script for the extension attribute Puppet Run
 verbose: Running script for the extension attribute Recovery HD Present
 verbose: Running script for the extension attribute SSH Public Host Keys
 verbose: Running script for the extension attribute UUID
 verbose: Running script for the extension attribute Verify Certificate Based Communication
Locating hard drive information...
 verbose: Finding CoreStorage information...
Locating hardware information (Mac OS X 10.8.3)...
 verbose: Checking AD status...
Locating accounts...
 verbose: Finished with user.*

Note the "Checking AD status... toward the end of snippet." Do you show this?

Running "sudo jamf recon -verbose" did fix the issue, but the checking AD was one of the first things to show up. All machines that I ran that on are now being reported as bound. So what does that mean? Info is not being properly sent to the JSS.

What angles would you take to fix this issue during the imaging process?

Thanks for the help!!! I'm still learning all of this.

Found out something new, I am pushing a configuration profile that has the Directory payload configured (in addition to binding during imaging) If I remove the payload from the Profile, machines show up as unbound in inventory even if I run "sudo recon jamf". The only way a machine shows up as bound in inventory is if the Profile has a directory payload.