Mac Mini 2009 vs Leopard Server

Question

Hi all...
I am hoping to get to the bottom of this asap, as I am looking forward to just getting on with things.
The issue is installation of Mac OS X Leopard Server 10.4 on a Mac Mini (Early 2009)
First of all.... Yes I have read the *Article HT3479* http://support.apple.com/kb/HT3479 and yes it allows you too boot your mini, however....
When you go through the installation process and are entering your information, there are several key steps missing from the interview[Server Assistant]. The main question missing is, "What type of installation" Standard, workgroup or advanced.
Another key set of questions missing is Network Setup.
So suffice to say the HT3479 does not address the issue i am experiencing.
Here are the methods I have attempted to use to install Server on this mini...
HT3479. {The result is that I can not run Server Preferences... Apparently the computer is in advanced mode and can not be reverted to standard}
The above method has been tried in the following examples...
* Install Mac OS X Client (10.5.6 from client disk)
+ Apply updates (at the time it was pre 10.5.7 so up to and including all updates to that time10.5.6)
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
* Install Mac OS X Client (10.5.6 from client disk)
+ Don't apply updates
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
I tried the above methods several times having no success
I contacted Apple support where I was asked to just try it again! and was told that nobody else was having these issues.
Great... 60Gb download capped reached so I had to wait for this month to continue.
10.5.7 update was released recently, so i thought I may be in luck.
So this month I have tried the above methods several times with the same outcomes.
In desperation I tried the following method...
Boot the Mac Mini in Target Disk Mode and running installation from an iMac targeting the disk in the mac mini. {The result is that during Boot up and Shut down verbose mode is invoked and there are numerous error messages in the log files, secondly I am experiencing several issues with DNS names etc.... won't accept SERVERNAME.local}
Anyway, this method gave me the most joy but still far from ideal.
Seemingly unfair it let me glimpse what leopard server can do, and yes i like what i see, but I really need to be able to install leopard server normally and have no issues.
*Hardware Configuration*.
Mac Mini (Early 2009) A1283 (2.0\1X1G\120\SD\AP\BT)
Upgraded RAM from 1GB to 4 GB (yes it works fine, full hardware test performed)
Upgraded HDD from 120GB to 320GB 7200 rpm (Caviar Black)
Samsung 22" monitor
Apple Keyboard (Aluminium with keypad) A1243
Apple Mightymouse A1152
Network
ADSL modem PPPOE
Apple Airport Extreme
Wired direct from rear of AEBS to Mac Mini
AEBS setup in DHCP, but reserved IP address for Mac Mini's Mac Address
Software
Mac OS X Server Version 10.5.4 [0Z691-6214-A] (Full retail version)
Mac OS X 10.5.6 Disk version 1.0 [2Z691-6344-A]
I am sure that others are experiencing the same issue, as many have listed similar issues to the above, however many are open ended with no resolution. I hope that if a solution is found or it is determined that there is an issue that news can be posted by apple so others are better informed before investing money in both products hoping to achieve a working network server.

Answer 1

I recently purchased a Mac Mini 320 GB model and OS X Server (Leopard). Before I purchased them I asked a couple of the Genius guys if I could run OS X Server normally on one of the new 320GB Minis? And the concensus among several Apple Store employees, was that yes, there should be no problem whatsoever...
So I bought the pair, and went through the install process numerous times, and was never able to get the standard installation until I resorted to dire measures which I have outlined below.
I tried to boot from OS X Server 10.5.4 on several machines at the Apple Store, and it does not boot any of the new machines (as of 2009.06.02). The normal install (use the os x server disk to boot) works perfect on an iMac 2.4GHz machine, and on a G4 Mirrored Drive machine, and on both of these machines the process is simple. Pop in the os x server disk, go get a sandwich, come back, answer a few questions, you are up and running, and life is great. It doesn't get any better...
The problem with the newer machines is that you must install the standard os x, get all the updates, insert os x server disk, and install os x server. The unfortunate part is that by the time you install OS X Server several items have already been set, OS X Server senses this and skips about 17 screens that allow for {"standard", "workgroup", "enterprise"} setup, and goes right into the "enterprise" mode.
One of the big conveniences with the standard setup is that quite a few things are created for you. Once you use the "standard" setup you can promote the installation to the "enterprise" mode by opening it with "Server Admin" which provides infinitely more control, but using "standard" setup to start with simplifies life considerably.
If you figure out how to do the "standard" install bear in mind that when it asks you for your administrative user account info it really wants :
name : Directory Admin
shortname : diradmin
password : astrongpassword
This will allow you to go from LOCAL to LDAPv3/127.0.0.1 when using Workgroup Manager
When it asks if you want add more users you can add one user, the "Local Admin" :
name : Local Admin
shortname : localadmin
password : astrongpassword (you will have to reset this password after you login as diradmin)
You can reset the "Local Admin" password via "System Preferences ---> Accounts"
and you can create the other users via the Workgroup Manager ---> LDAPv3/127.0.0.1 domain once you get DNS and Open Directory working.
if you use "standard" or "enterprise" the first thing to setup is DNS, everything else depends on DNS being configured correctly. "standard" really shines here because it won't let you screw up DNS.
You will need private DNS even if you have a provider handle public DNS for you.
If you are using standard you will be asked for, and can enter something like the following :
domain : crystal-palace.mac.private
machine : crystal-palace
if you are doing the "enterprise" mode you will also have to enter crystal-palace.mac.private in one more field,
Each machine will have a fixed PRIVATE IP address in the form of "192.168.1.n" and a "Computer Name" that was unique within the ZONE (the group of machines) via "System Preferences ---> Sharing".
Once you switch to the "enterprise" mode you can add more machines (using the "Computer Name" above) with their respective private ip addresses.
If you are using the "enterprise" mode, You want to setup Open Directory initially as "standalone", once that is working promote it to "Directory Master" via the "Settings" Tab. If you are using the "standard" mode, the Open Directory is setup automatically as "Directory Master" but there doesn't seem to be any way to add to the DNS, I think you have to use "Directory Utility" to do this. But if you've gotten this far it is easier to promote the setup mode to "enterprise" with "Server Admin".
I have a 1TB drive partitioned into 8 logical drives , the first seven standard partitions are named BUP_1 through BUP_7 and are provide 93 GB each. They are setup as test drives. The last partition is named TM_1 which is used for Time Machine backups and it provides close to 280 GB of backup storage.
On the first partition, I installed OS X 10.5.7 along with some basic applications that I normally use. I then created a dmg installer that I saved to TM_1 using disk utility and used that to install the image on the remaining six partitions (BUP_2 ... BUP_7).
The seven standard partitions then have OS X 10.5.7, which I basically use as test drives. It is here that I attempted different things trying to get this to be a simple deal. If one attempt didn't work I moved on to the next partition...
The BUP_n already have USERNAME setup as localadmin, not admin CHECK step ( 4 ) below. Also note that the dscl commands all have a dot following them.
Steps that worked for me, that allowed me to select the setup mode for os x server.
( 1 ) Boot mac into single user mode by holding down (CMD-S) during startup until you see text scrolling on the screen.
if the text on the screen stops, and you don't get the "root # " cursor, you may have to hit return once in order to get it. Once you get the root cursor you will need to enter the following commands very carefully. On the paths you can type part of the path and hit tab for auto completion. Everything is case sensitive...
NOTICE that USERNAME needs to be substituted with the correct shortname from step ( 4 ) in steps ( 6 ), ( 7 ) and ( 8 )
( 2 ) $ mount -uw /
( 3 ) $ /bin/launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist &
( 4 ) $ dscl . -list /Users
( 5 ) $ rm -R /Library/Preferences/
( 6 ) $ rm -R /Users/USERNAME/
( 7 ) $ dscl . -delete /Users/USERNAME
( 8 ) $ dscl . -delete /Groups/admin GroupMembership USERNAME
( 9 ) $ rm /var/db/.AppleSetupDone
( 10 ) $ rm -R /var/db/dslocal
( 11 ) $ mkdir -p /var/db/dslocal/nodes
( 12 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
( 13 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
( 14 ) $ passwd
( 15 A) $ shutdown -h now (if you want to reboot outside of single user mode)
OR
( 15 B) $ exit (if you want to continue booting in single user mode)
I think that to make this an easy install, there should be a small script from Apple that you can run once OS X, and OS X Server are installed, and updated, that reset everything to pristine, so that after running the script everything that needs to be removed, or reset is done so that you can go through the normal 17 screens that allow for simple setup of OS X Server, just like if you had been able to boot from the OS X Server disk.
The answer I got from Apple Support is that when new machines come out it takes a while to get the correct drivers and release an installer disk for OS X Server. The unfortunate part is that there is no simple way to allow the installer to select which mode they need for the particular installation. They are forced to take the "enterprise" mode...
I am not SURE whether the steps I have outlined above cover everything, that is why I am suggesting that if would be far more accurate if Apple provided an installer script when they have NON_BOOTABLE versions of OS X Server Installer.
After three weeks and about 150 hours worth of work, I finally gave up and took the Mac Mini and OS X Server back and bought another iMac 24. Whenever a newer version OS X Server that is bootable on the newer machines comes out, I will get it another shot...
The guy I dealt with at the Apple Store kept saying, it works, you're just not installing it correctly. He also said "I've installed OS X Server on a Mini". But everytime I asked him, "Was it a new new Mini?" and he would respond, "Well, NO!". I also asked him "Were you able to boot the Mini from the the disk ?", he responded "YES!"
I ran into some other issues, for example one night I shutdown the server, and the next morning none of the passwords would work, not even the root password. So I came up with the following, hope this helps.
PROBLEM :
This morning for some reason the Mac Mini would not allow me to log in, neither as the Local Admin, nor as the System Admin. The database containing the login info must have become corrupted.
FIRST LEVEL REPAIR ATTEMPT
I started the machine using the Apple Install DVD, holding the "C" key to force the CD to boot
Once the installer screen came up, hit return and select :
( 1 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Permissions
( 2 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Disk
( 3 ) Quit out of Disk Utility...
( 4 ) Menu Utilities -> Reset Password
( a ) Reset the password for the root user
( b ) Reset the password for the local admin user.
( 5 ) Quit out of Reset Password...
( 2 ) Menu Utilities -> Startup Disk
( 6 ) Select the correct disk to use for re-start.
( 7 ) Re-Start
( 8 ) I tried this several times, but could never get the new passwords to work after re-booting.
There must have still been some corruption in the database.
SECOND LEVEL REPAIR ATTEMPT
( 10 ) reboot and to hold the CMD-S to boot into the single user mode.
At the root prompt, type in the following commands. I might have to hit return, if there is a white cursor that appears to be hung up waiting for input, just hit return, then you should see the root prompt.
First try :
( 11 ) root # fsck -f
( 12 ) root # mount -uw
( 13 ) root # passwd
( 14 ) root # exit
( 15 ) when the login dialog appears try to login as root
( 16 ) if you can login, go to :
( a ) System Preferences -> Accounts and reset the password for the Local User in question.
ELSE
( b ) Go to step ( 20 ) below
THIRD LEVEL REPAIR ATTEMPT
This is the command set to reset the local DB on the server
20. $ reboot and to hold the CMD-S to boot into the single user mode.
21. $ mount -uw /
22. $ mv /var/db/dslocal /var/db/dslocal.old
23. $ mkdir -p /var/db/dslocal/nodes
24. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
25. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
26. $ passwd
FOURTH LEVEL REPAIR ATTEMPT
( 31 ) Shutdown the machine with the problem( we will call it the pm for problem machine)
( 32 ) attach a firewire cable to the pm on one end
( 33 ) attach the other end of the firewire cable to a good machine (call it gm)
In my case the gm uses firewire 400, and the pm uses firewire 800, so I had to get a cable that had firewire 400 on one end, and firewire 800 on the other,
( 34 ) start up the pm while holding down the "T" key until you see a large image floating around the pm screen. This put the pm into the "TARGET" mode, now it will behave like a drive, and you should see the drive on your gm desktop.
( 35 ) You can now copy anything you need from the pm to the gm.
( 36 ) Make sure you BACKUP anything and everything you want from the pm to the gm
( 37 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X SERVER :
At this point, if nothing else has worked you will have to erase the drive and
( a ) re-install OS X, and
( b ) re-install OS X Server on the pm
( 38 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X :
At this point, if nothing else has worked, from the Install DVD you can
( a ) Archive and re-install OS X on the pm
Another interesting thing that has happened several times now, is that I always install standard OS X on the first partition of the disk, and OS X Server on a different partition, and after installing OS X Server the machine would no longer boot from the standard OS X partition. This has happened like four different times, not sure what could be causing this problem. Booting from the install disk and running Disk Utilities to repair the disk (which comes back OK), and repair permissions always comes back with an internal error,and cannot be completed.
I have no clue what could be happening. I always had to reformat the drive and instal OS X all over again.
I have no clue what could be causing this to happen ?