Hey Matt,
So a couple ideas to try - I assume you're looking to get your new
machine going with the same IP and hostname, yes?
Try copying the contents of /var/db/authserver from your 10.3.9 box
and after setting up your 10.4 OD master, replace the contents of
/var/db/authserver with your copied contents rather than doing a
mergedb or mergeparent.
You may need to copy the AuthenticationAuthority from the admin
account of your 10.3.9 server into the AuthenticationAuthority of
your 10.4 diradmin user.
Another thought, although you said you had issues with the 10.3.9 -
10.4 straight upgrade - perhaps try the upgrade, backup the OD info
on 10.4, then try importing that 10.4 backup onto a clean 10.4
machine....
Cheers,
Andrina
On 29-Jul-05, at 10:15 AM, Matt Richard wrote:
Hi,
I've been preparing for months to move my OD accounts from a set
of 10.3 servers to a set of 10.4 servers. I much prefer fresh
installs over upgrades whenever possible and this looked like a
good opportunity. I regularly tested this procedure in a test
environment so that I knew it would work once I had the
opportunity. I even had Apple fix a few bugs for me that I found
along the way.
I used the procedure described here:
http://www.afp548.com/article.php?story=20050615173039158
I have a script which does the backup every night, so I just had
to do the restore on a new server.
Yesterday, the day finally came when I would migrate my OD servers
from 10.3.9 to 10.4. I used Carbon Copy Cloner to keep a close
backup of each OD server before wiping the hard drives and
installing a clean 10.4 Server system.
However once I imported my LDAP and Password Server information,
none of the users could authenticate. I tried importing several
times, with different variations, but nothing would work. I tried
restoring the 10.3.9 system on the OD master and then upgrading to
10.4, and I ran into worse problems with slapd crashes (which I
might address another time). So I had to revert back to 10.3.9 on
my OD servers.
Today I tried again, in my test environment and it worked. I
discovered that the test environment, even though it is running as
an OD master, is forwarding Password Server authentication
requests to my real (not test) OD Master.
It seems to me that the user records are somehow tied to a
specific instance of a Password Server database. If I install a
new Password Server instance, even at the same address, users
cannot authenticate against it.
Does this make any sense?
Does anyone have any helpful hints for me?
Thanks,
Matt
