Tiger Server Admin on Leopard

Before moving to Leopard I need to be able to administer Tiger Server.
However trying to install Server Admin Tools on Leopard tells me "you are not allowed to install the software on this disk for an unknown reason"
Can I run Tiger Server Admin from Leopard and how do I do the install ?
Kind Regards
Eric

You must install the Leopard Server Admin Tools on Leopard. You can use them to manage a Tiger system.
Page 157 of this document says:
You can use the version of Server Admin included with Mac OS X Server v10.5 to
administer Mac OS X Server v10.4.11 or later. Workgroup Manager on a v10.5 server can
be used to manage Mac OS X clients running Mac OS X v10.3 or later.

Similar Messages

Using Server Admin with Leopard 10.5 (not the server version)

I have recently downloaded the Server Admin and would like to use the xgrid function. I am running Leopard 10.5 (not the server version). Is it possible to set up a server functions to use just xgrid with Server Admin and the Leopard 10.5 non server version system software. I want to set up a really small computer cluster between my macbook and imac. My problem is that I cannot seem to get a server started so I can select which functions I want to turn on (such as the xgrid). Thanks in advance for any suggestions.

I tried several options from the link you suggested, by the xgrid lite seems to be for 10.4 Tiger. I have not been able to make it work for Leopard. Any suggestions?

Tiger Server and Snow Leopard Server

I have 2 servers. 1 is an old tiger server and the other a snow leopard. When I try to connect to either in the workgroup app. I am getting and error 14105 line 2334 error and the app unexpectedly quits. I want to be able to have a share point on the old server without users having to log in again. I would assume you could use LDAP for users but I am relatively new the MAC OSX servers. Thanks

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.

Server Admin & SNow Leopard

I recently updated my Macbook Pro to Snow Leopard. We have a Mac OS X server (10.4.8) and when i try to connect with Server Admin i get this message " Received an unexpected authentication failure. This may be caused by trying to connect to a server prior to version 10.5.8. If this is the ase, please install the latest ipdate of Mac OS X Server software and try to connect again."
We are unable to buy the software and update. And I need to manage the Server with Server Admin. Help!!

While the cost of upgrading hardware and software configurations is widely recognized, there are also costs involved with staying on older gear and older software.
If a site is planning to lock onto older software releases, then it is generally considered the site's responsibility to purchase enough hardware (servers, spares, etc) to maintain those requirements, or to make arraignments with a supplier or the vendor to provide services and support for duration of the installation; to reserve enough spare parts.
I regularly deal with enterprise-class computing gear that's a dozen or more years old, acquired from a well-known enterprise vendor, and newer hardware and component upgrades there are regularly not supported on older platforms, or newer platforms require newer software releases, or requires site-local customization work, or some combination of these. (I had problems a week or so ago simply because the mountings within the older 19" rack-mount cabinets differ, and the necessary rail-mounting kits simply aren't available.)
The deployments here can go for ten or twenty years and with few or no modifications, and that requirement requires acquiring and monitoring available spare parts and spare servers, and watching and resolving for failure patterns that might burn through the available spares.
Extending hardware support back a generation or three for newer gear also increases the testing and support matrix, and the associated costs. The vendor has more to test, is constrained around what can be upgraded, and there are the usual costs with maintaining the older gear. Those costs can and do get passed through to the customer, too, whether as vendor overhead costs or as reduced feature-sets, or both.

WGM vs Server Admin and Leopard server access

I am able to access my Leopard xserve through my firewall using Server Admin tool, but not when I try with WGM.Message is..."host unknown" ...."host unreachable." What is the difference? Not a problem with ARD either ....mmmmm. Can someone shed some light on the experience? Thanks, J Langloi

By filtering, (if I may), he meant restricting. IE: If you're going to do this, you absolutely need to have the Firewall restrict what external IPs are allowed access, rather than making those ports wide open to anyone and everyone.
But, it's pretty much industry-standard/ standard-practice to disallow connections across a company firewall to internal servers, except via VPN. (And by this I am excluding servers that are intended to be public-facing but are still appropriately firewalled).
In rare cases where VPN is not a readily-available option, it is possible to connect to both Server Admin and Workgroup Manager over ssh, but I don't suggest going that route without absolutely securing ssh in every possible way (has minor typos I wish I could fix but nothing that confuses the vital info): http://discussions.apple.com/thread.jspa?messageID=7082312

Setting the Software Update Server on Snow Leopard, Leopard and Tiger

I have made an app that will set the Software Update Server on Snow Leopard, Leopard or Tiger. It will set the Software Update Server by checking the Server's version to see if it is compatible with your OS version. If you try to use a Leopard (no Snow Leopard Hack (See http://discussions.apple.com/message.jspa?messageID=10297359#10297359)) or Tiger Server with Snow Leopard it will say it is not compatible. If it is it will set it. If you are trying to use a Tiger Server with Leopard it will set it but you will only get Tiger updates.
The app is beta, if you find any problems or have any comments please reply.
Download: http://iwczone.co.uk/projects/iSetSU/

You might want to look into throwing Software Update Enabler onto your clients.
http://www.macupdate.com/info.php/id/18059
Basically, it's just a little app that points the client in the direction of the Software Update Server - you just enter the IP of the server into the config field. With a standalone server I don't think you can get the clients to see the server without something showing them the way.
It's really very tiny and simple - I believe it just edits a com.apple.softwareupdate.plist or some such, but it made life a lot easier for us in our environment.
Hope that helps.

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

Permissions are not shown correctly in Get Info on Snow Leopard client, using Tiger server w/ ACL's

Invoking "Get Info" on a file or folder which is on a shared volume hosted by a G5 running Server 10.4 fails to show meaningful permissions when done from a 10.6 iMac. It says only that the user has "custom permissions", which is true since there are ACL's in operation. However, the Owner and Group POSIX settings are not shown, only the Everyone setting shows, making it impossible to determine which user created the file (in order to resolve issues when permissions prevent intended action). The same file or folder will show Owner and Group on 10.5 systems, as well as at the 10.4 Server itself, so we do have a workaround. I have noticed, though, that I have run into permissions restrictions where I should not, such as creating a folder on a shared volume using a 10.6 system, and then not being able to save into that folder from the same system/user.
Is there something about the implementation of ACL's in Tiger that confounds Snow Leopard's Finder?

Hi,
I did two things to get it working, and haven't taken the time to sort out which did it. But it is working so it's good enough for me.
First I followed TeenTitan's suggestion, and also checked "Allow printing from the internet". I'm behind a firewall so not too concerned I'll get someone's odd photo on the printer.
Second I went back to server admin, selected the queue under queues in the Print service, then selected IPP and deselected LPR. Bonjour went grey but stayed checked.
After this I see the printer with "@ server name" appended, and it added the printer drivers like it should.
So all working well.

Leopard Server Admin problem

I'm a bit flustrated with Leopard Server Admin - It gives errors like "Navigation operation cannot proceed" when click from one tab to another in DHCP/Subnets area back to another tab. This is one of the many problems. When I try to add Group in the Firewall, it doen't work, and things dissappear.
All in all, if this is what I have to look forward to in trying to build services using Apple's technology, no thanks.
Comments!

Leopard Server is only in beta so it's normal that there are some bugs...
If are trying to use it in an productive environment you should move to tiger which works well.

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.

How long should it take a well-qualified server admin to migrate from Tiger to Lion...

How long should it take a well-qualified server admin to migrate from Tiger to Lion...
For a small company, if the Tiger server is running on a G4 Tower:
-Roughly 500GB in user files
-Data resides on old-school ATA drives
-OD Master - Kerberized
-AFP
-Mobile Homes
-DHCP
-DNS (for 2 domains)
-FTP
-iChat
-Mail (non SSL)
-NetBoot
-Print Server
-SWUPD
-VPN
-Hosting website using MySQL
-User & Computer Management
Considerations/Hurdles/Challenges:
-Tossing old G4 into garbage, upgrading Mini client to Snow Leopard, adding Lion iMac client to the LAN
-Fresh OS installs on the Mini and iMac
-Upgrading from CAT5 to CATE on the LAN (not it the walls - just loose cables)
-All new hardware must be sourced out (take some time to price compare)
-Must find a way to transfer data from ATA drives to SATA drives or Lion Server
-Company must not have any email downtime (MX Records to be modified on DNS Providers site)
-Servers hostname goes from "companyserver.company.com" to "server.company.com"
-ISP blocks some SMTP ports
-DNS Provider doesn't support TSL/SSL SMTP
-Implementing a switch into the network
-Implementing a new router (for firewall and NAT) from ISP
Upgrading to Lion Mini Server
-All the same services
-Using SSL
-Implementing Mobile Device Enrolment and Deployment
That should just about cover it. I'll add any other details/hurdles as they come to mind.
Can you guys give me your best guesstimate as to how many hours you think this job should take? I'd appreciate any feedback as to how long you guys think it'd take you to make this transition. I'm trying to plan, and we're going to be down-and-out, the boss NEEDS to know for how long.!
Thanks in advance guys!

It's about a gigabyte, so if you have a slow connection, it might take some time.
But - you shouldn't be getting the beach ball - that's a different thing.
Can you do open Activity Monitor, or is it stuck completely?

Workgroup Manager and Server Admin 10.5 - Use to manage Tiger Server?

Is it possible to use Workgroup Manager and Server Admin 10.5 running on Leopard Client to administer Tiger Server?

I'm having major problems with server tools managing my 10.4.11 server. I'm finding that at least with the web management tools, I cannot make any changes to the 10.4 server Sites. To make matters worse, I cannot install 10.4 tools to get back that functionality.

How do I create a virtual directory in Snow Leopard Server Admin program?

Hi, how do you use the server admin program in snow leopard server to create an apache virtual directory? I can't see it in the applet anywhere. Thank you.

Well this is what I thought too but I don't think I'm doing something right. I have a default website on port 80 and I created a second site on the same port. They are two different websites. One is the initial one that comes stock with the osx. The second one I created.
When I browse to my server I get the second site. How can I get the default to be the one that points to the mail, wiki, calendar stuff, while my second domain is something totally different.
http://myserver (should be the default stuff like mail.)
http://myserver/mysecondsite (should be my other stuff.)
The problem is that when I go to http://myserver it is going to http://myserver/mysecondsite
What am I doing wrong? Thank you.

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?

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

Tiger Server Admin on Leopard

Similar Messages

Maybe you are looking for