Trying to change server to be a PDC; reverts back to Standalone Server

Question

I'm trying to get my Leopard server to run as a PDC for windows authentication, but when I change the role from "Standalone Server" to "Primary Domain Controller" and click the save button, after authenticating with the "diradmin" account the changed settings all revert back to "Standalone Server" and nothing gets changed. Any clues as to what I need to do? The server is fully updated to 10.5.3, with all other software updates as well.

Answer 1

Hi Topher
I'm guessing you're referring to the post? Well the figure has gone up a fair bit since then. My overall total is quite high as I have been installing servers since 10.2.
FWIW my general rule of thumb is:
1 Format drive, install server
2 On Restart Server Assistant launches (see linked post) don't start any services using Server Assistant
3 Server Assistant does start VNC and enables SSH and the Root Account
Depending on your view SSH and Root are potentially a security problem, deal with these later on.
4 Server Assistant writes settings and preps the server for first use
5 Don't launch WGM or Server Admin. If Server Admin launches, quit it
6 Manually download the latest OS update, don't use Software Update
7 Install this and on successful restart run Software Update again and install the rest of the updates
8 Make sure server is fully up to date before launching Server Admin
9 User server's .local name to log in initially
10 Enable and Configure DNS Service first
I can't stress this enough but if you devote time and energy on this before doing anything else it can prevent a lot of hassle and problems later on. DNS does not have to be running on the Server itself. If you have another server for example you can configure DNS Services on that. You could even use 3rd-Party DNS Software and install on a client machine for example. An old Graphite G4 with DNS Enabler installed is good enough. There are PC equivalents you could use as well. This approach does not require anything in terms of processing power, large drives or even vast amounts of RAM. Reliability and correct configuration is the key.
11 Test and Qualify the DNS Service before moving onto anything else.
Once you are happy enable AFP and SMB. Create a test user in the local node and see if you can access the default share points from a client. Try it with both protocols. Don't be tempted to delete the default share points either. You'll have serious problems if you do.
12 Enable the Open Directory Service
13 Promote to Open Directory Master
If DNS is perfect the Kerberos Realm and search base fields should autofill themselves with information based on the domain name defined in the DNS Service. For example an FQDN of myserver.mydomain.com would result in MYSERVER.MYDOMAIN.COM for the Kerberos Realm and dc=myserver,dc=mydomain,dc=com for the Search Base. I always use the default diradmin name rather than any other. You should not use the local administrator account name
Launch Directory Utility and verify the loopback address (127.0.0.1) is entered as a new configuration. Access Server Admin's File Sharing window and enable the Users folder to automount for home directories. Quit out of Server Admin and launch WorkGroup Manager
Try and get into the habit of only having one or other of the Server Applications open at any one time on the server itself. Its OK to have both open if you are administering the Server remotely if you install them on a client
Authenticate to the /LDAPv3/127.0.0.1 node and you should see Directory Administrator UID 1000 already waiting for you. Create a user and select Advanced. You should see the afp url for the default Users folder. Click create home now and Save. Navigate to the Users folder and you should see a home folder created for that user, inspect the contents of this folder and you should see the usual home folder folders. Quit out of WorkGroup Manager
Launch Server Admin select SMB and go for promotion. Supply diradmin as the user name and its password and you should have the server acting as a Primary Domain Controller
Everything can be achieved using the GUI. There should be no need to resort to the command line although if you want to - as you well know - you can
As for your question? No I have not seen any problems with the 10.5.3 update. The 10.5.2 update has given me a problem on a handful of occasions. The problem was traced - eventually - to failing hard drives.
I apologize for the long post but who knows you might find it useful?
Tony