Thought I would share this information with everyone here, as it’s a great resource for this type of info.
We have been running 10.3.8 on our Panther servers for some time and it’s been really stable so I was a bit hesitant to do the 10.3.9 upgrade, but having now added some Tiger clients I could no longer hold things off so I made the plunge.
To make a long story short it caused some problems that were very ‘interesting’ to work around. Any pre 10.3.8 clients had massive problems binding to the OD server after this, and I had to run around and do a lot of last minute upgrades on design machines (designers are funny, most didn’t want to update anything which is why they were all a bit lagged behind).
After doing the upgrade on the main and backup OD servers, all the problematic machines were running managed mobile accounts and to resolve things I had to do the following:
1) Upgrade all client machines to at least 10.3.8 (I did 10.3.9 but I think 10.3.8 is the wall for this one).
2) remove the accounts in question on the OD server, and recreate them (using the same UID as previous account to head off potential UID issues)
3) unbind and rebind the directory services in Directory Access on each client machine, for some reason using the DHCP supplied LDAP was no longer working. I also had to add BSD/Local to the authentication path which I didn’t need before (I didn’t do a ton of regression on this but this is what it took to make it all work for me)
4) do a full reboot of each client machine for everything to take effect
So long story short, if you are running a combination of older clients and managed mobile accounts be careful when upgrading things. In my situation I was unable to do extensive testing and _had_ to do all of this in a live environment (why oh why can’t management understand the need for a proper test environment!??!) and wanted to save others any potential hiccups in this process.
Mark
.
.
Comments are closed