• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1721
  • Last Modified:

OS X 10.5.5 integration with Active Directory

I'm trying to get a couple macs on my Windows AD network and I'm having a few issues.

First of all, this is what I want to have happen: When you boot up a Mac I want to see the login/password screen and allow network AD users to log into the computer.

And this is what I've done so far:

1. Enabled the Active Directory server in the Directory Utility
2. Added my AD directory server (and it's reporting that it is responding normally)
3. Within the Active Directory advanced settings:
    a. Checked "Create mobile account at login"
    b. Unchecked "Require confirmation before creating a mobile account"
    c. Unchecked "Use UNC path from AD to derive network home location"
4. Within the System Pref. Accounts:
    a. Set Automatic login to disabled
    b. Set display login window as name and password

I believe I also need to check the option that says "Allow network users to login to this computer" but it doesn't seem to be showing up. So the end result is, I can only login using my local credentials - no AD user.

WHat am I missing??? Thx!
0
graphicodyssey
Asked:
graphicodyssey
  • 3
  • 2
1 Solution
 
jhyieslaCommented:
I login every day with my AD credentials. I've done pretty much what you have done with the exception of creating the mobile user account and I don't specify the name and password option, but that shouldn't have anything to do with your missing field.

The option you want lives in the Accounts System Preferences and can be accessed by clicking on the Login Options button on the left side of the window. If it's there, but grayed out, click on the padlock, if it's closed, and enter in your local admin credentials, then you will be able to change those options.
0
 
curwengroupCommented:
What hardware platform are your Mac's?
The reason i'm asking i that in the past we have had great success with Macbooks and iMac's joining Active directory, but MacBook Pro's and Mini's have always had an issue of some sort.
0
 
jhyieslaCommented:
I am using a fairly new Intel-based Mac Pro running 10.5.5. When I first bound my Mac to AD, it was running 10.5.3 and I've upgraded since then to 10.5.5.  
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
graphicodysseyAuthor Commented:
So I walked through all the steps again this time and viola... the "Allow network users" checkbox showed up in the control panel and I was able to finally authenticate using an NT user.

I think the problem had to do with how I was connecting to the LAN. I was connected to the work LAN via a Cisco VPN client. The AD binding worked fine, but the Mac OS must need to see the AD network when booting up (and unfortunately the Cisco VPN client for Macs does not support that). When I created the binding the second time, I was at the office on the LAN so I didn't have to use the VPN client. Now that I was on the LAN once, Im able to be remote and it still works great.

Thanks everyone for your help.
0
 
graphicodysseyAuthor Commented:
BTW, I'm using a Mac Book Pro.
0
 
graphicodysseyAuthor Commented:
One other comment - that checkbox wasn't grayed out - it simple wasn't there - regardless of clicking on the padlock to change the settings. But once I connected to the network directly, it showed up fine.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now