I plan to have several posts related to Leopard (Mac OS 10.5) connectivity with SBS networks over the next few days, and I have a methodology defined for how I’m going to approach the various scenarios that present themselves. Initially, however, I’ve taken an existing 10.4 install that was joined to Active Directory and logging in with AD credentials and upgraded that system in place to Leopard. There was one hiccup with creating the mobile user account, but I’m not sure that wasn’t a carryover from a similar issue I’d already had with that machine.
After the upgrade, I was able to log in with the user’s AD credentials just fine. I was presented with the Setup Assistant, which I closed without completing. I was presented with two updates for Leopard, neither of which look critical to most of the clients I work with. One was an update for the Apple Remote Desktop utility, and the other was a login and keychain update. That one I reviewed the Apple KB and found that it addresses an issue with long passwords on direct upgrades from 10.1, which for me is going to be a very rare case.
I still plan on recommending a clean install with user settings transfer for most Leopard “upgrades” and that’s the case I plan on testing next. But on a clean install of Tiger with very few 3rd party applications installed, the in-place upgrade worked nicely and kept my user settings as close as they can given the changes with Leopard.
More to come…