Start Mountain Lion server on boot

Is it possible to start OSX Mountain Lion Server when I boot up my Mac Mini?
I have to login now each time I boot to start the server service.
Any help would be appreciated.
Mike

Once you have installed Server.app and configured and started the services you want to use they will automatically start when your Mac is booted. It is not necessary to login for the services to run, nor is it necessary to have the Server.app running. The Server.app is used purely for configuring settings and is not the server software itself.
Some administrators would argue having a server logged in and showing the Finder etc. is an additional security risk even if you have a good password and the screensaver locked.
It is purely up to you, however if you really want to have the Mac server automatically login and automatically run Server.app then you can do this in System Preferences -> Users & Groups -> Login Options, and then turn on Automatic login for the Administrator account. Then for the Administrator account set Server.app to be run in the Login Items tab.
Note: You also need to check to see if Automatic Login has been disabled in the Security & Privacy preference pane and if needed re-enable it.

Similar Messages

Server admin is unable to login to server.app after upgrade to Mountain Lion Server?

After upgrade to Mountain Lion Server I am unable to login to the server tools. When I input the admin user name and password the dialog box just shakes indicating the wrong password. But it is the correct password. How do I reset the password or if necessary how do I rest the server and start over on Mountain Lion. I found info on how to reset the server on previous versions of the server which involved executing a plist in the LaunchDaemon folder. However that file does not exist on the server following upgrade to Mountain Lion.
Thanks, Howard

I upgraded today and had the same issue. I took following steps to fix my computer.
Boot into Recovery Partition (Hold Option Button while booting)
Open Terminal.
Type resetpassword
Select your hard drive
Select the user account (Administrator)
Enter a new password for the user
Reenter password
Save
Restart
Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
Restart
Everything should be working as expected

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.

Regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections (any ideas???)

regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections. any suggestions would be greatly appreciated - thank you

Hi Jason
I was getting the same behavior after Apple support had me delete some plist files to get Airplay going. I was also getting the following error:
the error occurred while processing a command of type 'writesettings' in the plug-in 'server vpn'
I went into ~/Library/Preferences/ and /Library/Preferences/ and deleted every plist contating the word server. I had to re-set up my server (meaning walk through some intial steps) but all of my settings were still there after that and everything started working again.
Just a thought, obviously try at your own risk but it worked for me.
Kellen

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

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

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

VPN to Mountain Lion Server issues

Hi,
I checked a lot of VPN threads here today, but I wasn't able to find a solution for my problem just now. I try to connect by VPN to my Mountain Lion Server, but I get an error message that the VPN server is not responding. I get this message from iPhone and Mac. The Mountain Lion Server is a new installation, no upgrade from an older server.
Some informations on my setup:
I installed the server with a hostname like myserver.mycompany.com and option 3 (internet access), as I want to use it for email at a later stage. All services are working fine (except VPN). DNS is active, but basically it only contains the adress myserver.mycompany.com and forwards everything else to our router.
I changed the DNS settings of our domain ( hosted by an ISP - so not in the local DNS ! ). I created a subdomain vpn.mycompany.com which points to the static IP of our router.
In the router I opened the UDP ports 500, 1701 and 4500, and for 1701 i made the same thing for TCP (I found this in a forum, but I think this is not necessary?), the ports are pointing to the ip of the os x server.
In OS X Server I started VPN for L2TP using the vpn.mycompany.com hostname, and a shared secret.
When I try to connect with I client from outside I try to connect using L2TP via vpn.mycompany.com using the shared secred and user-id and password. The user-id is created in OS X Mountain Lion server and is configured to use VPN service. When trying to connect I get the error message "L2TP-VPN server is not repsonding...".
In the log file of the server I see some entries for each connect:
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: Connecting.
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IPSec Phase1 started (Initiated by peer).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 1).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 2).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 3).
Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 4).
Oct 10 20:21:48 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
Oct 10 20:22:06 --- last message repeated 2 times ---
Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (2,0)
Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Library/PrivilegedHelperTools/com.apple.serverd' [1716] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (100000,0)
Oct 10 20:22:06 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
No more entries in log file now. Anyone any ideas what's going wrong. Might there be a problem as I use another servername outside as inside (vpn... instead of myserver...)?
Thanks!

Solved, first of all we tested to establish the VPN connection locally by adding the ip address of the server to /etc/hosts for vpn.mycompany.com. The VPN connected without problems then, so it was clear that it is a firewall/router problem, and not a server problem.
After that we studied some more documentations and found that we don't have to open port 50, but ip protocoll 50 (ESP) on the firewall. After that was done, the connection was working from the internet as well.

OSX Mountain Lion Server - how do you uninstall this including services

Hi All,
Sorry if the question has been asked before.
I have Mountain Lion 10.8.5 and installed OSX Mountain Lion Server (2.2.2) and run into a couple of issues after installed successfully.
* I no longer can add users and groups.
* Open Directory fails to connect.
So I read some forums and uninstalled the server by trashing it, deleting /Libaray/Server, empty trash and reboot. But when I reinstalled the server it renabled all the services that I had previously and still not able to add users and groups. Open Directory fails to connect "not able to load replica" So I try to create a new OD and get an error the server is already a Network Server.
So basicaly I want to start from scratch and need some assistance how to get rid of OSX Server.
Thanks
Sahid

Wipe the disk, and reinstall OS X. (Not fun, of course. I just created a bootable USB disk for this purpose, and nuked an errant server configuration. A "target practice" server used for testing purposes had gone awry, and needed to be wholly reset. So I know what you're going through. Visit here or here for some instructions.)
FWIW, usual trigger for problems with OS X Server on a NAT'd network is bad DNS. That step gets skipped, or folks think they can refer to ISP or off-LAN DNS servers, and problems ensue. OS X Server needs LAN-local DNS when NAT is in use.

Server App can't connect to a Mountain Lion server

Hi,
I installed OS X Mountain Lion Server (2.2.1) on a 2012 Mac Mini running OS X 10.8.4. I am able to access all the options using the Server.app on the Mini. Then I installed the Server.app (2.2.1) on a 2010 MacBook Pro running 10.8.4. On trying to configure the Server options on the Mac Mini from the MacBook Pro by providing the correct Mac Mini admin credentials, the password is not validated correctly. This happens when both the systems are on the same network or on different networks.
I am certain that the username / password provided is correct, since using the same credentials I can successfully remote into the Mac Mini using Apple Remote Desktop (3.6.1) when both the systems are on the same network or on different networks.
My situation supersedes the resolution provided in http://support.apple.com/kb/TS3960?locale=en_US. Note that the command sudo launchctl list | grep -q com.apple.servermgrd && echo loaded || echo not loaded returns loaded on the Mac Mini.
Please help!

I am having exactly the same setup and exactly the same problem - nevertheless I would like to add some more information in order to hopefully find / get help from other readers in here.
I am using DynDNS - not a dedicated domain. I do not utilize an AirPort Extreme for port forwarding and else. All the necessary port forwardings were triple checked!
- First of all "Apple Remote Desktop" is able to connect to my server over the internet (screen sharing) and locally in my LAN. No troubles here.
- My iOS devices can connect using various VNC clients without any troubles.
- VNC connections started within Safari (MacBook Pro) do work very well, too.
- All kinds of WebDAV connections are working like a charme.
- When connecting with "Server.app" from my MacBook Pro it asks if I would like to trust the self-signed certificate before I can enter name and password. After trusting that certificate it doesn't matter which account information I am entering: none is accepted. It does not make any difference if I am using a local user account or a user network account (both configured as being allowed to administer that server). "Server.app" does not accept any information provided.
I've been following the KB advice, too that c xavier mentioned. "servermgrd" is loaded!
For some odd yet unknown reason neither WAN nor LAN FTP login does work, too. It just gives me a time out, as already mentioned WebDAV is working fine.
Sorry I could not help You, c xavier! I just thought that some additional information could help...

How do I properly change the server name in mountain lion server?

I need to change my server name to a FQDN, but tried this with Lion server in the past without success. I know in lion you'd use server app, but that's no longer avaiable in mountain lion server and I want to make sure I get this right the first time.
Thanks!

I was able to get everything working with some assistance from Apple's enterprise support. After changing the host name, the DNS was still not resolving properly and I couldn't turn on open directory so that I'd be able to start profile manager. The DNS interface is considerably different than that in previous versions of server. The network was set to manual ip with dhcp, which was pulling back an external IP. Overriding the DNS info coming in via the dhcp, setting it to localhost, resolved the issue.
Thanks!

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

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.

Update to Mountain Lion Server kills Time Machine Backups

Okay, here's the scenario:
Client:
MacBook Pro running Mountain Lion
Server:
Mac Mini running Mountain Lion Server using an SSD boot and Promise Pegasus Thunderbolt RAID
Prior to updating the Mac Mini to Mountain Lion Server (previously just using regular Mountain Lion) I was happily backing up using Time Machine over AFP. Since the update to Server I get the Time Machine message:
"The network backup disk does not support the required AFP features."
The network drive is also no longer available for selection within Time Machine (once it's been deselected).
Any easy ideas on a fix?

Time Machine won't back up to Mountain...: Apple Support Communities

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.

Start Mountain Lion server on boot

Similar Messages

Maybe you are looking for