Filed under: Enterprise, OS, Software
Sign on to your Mac using a Windows account
The title of this post is a little misleading, the actual account is an Active Directory account (which is Microsoft's directory product) and not a Windows account (which are machine specific). However, this post on Big Nerd Ranch's new blog will interest anyone who is using a Mac in a Windows centric workplace (but big companies don't blindly rely on Windows, right?).I have been struggling with getting a Mac of mine to see my office's Active Directory, so I'm going to try this on my Mac mini at my office, and I'll let you know if it works.
![TUAW [Cafepress]](http://www.blogsmithmedia.com/www.tuaw.com/media/tuaw-cafepress-promo.png)
Reader Comments (Page 1 of 1)
richard Draney said 12:31PM on 11-17-2005
where can i buy ghis shirt?
Reply
creanium said 3:23PM on 11-17-2005
This might help you out too:
http://www.macwindows.com/AD.html
Reply
Robin said 3:38PM on 11-17-2005
http://www.tuaw.com/2005/01/16/longhorn-its-whats-for-dinner/
The source of the Tshirt :)
Reply
Robin said 6:27PM on 11-19-2005
http://www.tuaw.com/2005/01/16/longhorn-its-whats-for-dinner/
The source of the Tshirt :)
Reply
James said 5:36PM on 11-17-2005
I work at The University of Melbourne, Australia and we have a campus-wide Active Directory (AD) with approximately 60,000 accounts. Our computers are roughly 60% Windows, 35% Macs and 5% Linux.
Since OS 10.3, we have officially supported Macs authenticating via the AD and it works pretty well (even more so with 10.4). See http://www.infodiv.unimelb.edu.au/lansg/osx/os-x3-ad.html for the instructions I wrote for joining 10.3 clients--most of the steps also apply for 10.4.
Reply
NNTPgrip said 11:18AM on 11-18-2005
I found it worked alright until the user changed the time on his machine. He then couldn't login cause the time wasn't in sync with the domain. Thing was, it screwed his profile for good as far as accessing network shares. The best method for me (in that that user doesn't bother me with it) is to just Pre-stage the AD computer and user account, Bind the mac to AD, and then just have him use a regular local mac account, access the network shares/printers, and save the credentials in the keychain.
(But then again, there are only two macs on the company net--also, all this was in 10.3 - he just upped to 10.4, and I'm interested to see if its any better now using AD login to come into the mac)
Reply