This is a really infuriating issue.
At work we're running a Casper Suite 8.62 system for OS X deployment. What we're finding is that the Casper imaging process is correctly naming the computers from the JSS, the computer retains it's name on first boot but loses it completely on 2nd boot.
Now I thought i'd traced this issue to our DNS (because we have Novell DNS and we're migrating to Microsoft DNS servers) and I was able to stop the issue on the MS DNS servers ... on WiFi. Today we changed over a couple floors of our building to the new servers ... and nada, the macs are losing their names on 2nd boot. It's a pretty serious issue as it compromises our inventory on the JSS. We've a string of computers that either have randomly assigned existing names or have been given blank names.
Now if you program the computer name on the mac manually at this point (as well as fix the inventory item on the JSS), the mac then seems to keep its name in perpetuity. I'm concentrating on the Microsoft DNS because that's what we're moving to anyway. I've made sure the Systems team have enabled the "updating clients that do not request updates (NT clients)" option and supplied the correct authentication credentials too for the DNS servers. This seemed to fix everything on WiFi, but seemingly no effect on Ethernet.
I thought we had DNS issues, then DHCP and now i'm back to JAMF bug?
Any thoughts?
