New Leopard Server
As I work more with Leopard (Mac OS X 10.5) Server, I really get excited in using the new collaboration services, especially the wiki and calendaring server. Unfortunately, these features of the Server are not ready for prime time. I had hoped with the release of 10.5.2 that the calendaring server and AFP would stabilize, but unfortunately in my experience, they still have too many problems to trust Leopard on a production server.
We have been using Leopard as a production Web only server since late November without any ill effects. The combination of Apache 2, php 5, and mySQL 5 works very well.
Unfortunately, I have tried to use Leopard as an Open Directory Master, Calendar Server, and AFP server at one account since 10.5.2 was released and in stops functioning under very light load at least once a week. The server starts refusing connections and complains and incorrect user:password combination was entered. After troubleshooting, I have not determined the cause, but I did find out the problem can be solved by stopping and starting the AFP server. Hopefully this will be fixed with the 10.5.3 release.
In remembering the transition from 10.3 to 10.4 server, I recall having problems until the release of 10.4.4. It was easy to hold off upgrading from 10.3 because there were not as many new features in changing to 10.4.
I guess that’s why they call it the bleeding edge.