RSS

Ok, Leopard is Now Enterprise-Ready

For the record, 10.5.2 fixes the problems that I was having before with Active Directory authentication and Workgroup Manager. Since last night’s upgrade, I’m able to bind and authenticate to Active Directory like we used to under Tiger, and group permissions set in WGM are picked up properly by users in those groups. This is great news for us, since we expect to be using Leopard next school year. So I guess my prior objections to Leopard in the enterprise are now moot.

Also, it looks like the crashing bug when changing colors in Preview on a first generation MacBook is now fixed. Not that that affects the enterprise, but it’s a good feature to have restored.

Powered by ScribeFire.


5 Comments Add Yours ↓

  1. Tom McNicholas #
    1

    Great news. There were wireless updates in 10.5.2 as well, I wonder if this helped you at all?

  2. 2

    10.5.1’s wireless seemed pretty stable, but we don’t have enough Leopard machines to effectively test this yet. We usually don’t do OS upgrades until the summer, so we’ll just continue trickling out Leopard to faculty and staff laptops, and see what kind of feedback we get. Personally, I’ve been rock solid since 10.5.1—but I’ve never had much trouble, even under 10.4.10 and .11.

    I’ll be sure to post here when I have something more concrete to relay.

  3. 3

    Sorry, Tom, though I have had rock solid wireless since upgrading to 10.5.2, our handful of users who’ve upgraded aren’t so lucky. It may be due to the difference in MacBook models (I have a 1st Gen, they’re using Summer 2007 models), or it may be environmental, but they haven’t seen the increased reliability that I have. Also, since I don’t have the tools anymore, I can’t test to see if their cards are still going to sleep with the same frequency as before—so I don’t know if the underlying cause is the same.

  4. Tom McNicholas #
    4

    What kind of access points are you using?

  5. 5

    We’re using Aruba AP-61s (B/G), not the AP-65s (B/G/A). We went w/ them, instead of the AP-65s because we have a majority of older machines, and at the time of our purchase there was no indication that Apple would be going with A (or N, for that matter). Had we known, last Spring, that the new MacBooks would support B/G/A/N, we probably would have gone with the AP-65s. Hindsight and all that.

    Back in October, when we had Aruba on-site for testing, we used an AP-65 in one of our worst rooms, and forced the user (who’s 2007 MacBook could support it) onto A. Unfortunately, it didn’t help. Now that Apple’s updated the drivers, we should probably give it another shot, just to rule out interference on the 2.4 GHz band.



Your Comment