![]() Anyway, this was not the same user as the one in step #1 that has access to AD - this user is our local administrator account on the machines. I added the -f and the original script looks like it starts with the $username and $password but doesn't actually enter them after that. (2) This is the only real change I made to the script that I figured out while playing with Terminal and manually unbinding it that way. I didn't want to use an existing admin password or my personal user, so I basically just made a user specifically for this purpose, but that's your decision. Just plug that in with its password between the parans. (1) In the first username/password field, I created a new AD user that can authenticate/remove a user from AD. The rest of the script is the same, just look at these two specific items and make updates: I started with the unbindAD.sh script provided on JAMF that can be located here: Okay, give this a shot when you get a chance. (1) Any ideas on what we can do or (2) if we can alter the unbind script to force it out of the domain anyway or (3) if we can force it to overwrite the existing bind (and rebind correctly)? We are trying to run software updates to get the machine on 10.7.5 (from 10.7.4) because there was an AD fix in that udpate, but so far it's not cooperating. (Attempt 5)Įrror: Giving up on Active Directory binding after 5 attempts. (Attempt 4)Īn error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. ![]() (Attempt 3)Īn error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. (Attempt 2)Īn error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. (Attempt 1)Īn error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. (2100)Īn error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. ![]() Script Result: Unbinding the computer from Active Directory.ĭsconfigad: Connection failed to the directory server. Mounting afp://ourserver.domain/CasperShare to /Volumes/CasperShare. However, on machines that we have not manually touched (which we don't want to touch, we want to use JAMF), we have used the unbind/rebind script but it fails out with the following error:Įxecuting Policy Unbind and rebind AD - TEST. If you used Disk Utility from macOS Recovery, you can now restart your Mac: choose Apple menu > Restart.We have noticed that we are able to manually unbind/rebind to our domain, and that process does both rebind the machine to AD and create an object in Active Directory. ![]() The order of repair in this example was Macintosh HD - Data, then Macintosh HD, then Container disk4, then APPLE SSD. Keep moving up the list, running First Aid for each volume on the disk, then each container on the disk, then finally the disk itself. If you're asked for a password to unlock the disk, enter your administrator password.Īfter Disk Utility is done checking the volume, select the next item above it in the sidebar, then run First Aid again.If the button is dimmed and you can't click it, skip this step for the disk, container, or volume you selected.If there is no Run button, click the Repair Disk button instead.In this example, the last volume on the disk is Macintosh HD - Data.Ĭlick Run to begin checking the selected volume for errors. For each disk that you're repairing, start by selecting the last volume on that disk, then click the First Aid button or tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |