Currently Being ModeratedAug 20, 2013 5:37 PM (in response to vyente)
Have you tried adding them with the Workgroup Manager for Mountain Lion?
Currently Being ModeratedAug 20, 2013 5:57 PM (in response to Francis Drouillard)
I've tried WGM however that didnt work either. I am able to successfully add a user in WGM however that user is unable to login to the server with the credentials I create. It looks like (for whatever reason), Server doesnt have permissions to access a certain ldapv3 file which is why this keeps happening. I dont know for sure but after comparing from a demo installation of ML server and looking at the logs, that seems like the culprit. Why that happened i cant tell you. Im just praying that there is a fix that wont involve me destroying my OD Master.
Currently Being ModeratedAug 21, 2013 2:59 AM (in response to vyente)
I had a similar problem... for me this worked.
Do not use screen sharing for this. Use the server app on a local machine and admin your server from that app on the local machine with admin credentials of your server machine.
Alternative: No remote, work physically on your server.
Currently Being ModeratedAug 21, 2013 5:48 AM (in response to vyente)
Anything interesting and relevent in the server logs?
Anything interesting in the server alerts?
Since it's far and away the most common cause of problems with OS X Server and with distributed authentication (Open Directory is entirely based on network encryption and digital certificates and on responses from your local DNS server(s)), verify your local DNS configuration is working and requires no changes with the following Terminal.app (Applications > Utilities) harmless, diagnostic command:
sudo changeip -checkhostname
sudo requires an administrative password. You might get a one-time warning about the sudo, and that can safely be ignored. The command will display some details, and indicate whether the local configuration appears valid and no changes are required, or further diagnostics for (most) common errors that can arise.
Currently Being ModeratedAug 21, 2013 9:52 AM (in response to MrHoffman)
I thought it was the hostname early on however there no issue with the hostname. I believe that the issue lies with the permissions and/or certificates. Somehow the permissions and/or certificates got corrupted and it doesn't have access to write to the ldapv3 file. I wish there was a way to restore the disk permissions to their default state (only on the main drive).
To me the logs indicated that the Server App cant write to a file which (I believe) is the file that lets me add/remove/edit users.
Since i don't know much about certificates i don't know how to resolve my issue and I cant rebuild this thing from scratch.
I read somewhere that the server app makes backups of itself but i don't know how true that is.