new domain other then .local

[rustednuggs]

We were able to get away from the .local domain with a new build of a .corp domain. I have placed only a dozen of Apples on the new domain for testing purposes. (Making sure everything is functioning correctly, before going global with the new domain) and its working great! I do have a few questions about this setup.

 

1.) I have a Open Directory server that we use for imaging only at this time. What would be its role at this time? What can I use it for and white papers on how to do so? Do I use the OD server for policy for the macs on this new domain or do I use the windows domain controllers to do so?

 

2.) Now that we are on the new domain, what should I do with it besides placing macs on to it?

 

3.) Any docs or studies I can look to for comparisons on a setup like this?

 

4.) What does anyone else do? Lets hear it!

[jwpercival]

Macs pretty much hate a .local domain so good to hear you are implementing a new domain for all of your clients.

 

Your OD server is capable of much more such as managed preferences for all of your Mac users, centralised software updates for your Macs and, one of my personal favourites, wiki server: Apple - Mac OS X Server Snow Leopard - Wiki Server

 

Windows can do policy control for the Macs, but it involves some costly software plugins to augment your MX records. I much prefer binding the Mac clients into both the Windows AD for authentication and the Mac OD for policy management. Binding the Mac server into your AD will also allow you to create OD groups to contain your AD groups for easy and effective management.

 

There is a bunch of really useful videos here with details:

Apple (United Kingdom) - Education - Resources - Information Technology

 

Cheers,

 

John