Lion client snow leopard server

I had 30 macbooks running 10.6 authenticating to a snow leopard server. All worked really great. 15 of the laptops were stolen and now I am in the process of replacing them. However, I am finding the macbook is no longer made and I will need to use a macbook pro. Macbook pros come with lion installed. Will Lion clients authenticate to a snow leopard server? Can I create home directories on the the server for lion clients as I have done with my snow leopard clients. Any suggestions would be appreciated. Thanks.

Hi
"Will Lion clients authenticate to a snow leopard server?"
Yes. Snow Leopard Server will support 10.5, 10.6 and 10.7 Client OS.
"Can I create home directories on the the server for lion clients as I have done with my snow leopard clients?"
Yes. AFAIK home folders are not dependent on the OS version in any appreciable way. Granted there are some very minor differences but as long as the Desktop and Library folders exist within the parent container and are read/writable for that user that's all there is to it.
HTH?
Tony

Similar Messages

Installing Lion on Snow Leopard Server

I have mac mini server running snow leopard server. I want to install Mac OS X Lion on it.
I have purchased Lion through App Store, but while installing on mac server it asks for Lion Server.
I am not using any server features as of now, Can I downgrade snow leopard server to client and instal Lion on it?
or is there any better way of installing Lion on Snow Leopard Server...
Thanks,
K

No easy way unfortunately.
OS X Server gets its fingers into all parts of your computer. You'd have to go in an manually remove hundreds of files, and replace them with their counterparts from the non-server version.
It would be MUCH easier to back up your home folder and any additional files you need, then nuke and pave with Lion non-server. Restore your info, and you'll be back up and running.
HTH
-Graham

Install Lion over Snow Leopard Server

I have a mac-mini that was purchased with Snow Leopard Server (the server model from just over a year ago).
Turns out, I haven't used any of the server functionality that wasn't already in the base User/Consumer version of OS X, so I want to just install Lion and not waste $50 on the Server Add on.
I've tried this via the Mac App Store _AND_ via the USB dongle. It wont install. When you try to run the Lion installer, it gives a "waiting for the App Store to download the Server Add-on" dialog. It gives you the option to cancel if you don't want that ... but cancel doesn't do what a reasonable person would think: skip the server add-on. Instead, it cancels the entire installation.
Anyone had this problem? Anyone know how to work around it? or if there's a work-around at all?

instead of that, I just told it to erase my time-machine partition, and install there. (it refused to install over the top of my "server" partition). Since I had recently done a full backup to an external drive, I wasn't worried about that path. It has taken a bit more work to get fully up to speed, but it at least worked.
But, either path (downgrade to SL client, then upgrade to Lion sans Server-add-on vs blow away an install and install elsewhere) are both ****-poor user experience designs in my opinion. Though, I doubt it matters now, since all future stuff will be via the Mac App Store, and you can just tell that to uninstall Server.

Admin tools on Lion to Snow Leopard Server on Mini

I recently purchased a MacMini Server with Snow Leopard Server and have everything working fine - except when I went to install the Server Admin tools on my Lion laptop - it would not let me! How do I manage my server? Currently, I have been using screen sharing to do everything - not the most efficient way - but I have my server up and running.
If I got the Remote Desktop on my Lion laptop, would that help me manage my server - just want to know, before I go and buy it.
Thanks,
-- Nash

I believe you can only use 10.6 Server Admin tools with 10.6 OS.
With Lion OS, you can only install Lion Server Admin tools: http://support.apple.com/kb/DL1419 - however, this may perhaps worth with 10.6 Server, although I haven't tested, but it may be worth a shot.
Apple Remote Desktop is not going to help you much in what you're trying to achieve - it is not designed to replace Server Admin tools, it has a completely different function. It simply allows you a convient way to do screen sharing, copying files, executing unix commands - all of which can really be done through the built in screen sharing applications or via ssh in Terminal.
Apple Remote Desktop will not allow you to directly change DNS, Mail, etc. settings. It will only allow you to get onto your server's screen where you can open Server Admin tools and change the settings directly on the server - no different from screen sharing.

Calendar mavericks client - snow leopard server

I am trying to connect calendar on a iMac running mavericks 10.9.5 to a Xserve running Snow Leopard 10.6.8
Where I have clients that I have upgraded from earlier versions of OSX to mavericks the calendar is still connected and is working correctly.
However this new system has been freshly installed with Mavericks and will not connect with errors such as:
Error Domain=CalSubscriptionErrorDomain Code=-1002 "The operation couldn’t be completed. (CalSubscriptionErrorDomain error -1002.)"]
Calendar[570]: [com.apple.calendar.iaplugin.log.CalInternetAccountsPlugin] [Autodiscovery error: [Error Domain=CoreDAVHTTPStatusErrorDomain Code=404 "The operation couldn’t be completed. (CoreDAVHTTPStatusErrorDomain error 404.)" UserInfo=0x6100004660c0 {CoreDAVHTTPHeaders=<CFBasicHash 0x610000466100 [0x7fff72d0cf00]>{type = immutable dict, count = 11,
The machine has been joined and bound to the "domain".
I have tried setting the calendar account to "Auto" - "Manual" and "Advanced"
I have configured it the same as other working systems - but still cannot connect
Can anyone advise of any workarounds or fixes for this issue please
Regards
Tony

The answer is to use the "advanced" setting for configuring the account - then enter the username in the format of
[email protected]
enter the server name in the server field
and I am now connected

Install lion when snow leopard server is installed

I have a mid 2010 mini server. It has two separate hard drives. I want to install Lion on the empty drive, migrarate what I need from the old install and format the first disk. I was told this was possible.
Now, when I try to buy Lion from the app store it won't let me. It tells me because I have a server edition, I have to pony up 80 bucks for Lion plus the server stuff. I don't need the sever stuff. I don't want the server stuff. I bought the machine because it was the ONLY (and by only I mean 1 of 1) mini in our authorized reseller (we don't have an Apple Store in Korea).
Is there any way around this? Do I have to wait for them to ship it on USB key and pay the premium for that?

Currently the only way around this is to use a second Mac and an external HD.
Boot the second Mac from the SL install DVD, select the external HD as the SL install destination.
Install SL and bring up to at least 10.6.6 via Software Update.
Shut down the second Mac, disconnect the external HD and connect it to the mini.
Boot the mini from the external HD.
Download Lion from the App Store.
Select one of the 2 internal HDs on the mini.
You should now have the option of installing Lion client.

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.

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.

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.

Lion clients with Snow leopard Server

Are there known issues with a Snow Leopard Server Mananging Lion Clients. I currently manage 40 IMacs in two labs
all running Snow Leopard, the only services I use on the Mac Server are Open Directiory, Print Services, AFP, and FireWall services
the Server is a Mac PRo with 2x3.2 Ghx quad-Core Intel Xeon Processor and 32. GB RAM

Snow Leopard can't serve AFP devices to Lion clients out of the box. There seems to be a workaround, but I haven't gotten it working myself yet.

Server Admin. file sharing lion client to Snow leopard server

I'm running Lion on my client Mac and my Server is Snow leopard 10.6.8. I have to use Server Admin 10.7 on Lion but there is no "File Sharing" tab to set up or edit the file sharing options on my 10.6 server?. I understand this is correct for Lion Server, but how do I get round it for Snow leopard Server?? On the Apple website compatibility page (http://support.apple.com/kb/HT1822) it states:
"Mac OS X Server v10.6
To administer a Mac OS X Server v10.6-based server, you can use the Server Admin Tools 10.6 on a Mac OS X v10.6 (client) computer. You should match the version numbers of the server, tools, and admin workstation as closely as possible; for example, use Server Admin Tools version 10.6.8 on Mac OS X v10.6.8 to administer Mac OS X Server v10.6.8. You may also use the Server Admin Tools 10.7 on an OS X Lion computer to administer Mac OS X Server v10.6."
So, How do I administer file sharing???

To configure File Sharing on a 10.6 server using 10.7 Server Admin, click the service (AFP, SMB, NFS, etc.) then click the Share Points tab.

Snow leopard server is created endless duplicates in OSX Lion clients

I am running a snow leopard server with address book server. My client computer was Snow leopard and have no problem syncing with the 10.6 server in address book. After the client computer is upgraded to 10.7 Lion, the address book application is creating a never ending stream of duplicate address entries in the client computer. It happens to all the upgraded 10.7 computers. The entries just keep multiplying into the thousands until I stop the address book server. Anybody know of this problem and how to fix it??

The address book on my mac somehow duplicated my contacts to the point where instead of about 200, I have about 100,000! The program crashes - if it even opens at all, which is sometimes doesnt - whenever I try to delete more than just a few. And if it doesn't crash, it just takes forever to process. At this rate I need a solid 3 hours to sit here and delete a few contacts at a time! Did you ever figure out how to resolve this problem?

Can I image Lion clients from Snow Leopard server using SIU?

I have a new iMac Lion client I need to image to a number of machines, using Snow Leopard Server, but System Image Utility will not recognize the Lion client as a valid source volume? Has anyone else experienced this yet?

Images must always be created on the same OS.
You'll need to download the Lion Server Admin Tools onto one of the clients and make it your "imaging system".
http://support.apple.com/kb/DL1419

How do I remotely access my Snow Leopard server from my Mountain Lion MacBook Air

Does anyone know of an idiot's guide to setting up a VPN to access my server? I'm running Snow Leopard server in the office and I'd like to be able to access the server, probably just from one computer (MacBook Air runnung Mountain Lion) from home.
I'm not sure if it complicates things or not, but the office is in an area with poor broadband and so the internet connection is via satellite broadband. The set up is a satellite modem into a Gigabit router and the server is connected to the router via an unmanaged switch.
As an aside, I'm considering changing this set up so that the modem plugs into a Time Capsule and the server will connect directly into the TC. The desktops will then run into the server via the unmanaged switch or wirelessly via TC - any thoughts on the best set up here? Are cables into a switch better/worse than using TC's wireless facility.
Is this something that I, as a reasonably competent computer operator but definitely not an IT expert, could do, or should I get someone in to set it up for me?
Thanks in advance
Jim

VPNs aren't particularly special or weird or secret or such. They're "just" a network connection. A sometimes very fussy network connection, but a network connection.
My preference is to use a firewall that includes an embedded VPN server. This for several reasons, as it avoids trying to forward the VPN through a device that's using NAT [1], and it means you can connect to multiple devices on the target LAN, and you can connect even if the OS X Server box is down.
Other folks will forward the VPN through NAT, and use the VPN server that's available in various versions of OS X Server.
Forwarding a VPN through NAT does work, but can also sometimes not work. NAT can cause some types of VPNs to get tossed off when (for instance) there's a second VPN connection arriving.
In various cases everything connects and works the first time, and in other cases it's trial-and-error.
With a VPN-capable firewall (which is a step above your average residential firewall), usually configuring the firewall as a L2TP server or the Cisco protocol, if you want to use the standard OS X or iOS clients. Or PPTP — which is easier to get working — but less secure. Once the firewall and the VPN server is set up — and that's where most of the "fun" is — then the set-up in Network Preferences is (usually) pretty simple.
There are thousands of OS X VPN set-up articles around, but the details all hinge on the particular VPN server, and whether you're going to try to push the VPN through (for instance) that Tome Capsule and its NAT. Until you sort out your VPN target and/or VPN client, and what sort of attacks you're securing against...
As for this case, satellite latency is large. The latency involved is the time it takes to the command or the text from your local Mac to the satellite ~35,786 kilometers up and then ~35,786 kilometers back down, and then the response back again. That's about a quarter second, each way, at the speed of light. Transferring big files is fine (once the connection is open and the transfer gets rolling), but anything interactive — such as a typical use of a VPN — is going to have a noticable lag.
Yes, it'll be easiest to get somebody to work through your requirements and expectations, and initially set this up for you. Or you can use this as an opportunity to read about and learn more about IP routing and networking and VPNs, too.
[1] VPNs seek to ensure that the network connection is secure, and from a known client IP source address to the IP address of the target VPN server. NAT explicitly obscures the network connections, and often has multiple client hosts located behind one IP address. Put another way, the VPN and NAT software implementations are working at cross-purposes.

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.

Lion client snow leopard server

Similar Messages

Maybe you are looking for