Will mountain lion overwrite lion server?

When I puchased my mac mini server I didn't need the server functions but at the time that was the OS offered, (I see recently that you can order a mac mini server with OS Lion as opposed to OS Lion Server), so I'm just running with the server functions shut off.
So when Mountain Lion comes out what will be the ramifications of installing regular ML on top of lion server? Will there still be server functions I need to keep turned off? Will it remove the server functions of Lion Server?
The latter would be my hope.

Yes, to my understanding, the server applications will be deleted from the computer and all will be good, providing you buy the normal 10.8 instead of server
Hope this helped

Similar Messages

Will Mountain Lion Server be slower that Lion Server on my 2009 Mac Mini?

I have a 2009 Mac Mini running Lion Server. Specs are: 2.0 GHz 8 GB ram.
As always, I'm wanting to reap the benefits of the latest OS without upgrading my hardware. I know mirroring won't be supported, but who cares about that on a server.
Does anybody have Mountain Lion on a similar setup?

We've found Mountain Lion Server to run just as fast as Lion. MLS boots a bit slower on our Mac minis, but it's
neglegable.
Also have had trouble migrating from Lion and 10.6.8 server to Mountain Lion Server. Issues with Open Directory and Mail.
Hope Apple puts out a .1 release to address the issues soon.

I recently (4 days ago) bought a Mac mini server with 10.7 lion; will I qualify for a free upgrade to Mountain Lion Server?

How has Apple honoured buyers of other releases of OS X immediately before a new version was announced?

omnomnomz wrote:
How has Apple honoured buyers of other releases of OS X immediately before a new version was announced?
I recently (4 days ago) bought a Mac mini server with 10.7 lion; will I qualify for a free upgrade to Mountain Lion Server?
Mtn Lion not due out until the Summer, so no, you will not get a free upgrade.

I am running Mountain Lion Server, and the App Store indicates an upgrade to Server.App version 2.2.5. When I try to upgrade it will not install. Is that because OSX8 is no longer supported; and if so, is there an alternate source for this upgrade if

Mountain Lion Server.app no longer supported?

Probably a long shot, but try resetting the App Store and Clearing Cookies.
Reset Learned from Old Toad
Resume Interrupted Downloads
Sign in Doesn’t Appear/Accept Text
Software Update - Adjust
Software Update – Stop it From bugging you
App Store support. There is troubleshooting and a contact link.
Support

Unable to add/remove users in Mountain Lion Server (Options are greyed out)

For some reason, im unable to add/remove users in Mountain Lion server. The + and - are greyed out. It seems like something is wrong with the permissons because it looks like it cant write the the Ldav3 file (although that may be speculation). Does anyone have any advice for me? I URGENTLY need to add users.
Maybe theres a way to restore default permssions for the boot drive (if that in fact is the issue). Hopefully there is a way that I can fix this while leaving all users, groups, their permissions and shares intact.

Anything interesting and relevent in the server logs?
Anything interesting in the server alerts?
Since it's far and away the most common cause of problems with OS X Server and with distributed authentication (Open Directory is entirely based on network encryption and digital certificates and on responses from your local DNS server(s)), verify your local DNS configuration is working and requires no changes with the following Terminal.app (Applications > Utilities) harmless, diagnostic command:
sudo changeip -checkhostname
sudo requires an administrative password. You might get a one-time warning about the sudo, and that can safely be ignored. The command will display some details, and indicate whether the local configuration appears valid and no changes are required, or further diagnostics for (most) common errors that can arise.

How To Set Up Mountain Lion Server/Point DNS to Mac Mini Server

Hello, First of all I have no experience with setting up servers whatsoever. Below is what I have
- Mac Mini with Mountain Lion Server
- Time Capsule as my router
- Comcast as my service provider
My goal is to set up my MacMini as a sharepoint for files and other data with my other partners.
- I have purchased a domaine name from NetworkSolutions. Does this mean that they are my DNS hosting as well? Not really sure. My biggest question is how to point my DNS to my mac mini server correctly.
1. How do you point the DNS to my mac mini server.
2. I've read somewhere to use the IP address from my mac mini server. The only IP address I see is from my Time Capsule (router). I know what my public IP adress is but I am not sure if that's the one to use. I think once I figure this DNS thing I can figure out the rest.
Thanks - Need lots of help.

Here's a detailed write-up on setting up internal (private) DNS on OS X Server, and no, you're probably not going to be setting up external DNS on your servers. Your public DNS service will be hosted on and served from the Network Solutions DNS servers.

Upgrading to Mountain Lion server and all services breaks down...

Hi!
I have, after endless hours of scanning logs and .plist and other files' content and permission settings found why Mountain Lion Server.app in some cases doesn't seem to be able to take control over all service, stating it can't read or write its own setting files etc.
As a Swede I of course run a system set in the Swedish language. Mountain Lion can't upgrade a Swedish system, only fore languages are accepted !!!
See Migration Logs!
//Excerpt from the Mail Migration log:
Begin Mail Migration: Thu Aug 2 19:34:24 2012
purge: 0
sourceRoot: /Library/Server/Previous
sourceType: System
sourceVersion: 10.7.4
targetRoot: /
language: sv
Did not supply a valid language for the --language parameter, needs to be one of [en | fr | de | ja]
As you can see, it can only upgrade in English, French, German and Japanese system language. With no inital warnings the system crashes and causes a true mess half the way through its installation when you start Server.app.
Solution:
Throw Server.app in the trash or move it outside the Application folder, to force the computer to realized "its not a server". It can take half a minute or so for the system to realize it is no longer a server. You will see a sign.
Change the language setting to English in your system preferences and restart your computer. Move back Server.app from the trash (or where you put it) and start Server.app, thereby initiating a new Servers installation. I was happy to find that all mail accounts etc was found again. I thought for several hours they where lost.
The various sites hosted by the server did however not appear in their correct new location (when I tryed this). I had to manually move them from the "Previous" folder in /Library/Server/Previous/Library/Server/Web/Data/Sites/ to /Library/Server/Web/Data/Sites/
I hope this helps anyone out there....
Cheers!
Stefan

Please explain.... when are you stoped from upgrading?
I haven't actually had problems with the actual OS upgrade it is when you launch Server.app the first time everything goes to f-n h....
Server.app should reconfigure and move around a lot of files and it does, but not succeeding doing it correctly. Many services can't read their config files and have them in two places. I trying to figure out which ones are being used. Somethime both locations are used but only parts of the settings in the files !?!?
I am soon giving up...

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

Smooth transition from Mountain Lion Server to Mavericks Server 3.0!!

After an new OS release that are always complaints about installation and configuration problems. First comers to using any new software tool provide valuable feedback we generally hope will help improve the new product. It's how things have worked since the first 6503 Apple II's and 8086 IBM PC's.
I've been using and upgrading PC's since THOSE DINOSAURS! And I can't remember EVER having an OS upgrade go as smoothly as my recent upgrade from Mountain Lion Server (OS X 10.8.5 w. Server 2.2.2) to Mavericks Server 3.0.
I chose to do a clean Mavericks install on a clean partition created on a 1 TB disk that was upgraded into my trusty MacBook. I used the DiskmakerX app to create a Mavericks installation USB drive. When the screen came up with the option to import users, programs & files (took a pass on email) from the Mountain Lion Server partition, I let it run overnight to transpose everything of value into the clean Mavericks installation.
The next morning the only program that wasn't PERFECTLY installed and configured on Mavericks was Server 2.2.2. I deleted it and bought/installed Server 3.0. After Server 3.0's setup ran that only thing I had to do manually was start Postgres! My domain setting, DNS, all my web applications that were set up on Mountain Lion Server were all GOOD TO GO again on Mavericks Server!
I'm disclosing this here, publicly because it was a BIG PAIN to install and deploy all my websites using Mountain Lion's server app. To say the easy transposition into Server 3.0 was an unexpected and pleasant surprise amounts to massive understatement.
Now I'm going to describe two small anomolies I've noticed in either Mavericks or Server 3.0 that other users might want to be on the lookout for. They're not fatal. But they might be "habringers" suggesting underlying problems in either the new OS or the new Server's internals.
The toolbar icon for TimeMachine doesn't "spin" when it backs up. It's not a big deal. But it's convenient to see the circle around the clock whirling so we know when TIme Machine is backing up.
Mavericks Server isn't reporting newly upgraded apps as available under the Updates Tab of the Server's Software Updates subsystem. It might be inconsequential. But with a new OS version it never hurts to let the developers know about the "little things" that don't apparently work.
Kudos to the Maverick's developers for releasing an OS X version that's THIS CLEAN. And hugs to Apple's management for making it a free download upgrade for developers!!!
Full disclosue: I don't now and never have worked for Apple. but I do own a few shares of Apple stock that we purchased many years ago at $14.00 / share. I'm not a big shareholder. But based on my recent seamless upgrades to Mavericks and iIOS 7, I'm a happy one who's not likely to sell any time soon.
If Apple can do for ALL THEIR HARDWARE AND SOFTWARE PRODUCTS what they seem to have done for OS X and iOS, they've got at least a fighting chance to recover from their losses after their stock peaked at about $700.00 /share.
Keep up the good work!
Dr. Bob Blomeyer

After an new OS release that are always complaints about installation and configuration problems. First comers to using any new software tool provide valuable feedback we generally hope will help improve the new product. It's how things have worked since the first 6503 Apple II's and 8086 IBM PC's.
I've been using and upgrading PC's since THOSE DINOSAURS! And I can't remember EVER having an OS upgrade go as smoothly as my recent upgrade from Mountain Lion Server (OS X 10.8.5 w. Server 2.2.2) to Mavericks Server 3.0.
I chose to do a clean Mavericks install on a clean partition created on a 1 TB disk that was upgraded into my trusty MacBook. I used the DiskmakerX app to create a Mavericks installation USB drive. When the screen came up with the option to import users, programs & files (took a pass on email) from the Mountain Lion Server partition, I let it run overnight to transpose everything of value into the clean Mavericks installation.
The next morning the only program that wasn't PERFECTLY installed and configured on Mavericks was Server 2.2.2. I deleted it and bought/installed Server 3.0. After Server 3.0's setup ran that only thing I had to do manually was start Postgres! My domain setting, DNS, all my web applications that were set up on Mountain Lion Server were all GOOD TO GO again on Mavericks Server!
I'm disclosing this here, publicly because it was a BIG PAIN to install and deploy all my websites using Mountain Lion's server app. To say the easy transposition into Server 3.0 was an unexpected and pleasant surprise amounts to massive understatement.
Now I'm going to describe two small anomolies I've noticed in either Mavericks or Server 3.0 that other users might want to be on the lookout for. They're not fatal. But they might be "habringers" suggesting underlying problems in either the new OS or the new Server's internals.
The toolbar icon for TimeMachine doesn't "spin" when it backs up. It's not a big deal. But it's convenient to see the circle around the clock whirling so we know when TIme Machine is backing up.
Mavericks Server isn't reporting newly upgraded apps as available under the Updates Tab of the Server's Software Updates subsystem. It might be inconsequential. But with a new OS version it never hurts to let the developers know about the "little things" that don't apparently work.
Kudos to the Maverick's developers for releasing an OS X version that's THIS CLEAN. And hugs to Apple's management for making it a free download upgrade for developers!!!
Full disclosue: I don't now and never have worked for Apple. but I do own a few shares of Apple stock that we purchased many years ago at $14.00 / share. I'm not a big shareholder. But based on my recent seamless upgrades to Mavericks and iIOS 7, I'm a happy one who's not likely to sell any time soon.
If Apple can do for ALL THEIR HARDWARE AND SOFTWARE PRODUCTS what they seem to have done for OS X and iOS, they've got at least a fighting chance to recover from their losses after their stock peaked at about $700.00 /share.
Keep up the good work!
Dr. Bob Blomeyer

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.

Currently running Snow Leopard with iWeb will Mountain Lion support it?

Currently running Snow Leopard but wish to upgrade to Mountain Lian to support new iphone etc. Only problem being that I've just set up a small online page using iweb through an ftp server. will Mountain Lion support any changes that I make to my pages and can it then publish trhough the outside server?

iWeb is supported in Mountain Lion. That said you need not upgrade to ML to support new iPhone 5. What OS are you using? All you need is iTunes 11.

Upgrade to Mac OS X Mountain Lion server

Hi folks,
I just bought the OS X Lion server for $49.99 and installed it on my Macbook Pro.
However when I upgraded to Mountain Lion, it no longer works, that's obvious.
So my question is that will get a free upgrad to Mountain Lion server or I need to buy the it which now @ $19.99?
Can anyone clarrify me?

Sorry but the Server that runs in 10.7 is incompatible with 10.8, it has an entirely different folder structure. If your Server purchase was recent you may want to ask about a free upgrade, but don't know what the procedure is. Good luck with that.

Mountain Lion Server bond support?

After migration to new Mountain Lion Server from Snow Leopard Server, the Server App don't recognize the Ethernet aggregation of my Mac Pro! The services that was active in Snow Leopard Server are active, but if I try to stop the service of net install I don't try to restar the services because there isn't no interface!!!!! it's Possible? And probably it's the same for the other services!!!

Yea, I actually run our current SUS on an older Mac Pro. It provides both Apple software updates and Adobe software updates (for our Adobe deployments) and is dedicated to these two services. My primary server (running Mountain Lion—capable of Mavericks, but again, because of the File Sharing issues in Mavericks Server, we're sticking with ML Server for the time being) is a loaded 2009 Xserve—which I don't run "secondary services" (my term <G>), like SUS, on.
Unfortunately, the current SUS box won't do Mavericks Server (though, I have tested running a VM of Mavericks Server, just for SUS and Caching, inside the physical OS, and it worked fine, but seemed like a waste of system resources and just really didn't make much sense—and a bare metal install doesn't work because of RAID, etc.), so I was considering the Caching Service in ML as an alternative (if it did, in fact, feed Mavericks clients). I realize I could just "turn it on" and see what happens, but would rather look into first (as I assumed others would have ML Caching Service on, and probably had Mavericks clients on the network, so would have the info I was looking for).
Anyway, at this point, unless ML Server Caching Service will do the trick, Reposado it is.
k.

Mountain Lion Server upgrade; "error reading settings"

Just upgraded to Mountain Lion server and now ALL services have an "error reading settings".
For example; I select "websites" and I get the message "an error occured on the server while processing a command. teh error occured while processing a command of type 'getWebAppState' in plug-in 'servermgr_web' "
There are similar errors for every service. I can't turn anything on.
Server can't even read the Logs. it just sits there with "Loading..." displayed.
My web site is gone and even the Groups have been gutted.
I have a backup of my Web site but how to I clean this up so I can even start from scratch !?!

I have the final solution and fix but beware you may not like it that much.
Having had all of the above problems with more or less everything I finally pieced it all together from various threads. This will fix both the AEBS control and the central services problems. Dont shout at me for being a bit basic and not coding etc. but it worked for me. If I can avoid code I do as often as possible as am less likely to balls it up!
This method will loose some data but the main files and users do remain
The Fix:
1. Close Server.app
2. Library/Server make a copy of Server file under a diff name as software server files and a few others would appear to still be usable and you will have to re download it all again of you dont copy it back in ( I didn't and now have learned my lesson). then delete the whole of the Server file.
3. Go to Keychain and search all Airport then delete associated keys permissions etc
4. Delete Server.app and reinstall.
5. Start new setup and it will migrate properly with no errors. This time a big green tick will appear!
6. Replace the software update files into the new Library/Server folder if you want to or leave it untill the rest is done
7 Reconfigure any missing bits..... any enrolled devices will have vanished but probably if you have saved the data from this in Library/Server prior to deletion you may be able to reinstate this but I didnt risk it
This is going to be a total pain if in a large organisation but once working the system is excellent with no swapping from one control set to the other. As each service is switched on it auto configures the AEBS and no further errors and a joy to work with unless you really like to get into the nuts and bolts.
Hope this helps and good luck

Will Mountain Lion work on my 4 year old iMac with Intel Core 2 Duo Processor Speed: 2.66 GHz

Will Mountain Lion work on my 4 year old iMac with Intel Core 2 Duo processor and a 2.66 gHz.
Really do not want to load it and find there are issues.
Oh I really not a big tech guy I just want everything to work well.
And I'm just about to purchase a Mac Book Pro as well.
Any thoughts and comments would be appreciated
Cheers

I also have a 4 year old iMac 24". it is the 3.06 GHz Core 2 Duo. I have been running Mountain Lion since it was released, and before that Lion. Runs great. Over the last month I have noticed some slow data transfers from a USB harddrive. But not enough to do any research. I use a USB harddrive for my Time Machine backup and notice no problems or slow transfers while the Time Machine backup runs. My iTunes has its nedia files on a USB harddrive and is used to watch videos, play music and share photos on the AppleTV. I also use Aperture on the iMac to store and manage 20,000 photos.
I have 6 GB of ram, 4GB and 2GB memory sticks. I know it is best to have identical ram sticks but my iMac model cannot run 8GB of ram and I feel 6GB is better than 4GB.
Mountain Lion is a great OS and I am glad I upgraded. It works great with the AppleTV (no airplay but iTunes on the iMac serves up all our music, photos and videos), iPhone, and iPod Touch. Also with my wifes brand new Macbook Pro. All the devices including the iMac can share data on iCloud.

No Entry Sign when trying to netboot new MacMini to Mountain Lion Server

My company just purchased a new MacMini i5 2.5 GHz and I am trying to netboot it to my Mountain Lion Server 10.8.2 but I am getting the No Entry sign when it tries to boot to the server. I tested my other Mac computers that are in my environment and they are able to netboot to the server fine. It just seems to be an issue with this latest Mac Mini.
As part of my troubleshooting, I created a new netrestore image from the new Mac Mini using System Image Utility on the Mountain Lion Server. The server successfully created it and I set it as the new default image in the NetBoot server. After taking these steps, I am still getting a No Entry sign.
I checked the log on the server to see what is happening when it tries to boot and this is what is displays:
Any ideas?
11/16/12 1:36:21.318 PM netbiosd[148]: name servers down?
11/16/12 1:36:53.638 PM bootpd[6740]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 1:36:53.638 PM bootpd[6740]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[LIST] sent 172.16.124.63 pktsize 380
11/16/12 1:36:54.159 PM bootpd[6740]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 1:36:54.160 PM bootpd[6740]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[SELECT] sent 172.16.124.63 pktsize 388
11/16/12 1:37:46.498 PM bootpd[6740]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 1:37:46.498 PM bootpd[6740]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[LIST] sent 172.16.124.63 pktsize 380
11/16/12 1:37:47.018 PM bootpd[6740]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 1:37:47.018 PM bootpd[6740]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[SELECT] sent 172.16.124.63 pktsize 388
11/16/12 2:03:21.107 PM netbiosd[148]: name servers down?
11/16/12 2:04:50.429 PM bootpd[6791]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 2:04:50.429 PM bootpd[6791]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[LIST] sent 172.16.124.63 pktsize 380
11/16/12 2:04:50.931 PM bootpd[6791]: BSDP INFORM [en1] 1,a8:20:66:31:ad:e0 NetBoot006 arch=i386 sysid=Macmini6,1
11/16/12 2:04:50.932 PM bootpd[6791]: NetBoot: [1,a8:20:66:31:ad:e0] BSDP ACK[SELECT] sent 172.16.124.63 pktsize 388
11/16/12 2:17:33.919 PM netbiosd[148]: name servers down?
11/16/12 2:20:58.585 PM netbiosd[148]: name servers down?
11/16/12 2:34:09.562 PM netbiosd[148]: name servers down?
11/16/12 2:39:03.753 PM netbiosd[148]: name servers down?

I'm seeing the same behavior with a new Late 2012 Macmini6,2 (2.3GHz quadcore i7).
I have a lab with several variants of minis up through the last generation. One of those minis is a NetBoot/DeployStudio server. I have it hosting a 10.8.2 NetBoot image, which works for all of the other lab minis but this new one.
I have tried 3 different methods for NetBoot:
Holding the 'N' key at boot
Holding option and seeing my NetBoot disk in the selectable options
Booting into the restore partition and selecting my NetBook disk from the Startup Disk preference pane
All 3 options result in what is described above - the Ghostbusters (minus the ghost) no entry sign. My particular mini then shuts itself down shortly thereafter.
My NetBoot server log looks similar to the above, where my BSD INFORM messages have sysid=Macmini6,2.
I have confirmed that - on the restore partition at least - the shipping OS on the new mini 6,2 is 10.8.1. It's likely a custom edition for this new hardware. It's possible that a component of a 10.8.3 update would fix it, but I'm unfortunately leaning toward this being an EFI firmware issue. I've noted on another site that these minis seem to have issues with VMware's ESXi, where the suggested course of action will be an Apple firmware update: http://communities.vmware.com/thread/423099
As the lab is hoping to purchase 40 of these systems, NetBoot support is rather critical.

Will mountain lion overwrite lion server?

Similar Messages

Maybe you are looking for