Leopard Server Upgrade Problem

I had a 10.4.11 server running without issues. Now attempted a 10.5 upgrade, everything went well. Did not disable or customize any of the install.
Serial entered ok, registration setup ok, and once I continue to the boot up, system just sits at blank space blue login window. Unable to login. I have verified through Remote Dektop'ing in that other display is blank as well. No login window appears, though ARD shows that the server is at the login window. And apparently it's running, because my old users are able to get to their lists of login names and login. Is there a way I can remotely install the server 10.5.2 upgrade. I tried using a Mac with 10.4 client to install 10.5.2 package but it fails. Any suggestions?

Okay, so after restarts and no solution, one boot gave me no video. PRAM reset wasn't even responding to keyboard input so I reset the SMU. Now it booted okay. Update went okay. But now I'm still having an authentication issue with my directory admin account. It's the server local host authentication that's failing. Even though I know the password and even reset it now. Still not allowing me to authenticate. So server is running, Tiger users can login but I can't make any new Workgroup changes.
2 things. One, how can I get the password to work again? I've seen people say to disable LDAP server to Stand Alone, then back on again. But I did that on a previous install attempt and lose all of the user and group info. To much of a pain to rebuild again. And any export I've done, doesn't resave all that info again. Is there a way to back up the users, groups and all the group permissions and shares in the Open Dir to restore back to the new directory admin?
Second, previously with 10.4 server Tiger machines logged in ok, but not leopard clients. They saw the list of network users but logged in unable to locate home directories. Now with 10.5 server, I thought it'd be resolved, but it isn't. What has to change in Directory Utility that I'm not doing? I have the server added, linking to the LDAP and AFP.

Similar Messages

  • 10.6 Server Upgrade problems for Kerberos

    While I will not claim to be the world's greatest living Mac OS X Server expert, I have setup quite a few 10.2, 10.3, 10.4, 10.5 servers. I am now trying to upgrade to 10.6 Server.
    It seems each time Apple make a major upgrade Kerberos gets even worse and more likely to break.
    I am upgrading a 10.5.8 Server which is (was) the Open Directory Master with working DNS, and Kerberos.
    After upgrading the DNS lookups still work, Network logins to Network Home directories still work - meaning Open Directory authentication still works, but Kerberos does not work, not even to the Open Directory Master server itself (let alone any other servers).
    Creating a new user account did not work either, nor did importing an archive of my 10.5 Open Directory database. What did work was converting it to a standalone server and then making it back in to a (new) Open Directory Master and then creating a new user account. Importing a text export of 10.5 users in to this 'new' OD Master and then resetting a password on the imported user(s) also worked. You will note this seems to conclusively prove that DNS is not the problem since that was not changed. As it happens changeip -checkhostname shows it is happy with the DNS name.
    Now while making a new Open Directory Master and importing the user records works, what I can't do is setup Kerberos records for the other servers I want to Kerberize. When I try using the add Kerberos record button it rejects all administrator accounts in the Delegated Administrator field. The Kerberize (server) button also is showing and also rejects all administrator accounts (I believe this button should normally not be showing if you have a working Kerberos config).
    I also can't make another 10.6 Server in to a properly working Open Directory replica as the PasswordServer refuses to start on the Replica. The same Replica did work before when running 10.5.8 as the replica to the 10.5.8 Master.
    Any suggestions from the audience? (Other than getting Hercules to house train Kerberos.)

    There was nothing obvious in the logs.
    The first attempt to upgrade the Replica (and Master) to Snow Leopard, I had before upgrading made the Replica in to a mere connected server. Last Friday I tried again but this time left it configured as a Replica. This second time the after upgrading, I still had to remake it as a Replica but it did this time successfully start and run the Password Server on the Replica.
    Both occasions used cloned copies of the Leopard installations. I don't see this small change should have made a difference but I am not going to complain if it works.
    The next issue was that Kerberos was still somewhat messed up. Clients could successfully do Kerberos logins to the Replica, and a Connected server but ironically not to the OD Master itself. The first time I got Kerberos working on the OD Master by making it a standalone server and then making it in to a (new) OD Master and setting up accounts from scratch. This second time I got it working by destroying the Kerberos database using sso_util and then using the "Kerberize" button on the OD Master. I then had to rebind the other servers to the OD Master.
    I suspect using sso_util the first time would have worked as well.
    So, it seems that upgrading from Leopard Server to Snow Leopard Server will often (100% in my case) result in a messed up Kerberos database on the OD Master, but the following will clear it
    1. sudo sso_util remove –k –d –a <directoryadministratorsshortname> -p <directoryadministratorspassword> -r <KERBEROS.REALM.ALL.CAPS>
    2. sudo rm /etc/krb5.keytab
    3. Then to rebuild the kerberos database relaunch Server Admin and go to
    ServerAdmin->OpenDirectory-> Settings and there should be a kerberize button in Server Admin>Open Directory>Settings>General at the bottom on the right.

  • 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.

  • Nslookup Snow Leopard Server DNS problems

    I have a mac mini that I'm trying to turn into a snow leopard server. Attached to the mac mini I have three external hard drives which act as back ups to our mac book pro laptops. I have installed the server software and downloaded all the updates and I can see the drives on the server and I can acess the external drives and backup to them with out a problem. The issue that I have is that when I run nslookup I get an error message which tells me that it can't find my name and that I need to rerun so software commands.
    I'm also unable to run either dns or podcast producer which was the main reason for buying the server software. I have a static ip address and believe I have configured everything correctly but I just can't seem to sort out the DNS and problems.
    Any thoughts - thanks
    Russell

    This is the Discussions > Mac OS X v10.6 Snow Leopard > Installation and Setup forum. Your questions involve Mac OS Server, which is a different OS product. Thus, you will get better results posting to the Apple - Support - Discussions - Mac OS X Server forums.

  • Snow leopard server upgrade to Mavericks server?

    I have a snow leopard server it is possible to upgrade it to Mavericks server?

    This support article has a lot of details.
    Refer to :  OS X Server: Upgrade and migration from Lion Server or Snow Leopard Server
    Your existing server sounds like it is reliable, configured correctly, has reliable backups and since you only have one service running, worst case would be to recreate the shares  and permissions once on new OS with a purchase  and installation of  Server.app 3.x from the App Store.
    Cheers

  • WLS server upgrading problems from 8.1 to 9.2

    We had our application running on WLS 8.1.
    Trying to upgrade to 9.2 using teh upgrade.sh script ( which uses 'java weblogic.Upgrade' inside ).
    Even after it has reported that it has successfully upgraded the domain, when I login using the admin console, I see that the managed servrs are missing. So are all the resources ( JMS, connectionpool etc ) and all our EJBs.
    Essentially we end up with a new admin server with nothing in it.
    Has somebody else experienced this problem ?
    If yes, are there any work arounds.
    --sony                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    I'll make this simple for you, from one point of view. You've ported your application from one major release to another major release of the application server. Are you actually considering NOT testing some aspect of your application after that major a change? You should retest every aspect of your application.

  • Cf8-cf9 and server upgrade problems

    I took over a system developed in coldfusion 8 and sql server
    2005 on a windows server 2003. I was new to all of this. I now need to upgrade to cf9 and sqlserver 2005 on a windows server 2008. someone has done the initial install of sql server cf and dreamweaver. I added java. All seems ok except I can't make the datechooser work. I activated the rds in but I still could not get to datechooser.png. I copied the directory from c.... to the same directory as my application and it showed the icon but did not do anything. I think I have 2 problems here
    1. how to I correctly map to the default CFIDE path
    2. is there something else I need to install to get the datechooser implemyed via cfinput datefield to produce a calender when I click on the icon
    Obviously I am a complete novice at this....
    Thanks in advance for any assistance

    @elizinn, someone may offer a single sentence proposal of how to fix things, but in my experience (helping solve such problems), this could be far more challenging problem to resolve than meets the eye, and all the more so if you're new to all this.
    I'll share my observations, for what they're worth. Sorry if ultimately your problem is totally unrelated, but perhaps then it will help someone else reading this later. Also, it's not clear, but I'm assuming that you DID proceed with the CF9 update. Even if you didn't, some of what I offer could still help you, if you can stick with me.
    First, you refer to not finding the DateChooser.png. Are you saying that it's somehow appearing as a broken link? Or are you getting a 404?
    As a test, it should be found at:
    http://[server]/CFIDE/scripts/ajax/resources/cf/images/DateChooser.png
    What happens when you do that? That could be useful, diagnostically.
    As for the question of mappings, and CF updates, that actually could be a real mess, from my experience, if people aren't careful about what they're doing. Things get all the more complicated when people support multiple web sites and start doing manual configurations. Let me explain.
    The problem could have to do with where the first install of CF8 put the CFIDE, and then where the update to CF9 expected to update those files. It wouldn't be hard for someone not understanding things to have told the update to put its files in a different place than the original install, which could cause IIS (and your sites and requests) to be finding the wrong files (even if not a 404, they may not be the updated version for CF9).
    At root, the problem is that during the install, one is asked whether they want to have CF use its built-in web server or an external one. If they choose the former, then the CFIDE (and related files) are put it in that web server's webroot (which is \wwwroot). If they choose the latter, then the files are put in a docroot defined for IIS. (Even there, someone may later configure things with the web server configuration tool to support several web sites, each of which could have its own web site. And for that, some will manually setup a an IIS "virtual directory" for the CFIDE, which points to whatever single one they think is the one that should be used.
    I appreciate that it may sound confusing. This is one of those things where it may be faster for you to have someone with experience look over your shoulder and help correct things. There are some of us who do that, if you're interested. I list myself and others at cf411.com/#cfassist.
    And things can get hairier still when someone then runs the CF update, where it again asks where to put the CFIDE files. They may not pay close attention to all this above (if they even understand it), and they may let the updater put the files in a different location than the IIS sites are currently configured to look at. That could then leave things not working, or not working well.
    If you want to try to sort this out yourself, look in IIS, view whatever site you're working with, and look for any reference to a CFIDE directory. If it's not there, that's a problem from the start. You will want to add a virtual directory that points to wherever it really exists (and again, you want to be careful that there may be two different ones, as only will likely have been updated by the installer.)
    If it is there, then if it's a "real" directory (within that site's docroot), then again you want to make sure it's the one that was updated in the upgrade to CF9. If not, then you may need to copy whatever files "were" updated into that directory (or delete that directory and create a virtual one to point to the right place).
    And if it's there and it's a virtual mapping, again, make sure it's whatever is the latest CFIDE (if you have multiples).
    I'll note as well that there is also a mapping in the CF Admin (on the mappings page) for CFIDE, and that's put there by the installer (and is not editable in the interface). That could help clarify where the installer put the latest files.
    Hope that's helpful.
    /charlie arehart
    [email protected]
    Providing CF and CFBuilder troubleshooting services
    at http://www.carehart.org/consulting

  • Server Upgrade Problem

    First off, I am kinda a noob when it come to macs and mac servers.
    I just got contracted by a company that runs about 40 Mac clients and 60 windows clients. Our Mail and shares are handled by a OS X 10.3.9 XServe. We have had mail problems and everytime I add a user in OD...the server laggs really bad and the server is unreachable(i.e. I cant ping it and all the shares/mail goes down). But then it goes back to normal if I just unplug the server from the network.
    These issues inspired us to upgrade the server to 10.4. First I installed all the downloadable upgrades. Got the DVD and ran the install on our extra Xserve just as a test run. I upgraded the OS, not a clean install. The install went fine with no errors. Then it restarted and it never gets past the icon of the Mac smiley face and the alternating question mark.
    Am i stuck having to run a clean install and migrate the data?

    http://www.apple.com/server/documentation/
    3rd PDF listed there, "Upgrading and Migrating"
    starting page 31
    Be careful to read each section, they mention "tar" early on, but that won't preserve all you need when dealing with certain items. "ditto" in 10.3 will be good for any Mac files with dual-fork files.
    As a general guideline (I'm simplifying but it's a guideline), what you can see in the GUI propbably has a resource & a data fork, and files hidden from the GUI ( /private/etc , /private/var /usr , /bin ) probably do not. They recommend using ditto for the mail files. A key point is that ditto makes sense for some things in 10.3 , but move away from it in 10.4
    NB page 37, "save a copy of the file /usr/bin/cyrus/bin/ctl_mboxlist"
    and page 42 onward.
    Good luck !

  • Leopard Server logon problems

    I have a G5 XServe running 10.5.7 server. Client Macs can logon OK and access all files/folders, however, if they then access files/folders locally and then go back to server it tries to reconnect and fails. This doesn't happen if the user has Admin rights - have set ACL rights to Read/Write for all users and propagated permissions. Any help much appreciated.

    Elaborate a bit about "When they access file/folders locally".
    Do you mean your users log in, access their home folder. Then click on say /Users/Shared, they don't have access?
    Keep in mind that most of the local files on the machines won't be write accessible to OD users. For instance, your users will not be able to install programs that place resources in /Library or /Applications. Nor should they be able to even place files in those locations.
    If you mean that after your OD users log in they access everything and it works... Then they log out. Then log back in as a local user on the client machine. No- they won't be able to access the file resources on the server without a proper user name and password for the shares.
    You can however defeat this by opening up the keychain access for the local user and deleting anything that stores passwords for AFP. This way, no matter what, the next time they try to access a server resource, it'll ask for a name and password. As long as that user has permissions for that resource, it should work.
    Do write back and elaborate a bit on the issue you're having.

  • Problems installing Leopard Server on Xserve

    I have an Xserve with no monitor or keyboard access. I need to install Leopard server upgrade, I read the instructions on-line and in the booklet that comes with the software. Obviously, I cannot press C upon boot since I cant see the monitor nor can I see if I need to update my bios.
    I tried enabling Remote Desktop using the kickstart command, but whenever use Chicken of the VNC to connect it says it cant find the server.
    I used the "Server Assistant" and it tells me the same thing "Cant find server" but i can ping it and log into it using terminal. I can also run all the other applications like "Server Monitor", "Server Admin", and "Workgroup Manager" just fine.
    The server is in another segment because it is in our server room I used one of the server room connection and still cant find server.
    Can someone please help getting Leopard installed on this Xserve?
    Thanks

    The general answer is yes. But the conditional answer is that you must have the original installation media from the Xserve model before it started shipping Snow Leopard exclusively. This means you would need to have bought an Xserve as recently as December to have the combo OS pack as I believe Apple stopped shipping Leopard around early January (although that might be on BTO models so if you got one from the channel it may still have the original media kit). You need to be mindful of the machine's Boot ROM version. The change of one digit can cause some issues with older installation media.
    If you don't have recent media kits, you "should" be able to construct a functional OS by building on other hardware and patching up to 10.5.8. Then cloning it to the new unit.
    And, you've peaked my interest. What specific issue have you had with 10.6 and Xsan?
    Hope this helps

  • Migrating from Tiger to Leopard Server

    Hi,
    I'm running two Mac Mini OS X Servers. One running Tiger and one running Leopard.
    All my virtual hosting is done on the Tiger server.
    I want to move everything over to the Leopard server, upgrade Tiger to Leopard (clean build) and then share accounts and sites between the two.
    I guess I'm probably going to have to go down the Open Directory route - is that correct?
    Does anyone have any good pointers of where to start this migration? Can it be done?
    Any input gratefully accepted.
    Cheers,
    Stu

    Done it the hard way.
    StuG

  • How do I upgrade Snow Leopard Server to Mountain Lion (client)?

    I have a Mac Mini Server edition (2010) with Snow Leopard Server (10.6.8) pre-installed. I don't like the interface of Server edition because 1) I don't need the server functions and 2) I prefer client OS's easier (less powerful I know) interface to do sharing, logging in, configuring.... etc.
    (I know I should've bought the non-server version with a DVD drive but I can't take it back now.)
    My question is, what's the easiest way of changing it to a 'client OS', preferably to the latest Mountain Lion? From forum posts it seems downgrading from 'server' to 'client' will definitely require a fresh install.  That's fine. I can move all my personal files to the second HDD in the Mini and do a fresh install of OS on the first HDD.
    I can see 'Mountain Lion' upgrade in the App Store, but it doesn't say if it's server or client. I am assuming it's a server upgrade?? What will happen if I purchase it for £13.99 in App Store? Or is there an alternative way?
    I have a USB Apple optical drive. I have a USB thumbdrive too for storing the OS image if required. Thank you. Any tips will be appreciated.

    Not_So wrote:
    I went to the AppStore and as I was running Snow Leopard Server it prompted me to purchase Lion Server which I didn't want.
    Luckily, I wasn't asked to purchase the 'Server' when I upgraded from SLS to Mountain Lion via the AppStore. I think your particular problem was mentioned in some other posts where the upgrade path to Lion became an infinite loop (hmmm... ). But that's all in the past now. Glad it all worked.

  • Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

    Hi,
    are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
    Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
    Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
    Thanks!

    We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

  • SNOW LEOPARD SERVER PROBLEMS REQUIRE CERTIFIED CONSULTANT TO HELP

    I've had a pretty unstable Snow Leopard server install since it was upgraded from Leopard a few months ago. Some of the problems were said to be hardware related, but I've been unable to migrate it to a different computer (Mac Mini).
    The current installation is running, albeit poorly.
    We had a Mac consultant involved in these issues, but he has proven to be unstable and unreliable as well - so we're on a search for a new consultant to give us some paid assistance in straightening this thing out.
    We're not on the US mainland, but can make the server accessible by ARD and/or SSH to someone.
    Someone with Apple certification would be preferred.

    Hi Brian,
    I'm an IT consultant dealing with Mac OS Servers and Windows Servers as well as Linux. I can offer a few helpful suggestions since just recently I transferred data from a Mac OS 10.5.8 Server to a 10.6.2 Server.
    My first question to you is what data are you immigrating from? example 10.5.8 Server Data to 10.6.2 server?
    The reason why I ask this since IMAP data in 10.5.8 and before was using Cyrus and starting in 10.6 apple switched to Dovecot.
    Initially, I did not realized that apple made the switch and had stalling problems using the apple migration tool. (Personally I don't think the tool works well since a lot of others are running into this problem when researching this issue).
    In the end I decided it was best to important everything manually, mail and not use the apple immigration tool since I think it has some issues.
    The first thing I would do is make sure the DNS is configure right so that the server can resolve it's name which is very important.
    Hopefully you're been running Open Directory . Export the users from the old server and import it to the new 10.6.2 server.
    Next transfer the IMAP mail from 10.5.8 server to the 10.6 server to the same locations.
    Example in 10.5.8 server default location is
    /var/imap
    and
    /var/spool/imap
    note this is where cyrus stored imap data in 10.5.x and maybe before. I have to look at my old 10.4 server since I'll be upgrade my own server soon.
    My clients Servers have been upgrade fine by doing the manual method.
    anyway...
    keep those two locations in mind of where you mail is stored.
    next I would copy your old cyrus mail to the new server. Don't use the migration tool at all. Just setup the new server and get the DNS running so it can resolve itself before you do this.
    also make sure mail server is not running and it's off.
    open up a terminal window
    copy and paste this but change the name of the volume/hard drive name (HD_name)
    sudo /usr/libexec/dovecot/migratemaildata.pl --cyrusBin "/Volumes/HD_name/usr/bin/cyrus/bin" --database "/Volumes/HD_name/var/imap" --sourceSpool "/Volumes/HD_name/var/spool/imap" --targetSpool "/var/spool/imap/dovecot/mail"
    ok do this will convert all of your cyrus mail to dovecot. Make sure you've already imported the users from Open Directory before doing this script.
    after all of this
    there's still one more step
    for some reason the postfix "main.cf" file is configured to use cyrus in 10.6.2 update.
    /etc/postfix/main.cf
    you can use the pico editor if you like.
    example
    type in at terminal window
    sudo pico /etc/postfix/main.cf
    it should be near the end of the file
    don't bother with anything that's in # which is ignored.
    look for
    mailbox_transport = cyrus
    then change it to
    mailbox_transport = dovecot
    save the changes
    edit settings in the mail server with server admin to what you had... I recommend don't importing the mail settings from the old server admin since some people reported that its better just to manually configure it.
    however for other server admin settings you might try to export and import to the new server.
    If you have any questions just let me know and I'm glad to help the mac community.

  • Upgrade MySQL in Snow Leopard Server

    Hi all. This is my first post.
    I have a Mac Mini Server with Mac OS X Server 10.6.8 (aka. Snow Leopard Server)
    wanted to update the native MySQL. I followed these instructions
    http://support.apple.com/kb/HT4006
    Now I know that it is parallel installation of MySQL.
    https://discussions.apple.com/message/15535136#15535136
    Finally,I installed MySQL 5.5.15 from MySQL.com (x86 dmg file)
    Now I have three MySQL servers in the system. Runs only the oldest (native 5.0.92)
    I want to:
    1) Remove unnecessary MySQL servers.
    2) I would like to MySQL service could be run in the Server Admin.app. If this is not possible to run the “MySQL Preference Pane” in System Preferences.
    If this is not possible then I would be able to run in "MySQL Preference Pane" in System Preferences.
    Working with AS is probably possible.http://www.jamesbantz.com/2010/08/08/upgrading-mysql-on-mac-os-x-10-6-snow-leopa rd-server/#more-172 (See step 6)
    Now I have a “little problem” with the distinction which files belong which MySQL.
    Please help
    Thanks

    Welcome to the forums.
    The cited Apple directions in HT4006 are for adding headers and client components for Mac OS X Server for MySQL, and not particularly for upgrading MySQL on Mac OS X Server.  (That may well cause problems.)
    How good are your pre-installation backups?  I'd roll those in, and undo the HT4006 changes, and (if you're not going to scratch this whole upgrade) follow what Mr Bantz describes in his posting.
    Irrespective of the particular path followed here, you do also still get to "own" all of these changes, including the on-going maintenance and upgrades, which means that you own any security problems, the inevitable software upgrades and updates, and whatever other fixes might be needed.
    Alternatively, consider moving to Mac OS X Server Lion (10.7), as it does not contain MySQL, so you can load whatever MySQL you want and (so long as you keep it from getting tangled with PostgreSQL) you're good to go.
    I would not generally expect to be able to use Server Admin or the other tools to use or manage your local MySQL.  The Server Admin tools are not set up for these sorts of changes and have a history of getting tangled when the underlying servers are changed.   If you do manage this goal and do have Server Admin working and whether following Mr Bantz's directions or via some other means, then your changes still might not survive any particular future Mac OS X Server upgrade, or Server Tools upgrade.  (Which means you'll have to debug and rework the changes, or find somebody that has figured out what broken and follow those instructions.)
    If you discover you have the need for these sorts of upgrades often, I'd suggest loading and using Linux or one of the BSDs.  Installing newer versions of stuff means more work and sometimes far more work, and tends to un-do what Apple provides, and tends to cause problems like you've encountered here.  In all seriousness, Linux or BSD is the platform you'll want, if you find yourself tweaking; they're set up for exactly this sort of tweaking.  Mac OS X and Mac OS X Server aims at a different market.

Maybe you are looking for