Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Active Directory? Can't get it to work.

I am not sure if my network and/or server is really misbehaving or that I am just too stupid to understand how this should work.

I am preparing my macmini server to run a small (audiovisual) company network. I especially want to use the server as a multiplatform fileserver. I am planning to hook an Areca ARC8050 thunderbolt RAID up to my macmini as an all client shared drive.

Can OS X Server (I am running the latest version) be an OD and AD server at the same time?

Do I have to setup an AD or is it already present/active on the server side?

How do I create or find the AD domain? Both my domain and subdomain.domain don't work.

How do I find my network administrator credentials? I have never registered a network administrator account so how would I know these credentials?

User uploaded file

I have been bumping into errors all the time. No matter what settings or credentials I use.

My FQDN is server.domain.com

When I use domain.com (trying to bind client to server)

User uploaded file

I get this error.

User uploaded file

When I use server.domain.com I get this error.

User uploaded file

DNS on the server side seems to be setup alright (nothing to change).

Client uses server as DNS lookup (server has the static IP adres 10.0.0.2).

All AD related ports are open.

Binding to OD works fine.

I am really lost here. What am I missing? Hope somebody can help me!

Thanks.

Mac mini, OS X Server

Posted on Jan 2, 2014 1:57 PM

Reply
21 replies

Jan 4, 2014 4:45 AM in response to pepmachine

It is possible to run your AD server as a VM on your Mac server as long as you are using a discrete IP address for the VM. This is a precarious setup however. If you are using Parallels desktop or VMWare you are using client based tools and you will have procedural startup issues.


Consider this. In a dual directory model (AD is the master directory and OD is the subordinate), you are 100% dependent on the function and existence of the AD domain and its services. This, most importantly, includes DNS usually published from the AD controller and time. So now you have the chick/egg conundrum. If you reboot the Mac server, OD will start first but will fail to find the AD domain because it has not started yet. To start the AD domain, you will need to (1) Login to the Mac server, (2) launch the VM tool, (3) launch the Windows VM, (4) restart OD and likely all of your services to ensure that they "see" the AD domain.


This is a very manual process and one that is ripe for conditional failures.


Running Windows in a VM is great for a lab device or for testing. But running an AD domain controller in a desktop VM for production I envision being a real headache to manage. If you are going to do this, you probably should be looking at Parallels Server or another product that can be daemonized to allow for automatic start of the VMs. However, even with this, the Mac services will start first and fail to acquire the domain.


Test this before rushing into production.

Jan 4, 2014 5:01 AM in response to pepmachine

Hi


"Is the Golden Triangle achievable on a single MacMini running OS X Server and Windows Server in Parallels Desktop simultaneously?"


I did this a few years ago on a MacBook Pro using VirtualBox (which is free) as an experiment. It worked well enough although login was unpredictable at times and this was on a network consisting only of a handful of users - 3 macs, 3 PCs. But in all practical terms? Not really and Strontium90 has given you most of the reasons as to why not. However if you're determined to do it simply to answer your own question and through it gain experience, by all means have a go. You will in all likelihood be on your own though with very, very little support from anyone but yourself.


Doing it the 'other way round' ie: OS X Server in VM on dedicated Server hardware (a MacMini is not server hardware IMO) running dedicated Windows Servers gives better results.


HTH?


Tony

Jan 13, 2014 10:46 AM in response to pepmachine

piperspace wrote:



It IS possible to bind Macs to both AD and OD at the same time. This is often done in large organizations so that users can login to Macs with AD credentials and also receive desktop preferences from a departmental Mac server. However, I don't think this is a good path to a solution for your problem.



I currently have this precise setup running, at a Uni, want to use credentials from the 'global' AD here (so the students don't have to have multiple login credentials, etc) but want to restrict who can actually log in to the lab's machines, share things from the labs servers, etc.


I -think- I've done it correctly, as it pretty much works (I have strange behaviors like having to login multiple times before the login 'takes') but there are a variety of issues here and there that I'd like to look into when I have the time. For example, the AD server sets everyone's shell as csh, but I'd prefer bash be the default. Yet, I can't seem to override this anywhere, etc.


So my question is this- is there a 'best practices' document out there for AD/OD integration? I pretty much had to ad-hoc my way through dozens of people's web pages, apple's docs, etc.

Active Directory? Can't get it to work.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.