Upgrading Tiger Server to Leopard Server

I'm about to go from Jaguar > Tiger. I'm sure it's a lower effort going from Tiger > Leopard, but I'm very interesting in seeing what the possible pitfalls might be.

My Jaguar services are pretty minimal, so to start, I only need to get DNS, Mail, and Apache. But, I had to do some manual editing of http.conf and httpd_macosxserver.conf to get virtual domains working properly. It's also my router, so again had to do some ipfw configuration for port forwarding. That stuff has probably been integrated long before Tiger server (in Panther), but it's those type of configuration issues I'm looking out for when upgrading.

Well I upgraded Tiger to Leopard... and now:

- web server doesn't work
- Software Update doesn't work
- FTP server is spotty

But other than that it worked fine Oh and Apple Tech support are of no help!

A clean install on another server worked just fine.. my advise... if you can do a clean install then do it.

--Zed

I've got to head down to Engerland at the end of the month to do an upgrade to Leopard on a bunch of G5 Xserves which are currently all running 10.3.9....

Apart from the fun that's going to be ( ), I've started to realise, via Remote Desktop, that they're all so badly in need of a complete clean up, that I'm probably going to have to rebuild them from scratch.

So I've come up with a few external Firewire drives, and I'm going to install a base Leopard install on each, then configure them over a weekend while the office is closed, meaning I can make changes and fiddle about until the cows come home - all without stuffing anything up permanently.

Once it's all working properly, I can just CCC the images on to the primary internal disks.

I think the best way to do it is always CCC it off to a second disk, upgrade there, and test the installation. Once it's working, drop it back on to the main drive.

I upgraded mine from Tiger to Leopard and it was a total disaster. The upgrade from Apache 1.3 to 2.mumble didn't work and the web services (wiki, mailing list web interface, etc) never worked right. I ended up having to wipe the box and do a fresh Leopard install before things were proper and functioning.

The impression I'm left with is that unless you're using your server in "Simple" mode, an upgrade is going to cause you grief.

Its best to just do a reinstall then an upgrade.

I plan to do 10.5 but I will wait then the school year is over and then do it. Im going to have to add new students to the list anyway.

Also, Tiger LDAP servers cannot talk to Leopard LDAP servers. So the only way you can import LDAP data is export/import if you are changing physical machines.

Seems messed up to me...

Don't Upgrade Yet!

Leopard Server from Tiger Server upgrades are AWFUL!!! iCal Server especially is virtually unuseable, and Open Directory has too many issues. Also, there is a MAJOR AFP connection bug.

Leopard Server 10.5.1 out of box seems OK, although iCal Server is hosed on one of our clients, even out of box!

Wait for 10.5.2!

We have a couple of services running on 10.5.1, but they certainly have their bugs. I recommend waiting if you can for 10.5.2 which shouldn't be too far away. Either way, do not upgrade....clean install.

Upgraded - not happy - Can I go back to Tiger?

Hi,

New to this. I'm a graphic design teacher and have to do most of my own IT. So this has been a pain in the butt! I upgraded from Tiger. Now I'm having the unknown error from Appletalk. It says -5019 error. Even after a clean install!

I have worked with Apple on the phone and paid an Apple Tech to come in. Neither fixed the problem.

So I think it would be easier to downgrade back to Tiger and wait for the 10.5.2 upgrade or this common Appletalk problem to be fixed.

Am I nuts? Should I downgrade? I currently have users with Tiger and Leopard OS. I want them all to run Leopard.

Will that work - Leopard OS users with Tiger Server?

Thanks for any input!

I second the replies for a clean install. My OD database was messed up, several of the services didn't work right or at all (wiki, SU, iCal, Web, etc). I dumped it and went back to Tiger until I had the time to do a clean install.

Everything basically works now, but I have been bitten by some weird bugs with the clean install, like AFP not authenticating properly, thus network accounts didn't work. I fixed it by archiving my OD database, then switching to a stand-alone server. Then I switched back to an OD master and restored the database. Seemed to fix my Kerberos and AFP issues. It definitely doesn't like it when you change IP addresses. I guess the devs should spend some more time with the `changeip` command.

I can't imagine actually using this in a production environment. I use it on my home network to help keep my machines in sync and to screw around with the different features. Hopefully 10.5.2 will make many of the problems go away, though I'm not optimistic.

crackpip

Leopard upgrade could be ... an issue

Upgrading MacOS server is a very hazardous undertaking.

In general, I think that upgrading from MacOS 10.4 to 10.5 is a serious problem. For commercial MacOS client boxes, doing the "archive and install" is pretty clearly the way to go.

Doing the default upgrade leaves MacOS with a lot of bad stuff.

It has been explained elsewhere that upgraded MacOS systems (both server and client variants of the OS) leave one with stale man pages. This problem can be corrected simply by deleting the old pages which allows the new (10.5) pages to be used.

There are more serious issues.

After I upgraded a number of Intel Xserves (upgrading from 10.4.10 to 10.5.0), I found that their lights off management (LOM) seemed broken in several ways. I noticed that the Server Monitor app was also broken. Investigation (both on my own and with Apple's tech support) revealed that the problem stemmed from an old kernel extension (kext). The problem could be corrected by doing a clean 10.5 server install (and then a full system reconfiguration). For MacOS server, there is NO "archive and install" option. The problem could also be corrected by moving the correct kext package (AppleBMC.kext) from a clean install to the troublesome upgraded box(es).

But here is something I think is deeply disturbing.
My upgraded boxes don't just have the one old kext.
They have have many many old kext's!

If you go to the extensions folder on upgraded and freshly installed MacOS Server systems, there are tons of differences. On my upgraded system, all (at least many many) of the kernel extensions are old whereas the same extensions have 2007 dates in the fresh installation. Since kernel extensions are essential low-level pieces of the OS, one has to imagine that they're important and that using old versions is bad and maybe dangerous.

For example, the extension autofs.kext exists in both trees. On the upgraded tree, its date is 10/29/06, its size is 166,989B and its version is 1.0.0d1. On the fresh install, its date is 10/9/07, its size is 166,525B and its version is 2.0.0.

As another example, there is an extension named AppleI2S.kext. On the upgraded tree, its date is 10/29/06 and its version is 1.0.0. On the fresh install, its date is 10/9/07 with a version of 1.0.1.

These are just two of many examples.

In many cases, the kexts seem to be the same (e.g. they have the same size and version numbers) even when the dates are different. In many many cases though, the files are different.

As a solution to my LOM issue, Apple's advice was to do a clean install. Of course this is something of an undertaking on a large set of Xserves.

As more general advice though, doing a clean install of 10.5 seems like the only way to go!

This seems more than a little worrisome and suggests very serious issues with Leopard upgrades!

My $.02,

K

Same Issues

macnrg said:

Leopard Server from Tiger Server upgrades are AWFUL!!! iCal Server especially is virtually unuseable, and Open Directory has too many issues. Also, there is a MAJOR AFP connection bug.

Leopard Server 10.5.1 out of box seems OK, although iCal Server is hosed on one of our clients, even out of box!

Wait for 10.5.2!

Click to expand...

I had identical issues (minus iCal 'cuz not using it). Luckily i got free AppleCare support and was on the phone for days...really, 24hrs+. AFP still is giving me problems...I have to reboot about every other day and it's getting annoying!

Anybody know when 10.5.2 is coming out and if it is going to fix the AFP issues...along with all the other ones?

KGoetz said:

Upgrading MacOS server is a very hazardous undertaking.

Click to expand...

...no change on 10.4 -> 10.5 then

Hell, upgrading ANY server OS tends to be rather fraught - and is something I try to avoid doing unless there is a pressing need. I generally don't upgrade unless I'm also upgrading the hardware it's running on (that goes for Windows server too - of which I've had ample experience lately, let me tell ya...)

My own Tiger server machine is staying that way - I'll upgrade to Leopard server when I buy a new box, and not before =]

artinstructor said:

Hi,

New to this. I'm a graphic design teacher and have to do most of my own IT. So this has been a pain in the butt! I upgraded from Tiger. Now I'm having the unknown error from Appletalk. It says -5019 error. Even after a clean install!

I have worked with Apple on the phone and paid an Apple Tech to come in. Neither fixed the problem.

So I think it would be easier to downgrade back to Tiger and wait for the 10.5.2 upgrade or this common Appletalk problem to be fixed.

Am I nuts? Should I downgrade? I currently have users with Tiger and Leopard OS. I want them all to run Leopard.

Will that work - Leopard OS users with Tiger Server?

Thanks for any input!

Click to expand...

What are you trying to do that causes that error? Connect to a network share? Login? etc.

Without knowing anything about your setup I'd say you need to ditch AppleTalk and use a more modern protocol for file-sharing/networking. Depending on what your trying to do, Bonjour may work, or AFP.

Upgrading Tiger server to Leopard server does not work

I tried to install in many ways for ten days and an upgrade never worked; the only way I know of getting Leopard Server to work in the least is to set it up from scratch and hand-configure everything including accounts from scratch. We use ACLs, AFP, OD, DHCP, DNS, at times FTP and Print. The OD account import doesn't work, the max. I got was to import the Archive, then import the users from WGM, and then change all their passwords form crypt to OD, needing to assign new passwords to all users; seems to be related to ACLs somehow. Since you probably don't know all users and groups and sharepoint settings out of the top of the head you need a dedicated machine with a dedicated network to peak at the old running installation, because changeip doesn't work properly neither any more, for me it never got over updating local node, I had to run each tool separately that changeip calls and for lack of feedback am not sure if each one really did what it was supposed to do. If you think you found a way to upgrade, just wait, eventually you will find a major fault with it and need to start over. The DNS has a major bug, too, if you don't know how to hand configure bind, read up on the reports on the web, don't hit the save button before changing the domain to what you want it to be, or you can start over. This was with a 10.5 install DVD, I don't think 10.5.1 or 10.5.2 is any better though.
Btw, Leopard users on Tiger Server work fine also with OpenDirectory, we use it in our office without any problems, but the Server Admin tools do not work, so your best bet --should you have an admin machine with leopard-- is to install ARD Admin and log on to the 10.4 server and manage it quasi-locally with its own 10.4 Admin tools. Of course, if you need no GUI just log on through ssh and use the CLI.

I though Microsoft was dodgy....

Reading the tread with interest…..

I have tried Apple upgrades in the past and always had to resort to a clean install. However this time I have a new server, brand new 10.5 updates to 10.5.2 and I can't brows it from MACOS9. I can mount it using the IP address, but can really use it as Sherlock fails to search, so I can't find the files I need...

I am possibly facing putting the good old 10.3 server software on instead.

Any ideas or is this "just as expected"??
Maybe I should just be happy....

Upgrade to Leopard

I’m just about to do this with 10.3.9 servers. I found that the standard POSIX permissions on are not compliant in 10.4 and 10.5. This is not a major issue in 10.4 but is for 10.5 clients, they just can't read standard POSIX structure because of ACLs. This problem shows it's self in QuarkXpress 6.5 by locking the file to Stationary Pad. (Use QXP7.3 to fix)
So what I've done is build a 10.5 Master Directory server on an old G5 and started migrate my key services one by one. Once I’m happy the 10.3 Servers will just be file servers. I'll just install clean copies of 10.5 and re-share. I'll upgrade the clients with an image using CCC.
It's a plan?

Is this the Quark 6.5 problem I'm having?

GavCam said:

I’m just about to do this with 10.3.9 servers. I found that the standard POSIX permissions on are not compliant in 10.4 and 10.5. This is not a major issue in 10.4 but is for 10.5 clients, they just can't read standard POSIX structure because of ACLs. This problem shows it's self in QuarkXpress 6.5 by locking the file to Stationary Pad. (Use QXP7.3 to fix)
So what I've done is build a 10.5 Master Directory server on an old G5 and started migrate my key services one by one. Once I’m happy the 10.3 Servers will just be file servers. I'll just install clean copies of 10.5 and re-share. I'll upgrade the clients with an image using CCC.
It's a plan?

Click to expand...

If I understand you correctly, this may explain the problem I just started having... my big concern is that I have new Macs on order and they'll all be running Leopard. We're in the process of moving to InDesign, but will still be using Quark 6.5 for several months with the new Macs. I'm trying to determine if the issue has to do with just Leopard working with Quark 6.5 files, or if it has to do with the Quark files being on my server running 10.3.9.

Is the issue with files from a server or even with just Quark 6.5 files on a stand-alone Mac running Leopard?

Don't really want to upgrade all Quark's to 7.3 when moving to InDesign in the Fall anyway.

Thanks.

Hi kfetzer,
I have found a problem with QXP6.5 files in Leopard's filing structure. You can save to a Leopard Server from Panther client as long as you set Leopard's POSIX permissions correctly. But Leopard clients want to apply ACL permissions and this is what messes everything up and QXP6.5 does not like it. We are also moving over to InDesign CS3 but have also upgraded to QXP7.3 as well because the production problems are so great. My main problem is Panther clients can't read Leopard's profile so it won't be directed to users Home folder. So I will have to upgrade 24 users all at the same time I do the servers, unless I can crack this problem. and so it goes on. Good luck to anyone else doing this upgrade.

Planning Leopard Clients, QXP 7.3 and Panther Server

GavCam said:

Hi kfetzer,
I have found a problem with QXP6.5 files in Leopard's filing structure. You can save to a Leopard Server from Panther client as long as you set Leopard's POSIX permissions correctly. But Leopard clients want to apply ACL permissions and this is what messes everything up and QXP6.5 does not like it. We are also moving over to InDesign CS3 but have also upgraded to QXP7.3 as well because the production problems are so great. My main problem is Panther clients can't read Leopard's profile so it won't be directed to users Home folder. So I will have to upgrade 24 users all at the same time I do the servers, unless I can crack this problem. and so it goes on. Good luck to anyone else doing this upgrade.

Click to expand...

My current plan is to run Leopard clients (we have new Macs on order and don't want to downgrade them to Tiger), upgrade our QXP 6.5s to 7.3s and keep running Panther Server.

From what I understand, QXP 7.3 will resolve the problem of Quark running on Leopard clients. As best I can tell, these clients running QXP 7.3 and Leopard will be able to save to my Panther server still.

Does this sound right to you?

I'm holding off upgrading the server to Leopard because (A) it just works, (B) the expense, and (C) I read so many accounts of people running Leopard server and reverting to Tiger Server due to problems still.

Thanks.
Kfetzer