This is what I am experiencing right now.
I created a configuration in Casper Admin to image a machine using 10.8.2 and set it so that configuration also enrolls the machine as they are imaged under the Management tab of Casper Admin via browser, as well as to bind it to our Active Directory domain.
Image process completes, I boot up the machine and after a couple of minutes it is up and has checked into Casper and now shows up in Inventory with the Computer Name I gave it while in Casper Imaging, let's say Mac01. The built-in Bind by default is set to run as a FirstRun script which it does and works but requires a restart to allow AD users to login. I restart, login with an AD account. After its inventory interval Inventory now shows that machine as having the Computer Name of localhost instead of Mac01. I go to Sharing in System Preferences and the Computer Name field is now blank and no policies seem to hit that machine/user.
What I have done to get around this is re-create my configuration but this time without setting it to enroll during imaging. I image the machine, power it up give it a minute, then restart it to allow the bind to take effect, then I can either manually enroll by running the .pkg or push it to the machine remotely.
I want to be able to both enroll and bind to AD without any issues during the imaging process because I eliminate the possibility of our technicians forgetting to enroll a machine. Has anyone else run into this? Thanks.
Solved
Binding to Active Directory during imaging clears the Computer Name field
Best answer by kbailey
I've seen this too but we don't do an AD bind. I found this solution by Casper Sally https://jamfnation.jamfsoftware.com/discussion.html?id=4521 and followed cbrewer's script and set it to After. I don't know if it would help yourselves or whether you are running into a different issue. 8.64 is supposed to fix the naming issue. Hope that helps.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
