Server 4 on Mac clients won't manage Mavericks Servers

I've upgraded client Macs to Yosemite and had to upgrade SERVER to version 4.  I would like to wait a while before upgrading 2 Mavericks Servers to Yosemite Servers.  Unless I'm missing something, I can no longer use SERVER 4 to manage the 2 Mavericks Servers and I can not run Server 3 on Yosemite to manager the Mavericks servers.  So it seems to me that remote management of Mavericks servers is no longer possible unless you keep around a client Mac with Mavericks as the OS.  In the past, I believe, we could run Server on a Mac and remotely manage current and at lease 1 level older Servers, pretty much the expected way to migrate servers over time.
Now the only way to manager Mavericks Servers is to use Remote Desktop (or screen sharing) to the server and run SERVER on the server, itself.
This restriction seems to be a step backwards and violates all the best practices I'm familiar with in server migration.

This particular situation has happened with nearly all versions of OS X Server over the years; at least as far back as 10.4, and quite possibly earlier.
It's rare for the OS X Server tools to work across versions, whether it is Server.app or the older Server Admin.app tools.
Usual recommendations resulting from this are either to use screen sharing into the target system or into another (older) system with the management tools, or to keep a VM around on your current with the older version installed in it where that's permitted by the Apple software license agreements, and use that to manage the remote servers.
If you want or need longer-term support and compatibility across versions and less of a push to upgrade your software to current, then one of the Linux Long Term Support versions or the Microsoft Windows Server environments are potentially better choices.  Apple traditionally doesn't keep support for older versions around.  Or get used to having some issues across versions until and unless you get everything upgraded to current. 

Similar Messages

  • Reset server password now mac mail won't except it

    reset server password now mac mail won't except it

    Applications/Utilities/Keychain Access - try deleting the old password there.

  • Blocked Incoming FTP from Mac OS X Server Via The Mac Client Firewall

    This problem began with Mac OS X Tiger's firewall and lives on in 10.6.2.
    Situation:
    Anyone with Tiger through Snow Leopard connects to my Mac OS X Server, v10.3. They have 'Passive Mode' OFF in their FTP client. They are 100% successful logging in. Their FTP client sends the LIST command and the server successfully responds with the list data.
    But the data can't get into the client's Mac. Why? The Mac OS X firewall BLOCKS IT.
    The solution? Nothing sane! You have to turn the Mac OS X firewall OFF. There is NO OTHER SOLUTION.
    All the settings on the client machine are perfect. I've been over them a hundred times over the years, tried every single combination possible. So please don't ask or I may bite you.
    What's going on: Mac OS X Server 10.3, despite never accepting Passive Mode, sends the LIST data to all client computers in, you guessed it, Passive Mode. The Mac OS X firewall will NOT accept Passive Mode. Result: Catch 22. You can't do it. You are screwed.
    Oh, but you could open all the Passive Mode ports in the firewall, and that would work? Be my guest. No way am I going to suggest that horror of a workaround to the hundreds of Mac clients I have accessing my Mac OS X Server.
    So Apple, FIX THIS. Integrate FTP Passive Mode into the Mac OS X firewall already!!!

    Ok. I was doing something a bit silly. I had the network user and the local user with the same short name. So when they were looked up the local user got preference. So I've fixed all that and am moving huge amounts of data across my humble 802.11g network now. Will have to leave it for a few hours.

  • Final Cut Server 1.5: G5 clients won't launch from icon

    So I upgraded my client from FCServer 1.1.1 to 1.5. They have a mix of G5 and Mac Pro stations. The 4 Mac Pros are all working fine after some fiddling and Java cache deleting. The G5s, however, won't run the client launched from the saved icon.
    Scenario:
    Access the client download from (IP address)/finalcutserver in a web browser - this works.
    The applet downloads and saves - this works.
    SOMETIMES it asks where to save the app - sometimes works.
    The client app runs, logs in, all working fine - great.
    BUT...if you quit and try to relaunch from that icon, it doesn't work. Purged Java caches, emptied the cache in the client, etc. - nothing. Updated from 10.5.7 to 10.5.8, same problem.
    The Intel boxes all work, none of the G5s do - seems entirely platform specific.
    -mike

    Heh... I solved this... in a manner of speaking. I really appreciate the input from Nicholas, Andy, RadUS, and everyone else, but nothing worked.
    Weird. May be actually a Java problem, not a FCSvr problem, maybe something in the Java implementation of 10.5.7 and later. But who knows? No word on this from Apple. There's a surprise.
    Here's the solution I ended up with. It's a cop-out I know, but it works!
    My solution was to put the Final Cut Server.jnlp file on my desktop and just launch it from there. You can even make it look like the desktop app if you want. Here's how:
    First you have to get the Final Cut Server.jnlp file on your desktop. It's not easy to find, because it's located in some weird temp directory somewhere buried in the recesses of the OS. If you don't know where it is, look through your browser's download history and find it. You can always redownload it by going to your server (yourserver.com/finalcutserver) and redownloading it. When you find it, move it to your desktop. Then do a Get Info on both the desktop app and jnlp file. Click on the icon for the app (the tray with the balls) and press Command C to copy the icon. Then click on the jnlp icon (the document with the cup of java) and press Command V to paste the FCSvr desktop app icon to the jnlp. Then check "hide extension" in the jnlp's get info window. Voila. You now have a "fake" desktop app. Yes, it's fake. Get over it! You won't be able to tell a difference. This is the only solution I came up with and I reinstalled Leopard twice.
    Hope this helps others too!
    Jason
    Message was edited by: nylonoxygen77
    Message was edited by: nylonoxygen77

  • Old clients won't switch from Self-Signed Certs to PKI.

    Greetings.
    I am wondering if anyone can give me advise on problem I am having with some of my sccm clients.
    When I originally deployed SCCM i used self signed certs on clients.
    We needed to add MAC and Linux support and MAC clients won't work without PKI, so I following this http://technet.microsoft.com/en-us/library/gg682023.aspx to configure Certificate Authority.
    It all seemed work well, I can now join MAC client with auto-enroll and all machines are requesting client certificates and I had couple of machine with new push on windows site installed with PKI.
    So right now I have about 250 windows clients, only 22 of them use PKI and the rest keeps using self-signed certs.
    I foolishly switched main site settings, MP settings and DP point settings to use https only.
    As a result I lost all self-signed clients and have full log for mpcontrol saying that it's rejecting clients cause they certificate cannot be validated.
    I logged in to couple of those machines and MMC i can see that it did enroll machine with valid Client Cert but Configuration Manager client itself still saying that it's using self signed one.
    Am I missing a step that I need to do to make sure that all those clients switch to PKI?

    It is. but how can i redeploy them?
    I was under impression auto push won't reinstall them. If i do deployment - that seem to reuse existing configuration and still use self signed on old machines.
    How can i verify that it does push clients to machine that already have it correctly and start using new config and not reuse old one.
    I even tried removing clients from couple of machines and see if it gets pushed again on them with proper config and those machines don't seem to get client but used to get it fine before. I keep getting new machines being added to domain and they get client
    pushed to them, but anything that had client with self signed doesn't seem to be happy.

  • FileMaker Server problem on Mac Mini Server - Mac Mini won't boot

    I just installed a brand new Mac Mini Server today, and also FileMaker Server 11. A first-timer for both Mac OS X Server and FileMaker Server, I made an error as explained below, and right now I don't know how to get back on track with the system. It won't boot.
    So, how did this happen?
    At first everything was proceeding according to plan. I configured the pre-installed Mac OS X Server on the Mac Mini with users, groups and services. This was tested from clients and this seemed to work just fine. Then I installed and configured FileMaker Server. This was also tested from a client, and the example database that came with FMS was served up just fine.
    The problem arose when I tried to install my existing FileMaker databases. I simply checked to see where in the file system the example database was located, and then copied my old databases to that location (I think it was Library > FileMaker Server > Data > Databases or something close to it - can't check it now...). I had the FileMaker Server Admin Console running, and hit the Refresh button hoping that this would make FileMaker Server find the databases.
    This was my first error. I should have read ahead in the instructions to see that one is supposed to use an Upload Database assistant instead...
    What happened when I hit refresh was that the FileMaker Server Admin Console became completely unresponsive with a spinning ball as cursor. I left it for about an hour hoping it would terminate, but gave up and tried to shut it down. It wouldn't close, so I force quit it from the Finder. Then I tried to shut down FileMaker Server, but I needed to force quit this as well. After this I thought it would be best to reboot the Mac Mini, so I shut it down, but now it won't even boot, it just stays on the screen with the spinning wheel for ever!
    I have tried all the keyboard options while booting, but nothing seems to help. In safe mode, the grey progress bar just grows to about one third, then disappears and leaves the eternally spinning wheel.
    The server version of the Mac Mini doesn't have an optical drive, only two internal hard drives. I tried to reinstall from scratch using the optical drive on another Mac on the network. The startup disk appeared when I tried to boot the Mac Mini holding down the option key, and after about 20 minutes or so of the spinning wheel I could actually access the discs. I started by running Disk Utility to check disk permissions. There were a lot of repairs concerning permissions and groups, especially on "Library". It said "ACL differs on Library", I don't know what this is but this was repaired. I then ran Repair Disk. The volume appeared to be OK.
    When I tried to reinstall Mac OS X Server however, this failed with the message
    "You can't upgrade this version of Mac OS X because a newer version is installed. Mac OS X Server couldn't be installed on this disk." I don't know how this can be, but I may have run software update earlier today.
    What should I try next? Should I erase the primary HD and try to install again? Or should I install the system software on the secondary HD? Or should I just try to reboot as is in the hope that the disk permission repairs did the trick...?
    Any helpful pointers would be greatly appreciated!

    Hello there, I came across your post when browsing the forum for passive advice. I am in the same boat as you and am a first timer for both of these tools. I work for a company who now needs to expand its network and database capabilities. I have been assigned this task and these are the tools i have opted for. I have not yet purchased them and i am pleased to find someone who has my desired setup. Could you please advise on the simplicity of the setup and whether an advanced knowledge is required.
    I want to use it in a mixed operating system environment. Is this possible?
    Regards
    Matthew

  • Best way to connect mac clients through Lion Server to AD?

    Ok, so here's what we are trying to set up for our school network. We currently have a 2003 server system hosting our PCs.
    Authentication - through 2003 server AD
    When client logs in:
    Mac Client -------sends info to --------> Lion Server ----passed data through to-----> 2003 Server
    2003 Server -----responds with authentication----> Lion Server ---applies profile management to client------> Mac Client
    My thought is that Lion Server needs to connect to the 2003 server via the active directory setup in Users and Groups, but the clients should be connecting to the Lion server via LDAP3.
    We can authenticate to the AD server directly from the clients or from the server, no issues there. Yet putting the Lion Server in "attached to another server" mode in Server Admin Tools doesn't Kerberize, even after giving proper permissions to the server via AD. I'm assuming that Kerberization needs to happen in order for Lion server to pass ther login data from the mac client to the 2003 server and vice versa, right?
    Also, we would like to have the users' 2003 network user folders on the desktop automatically, or preferrably what they access when they go to Home. I noticed some options in Profile Manager as well as Workgroup Manager to make this happen. I assume that once the data between the 3 is working proerly, this will be close to a no-brainer.
    So, advice is much appreciated here, first time setting up this type of hybrid system. Thanks!

    I appreciate all your help. I really do.
    This is basically what I needed to know - You said,
    "The audio out on a TV will source whatever input is associated with the current screen."
    With my current macmini to TV setup - I have to have a separate audio line (apart from the dvi cable for video ) to the TV. I was not sure if that macmini audio line to the TV would transfer to the receiver. If it did not then I assumed (since the macmini only has one audio out line that I would have to split that audio line - one to the TV and one to the receiver ). That was my thinking anyway, but if whatever is on the screen will transport to the receiver then I should have no problem.
    Thank you again for helping me think through this.
    Pete

  • Certain mail won't come in off the server to my Mac Mail

    Certain emails won't come in to my Mac Mail off the Time Warner Servers. (TW is intotally unhelpful and say it's my Mac Mail settings, even though some of the senders have come in before with no problem. Newer people have a hard time getting through, even though, I put them in the address book of both the TW server, and in Mac Mail.
    I also set a preference to "allow" them in both filters section  And I'll hear a "ding" when mail arrives from this person, but while I can go see it on the TW server, it doesn't come into the Mac Mail.
    It's like it's trying (the ding) but what happens to the message?
    thanks for any info you can give.
    mz

    thanks for your help... but I've deleted all my iPhone mail accounts and reentered them. The phone then proceeded to re-download all the messages from the server...except for the same ones it wouldn't before! I'm mystified. I called ATT and they didn't know what to do either. Time Warner doesn't know either.
    I've got them in my address books as well...
    Any more ideas?
    thanks

  • If I install the Mail server on a Mac Mini as a server, can my users utilize Outlook as their mail client and how will it be different for them?

    If I install the Mail server on a Mac Mini as a server, can my users utilize Outlook as their mail client and how will it be different for them?

    Your users can utilize Outlook no matter where your email is hosted at.
    how will it be different for them
    different from what?

  • Integration Mac Client and a Windows Print Server

    I want to know if it is possible to install a Mac Printer in a Windows Print Server so that later Users could connect to the WIndows Print Server and install their Mac Printer on their Mac Clients.

    I think he means the Windows server will host the printer queue and he want to add the Mac drivers to the server so that when the Mac connects to the queue the driver is downloaded automatically. This is known as Point and Print on Windows and AFAIK this is only available for Windows clients.
    When you go to the Sharing tab on a Windows server to add drivers for an alternate Windows OS to that of the server (if needed) or alternate platforms (such as x64), there is no provision to add a Mac driver.
    Another point is that the Mac drivers are usually in a format not supported by Windows, such as DMG. The Windows drivers are copied to a repository in system32 for download to the client computers and the files are typically already unpacked (installed) on the server. The drivers would not be capable of being saved in the same format.
    So I believe that by default, Windows has no ability to host the Mac driver. He would have to rely on a 3rd party product to perform such a task...
    Pahu

  • Mac Lion won't accept IP address sent from DHCP server

    Upgraded to Lion a few days ago.  Everything worked for a couple days.  Plug in the ethernet cable today and I never get an ip address with DHCP from my router.  I have 2 other devices plugged into the router and they get ip addresses normally.  Captured the DHCP communication to see if I was getting a valid DHCP offer and I am...it is included.  The Lion firewall is disabled.  For some reason Lion isn't accepting the DHCP offer.  Could this be a bug or maybe something in a cache needs to cleaned out.  I connect to several different networks daily and they all work except for this one.
    The line in Bold type shows the ip address being offered that never gets accepted by lion.
    No.     Time        Source                Destination           Protocol Info
         26 21.993141   10.19.39.97           255.255.255.255       DHCP     DHCP Offer    - Transaction ID 0x4e299603
    Frame 26 (353 bytes on wire, 353 bytes captured)
        Arrival Time: Aug  5, 2011 19:30:01.105566000
        [Time delta from previous captured frame: 0.001086000 seconds]
        [Time delta from previous displayed frame: 0.001086000 seconds]
        [Time since reference or first frame: 21.993141000 seconds]
        Frame Number: 26
        Frame Length: 353 bytes
        Capture Length: 353 bytes
        [Frame is marked: False]
        [Protocols in frame: eth:ip:udp:bootp]
        [Coloring Rule Name: UDP]
        [Coloring Rule String: udp]
    Ethernet II, Src: e8:b7:48:e6:ab:5c (e8:b7:48:e6:ab:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
        Destination: Broadcast (ff:ff:ff:ff:ff:ff)
            Address: Broadcast (ff:ff:ff:ff:ff:ff)
            .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
            .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
        Source: e8:b7:48:e6:ab:5c (e8:b7:48:e6:ab:5c)
            Address: e8:b7:48:e6:ab:5c (e8:b7:48:e6:ab:5c)
            .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
            .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        Type: IP (0x0800)
    Internet Protocol, Src: 10.19.39.97 (10.19.39.97), Dst: 255.255.255.255 (255.255.255.255)
        Version: 4
        Header length: 20 bytes
        Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
            0000 00.. = Differentiated Services Codepoint: Default (0x00)
            .... ..0. = ECN-Capable Transport (ECT): 0
            .... ...0 = ECN-CE: 0
        Total Length: 339
        Identification: 0x00fa (250)
        Flags: 0x00
            0.. = Reserved bit: Not Set
            .0. = Don't fragment: Not Set
            ..0 = More fragments: Not Set
        Fragment offset: 0
        Time to live: 255
        Protocol: UDP (0x11)
        Header checksum: 0x882c [correct]
            [Good: True]
            [Bad : False]
        Source: 10.19.39.97 (10.19.39.97)
        Destination: 255.255.255.255 (255.255.255.255)
    User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
        Source port: bootps (67)
        Destination port: bootpc (68)
        Length: 319
        Checksum: 0x038d [validation disabled]
            [Good Checksum: False]
            [Bad Checksum: False]
    Bootstrap Protocol
        Message type: Boot Reply (2)
        Hardware type: Ethernet
        Hardware address length: 6
        Hops: 0
        Transaction ID: 0x4e299603
        Seconds elapsed: 0
        Bootp flags: 0x8000 (Broadcast)
            1... .... .... .... = Broadcast flag: Broadcast
            .000 0000 0000 0000 = Reserved flags: 0x0000
        Client IP address: 0.0.0.0 (0.0.0.0)
        Your (client) IP address: 10.19.39.98 (10.19.39.98)
        Next server IP address: 0.0.0.0 (0.0.0.0)
        Relay agent IP address: 0.0.0.0 (0.0.0.0)
        Client MAC address: Apple_17:fd:5d (c4:2c:03:17:fd:5d)
        Client hardware address padding: 00000000000000000000
        Server host name not given
        Boot file name not given
        Magic cookie: (OK)
        Option: (t=53,l=1) DHCP Message Type = DHCP Offer
            Option: (53) DHCP Message Type
            Length: 1
            Value: 02
        Option: (t=54,l=4) DHCP Server Identifier = 10.19.39.97
            Option: (54) DHCP Server Identifier
            Length: 4
            Value: 0A132761
        Option: (t=51,l=4) IP Address Lease Time = 1 day, 23 hours, 39 minutes, 50 seconds
            Option: (51) IP Address Lease Time
            Length: 4
            Value: 00029E46
        Option: (t=58,l=4) Renewal Time Value = 23 hours, 49 minutes, 55 seconds
            Option: (58) Renewal Time Value
            Length: 4
            Value: 00014F23
        Option: (t=59,l=4) Rebinding Time Value = 1 day, 17 hours, 42 minutes, 16 seconds
            Option: (59) Rebinding Time Value
            Length: 4
            Value: 00024A78
        Option: (t=1,l=4) Subnet Mask = 255.255.255.240
            Option: (1) Subnet Mask
            Length: 4
            Value: FFFFFFF0
        Option: (t=6,l=8) Domain Name Server
            Option: (6) Domain Name Server
            Length: 8
            Value: AB44E278AB46A8B7
            IP Address: 171.68.226.120
            IP Address: 171.70.168.183
        Option: (t=44,l=8) NetBIOS over TCP/IP Name Server
            Option: (44) NetBIOS over TCP/IP Name Server
            Length: 8
            Value: AB443935AD2573BF
            IP Address: 171.68.57.53
            IP Address: 173.37.115.191
        Option: (t=3,l=4) Router = 10.19.39.97
            Option: (3) Router
            Length: 4
            Value: 0A132761
        End Option

    I have seen the same issue with my iOS and Mac OS devices (iPhone and MacBook Pro). I have written my own DHCP server (http://notebook.kulchenko.com/embedded/dhcp-and-dns-servers-with-arduino) and have had troubles getting my devices to connect (Windows Vista and Ubuntu devices connect fine). I suspect that this problem happens because the DHCP Offer message is sent to a broadcast address, even though (at least in my case) the broadcast flag is off in the DHCP Discover message I see.
    Unfortunately you didn't include the Discover message, so I can't tell for sure, but if it indeed has the broadcast flag set to 0, then the server should send the response message using unicast as per DHCP spec (http://www.ietf.org/rfc/rfc2131.txt, section 4.1):
      If the broadcast bit is not set and 'giaddr' is zero and
       'ciaddr' is zero, then the server unicasts DHCPOFFER and DHCPACK
       messages to the client's hardware address and 'yiaddr' address.
    So, it seems like in this case the server may be at fault, even though it would be nice for Mac OS to accept broadcast responses (and would solve my problem too).
    Can someone confirm that Mac OS does not accept broadcast responses to DHCP Discover and DHCP Request messages? Thanks.
    Paul.

  • OSX serv file saharing on AD to mac client

    I have a mac server with a shared folder, I am trying to connect to with a mac client, these are both sitting in an Active Directory environment. I can connect the mac client to my Windows server no problem, when I try to connect to the mac server I get invalid username or password error. As far as I can tell I have givewn the correct permissions etc. Any advice would be helpful as I have been trying this on and off since August last year.

    I think you are going to have to recovery the complete iPhoto database from Time Machine and then use iPhoto on the recovered database to get the photos you want.
    Allan

  • Mail won't let me turn off Server Authentication for .Mac accounts

    Greetings. Mail won't let me alter my server settings for .Mac. I am attempting to turn off "server authentication" so that I can use my .Mac account via mail through a hotel network, but every time I change the setting and exit the preferences screen Mail automatically reverts back to the previous setting. Ideas?

    Set up a new account for that with account type either IMAP or POP (not .Mac) as you desire.

  • 10.6 Email-Server/Postfix Helo command rejected - local SMTP clients won't use FQDN

    Hi,
    I set up a 10.6 server as mail-server which works (more or less) fine. I can send and receive internal and external Emails from various Macs with mail.app and Windows-Boxes with Thunderbird. However, some clients will be rejected due to wrong Helo strings
    e.g. a Windows-Box using Outlook express
    server postfix/smtpd[73194]: NOQUEUE: reject: RCPT from winbox.intranet.example.com[192.168.2.21]: 504 5.5.2 <winbox>: Helo command rejected: need fully-qualified hostname; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<winbox>
    similar happens with my router sending status-Emails (replace "winbox" with "router")
    finally my stand-alone-fax-machine uses it's ip-address as helo-string (helo=<192.168.2.10>, similar error)
    For now I've commented out
    smtpd_helo_restrictions = reject_invalid_helo_hostname
    #reject_non_fqdn_helo_hostname
    which makes things work. But that's not the right way, I guess, moreover since this entry is "fixed" by Server-Admin ever now and then.
    Does this problem arise from misconfigured boxes or a misconfigured OSX-Server? Hope the latter since there're no options to change this in my router nor my fax-machine...
    Thanks

    Try this.
         Symptoms   Users who use Microsoft Outlook as their email client and whoconnect to an email server running on Mac OS X Server v10.6 may not beable to send mail. The following (or similar) alert is returned toOutlook clients:    The message could not be sent becauseone of the recipients was rejected by the server. The rejected emailaddress was "[email protected]" is subject "example", account:"mail.example.com" , server "mail.example.com", protocol: SMTP, serverresponse: "504 5.5.2 < hostname > : Helo command rejected: needfully qualified host name", port: 25, secure (SSL): no, server error:504, error number: 0x800CCC79.      Products Affected   Mac OS X Server 10.6        Resolution    In Mac OS X Server v10.6, Postfix is configuredto require a fully qualified hostname from SMTP clients. This settingis configurable and the restriction can be removed, however anymodification of a security-related setting should be evaluated prior tomaking the change.   Once you have evaluated the change, you can use the following steps to implement it:   Note: Before proceeding, back up the /etc/postfix/main.cf file as a precaution.  
    In /etc/postfix/main.cf, locate the smtpd_helo_restrictions setting
    Remove "reject_non_fqdn_helo_hostname" from the list of settings.
    Restart the Mail service.

  • Will ML Server manage Mavericks clients?

    With the free 10.9 OS notification popping up in the App store I'm tempted to update our client computers within the media department (20 iMacs) however am a bit concerned about updating the Mini Server we have running. A couple of questions I'm hoping the community can help answer:
    1) I'm considering updating all client machines on our next INSET day. Once updated will networked user data (stored locally on the computer) remain intact? I think it will because OSX gives them a "user" folder but would just like some clarification.
    2) We're running ML server. I know there's a lot of issues with the Server App and these massive updates tend to give problems - it did when we upgraded from Lion server. Is it best to keep ML server running and not update? If we keep ML Server will it still be able to manage the Mavericks clients within our department?
    Thanks in advance, Chris

    Hi,
    I had an OSX Mountain Lion Server with open directory, profile manager ,etc. with OSX mountain Lion clients.
    This network with OSX mountain lion server continued to work fine when the clients were updated to OSX mavericks.
    However: since I updated the server with OSX mavericks the new downloaded server 3 app does not complete the configuration / installation.
    I would stay at ML for the server and mavericks for the clients the coming weeks, but that is my 2 cents
    hope this helps

Maybe you are looking for