GUI in MacOS for defaults

Only requests that do not match any of the IP and port specified in declarations are handled by the main nonvirtual host.

When choosing the Virtual Host that will be used to serve a request, Apache works this way:

1. It filters the Virtual hosts with matching IP adress and port.
2. IF no match was found, the default nonvirtual host is used.
3. IF one match was found, it is used.
4. IF more than one match was found, the first of them that also matches in ServerName or ServerAlias is used.
5. IF more than one match was found, but subsequently no match in ServerName or ServerAlias could be established, the first Virtual host matching in IP address and port is used.

Therefore, if you specify a Listen 80 and <VirtualHost *:80> directives in your config, that means the nonvirtual host cannot possibly be used, because everything we listen for will be caught by that Virtual host and even if the ServerName on that virtual host mismatches, it will still be matched to it according to my rule 5.

Solution is to change your main nonvirtual host into a virtual one. Putting <VirtualHost *:80> declaration around the DocumentRoot directive for the main host should be enough.

You can read about this more in Apache documentation on Name-based Virtual Host Support. Check especially the Main host goes away note.

If you want roaming profiles, your best bet may be Samba 4, which has recently become stable enough to have release candidates.

Here's a Samba 4 HowT-To which takes you step-by-step. In this howto, you configure Samba 4 as a domain controller. Then you can join your Windows clients to the domain, which gets you roaming profiles, group policy, centralized account management, redirected folders, and so on. Here you'd manage your domain using Microsoft's graphical tools (MMC snap-ins) called Remote Server Administration Tools (RSAT), so you'd never need to use OpenLDAP's command-line tools. (Though you could use those tools to query your Active Directory.)

Here's another ServerFault thread about what you can expect with Samba4: Active Directory Domain with SAMBA or Other Tool.

I am not sure about syncing Mac's user home folders with the server. Here you could take several approaches... use something to join Macs to the domain (if such a thing exists), or give Macs the ability to access files over NFS / SFTP. Here the worry is that Samba 4 uses the filesystem's extended attributes / ACLs to track file access control list, and if you give users direct access to the filesystem on your Linux/Samba server, bypassing Samba 4, NTFS permissions will be messed up. I don't know a way around this. I hope others contribute to this question.