Reverting from OS Lion Server to OS Lion

I run OS Lion Server on a Mac Mini, and everything is going relatively well.
I am contemplating using my current Mac Mini as a music server only and buying a new Mac Mini with Lion Server pre-installed.
If I go this route, I will want to "remove" OS X Lion Server from my current Mac Mini and "replace" it with OS X Lion.
Anybody knows how to proceed?
Regards,

Same issue with me. I am a new mac user, actually Mac Minii server is my first mac. I am not interested inthe server aspect but rather the pure Lion as I also plan to install bootcamp with windows 7. (Sorry but I am not ready for a full pc to mac migatrion). Being the only user of the mac mini does ot make sense to have the full server installed.
Please help !!! Idiot (yours trully) proof guide will be highly appreciated. Thanks

Similar Messages

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.

I have a new lion server and 4 lion laptops. The laptops loose connection to the shared documents and printers from the server after roughly 1 hour. By disconnecting and re-connecting wireless the connection is regained to shares and printers

I have a new lion server and 4 lion laptops. The laptops loose connection to the shared documents and printers from the server after roughly 1 hour. By disconnecting and re-connecting wireless the connection is regained to shares and printers. We can still surf the web when it goes down.

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

Do you have to download Lion and also lion server , or just lion server ?

Do you have to download Lion and also lion server , or just lion server ?
And also will you have all the features of snow leopard server ?

Yeah it is a bunch of apps that you will download from the App store WWDC Keynote by Phil Schiller. "Server isn’t another operating system. It’s just a bunch of applications you can purchase to run on top of Lion. " And in terms of upgrading to Lion server, i read an article that explains the process as this:
"Snow Leopard Server - You can not upgrade to Lion directly. If you try to run the Lion installer on Snow Leopard Server, it will first look for the Server.app in the “Application” folder of the Mac. When you have that in place, the installer will first install Lion. Then, when it restarts, it will walk you thru some very minimal steps for the Server.app (hostname confirmation, admin email, etc). At that point, the Server.app will take your Snow Leopard Server settings and upgrade them. This will include migrating OD to 10.7, updating LDAP, importing data, etc. This can take some time. "
That is for snow leapard server specifically. If you come from a basic snow leapard installation, that is when you updrage to Lion and then download and install the server apps.

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

How can I make my Lion Server into a Lion Workstation?

How can I downgrade my Mac OS X Lion Server to just a standard Mac OS X Lion machine?
I've tried everything including re-installing Lion. When re-installing Lion, it seems to automatically pickup on the fact that this is a Server OS & installs Lion Server OS.
I want to simply downgrade my Lion machine to be running the standard Lion OS instead of Lion Server.
In case you're wondering, this is on my iMac 27" which I originally upgraded from Snow Leopard to Lion, then from Lion to Lion Server.

@Chris BeHanna
You were right for the firewall Issue. I was also running IPSecuritas and I installed Lion Server and the traffic stopped responding on the tunnel, although it connected well.
I figured out that, for some reason, even if the ServerAdmin indicated that the server firewall (my local "new" server, my own machine) was inactive, some rules must had been set during Server.app installation.
Anyway, what I did was activate the firewall, and then, allow all traffic on every ip. You can do that in the ServerAdmin app.
And then the traffic turned back on, on the IPSecuritas tunnels.
The next step would be to be configure rules precisely, but since I am already behind a firewall, I prefer using a "transparent" setting.

I cannot upgrade lion server to mountain lion server. i get an message that Server can't be installed on "Server HD" because Mac OS X version 10.8 or later is required.

I am trying to upgrade to mountain lion server from lion server. When i try an download the latest version of OXS from the app store, i get an message that Server can’t be installed on “my HD” because Mac OS X version 10.8 or later is required. I have lion 10.7.4 installed

OS X Server: Upgrade and Migration

Is it possible to install Lion Server over regular Lion?

I am considering buying Lion Server, so that I can get a feel for administering it (my background is in Windows Server and Warp Server for eBusiness). I have a 2010 21.5" iMac, which I upgraded to Lion a couple of weeks ago. I also have a MacBook Air with Lion.
I am wondering if I can just purchase Lion Server from the App Store and install it on my iMac, using the MBA as a client machine.
(1) Is this possible?
(2) Will I still be able to use the iMac as a regular machine, running (principally) Aperture and later on Final Cut Pro X as local programs
(3) What likely pitfalls am I going to encounter, and what (other than the client services) will I gain? I'm thinking that hosting Podcasts might be useful, but I don't know much about it
and finally,
(4) What resources are there to help me migrate my skills from Windows Server?
TIA,
Thomas

The other option is boot from your restore partition use diskutility to add third partition then use the reinstall lion option to install lion on 3rd partition, this will then download lion for you and reinstall it!
When this is done you can set it up properly (static ip etc) and then download the server app and install it!
Depending on what you want to do running it as your machine is not a big problem it works fine just keep in mind you might need to restart a few times and if you using it as a server that could be an issue!
in order to boot from your restore partition just reboot and hold down <alt>

What kind of disadvantages lion server compared to lion

If I will install LION server version on an iMac core duo instead LION standard version. What kind of disadvantage can I obtain ?

I've installed it on my MacBook Pro and it's just like another application, it does not do anything with your computer, if I've understood right

Lion Server with mountain lion computers?

Hello,
So i am running a mac pro 1.1 with Lion server because it won't run mountain lion, I am thinking about upgrading my other computers to mountain lion are there any issues or features that aren't availible or will be problematic?
Thanks

The difference between case 1 and cases 2-4 are that in 1 the client is letting the server expand the group membership, and in 2-4 it's the client doing that expansion. The group members returned by the server when it expands the group are "guaranteed" to work because the server definitely knows about them (and providing them to the client). In the cases where it's the client adding the attendees, I suppose there must be some mismatch sometimes, although I don't know what that could be if the email addresses are the same between the users you've created via Contacts.app and the users you've created via Server.app.
I actually tried this setup and it was working fine. What caused you to want to duplicate the users and groups that you have in Server.app into Contacts.app?

Can't acces lion server with Mountain Lion

I upgraded to to Mountain Lion and now its telling me I cannot access Lion Server on this Mac? I was able to access it before the upgrade.

Did you upgrade to the Server version of Mountain Lion? If you did not that explains why you cannot access it. However if you did please repost in the correct forum which is:
https://discussions.apple.com/community/mac_os/os_x_mountain_lion

Lion Server under Mountain Lion OS X

Hello,
I have upgraded to Mountain Lion, but I forgot to switch off all Lion Server services before upgrading. Now Lion Server cannot be started under Mountain Lion, and I don't want to upgrade it. Is it safe to just delete Server.app? Or maybe are service still running in the background, and I need to do something more complex?
Thanks in advance for your help
Roberto

If you don't want to upgrade to Mountain Lion Server, you're only other option is to completely erase your OS volume and reinstall Lion; then Lion Server. Or if you don't want to run Server any longer, you can just install Mountain Lion.

Time Machine on Mountain Lion Server Accepts But Doesn't See Backups From Lion

I recently (hopefully) upgraded our Mac Mini Server from Snow Leopard Server to Mountain Lion plus the Server app. A Drobo F is attached via FireWire and has a Time Machine partition on it. I've configured the Server app to offer the Time Machine partition on the Drobo for backups and we've got three machines using it: a relatively new MacBook Air running 10.8.2, an aging MacBook Pro running 10.8.2, and a pretty new MacBook Pro running 10.7.5. All three of the machines are able to backup to the Time Machine volume on the Mini. However…
Only the backups from the two machines running ML show up on the Time Machine Backups tab in the Server app. There is an entry for the Backups from the Lion machine, but the latest backup is reported as "Unknown." If I click on the Time Machine icon in the menu bar on the Lion machine it shows a reasonable (and recent) time for the latest backup. The log entries in Console for com.apple.backupd also look reasonable – and uninteresting. And newly backuped up files are visible in Time Machine.
The on obvious difference that I notice is that the in the .sparsebundle folders for the ML machines there are two files called:
com.apple.TimeMachine.Results.plist, and
com.apple.TimeMachine.SnapshotHistory.plist
Those files are not present in the .sparsebundle folder for the Lion machine (even after a successful backup).
Is this a clue or is it a Lion vs ML difference?
Does anybody have a Lion machine successfully backing up to a ML server and showing up on the Backups tab?
Any advice on this would be appreciated!

Same here - TM clients running 10.6.8 display as "unknown" on the /Backups tab on ML Server (ML 10.8.3).
My one client on a ML machine is correctly displayed (time/date of last TM backup).
As far as I can tell, the TM backups are working properly on the 10.6.8 machines. The problem seems to be a bug in ML Server
Solution: upgrade all 10.6.8 machines to Mountain Lion.
Roadblock: my 1st-gen MacBook Air doesn't support ML.

Configuring postfix on Mountain Lion Server

I'm trying to upgrade from Snow Leopard Server to Mountain Lion Server and did an install of Mountain Lion Server on top of a working instance of Snow Leopard Server. The "crippled" GUI on Mountain Lion Server is forcing me into using terminal to configure Postfix to handle incoming email.
I would like to configure Postfix to only accept email that is forwarded from a gmail business account. The public email address is [email protected] which is received by Google Mail, goes through their spam filters and then is auto-forwarded to [email protected]
The server WAN domain is nonpublic.com The ip address is 96.231.165.126
The server LAN is nonpublic.local The ip address is 10.6.18.201
The server is a MacMini running Mountain Lion Server 10.6.8 hostname server so the FQDN is server.public.com.
The network on the MacMini is configured to handle both LAN and WAN traffic through the 1GB physical ethernet port which plugs into a CISCO 3750 switch. The external traffic to the WAN flows through the switch as tagged packets. The LAN traffic is not tagged. The VLAN connection is running 802.1q
When an email is sent through the WAN to [email protected] the Postfix SMTP log shows:
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: connect from cisco.public.com[96.231.165.123]
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: disconnect from cisco.public.com[96.231.165.123]
I can send emails from a client on the LAN through this server with no problems. The incoming mail server can connect to the machine via the Cisco router/switch but Postfix just shows "cisco" as the connection (that's the router's DNS name) and provides no more info. I suspect Postfix possibly doesn't like the 802.1q connection and drops the SMTP request to connect on port 25.
I have turned on "debug" logging in Postfix, but that is all that appears in the SMTP log file
I've spent most of the week reading through everything I can find on how to install and configure postfix on Mountain Lion Server and work around the cripled GUI in the "server" application. I'm barely OK using Terminal and not familiar at all with configuring Postfix directling editing the config file.
What is the best approach to configure Postfix to allow SMTP connections from the outside to deliver incoming email that is forwarded from gmail.com?
I did find an "aliases" file in /etc/postfix/aliases but I'm not sure how to add the aliases and if adding aliases with a text editor is going to cause the "server" app problems and if the changes will be lost when the machine is restarted.
Any help would be appreciated.

MrHoffman, thank you for your response to my challenge to get the new test server working. This is a migration from Snow Leopard Server to Mountain Lion Server.
Here is the "checkhostname" test results:
blue:~ admin$ sudo changeip -checkhostname
Password:
Primary address     = 96.231.165.211
Current HostName    = blue.pderby.com
DNS HostName        = blue.pderby.com
The names match. There is nothing to change.
dirserv:success = "success"
blue:~ admin$
Here is the response from postconf -n
blue:~ admin$ postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
dovecot_destination_recipient_limit = 1
html_directory = /usr/share/doc/postfix/html
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
inet_interfaces = loopback-only
inet_protocols = all
mail_owner = _postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
message_size_limit = 10485760
mydomain_fallback = localhost
newaliases_path = /usr/bin/newaliases
queue_directory = /Library/Server/Mail/Data/spool
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_tls_ciphers = medium
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
use_sacl_cache = yes
blue:~ admin$
I agree that I should change the LAN domain from .local to something like .internal or whatever.   I've been running with .local for 5 years on snow leopard server and never had any problems so that was a low priority.
I hope I'm just not seeing some obvious setting in main.cf

Mountain Lion Server 10.8 DNS ERROR READING SETTINGS

Hi! Well I changed from windows 2008 server to Mountain Lion Server. So far, I have been able to set up website hosting for one website, and I must say works better than windows server 2008, maybe thats because the mac keeps the drive spun up, while in windows server it was an external drive, whatever the issue mac serves up the site much faster that it comes exploding onto the screen of the searcher.. Then I went to try to set up email, I was totally excited, but I think I did a no no in the dns settings, and now, I cant even see them, I just get "Error Reading Settings" Of course I see things in the log that I should undo, but I cant access the DNS settings at all. Any ideas how I can get to the dns settings so I can undo my booboo? Now it has streched its error self into the file sharing, and I cant access those settings anymore either, so that means I cant set up other websites because I cant give permission to view those folders. I also just got another err saying "Multiple errors occured on this server while processing commands. Just exactly what the heck did I do? I must have REALLY SCREWED THIS THING UP! Also strangely Safari browser no longer acceses the web from the server computer. I THINK I KILLED IT.
Any Ideas?
Thanks I really appreciate any tips, I havent got to calendar or vpn, or any fun stuff yet.. Or maybe it might not be fun at all? hahahahahaa!
Thanks

I've gotten into this mess as well and Apple solved it for me.
The Server should be able too lookup itself so running DNS is a good thing, actually the server sets up DNS at install time if it can't find a server to serve it's DNS so it can lookup itself.
The main error in my case was that there wasn't a NS record pointing the machine itself and that there were some firewall rules preventing DNS lookups. Since there is no way to edit the firewall rules via GUI the engineer manually changed some stuff, but wasn't sure where the problem lies exactly, so he passed it on to another engineer.
At this point I was already forced to switch to Google Apps for Business and my website was already running at GoDaddy, at much lesser costs and to much lesser frustration I might add.
Let's face it, Apple has to deliver a better product with the old Server Admin back into place for those who want it for the extra control.
My servers were running great with Lion (eventually), but Apple just had to remove Server Admin from OS X Server... #their_loss

Reverting from OS Lion Server to OS Lion

Similar Messages

Maybe you are looking for