Snow leopard server licenses are still valid if I buy one today at a dealer?

Hello,
I want to buy a license for Snow Leopard server from a dealer(new license, never use) but I want to be sure you can always enable it now that other OS are output.
(I do not want to go under Lion or Mountain Lion)
(sorry for my english)
Thank you.

Welcome to the Apple Support Communities
Apple still sells Snow Leopard by phone, so you can activate Snow Leopard Server without problems

Similar Messages

  • Windows 7 (Client) map a network drive VPN Snow Leopard Server

    Hi,
    I have a Mac Mini Snow Leopard Server and are using a VPN service.
    My services on the mac os x sls server are: AFP, DNS, Firewall, Open Directory, SMB and VPN.
    I can connect the VPN from Mac clients and Windows 7 clients, but I can only map a network drive/share point on Mac´s.
    On Windows 7 I get an error: path or name not found ( I am sure using the correct path, same from Mac client that works).
    When I am using my internal network LAN I can map a network drive using Windows 7 and Mac but outside over a VPN not (only Mac works).
    The only service, at this moment,  that I need is File Sharing outside my network LAN using a VPN.
    How can I map a network drive from a Windows 7 client using a VPN, is there any Firewall rules / SMB rules / File Sharing rules that I missed on the server side?
    Thank You.

    I really don't know what are going wrong with my settings. As you said/write it must be an easy setup.
    I'm using a Time Capsule and used the Server app to add VPN to the port forwarding also.
    When I am connected thru the VPN I tried to ping the Server IP and got no answer from it, from W7 client!?
    My Mac's are just working fine with AFP and SMB share points thru the VPN.
    I think I have missed some settings from the SMB or Firewall services for VPN with W7 client's or it is a Windows issue.....

  • Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

    Hello,
    I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4.  While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD.  I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager.  Towards the end of the week though this stopped working.  Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding".  If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen.  My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else. 
    I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly.  I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD.  I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
    Is anyone else having this issue?  Any help would help me keep my sanity.
    Thanks,
    Dane

    Have you had any luck finding a solution to this?  The only thing I have found was to unbind and then bind without authentication.  Any help with progress on your end would be appreciated!
    Nick.

  • The Windows SMB feature has file locking if multiple users are accessing the same file.  Does Snow Leopard Server File Sharing (AFP) provide similar features?

    The Windows SMB feature has file locking if multiple users are accessing the same file.  Does File Sharing (AFP) on Snow Leopard Server provide similar services?

    Were you ever able to solve this problem. I'm having similar issues since upgrading to snow leopard. Four macs connect to a Windows Server 2003 for shared files. Each user has full permissions & when we "get info" it shows read & write permissions. Two of the computers were running 10.4, two were running 10.5. Everything worked properly until upgrading to snow leopard. Some files let me copy, move, delete. Others either just hang up or we get a "no permission" error. Also getting a "pdf is in use" error, even when the file/folder doesn't contain a pdf. We had our IT rep check the server who said everything is in working order. They don't represent macs any longer but feel that it's a mac problem. I would have to agree since this problem only started after the upgrade, and the one machine that was not upgraded (still running 10.5.8) is not dealing with these problems.
    Lastly, I would install 10.5 back on all of the computers if I could, but the leopard disk that came with one of the computers wouldn't work with the 2 machines running 10.4 and I didn't see it available at the apple store. I'll buy it if it's still available, but why wouldn't the disks that I have work?
    Thanks for any help

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

  • Control CS4 Licenses with Snow Leopard server

    Hi there i have a team of designers and i have to control the applications that the access and im wondering if theres a way to control the lisenses with snow leopard server application restrictions.

    You can allow or deny launching an application, to individual users, groups, computers or computer groups.
    You can't allow x number of copies of Photoshop or any application to run concurrently until a license limit is reached.
    You would need something like Sassafras Keyserver for that.
    http://www.sassafras.com/

  • I want to install Snow Leopard Server on our MacPro (2.66) using Mac Mini Snow Leopard Server disks?  I kept getting an error for backwards compatibility.   Is this possible or do I need to purchase another copy of Snow Leopard Server?

    I want to install Snow Leopard Server on our MacPro(2.66) using Mac Mini Snow Leopard Server disks?  I kept getting an error for backwards compatibility.   Is this possible or do I need topurchase another copy of Snow Leopard Server?

    The OS disks that are shipped with a particular product
    are set up so that tey will only install on that product.
    It will install on any Mini of that exact vintage, but that
    is all.
    This is to prevent people from doing exactly what you
    are trying to do.  The license for OSX shipped with any
    is only valid for that product.  Also, Snow Leopard,
    including Server, is only permitted to be run on one
    computer at a time.  Bottom line, unlike Lion, legally
    you cannot install the same copy on multiple
    computers unless some "family pack" or site license
    is purchased.
    Yes, you need to purchase another copy.
    The copy of Snow Leopard license is here:
    http://images.apple.com/legal/sla/docs/macosx_snowleopard.pdf

  • Windows VNC clients cannot connect to Snow Leopard Server native VNC server

    I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
    I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
    Does anyone have any solutions?
    == QUOTED TEXT BELOW ==
    Re: Newbie: Connect Windows -> OSX Server
    Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
    I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
    For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
    Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
    The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
    On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
    Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
    Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
    Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
    Peter
    * The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
    minor version numbers, padded with zeros.

    Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
    http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
    http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
    I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

  • Can't rename folders on Snow Leopard Server

    I have 10.6.8 Snow Leopard Server running on a new Mac Mini server. Attached I have a Pegasus Raid storing all my files. I have a sharepoint set up for every project we work on but a couple act strangely. Users can create and delete folders but can not rename them once created. In order to rename they must drag the folder onto the desktop, rename and then replace the folder on the server. All permissions are set up identical to the other sharepoints which work fine. I have had a couple so-called "experts" look at the permissions in both the terminal and Server Admin. Everyone seems stumped. Any ideas?

    Thanks for the input but I finally soved the problem. Here is what I found...
    Although I had given users/group the ALLOW/FULL CONTROL premission with a sharepoint, I discovered that in Server Admin if you double-click on the User or Group name under the ACL permissions that a drop down box appears. This box allows you to fine tune the ACL but it appears that by default all of the boxes are not checked even though I granted the user Full Control. After checking all of the boxes I was able to create and rename folders in my share as expected.
    This also had an similar effect if I denied Full Control. Some of the boxes remained unchecked and it left holes in my system where denied users could still access some files. Again by checking all boxes these holes were closed.
    Does anyone know how to change the default so that all boxes are checked when assigning the Full Control permission?

  • Error configuring services from Snow Leopard Server to Mountain Lion Server

    I am trying to upgrade a Snow Leopard Server Mac Mini to Mountain Lion Server.
    We have two Mac Mini servers at our office (production and backup) so I migrated the everything from our production server to the backup using the migration assistant when setting up the backup computer.
    I now have the backup at home trying to upgrade it to Mountain Lion Server.  I have downloaded and installed Mountain Lion as well as the Server App version 2.2.  I basically followed the simple directions found in the Apple documentation.
    I started the server app and it got to the part where it said "Upgrading services".  After running for a few minutes, I get a window that states "An error occurred while configuring your server."  It also sayd "The following actions failed or were not attempted:" with a red dot next to "Upgrading services".  The other three items:  "Authenticating to local directory", "Reading directory configuration" and "Authenticating to local directory services" have gray dots so I'm sure they were not even attempted.
    Our Snow Leopard server is setup for SMB file sharing, LDAP services, FTP, Web, DNS, DHCP.
    Can someone point me to where I can figure out what exactly is failing?  Are there specific log files I need to look into?
    Thanks

    Have EXACTLY the same issue - also tried reinstalling mountain lion server fresh and still had the same problem...

  • Moving accounts from Snow Leopard Macs to Mac mini with Snow Leopard Server

    I got my brand spanking new Mac mini today with Snow Leopard Server! So far, we (at home) were managing our accounts on individual iMacs and a MacBook Pro. While I will be getting into the innards of account migration, management etc. I thought I'd post a quick question here; Currently I have an iMac with three user accounts on it (wife and two kids). I also have my own personal MacBook Pro with my account (the only Admin account) on it. We'll soon be getting another iMac for our daughter (who currently has an account on the existing iMac). My idea in getting the Mac mini was to move to and centrally manage all the user accounts in the household on the Mac mini server. What is the best way to accomplish this? What is the best way to move the existing accounts on to the server?
    Additionally, I'll be looking into connecting the two stationary iMacs with Powerline Ethernet (where one runs Ethernet over existing electrical wires in the walls). My other option would be to rely on wireless network (I don't think this would be a good idea for if I am going to be placing the user accounts on the server and there needs to be a constant on, reliable connection between the server and the client computers as they will be talking to each other a lot!). Any thoughts on Powerline? (I am not looking forward to installing Ethernet cabling behind walls :o))
    What say the wise men of Mactopia?!
    Thanks,
    Kenneth.
    P.S. I had earlier accidentally posted this in the corresponding section of Mac OS X instead of the Mac OS X Server forum.

    Ok so the esiest way to explain this is to tell you what i just went through.
    I have 3 user accounts. All the accounts are network Users meaning that there home folder are kept on the server. I was having a problem with Time Machine giving me error 41 and error 11. After scratching my head for 2 days I ended up copying (Drag-n-Drop) the Home Folders to an External Hard Drive. I then proceeded to erase both of the internal hard drives on the mac mini and did a fresh local install of the Server OS.
    Everything was fine at that point. Now this is where Snow Leopard stopped being nice.
    I went and Created the user account again using WGM. I let WGW create the home folder and the 9 folder inside. I made sure the short names were the same and the passwords were the same as they were previously.
    However, once i Copied files from the external drive to the home folders the permissions copied as well, Which i guess should be expected. So now at this point apparently the UID's of the newly created users wasn't the same as they were before the clean install. I have multiple instances of root listed in the ACL for several folders and also had several instances of System listed sporadically.
    Now, This isn't to say that you can't drag n drop because now That I have it all squared away and everything is now working ok, I would probably still drag n drop the home folder off to an external disk, but only because I now know what to do to clean things up.
    if you drag and drop be sure to use the CHOWN command and theCHMOD commands afterwards. Take a look at this MacFixIt article: http://reviews.cnet.com/8301-13727_7-20013630-263.html?tag=mncol;title
    If you copy your local imac users to the home directory on the server you may want to follow the steps on the URL I gave plus you will most likely also have to do the following. In a nutshell you are going to use the chmod command to strip all the ACL Permissions then you are going to use the chown command to re-specify the correct owner and the correct permissions for the network user.
    !) Go into ServerAdmin and click on Sharing
    2) Go to the users folder you are using and select the user you are going to work with.
    3) Click on the Permissions option
    4) click on the +sign at the bottom (this will open the users & groups list to the right)
    5) Drag the current user from the users list to the owner permissions line under posix section
    5a) Click Save
    6) Click on the Gear button at the bottom
    7) Check the box for Owner Name and Owner Permissions.
    8) Uncheck the box for Access Control List then click ok
    Once you've gone through that rigmarole you can go back into ServerAdmin and fix the permissions for public and Sites folder which should only take a minute or so.
    So the moral of this story and as I found out when i ended up calling Enterprise support is that the act of dragging and dropping user home directories from one server to another, or as in your case, from a local machine to a the server isn't anything that apple recommends or supports. you might want to read through the man pages for "Ditto" or so apple tells me, but honestly now that you know, the steps above aren't all that bad. It's true Knowing IS half the battle!
    have Fun!
    P.S. FWIW If you run into problems and have to call Enterprise Support be prepared for them to tell you to refer to the user Guides. So reading those would be to your advantage even though they aren't the easiest things to understand unlike apple's consumer products user guides

  • Snow Leopard Server combined with Snow Leopard OS

    I have a MacPro (4x1 TB Drives, 16GB, RAID Card, 2 x Quad-Core Intel Xeon 2.8 GHz) that has MacOS 10.5 installed (including MS Windows running under VMWare Fusion).
    The RAID setup is shown at https://www.radii.org/doc
    The computer is used as an everyday workhorse (running OS 10.5.7 on Volume RS1, with Volume R1V2 partitioned into 2 data and file/document stores).
    Given the specs of the machine, I plan to setup Snow Leopard Server (Raid 0) also — on a separate partition so that when the system on RS1 freezes, the server does not have to be crashed also.
    Is there any advantage in partitioning the volume OSXSERVER to install Snow Leopard Server to perform a number of tasks:
    1. provide first level backup and coordinate backup of data to an external/offsite filestore in the clouds for two Microsoft Small Business servers, plus about 5 Mac and Windows desktop machines
    2. Provide a mail server
    3. iCal server
    4. address book server.
    The above assumes that I can run both OSs simultaneously — is that possible, or does the system for everyday usage need to be virtualised within the Server OS?? If not, which OS will manage access to the processors?

    I guess my biggest concern is the frequency with which Mac OSX gets itself tied in knots and a reboot is the only way out of the mess.
    I haven't seen that myself, personally. About the only time any of my machines get rebooted is after software update.
    Of course, server systems tend to be more focussed than client systems, so that might help too - the server is typically setup, configured and left to do its thing. It's not like you're constantly launching and quitting different applications throughout the day.
    However, I know from years of experience with desktop systems in a variety of flavours that they will need to be rebooted at least once a week.
    Ahh, there's the Windows-thinking coming through.
    I have Mac OS X Server systems that, quite literally, have not been rebooted in years. Most of them have months of uptime. Of course, this means that not all my systems are running the latest OS updates but that's a call I've made.
    in general, the smaller the capacity (memory, speed, HD) the more often they need to be rebooted.
    Sure, but that's a matter of right-sizing your server for the load you're putting on it.
    Again, there's a difference between client and server installations - client systems tend to jump between active processes with minimal background processing, whereas server systems tend to run more focussed tasks.
    I have found that software such as MS Office has been highly unreliable in the last couple of years — I still get Excel saying that it 'had to close' sometime in about 10% of the times I am using it.
    Right, but you're not running Office on your server, right?
    I was hoping there would be a better solution than having to reboot the server — or crash it when the system freezes with a kernal panic brought on by a desktop app
    Sure - don't run a desktop app on your server
    If you do see that need, then run another virtual machine for your desktop apps. That means you've got one 'master' OS running multiple virtual machines - one per server process, plus another one for desktop/GUI apps.
    Or, run all your server processes on a single server with sufficient resource (CPU, disk, memory, etc.) for the tasks you're running, and get an iMac or a Mini for those desktop tasks. Be cheaper that way, anyway.

  • How do I reinstall Snow Leopard Server on a Mac Mini Server 2010?

    How do I reinstall Snow Leopard Server on a Mac Mini Server 2010? I have already attached a Mac Superdrive and tried to download, but the buttons at the bottom of the dialog screen are greyed out.

    Not sure where you're getting tangled here or how much you know about OS X Server 10.6, so...
    AFAIK, Snow Leopard Server wasm't available as a download, it was a separate DVD distribution. 
    Unlike more recent versions of OS X Server, the 10.6 server distributions were usually standalone DVD disks, as well. 
    (There is a slight wrinkle if your Mac needs a newer version of 10.6 than your server distribution; there was a different streaming upgrade process for that.  IIRC, the appropriate OS X client version was installed first, then you booted that client version and loaded the DVD and installed OS X Server.)
    But if you have a Snow Leopard Server distribution that supports your particular Mac Mini model, then boot the DVD, use Disk Utility from the Utilities menu in the bootable DVD environment, wipe the disk, and then install OS X Server.
    You'll need a 10.6 license key, if you don't already have that.
    FWIW, here are the available manuals.

  • Complications migrating from Snow Leopard Server to Mountain Lion Server.

    I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
    "Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
    This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
    As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
    My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
    What are my options here ?
    This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
    Clear directions on how to procede would be VERY MUCH appreciated
    Thank you.

    Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
    If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
    Destroy any Open Directory replicas
    Archive your Open Directory Master (to make a backup)
    Note down your DNS records in case they get messed up
    Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
    Keep a full back of the server (you should always have backups)
    Note down your DHCP server settings in case they get messed up
    Note down any other service settings
    Install Mountain Lion
    Install Server.app
    Install Workgroup Manager (extra free download)
    Run Server.app
    Make sure settings for services are as much as possible the same as before
    If your lucky that may be all you need to do, otherwise...
    Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
    Make new Open Directory Master
    Run Workgroup Manager
    Import users and groups you previously exported
    You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
    When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

  • Snow Leopard server, Lion clients

    Good day I am running a 10.6.8 server (Mac Pro 2010) with 300 user account on it. At this time because out client computers needing compatibility with multiple applications upgrades we need to upgrade all out clients to 10.7.3. The decision has been made and I need to go with it. The server only runs user accounts, shared folders, Wiki and DNS. I am hesitant to upgrade the server to 10.7. I have attempted some quick searches for any issue with running 10.6.8 Server and 10.7 clients but it has not resulted in much.
    What is the biggest issue I am going to be running into?
    Will AFP still work with 10.7 clients?
    Should I upgrade the server to 10.7 also?
    What will I loose at this point upgrading everything?
    Looking forward to what I can learn.

    What is the biggest issue I am going to be running into?
    What issues will you run into if you upgrade your clients to Lion, but leave your server on Snow Leopard? none. That's entirely valid.
    Will AFP still work with 10.7 clients?
    Yes
    Should I upgrade the server to 10.7 also?
    Not unless you specifically need some of the features in Mac OS X Lion Server, and absolutely not if you only have one server.
    What will I loose at this point upgrading everything?
    Probably several nights' sleep. Upgrading a server, and maintaining all the services without any downtime is a significant process. Snow Leopard Server doesn't stop running just because Lion is available, and it won't stop when Mountain Lion comes along, either.
    If your mandate is to upgrade the clients, then do that, and take your time planning your server upgrade/migration.

Maybe you are looking for