Can Tiger Server host Leopard Clients?

Can Tiger Server host Leopard Clients?
I have Mac OS X Tiger clients on Tiger Server. If the clients upgrade to Leopard will they be able to access their user accounts or network shares?

In my case, rebooting the Tiger server restored access to all accounts except the original one that would not work. I've successfully logged in with 3 separate user accounts, and have just the one returning an unspecified error.
I did review the other post regarding setting up AFP, but we've already done that. I don't see that that could be the issue given I've got 3 of 4 accounts working. Unless there's something missing on that one account that I'm not thinking of.

Similar Messages

Tiger server, Snow Leopard Client and Illustrator CS4

We have a strange problem happening with the one Snow Leopard client we have accessing our Tiger server. In certain directories (not in all) if the user opens an Illustrator CS4 file, makes changes and goes to save the file they get the message that the file is either locked or in use by another user (it is not). This does not happen with any other kind of file in that same directory. The server is connect to AD so the user accounts come from the AD but on this machine we have the same problem regardless of the user account used to mount the server volume. It also doesn't matter if I use a local account on the server to mount instead of AD. I have the same problem if I connect via SMB instead of AFP. Other machines (Leopard) can work on these files with no problems.
A couple of other bits of information which might be useful. If the user opens the file, does a save as to the same name and same folder and replaces the original they can work on the file and save it with no problems. As soon as they close the file and reopen it they have the problem again. Also, if they run into the problem, close all programs on the computer and try to unmount the server volume they get the message that the volume is in use and cannot be ejected. I have checked and there are no invisible files being created in the directory where this file resides.
What is strange is that the problem does not happen in all directories although when it happens it is repeatable in that directory. Happens every time. I have tried changing the name of the folder to something simple and it still happens.
Any suggestions on where to go with this problem??

No progress yet. Have tried a lot of things with preferences on the server. I have confirmed with another snow leopard machine that this is not related to the machine in any way. I have not yet had a chance to test it on another Tiger server but given the fact that you are seeing it as well I would say there is a problem with the two operating systems cooperating.
As I said, I do have a temporary workaround. If you do a save as with the document, choose to overrite the original it works and then lets you continue to work on that file and save for that session. After you close the file and reopen the problem returns but at least for that session you are fine.

Tiger Server and Leopard workstatiger and Lepard workstons - Print Services

Good morning. We are running Tiger server with a 'mixed economy' of Tiger and Leopard workstations. I am finding that Workgroup Manager does not manage the print queues for users at Leopard workstations. They can see and use all the printer queues managed by Print Services. The Tiger machines are fine i.e. they just present the print queues that have been allocated by Workgroup Manager.
I assume that this is an anomaly due to Tiger Server not being 100% compatible with Leopard. But has anyone else experience of this and or a possible solution please?
Brian Bowell
ICT Support
Berkley School.

Hi Brian
Not with the Print Service specifically but I have noticed similar 'anomalies' elsewhere. For an OD environment nothing specific as such. Tiger MCX do not seem to 'take' in the same way for Leopard Clients as they do for Tiger Clients.
No shattering insight so sorry for that. Of course - you've guessed it - if its all Leopard there are no problems.
Tony

Cannot connect to iChat Server from Leopard Client

I just installed Leopard Server fresh and did all of the software updates. I let Directory Utility configure my Leopard client machine to setup all of the accounts. When I try to connect with iChat, I get the following prompt:
*Please type your Kerberos password for patrick@LKDC:SHA1.48E73...0D0.*
I enter my password on the server, and I then get:
*Kerberos Login Failed:*
Cannot resolve network address for KDC in requested realm.
My co-worker has a similar problem, but it instead asks him to type in the Kerberos password for "[email protected]". It also fails for him.
Keep in mind this is a freshly-installed Leopard Server set for basic usage. I'm literally shocked that it doesn't *just work*. I'm even more shocked that nothing I seem to try actually has any result on fixing it.
What am I doing wrong? (Or rather, what is Leopard Server doing wrong, since all I did was follow the instructions to install this thing.)
Thanks,
Patrick

Yes, the problem turned out to be that when I initially installed Leopard, the IP address I was using didn't have a reverse DNS entry. Leopard should really provide a WARNING when this is the case, as it causes so many problems across the board, and I've read so many other users having other problems because their DNS was not set up properly. Since there is no easy way to remedy this once it's installed, it's even more pertinent that an administrator be notified at the time of installation that this is the case. I fixed my DNS issue and reinstalled Leopard Server, and that solved the problem. (And yes, I will file a bug report with Apple.)

Problems when trying to admin 10.4 server from Leopard client

This seems to be a growing issue now with people updating to Leopard on their Client computers and then trying to continue administering their Tiger Servers.
Here's my story to add to this whole thing:
Updated my MacBook Pro to 10.5. I have 2 Xserves, one is a G5 and the other is an Intel. Both are running 10.4.10. The 10.4 Admin Tools were left intact after the upgrade, but I was quite excited to use the 10.5 Admin Tools, as the UI looks like such a huge improvement, and I updated those apps asap. Yes, without checking to make sure you could even admin 10.4 servers with 10.5 admin tools! Silly me!
So I tried to connect to my servers using the 10.5 tools, and it wouldn't connect. I didn't even get the message saying my servers didn't have Server 10.4.11, but I knew something was wrong, so I searched to find the requirements for using 10.5 tools. Lo and behold I stumbled upon the tech doc stating 10.5 Admin Tools requires 10.4.11 if you want to admin Tiger servers. Bummer.
So then I had to reinstall the 10.4.7 Admin Tools, and yes, you can't install these tools in Leopard. I did find out that you can just bring these apps from a computer that already has them installed and just use them, so I grabbed the apps out of the /Applications/Server folder on the 10.4 servers themselves using ARD.
Everything seemed to be working ok, until I tried to edit an account in Workgroup Manager. All aspects of an account's information is grayed out and un-editable. I made sure it was authenticated to the LDAP as the directory administrator and it was. I tried repairing permissions and while Disk Utility did fix a whole bunch of permissions in the Admin Tools apps, it still did not solve this issue.
Has anyone else seen this? I really hope I don't have to wait until the release of 10.4.11 to edit user accounts. If so Apple better release it soon!!
Thanks in advance.
Message was edited by: DanIsHere

I think the problem is that typically in Apache if you don't have an index.html file then the server will display a listing of files in its directory. This is controlled by having an "Options Indexes" directive in the configuration file httpd.conf.
If your permissions on the folder in question don't allow you to read the folder contents, then if your index.html is missing this error may come up.
Also, if you don't have an index.html file, and you have "Options -Indexes" then you will not be allowed to browse the folder.
Your best bet is to create a new index file.

Can the server kick the client?

Hello,
how can I realize, that the server is able to quit the connection to the client?
thx
Tobias

Well there may be a way to extract the socket reference from the client reference, and close it;
but I suspect most clients would think this a network related failure, and simply reconnect to your server.
Basically, once a reference to your server is given to a client, either using a registry, or some other method; that client is free to pass it around to other remote clients, and all of them can use it to contact your server.
I think that's a neat part of RMI, I use that tecnhique a lot in my free RMI project : https://cajo.dev.java.net
RMI is not like a standard socket-based network application. It is intended to allow access to an object in one VM, by other remote VMs. The socket mechanism is abstracted away, in fact, you can even run RMI on non-socket based communication channels. Why I've even heard that one crazy guy managed to get RMI working over UDP! :-) http://www.rmiproxy.com/download/RMI-UDP.zip
(BTW: rmiproxy.com has some excellent solutions, if you are in a position to purchase them)
If not being able to disconnect clients is a feature you can't work without, then perhaps RMI is not the right technology for your application, but I hope it can be, because it's so cool! :-)

Can the server software be downloaded independently for SL server, as it can for 10.9?

I have a Mini with 10.6.8 and want to add server capabilities. What are my options, aside from "find a used copy of SLS , buy it, and instal over your existing system"?
Grant

If your box supports it, upgrade to Mavericks. As you are aware, that involves purchasing and downloading OS X Server from the Mac App Store.
Snow Leopard Server is a separate DVD distribution, and it's getting tougher to deal with 10.6 in general — the newer AirPort can't be managed that far back, for instance. Other software is already dropping 10.6, too. You won't be able to remotely manage the 10.6 server from Mavericks, other than via command line or screen sharing.
As for your question, you can upgrade from Snow Leopard client to Snow Leopard Server given the DVD (possibly still available from Apple, if you call), though there are some wrinkles in how that is done depending on whether your Mac needs a newer version of Snow Leopard than the available Snow Leopard Server DVD might contain; there weren't as many releases of Snow Leopard Server as there were of Snow Leopard client. If the OS X Server version is older than the OS X version your Mac requires, you'll have to boot 10.6 client, load the DVD, and install that way; you won't be able to boot the DVD directly.
Here's the Apple web page for older versions, but you may (will?) have to call and see if Snow Leopard Server is still available.
And FWIW and though I'm aware of OS X Server 10.6 boxes at various sites at various sites, I'd still encourage using 10.9 for new installations and not 10.6.

Client Upgraded from Tiger to Leopard Can No Longer Connect to Tiger Server

I just finished upgrading a G5 2GHz DP Powermac from Tiger to Leopard. This was an Archive and Install upgrade with importing the old settings. After verifying the account migration, including .Mac connectivity, and fixing all 3rd party software compatibilities/upgrades, I tried to connect to our Tiger 4.11 server by clicking on the server's Icon in the Shared section of the Finder Sidebar. The finder then switches to browse the the server for shares: "Connecting..." is displayed under the tool bar, with a "Share Screen..." and "Connect As..." buttons to the right.
At this point the "Connecting..." remains displayed with the spinning circle in the bottom right of the Finder window.... spinning. This situation continues for several minutes until is seems the system gives up.
If I click on the Path button on the Tool Bar, and go up to the Shared level, ALL the Shares on the Network are displayed, including all the Tiger Client machine shares. I can click on the triangle beside the Tiger Client's icon, and all the drives and home directories on the Mac are listed. All the client shares can be accessed without any issues. NOTE: There are no other Leopard clients on the LAN.
Prior to the Leopard upgrade, this client could connect to the Tiger server as well. All the other clients on the LAN can access the Tiger server also.
On the Leopard client I have tried clicking and the "Connect As..." button and using the menu "Connect to Server" and specifying the server's IP, and I get the same "Connecting..." message with a "non-connecting" result.
I can only assume that somehow the Account Name and password are not being passed correctly. But, using "Connect As..." should resolve that. However, "Connect As..." does not give me a user/password window!
If I check the AFP Access log on the Server, the only messages displayed are "Mounted Volume..." No messages in the error log, and no messages in the "Connections" section.
Can anyone help me figure out why the Leopard client can not connect to the Tiger Server?
My apologies if the description of my problem is a bit disjointed. I have been thrown into server admin and am learning "Trial by Fire".
Any help or suggestions on how to resolve this issue will be greatly appreciated.
Thanks
Gary
Message was edited by: Gary Sumlak

OK. A quick update.
After waiting for about 10 minutes for the rotating circle in the bottom right corner to stop, I was able to click on the "Connect As..." button. It took another 10 minutes, but the Connect As window eventual popped up. I entered the Userid and Password (saving to Keychain) and was able to see all the sharepoints on the the server. I browsed all the connected drives and folders without issue.
I then disconnected from the server. Reviewing the AFP logs on the server shows messages for the connection Login and Logout.
I then tried to reconnect to the server, and again another 10 minutes wait, although this time the Leopard client eventually connected automatically with the proper User, as per the AFP logs confirms.
Although, the client can now connect to the server, for it to take 10 minutes will be unacceptable to management, not to mention the end user. Tiger clients can connect in a couple seconds!
Is there a way to reduce the Leopard login time to, say, a couple seconds, like it does with the Tiger clients?
Again, any help or suggestions would be greatly appreciated.
Thanks
Gary

Leopard client login problem (Tiger server)... why can't I authenticate?

I look after a number of Macs and PCs at my company. Most Macs are running the latest version of Tiger but the newest machine came with Leopard. All users log into network accounts on our Xserve, running OSX Server (Tiger). However, the Leopard client machine refuses to log in to any network account, including the one I set up specifically for the machine's user, shaking its login window at me.
Users connect using Open Directory Master on the server and none of the Tiger clients have ever had problems logging in.
On the troublesome client machine, I have bound to the server correctly in Directory Utility which declares that the server is responding normally. At the login screen I get a green light and "Network Accounts Available" when I click through the options above the user name field so I know the machine can see the server.
I can successfully log in to a local account and subsequently mount the server volumes using the new name and password I've set up for the user.
What have I missed?
So far, in my attempts to resolve this I have done the following:
Removed the password from the new account;
Unbound from the server, changed the short name of the computer, re-bound to the server;
Tried logging in to other accounts known to be working;
In WGM checked that the NFSHomeDirectory entry shows the complete path for the user's home directory;
Trawled through endless forums for clues.
Kerberos is not running. Does it need to be for authenticating Leopard users?
Is there an issue with clear text passwords in Leopard? Seemingly eliminated through a no-password test account.
I'm sure that I logged in successfully once after setting up the machine but, after installing Leopard updates, logging in has consistently failed.
Anyone else having similar problems? Better yet, anyone have any answers?

No need to apologize. I learned the same way you are...
I think you may end up re-binding the 10.4 clients if you kerberize the server.
You may want to go to the server forum for folks with more definitive annswers.
http://discussions.apple.com/category.jspa?categoryID=96
In any case, make sure you have a reliable backup before you do anything.
Jeff
Message was edited by: Jeff Kelleher

Local KDC (LKDC) relating to Leopard clients logging into Tiger Server

This is a follow-up to my posting on this thread:
http://discussions.apple.com/message.jspa?messageID=5982070#5982070
Pursuing the problem I had when I upgraded to Leopard, I found it odd that trusted binding to Tiger OD from a Leopard client created a funny computer entry in the Workgroup Manger (WGM). Previously when using trusted binding from a Tiger machine to a Tiger server, one entry would be created. And Logging in as an OD user worked every time for me. However, it appears that under 10.5.1 Kerberos has changed significantly in that it is now being used extensively through the Leopard OS for Peer-to-Peer applications. This may account for the screwed up Computer account entries in WGM when a 10.5.1 client binds to 10.4.11 Server using trusted binding. The giveaway clue to this is the LKDC:SHA1 entry created in the WGM computer record (usually 3 seperate records for 10.5.1 instead of the normal single record with a Tiger client). My question is this:
Are there any changes that can be performed via command line on the 10.5.1 client to mimic the old 10.4 client Kerberos configuration without pervasive Peer-to-Peer use of Kerberos? Is is a config setting for the mit.kerberos file? Could it be as simple as flipping a switch to get the older more compatible Kerberos config of a 10.4 Tiger client? Can I dump the Local KDC present in Leopard, and get back to the good old days of non-local KDC under Tiger?
http://www.afp548.com/article.php?story=LeopardServerReview-LocalDirectory
"The Local KDC
Yes, you read that right, the local KDC. All Leopard client systems will now create a Local KDC for use with peer to peer file sharing.
While this isn't even as close to as scary as it seems, it is a topic worthy of at least a separate article, if not a whole series. I put on my thinking toque and sat in my thinking corner for a while on this, and I've not yet been able to come up with a reason for why having a KDC on every machine is less secure than how 10.4 did things. Having said that, though, I fully understand how this can seriously freak out your network security team as they don't quite grasp all the ins and the outs of this. Combine this with Back to My Mac, another article that's forthcoming, and you have a very interesting collection of some "sleeper" features in Leopard.
So, in a nutshell, a Local KDC, the LKDC, is created when 10.5 is installed. Local users will get LKDC authentication authorities allowing them to get Kerberos tickets and use that for single sign on to all the services hosted on that client system. Kerberos is supposed to be only used when you use Bonjour to discover the other machine. So primarily in peer to peer on the same LAN cases.
It works, you can see this for yourself. Screen share to another machine as a local user by picking the machine out of the sidebar in the Finder. You'll have to enter in your password the first time, but after that you can close out of that screen sharing session and restart it without having to re-enter your password. You can also see the ticket in the Kerberos.app, still buried in /System/Library/CoreServices."

Eric,
Thanks so much for your thoroughness and assistance. I think we have decided, for now, to forgo the 10.5 clients attaching to the 10.4 server because of too many intermittant issues. Similar machines on 10.5 gave different results. And at this point, our client is very skittish about the process working at all. I think we need more testing and that is the directon we'll take for now.
Here are some of our results:
I did find information on afp548 regarding the 10.5 preference. It was specificall referenced in this article:
http://www.afp548.com/forum/viewtopic.php?forum=18&showtopic=16064
Clearing the check box on the 10.4 server under OD > Settings > Security "Require password change on new user login" did solve the memory issue that kerberos was having. After clearing the setting, I:
* deleted all binding references at the server (WGM > Accounts > Lists > All Computers
* Deleted the bindings at the client and the the LDAP server references in Directory Access
* Restarted the machine
* Reconnected the LDAP server, Rebind the machine
* Check the LDAP search in issuing id <username> in Terminal
* OPen System PReferences > Accounts > Login Items, the preference is there!
* Yeehah
Oh, but the user still can't login in that machine. Uhm, why? I have no idea. I take a new machine, 10.5.1, no login accounts except a local admin, and no that user still cannot login. Other users, no problem, but not that user.
Take a new system, 10.4.11, set up the binding, the LDAP server, try to log in that same user: works every time. Ugh.
So of course, I think there is something up with that user, but nothing in logs gives an indication of what is going on. That I can find. THis is after 10 hours of testing and trying. Needless to state, the client is frustrated, and so am I.
You know, we do have one 10.5.1 client laptop that did work. After lots of binding and rebinding, it just somehow starting working as expected. But, the reason that we're sticking with 10.4 clients for now is that machine will not respond to password change mandates. I select that user in the WGM, check the "require password change on next login" and nothing happens on their end. They are not an admin, I have reset their account more times than I can count, and so I expect there are more non-working items with 10.5.1 clients and 10.4 server that will get me. It needs more testing for now.
So, back to your message, I haven't tried the SSL certificate, but I will give that a try.
In general, for your network, how are your laptop users configured? As mobile users? Network homes? Or Local homes?
Thanks again for your help. I really appreciate it.

Leopard Clients Take 10 Minutes to Connect to Tiger 10.4.11 Server

I have a single Tiger server OS X 10.4.11, on a LAN with 5 Tiger Clients and 2 Leopard clients, all with up-to-date patches.
My problem is, that ALL of the Tiger clients can access any of the server shares almost instantaneously, but when I try to connect a Leopard client the the server, it initially takes a minimum of 10 minutes! If I just click on the server <as displayed on the Finder SHARED tab>, the connection eventually fails. However, if I click on the "Connect as" button, after about 10 minutes, I get the user/password login, and the Leopard client connects immediately, and all the data on all the share points are accessible.
But, if I don't actually mount a share point (i.e. see a the Network drive icon on the desktop), and use finder column mode to navigate through the shares, if I click on a local drive in the same finder window, I have to go through the whole 10 minute wait again before I see the user/password login.
So my question:
Why is it taking a minimum of 10 minutes for the Leopard clients to connect, where as the Tiger clients connect immediately?
So, if anyone can help me trouble shoot or resolve the server settings so that the Leo clients can connect as quickly as the Tiger clients, I would be extremely grateful.
BTW - I followed the setup instructions precisely as per the Linda.com *+Mac OS X Server v10.4 Tiger Essential Training+* CD.
TIA
Gary
All the shares are setup as:
General:
Share this item and its contents.
Access:
Owner=Root (Read & Write);
Group=Staff (Read & Write);
Everyone (Read Only);
No ACL
Protocols:
Apple File Settings:
Share this item using AFP;
Allow AFP guest access;
Custom Name=<unique name>;
Default permissions for new files and folders=Use standard POSIX behavior
Windows File Settings:
Share this item using SMB
Allow SMB guest access
Enable strict locking
Default permissions for new files and folders:
Assign as follows: Owner=Read & Write; Group=Read & Write; Everyone=Read Only
FTP Settings
Share this item using FTP
Allow FTP guest access
Common FTP name: <same unique name>
Network Mount
Where: LDAPv3.127.0.0.1 (locked)
AFP is setup as follows:
General:
Enable Bonjour registration
Access:
Authentication=Standard
Enable Secure connections
Client & Guest connections=Unlimited
Logging:
(Everything); Archive every 7 days
Idle Users: (nothing checked
All staff members are defined as part of the "staff" group.

Windows File Settings:
Share this item using SMB
Allow SMB guest access
Enable strict locking
Default permissions for new files and folders:
Do you have any Windows clients on your network? If not turn OFF the SMB server and change the settings here so there is no SMB sharing.
FTP Settings
Share this item using FTP
Allow FTP guest access
Common FTP name: <same unique name>
Do your users access this sharepoint with FTP from inside your network? If not, stop the FTP server and change the settings to not share this via FTP.
General:
Enable Bonjour registration
Turn this off for all sharepoints. If you have no Bonjour-only printers -like some of those POS HP color Laserjet 26xx or 36xx series- enter this in Terminal.app or through the 'Send UNIX command...' in ARD to all of your Leopard clients:
launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
user should be root if sent from ARD, prepend 'sudo' (without quotes) if in Terminal.app or if you're using an admin username from ARD. This turns off Bonjour.
Also, in WGM, look at each individual user account and see if the 'Primary Group ID' is listed in the 'Other Groups' list. If it's not, click the '+' sign and drag the user's primary group into the 'Other Groups' list and then save. You can 'shift-click' and select groups of users and add the group to them all at once if they are all in the same groups.
Access:
Authentication=Standard
Change the access to 'Any Method'. If your clients are all bound to the OD master and the sharepoints are listed in the directory (meaning Kerberos SSO works for all clients and users), the clients will try Kerberos first and anything else -like DHX authentication- if that fails. Also, if you are managing your clients with MCX you should have those shares mounting before log-in -meaning at startup- using guest access or at login with the username/pass.

Leopard client controls view of tiger server share point

Hi, recently purchased a Mac Mini running Leopard all patched. Connected via afp to a Xserve RAID, Xserve running a sharepoint using ACL's. In list view the leopard client controls the list view on the Xserve, meaning that all the other Tiger clients see the leopard clients folder structure when they connect to the sharepoint. I have not changed any settings on the Xserve, just re-propogated the permissions and ACL's.
Any ideas would be great,
Andy

ipb1962 wrote:
BUT When I use the DHCP service to specify my DNS to a Leopard Client from (Tiger Server on a G5)
it does not resolve to any internet address.
Can you clarify what you mean here?

Panther and leopard clients on a tiger server...expected problems...

I wanted to share a scenario that is happening in the school district I work for and see if anyone has had any experiences similar and can offer some advise before I blindly proceed.
One of the schools I work in uses a single 10.4x server, and all the users in the school have a network account where they can log into managed work groups.
The computers are all running 10.3x and I have had no problems at all. Users are able to log in, see their network home folders, launch all the allowed applications.
The school is purchasing 76 new Imac computers with the new 10.5 OS on them and I was wondering what kind of problems users might experience when logging into these new workstations if they are bound to the existing server.
I was able to bind a 10.5 mac to the 10.4 server and was able to log in using a network account, see the items that were in my network home folder, launch applications I was permitted to launch and was denied applications denied in the applications preference in workgroup manager for the workgroup I was logged in to.
This is very preliminary testing and was wonder what some of you who are in similar situations have experienced.
Another concern is best described by painting a scenario.
A user logs onto a 10.3 computer and launches an application like imovie, an older version of imovie, and does some work on a project. He then saves it and moves to one of the new imacs with 10.5 on it and a newer version of imovie.
Will the newer version of the application run with the older preference files for it.
Will the preference files be rewritten and if so will the old version of imovie be able to read those or will it try and rewrite them.
Will the project created with the old version of imovie be readable by the new version.
Will the new version of imovie update the project file and if so with the old version of imovie still be able to open it?
I seem to remember reading something about how panther wrote preference files for applications completely differently than tiger did, and if so then can I expect the same for leopard client written pref files.
As you can see I have lots of questions and if I can learn from other peoples experiences then I can go into this knowing a little bit on what I can expect and hopefully this wont be a big disaster.
Mark
SD34

Will the newer version of the application run with the older preference files for it.
While I dont know this for certain, I do know that when I did an archive and install (which copies the old preferences for applications as well as the apps themselves to the new system folder) things have worked fine. I think the preference-writing scheme depends on the individual program version, and minor updates to the program (ie: Safari 3.0.3b vs 3.0.4) shouldnt change this.
Will the preference files be rewritten and if so will the old version of imovie be able to read those or will it try and rewrite them.
When you modify any preferences the files will be rewritten. If the programs have similar versions then they should be fine. All preferences are written to the same directory (~/Library/Preferences/) so if the program versions are the same then the preferences will be written similarly.
Will the project created with the old version of imovie be readable by the new version.
I'm assuming you mean going from iMovie HD to iMovie '08. I've not done this personally, but as far as I know the files will import, but the transistions and other special effects that are only available in the older version of iMovie will be removed. The media files and sequences should be preserved.
Will the new version of imovie update the project file and if so with the old version of imovie still be able to open it?
I dont know about the old version of iMovie being able to import the new version's projects, but the new version will update the projects when you save it.
I seem to remember reading something about how panther wrote preference files for applications completely differently than tiger did, and if so then can I expect the same for leopard client written pref files.
I believe the writing of preference files usually depends on the individual application, not the system.

What client-style apps can you run on Leopard Server?

I have a small network and therefore want my Leopard server to also support a small number of OSX applications: iTunes (including iTunes sharing), DVD Player, Safari, Mail, etc. to allow me to use it as an occasional workstation for small tasks.
Is this possible? I assume Leopard Server has all the underpinnings of Leopard, but it's not clear on the Apple web site.
Other than risking server stability, are there any other issues with doing this?
Thanks.

I would agree with the assessment that Tiger Server is roughly as stable as Tiger Client where running 'client' applications (I would refer to them as GUI-based apps run from the console). I can't comment on the stability of Leopard Server in the same regard; haven't had it out of the box long enough yet.
You have to ask yourself how much stuff you really want to run on the server; if it's a business-critical server that you can't afford much downtime on, then installing a lot of applications will start to work against you. In addition to eating up processor and memory resources that could be used by Mail, Web service, etc., GUI-based apps may make your server somewhat more crash-prone.

Leopard Client Tiger server mobile home directory not working... hmmm

Mobile home directory is not working for my leopard clients with my tiger server.
I can log in via the Apple server account that is set for mobile.
On my tiger clients it prompts me to confirm my mobile account on log in and everything works fine if i unplug the network cable.
on my leopard clients no prompt at log in. so i go to account under system prefs and see that the account says mobile..and i click on make mobile account in the account pane in system prefs says will reboot and make account.. prompts for password for mobile account i put it in and then it says there was an error in making mobile account and then it takes me back to the main log in window.
every client i have on leopard does this...
am i missing something?
thanks in advance,
Jesse

Tiger server can control mobile account syncing and other features present on Tiger clients.
See this post for some more info on setting Leopard mobile account preferences on Tiger servers:
http://discussions.apple.com/thread.jspa?messageID=6829482&#6829482

Can Tiger Server host Leopard Clients?

Similar Messages

Maybe you are looking for