Skip to main content
Question

Set Computer Name and AD bind

  • May 14, 2012
  • 2 replies
  • 2 views
A
Forum|alt.badge.img+14

Hey Guys, I am working with 10.6.8 and 10.7.3 machines and beginning the summer re-imaging process. We have a number of machines that are moving to different schools therefore requiring a different image and change of name. My techs are having issues with pulling a machine from a cart that is already bound to AD, re-naming and re-imaging in Casper Imaging. The issue lies in that the Computer Name is not reflected in DirectoryUtility and the machine is left unbound with the old computer name populated. I am using the built-in AD bind from the JSS. We are also seeing that sometimes it will show the computer name from the base image in the directory utility as well still unbound. I have googled and tried a number of fixes, i.e. deleting /Library/Preferences/DirectoryServices and rebuilding my base image to no avail. PLEASE HELP!! thanks in advance guys.

    2 replies

    K
    Forum|alt.badge.img+6
    • Kev
    • Contributor
    • May 14, 2012

    Andy-

    I have ran into similar issues, but it could honestly be one of many things.

    If you take one of the problematic machines, turn it on and make sure it is on the network. Then use Casper Remote to deploy the same built-in AD binding, you may be able to see what your error is. The logs are pretty useful in Casper Remote when troubleshooting binding issues.

    In the end, I ended up writing three different custom scripts to bind to AD as opposed to using three different built-in bindings.

    I hope this helps!

    -Kev

    A
    Forum|alt.badge.img+14
    • AndyBeaver
    • Author
    • Contributor
    • May 14, 2012

    I figured it out, it was a two-fold issue.

    1. The order in which the Built in AD bind was running in the firstRun script was too soon. The machine was not yet unbound.
    2. I was not removing the machine from the JSS prior to re-imaging.

    I re worked my configurations to just include the unbind.sh @reboot....then...autologin ....thus triggering a policy scoped to unbound machines and use the Built in AD bind!

    Kind of messy but it works for now. I will continue to troubleshoot this and smooth out the process. Thanks for your response though, I will give casper remote a shot and take a look at those logs! Take care

    Terms & ConditionsCookie settingsAccessibility statement