Ok, here's ViRGE's review of 10.2, even if it is a day late.
As I've said before, I love Jaguar Client. So what about Jaguar Server... it's even more lovable. Where do I start?
Server Monitor: Almost the same as it was last time. Somehow, Apple added a thermal reading for the CPU blower, which is nice considering it was the last thing I was expecting.
Server Settings: This is the depreciated form of Server Admin from 10.1. It's been stripped of most of its controls(read on), and is mainly used for settings that don't involve users/groups/access.
Server Status: This is where the logging from SA went. It features more information in terms of availible logs and statistics than SA did, and is more functional in general now that it's its own application.
Workgroup Manager: This is the workhorse of 10.2 Server. This is where all the controls are for users, groups, access, etc. Besides a new GUI, it features more features than SA ever did. Skipping what's the same, we'll talk about what's new:
You can now see what groups a user belongs to(a much needed feature that dissapeared in the ASIP -> OS X transition).
Password Server: While this needs to be activated outside WM, its main interface is in WM. While it's only compatible with 10.2 forwards, it's still nice. With PS, you can force password length, password resets, logon disables, etc. Not nessisarily new compared to ASIP, but the fact that in theory you can integrate it with other systems via LDAP makes it very interesting.
Quotas: You can now place quotas on printing and home directory size(this applies to network logins only). Printing quotas will probably be popular with a lot of people.
Mail: Slightly different features here for user settings, but nothing major unless you use it much.
Preferences: This is where half the fun is right here.
"Preferences" is the OS X version of Mac Manager, combined with some simple group policy ideas such as what's under Win2K/XP. Among other things, you can explicitly define what icons are in the user's dock, what their internet settings are(default browser, homepage, etc), what printers are listed for them, and other prefs. Most of the preferences come in both the "user can add" and "user can't add" variety, allowing you to go as far as you need to to lock something down. Perferences can be defined for someone 3 ways, per user, per group, and per computer. User and group require that the machine do a network login.
Computer control: By having the machine subscribe to LDAP(but not explicity do a network login), you can control settings by computer by having said machines MAC addresses grouped. This allows you to control a machine's preferences even if it does a local login(I haven't tried a login that's broken network wise). It also lets you set up computer groups where only certain user groups can log in; so the Sanitation Engineer isn't trying to log in to one of the Administration's computers, as this will prevent certain user names from doing a network login from certain machines.
Open Directory: OD is Apple's name for their directory system. Really, OD is 2 things. First, the OD Manager, which sets up the server to serve(or recieve) certain Directory Services, and the Password Server. If OD is on the sending end, it can serve up both the now semi-depreciated NetInfo, and LDAPv3. OD is probably the most powerful thing outside of Unix itself to come to the Mac in a long while when it comes to buisness use.
For starters, setting up a machine to do a network login is far easier under LDAP than under NetInfo. No longer do you have to mess with NI tags, instead you can let LDAP find its way on its own. Also, since it's LDAP, it's cross-platform compatible, and can hold all the usual data types. What this boils down to is integration: OS X Server can serve LDAP information for address books, where half the information is already created by creating users in Workgroup Manager. A little extra editing via the NI Manager(or the LDAP editor of your choice), and you can popular the LDAP DB to be fully functional when it comes to holding data for said address book. The new OS X Address Book integrates beautifully with this, as it can read off the users, complete with phone numbers, email addresses, etc, off the LDAP DB, all with minimal work.
Really, it boils down to the server taking care of everything for you. Under the "ideal situation", you have a Jaguar Server do your email, file serving, LDAP hosting, etc. Because of the integration, when your clients fire up Mail and look for addresses from the Address Book, they'll end up grabbing them off the LDAP DB, which got its information from the mail/file programs themselves. It's not that impressive all things considered(you could do it just as well given the time as resources on any Unix network), but its impressive for how little work it takes.
Outside of that, 10.2 Server has all of the improvements 10.2 client had. While 10.2 client was a nice upgrade for the clients, 10.2 Server really is more of a catipult for the OS X server branch. It's a bit expensive at $1000 for the unlimited CAL version, but even for simple file serving, it really is worth the upgrade. ViRGE's final judgement, 2 thumbs up.