Mac mini Server with normal Lion install?

Can i install on the Mac Mini Server (Mid 2011) a normal Lion OSX?
I don't want to use Server features, i only need the hardware power.
Is the Server pre-installed?

The 'proper' way is to have the Mac Mini Server running the version of OSX that's written for it, the hardware IS different hence there's (subtle yet real) differences to the software installed on each. I can't confirm if it would Boot from an external drive with the normal 10.7 softwarre as I've never tried that ...
If you don't need the Server applications then run Server, turn the services off and uncheck:

Similar Messages

  • MAC MINI SERVER WITH Mountian lion....

    I purchased a mac mini "server" after Mountian lion came out I did the upgrade in OS only to find out my "Server" function will not work on Mountian Lion.... what's up apple....I've been a fan for 6 computers and didn't expect this.

    Restore your previous installation or purchase Server 2.0.
    The "server" part of te system has been broken out into
    a seperate add-on application instead of being tightly integrated
    as a seperate version of OSX.

  • Error starting wiki server in Mac Mini server with Mountain Lion 10.8.3

    Hi, i've got a problem with my wiki server.
    The service doesn't start!
    It does an error while i try to start the wiki!
    The service can't read the service impostation!
    How can i solve it??
    Anyone with the same problem??
    Thanks!

    here the /var/log/apache2/error_log
    [Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:28 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:36:31 2013] [notice] FastCGI: process manager initialized (pid 145)
    [Fri Jun 28 10:36:31 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:36 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:36:39 2013] [notice] FastCGI: process manager initialized (pid 196)
    [Fri Jun 28 10:36:39 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 10:37:25 2013] [notice] caught SIGTERM, shutting down
    [Fri Jun 28 10:37:38 2013] [crit] (17)File exists: mod_rewrite: Parent could not create RewriteLock file /var/log/apache2/rewrite.lock
    Configuration Failed
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:37:48 2013] [notice] FastCGI: process manager initialized (pid 432)
    [Fri Jun 28 10:37:48 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:28:22 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:28:26 2013] [notice] FastCGI: process manager initialized (pid 31415)
    [Fri Jun 28 16:28:26 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:30 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:28:33 2013] [notice] FastCGI: process manager initialized (pid 31466)
    [Fri Jun 28 16:28:33 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:43:46 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:43:49 2013] [notice] FastCGI: process manager initialized (pid 33283)
    [Fri Jun 28 16:43:49 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:43:51 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:43:55 2013] [notice] FastCGI: process manager initialized (pid 33322)
    [Fri Jun 28 16:43:55 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:44:41 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:44:44 2013] [notice] FastCGI: process manager initialized (pid 33499)
    [Fri Jun 28 16:44:44 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:49 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:44:52 2013] [notice] FastCGI: process manager initialized (pid 33579)
    [Fri Jun 28 16:44:52 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations

  • I just purchased the Mac Mini Server with the intention of replacing Lion Server with Lion for the first hard drive while installing Windows 7 thru Bootcamp on the second hard drive. Is it possible for me to do this? Thanks.

    I just purchased the Mac Mini Server with the intention of replacing Lion Server with Lion for the first hard drive while installing Windows 7 thru Bootcamp on the second hard drive. Is it possible for me to do this? Thanks.

    I would use Parallels or VMWare and use the second drive to hold the virtual machine. That way the VM only uses the space that it needs and you can still use the remainder of the drive for other things, not to mention that you would not need to reboot to run windows.
    Also Time Machine does not back up a boot camp partition.

  • How to install OSX 10.6 client in Mac Mini Server 10.7 Lion Server

    I am ordering a Mac Mini Server with Lion Server 10.7, with 256GB SSD and 750GB HD.  I want to use Snow Leopard (client/workstation) instead.  Previously I have already purchased retailed version of 10.5 clients and 10.6 client upgrade.  Please advise the best approach from the followings (or more suggestions from you guys...). 
    (A) The boot disk (likely to be the SSD) will be re-formatted and re-installed by "clean" installation of 10.6 client.  But I am not sure whether all hardware drivers for the new Mac Mini (2011) are available in the 10.6 client disk.  Also, it seems to me that installation disk of 10.7 server will not be provided.  So I shall not be able to re-install server version again if I want to change this Mac to a server sometimes afterwards.  Of course I would like to keep this server software for investment protection, no matter I use it or not.  If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also.  So there will be 2 partitions to be usable aparently.
    (B) The factory-installed OSX 10.7 server is kept, and one more partition is created (with Disk Utilties).  Snow Leopard workstation 10.6 will be installed at this new partition.  If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also.  So there will be 4 partitions, including 10.7 server, 10.6 client, 10.7 recovery drive and bootcamp for Windows 7.  Since I want to put all OS software at the SSD (faster boot-up and better performance), the drawback is that each partition is with less space.
    Do you guys have other ideas or suggestions?
    [Background]
    In fact I want to make use of its strongest computing power (amongst available Mac Mini computers in store), quad-core CPU & dual disks,  to run music applications (DAWs).  Operating systems are put at SSD, and data is put at traditional harddisk.  As some music applications (e.g. Calkwalk Dimension) only support 10.6 currently, I need to down-grade from Lion server to Snow Leopard workstation.  Also I think applications can run faster in a hardware with  workstation OS (rather than server version). Please correct me if this belief is wrong. 
    Thanks / Howard.

    If you completely wipe the original Mac mini boot drive you will wipe the Server.app software an dlose it. You should make a backup first, perhaps by saving the entire boot drive as a Disk Image file on to another drive.
    In terms of install 10.6, the 10.6 DVD will not boot on the new Mac mini even if you connect a DVD drive. You need to put the Mac mini in to FireWire Target Disk Mode and connect it to an older Mac that will allow booting from that DVD, then install on to the Mac mini (over FireWire), you then need to upgrade it using the 10.6.8 Combo Updater this will add the drivers needed for the new Mac mini.

  • How to use webmail address book on Mac Mini Server with Lion Server.

    I have a Mac Mini Server with Lion Server installed; the webmail is setup and working but I can not get the address book to work.
    I have followed an instruction from this website on how to activate the address book icon in webmail but can not add any addresses.  Is there something that needs to be activatied before it will work?

    No, I didn't solve the problem. The monitor still goes to sleep with WIndows but not with my Mac Mini. About 8 months ago I basically wore out the power switch on my monitor so I bought a wireless power switch to shut it off at the outlet. The VX2835wm monitor itself is now starting to fail as well-- a couple of times it's gone through a weird sequence of flashing screen colors on power up and ended up in an overscan mode (that took me for ever to figure out how to fix). I have decided to replace my VX2835wm with a Dell u2412m once it fails for good partly because I really want to keep the 16:10 resolution (very hard to find these days) and partly because I want to see if a different make of monitor will go to sleep properly based upon my Mac Mini power down settings.

  • Purchased mac mini server with lion, can i download lion for my macbookpro ?

    Hi,
    I bought a mac mini server with lion server. I have macbookpro with Snowleopard. Do i need to purchase Lion again to install in macbookpro ?
    I registered my mac mini with my apple id .. still when i check app store in my macbook it is asking me to purchase again.
    Can someone clarify ?
    - thanks LP.

    Yes. What came on your Mini cannot be installed on your other computers. You will have to purchase and download Lion for the MBP. If you wish to install Lion server on the MBP, then you will have to purchase and download Lion Server, too.

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

  • Mac Mini Server with Raid 1

    Hi,
    Is it possible to set up a Mac Mini Server with Raid 1 using only another mac computer such as a mac book?

    Yes- Colin Jeukens posted step by step instructions back a couple of months ago. Here it is again...
    Out of the box the mini comes without Raid. You have two identical HDs of 500Gb.
    I have just set it up as Raid1. You can't do this when you use the startup disk from the mini. And as you don't have a Superdrive ... you need to be creative. You need another Mac with Firewire.
    Step 1: Start the Mini in Target Mode. Press the T during start. In a few seconds the firewire logo will appear on your screen.
    Step 2: Go to your second Mac. Connect the firewire cable between second Mac and Mini.
    Step 3: On the second Mac start the disc utility. The two identical drives on your mini will show. Create a new Raid set (mirrored = Raid 1). Include both drives. Confirm the warning that all data on the mini will be lost.
    Step 4: Make sure your second Mac has CD/ DVD sharing option installed. This is tou use the superdrive to install OS X Server on the mini.
    Step 5: Shutdown both Macs
    Step 6: Start your second Mac in target mode. Make sure the firewire cable is still connected.
    Step 7: Start the Mini with the option key pressed.
    Step 8: Insert the OS X Server install disc in your second Mac.
    Step 9: wait till the drive logo apears om the Mini. Continue the install. Will take about an hour.
    Here is a link to the original post...
    http://discussions.apple.com/thread.jspa?threadID=2213470&tstart=0

  • Hello, I just wanted to know when an update would be available for my mac mini server os x lion to resolve the issues regarding my m-audio fastrack pro usb audio interface (no midi messages recognized)

    Hello, I just wanted to know when an update would be available for my mac mini server os x lion to resolve the issues regarding my m-audio fastrack pro usb audio interface (no midi messages recognized)

    Have you reported your problems to Apple?
    BugReporter
    <http://bugreporter.apple.com>
    Free ADC (Apple Developer Connection) account needed for BugReporter.
    Anyone can get a free account at:
    <http://developer.apple.com/programs/register/>
    And/Or
    Mac OS X Feedback<http://www.apple.com/feedback/macosx.html>

  • Do I get a free upgrade to Mountain lion on my MacBookPro if I just purchased a new Mac Book Air with Mountain Lion installed?

    Do I get a free upgrade to Mountain lion on my MacBookPro if I just purchased a new Mac Book Air with Mountain Lion installed?

    Sorry, no.

  • Monitor Not Going To Sleep on Mac Mini Server With Lion

    Summary: I am attempting to configure a Mac Mini Server that runs OS X Lion. This machine was originally shipped with OS X Lion; it is not an upgrade. My current specific problem is that my Viewsonic VX2835wm monitor will not go to sleep when the minutes setting on the Display Sleep setting for Energy Saver has been reached. Instead, the screen goes blank for a couple of seconds and is replaced with a blank blue backlit monitor. (Ironcially, the display sleep menu cautions: "Never letting your display go to sleep may shorten its life".) I very much want and need the ability to have my monitor go to sleep so as to save energy and to extend the monitor's life for as long as possible.
    Additional Background: I have had a couple of calls with Mac support and they have been unable to tell me whether this is a "design feature" or a flaw in the Lion OS because they have had no similar reports and they do not have the latest hardare available running Lion Server to test to see if this happens with other monitors. (They also, of course, don't have the VX2835wm monitor.)
    I do, however, know the following:
    (1) My HDMI monitor is connected to my Mac mini via a DVI KWM switch (ATEN CS1784) such that the HDMI output from my Mac is converted to DVI (using the DVI to HDMI converter that came with my Mac Mini) and is then run through the KVM and then converted back to HDMI (using a full pin DVI to HDMI cable). However, I have tested the monitor with a straight HDMI to HDMI cable running directly from the Mac Mini to the monitor and it has not changed anything.
    (2) The Lion operating system correctly recognizes (in Hardware / Displays) the model of my ViewSonic monitor.
    (3) I have a MacBook Pro running Leopard (OS X 10.5.8) that is connected to the same monitor through the same KVM switch (by way of a BookEndz docking station) which properly shuts down the monitor when there has been no activity for however many minutes are set in the Display Sleep setting under Energy Saver. (Indeed, all I want is the same functionality on my Mac Mini that I have enjoyed for the last two years with this MacBook Pro.)
    (4) When fully connected to the KVM, if I switch from my Mac Mini to my MacBook Pro and my Mac Mini display goes to sleep while I am working on my MacBook Pro, when I switch back to the Mac Mini, my monitor backlight will be off (and the power light will be standby yellow rather than the blue on) until I wake my computer up by touching the mouse of keyboard. I wonder if this may mean that the Mac Mini's signalling of the change in status from on to standby is somehow dysfunctional.
    (5) Shutting down the server functions (and other open applications) has no effect.
    I would greatly appreciate feedback from anyone out there running a Mac Mini with Lion regarding whether or not their monitors go into standby mode when the Display Sleep time is reached (please note whether or not you are running the Server or Client version, whether or not it is a new install or upgrade, and what monitor you are using).
    Thanks in advance to anyone who can help.

    No, I didn't solve the problem. The monitor still goes to sleep with WIndows but not with my Mac Mini. About 8 months ago I basically wore out the power switch on my monitor so I bought a wireless power switch to shut it off at the outlet. The VX2835wm monitor itself is now starting to fail as well-- a couple of times it's gone through a weird sequence of flashing screen colors on power up and ended up in an overscan mode (that took me for ever to figure out how to fix). I have decided to replace my VX2835wm with a Dell u2412m once it fails for good partly because I really want to keep the 16:10 resolution (very hard to find these days) and partly because I want to see if a different make of monitor will go to sleep properly based upon my Mac Mini power down settings.

  • Mac Mini Server with Lion (without Lion Server) ?

    I intend to buy a new Mac Mini and obviously the Server Hardware version is the best option with a i7 Quad Core and 2x HDDs (the option to 2x 750 is $100 whereas the option for 1x750 is $150 !!! for the standard Mac Mini) ... well lets make it shor, I would like the Mac Mini Server hardware but I don't want the Server components in the OS, I don't need them, I don't want to configure them. Does anybody know for sure if I can deinstall the Server components easily ?
    Thx

    Hi RajPad,
    i have not yet found a commandline tool to remove pages. If you're familiar with SQL you can use a tool to connect to the postgresql database where the pages are stored.
    I won't try to write a "howto connect to pgsql on lion" here because i know this has been answered already.
    If youre connected to the database collabd and you have a page url like:
    http://my.lion.server/wiki/pages/P9c196z/somepage.html
    Then your SQL to find the entity is:
    SELECT * FROM entity where tiny_id='P9c196z';
    Note the uid from that result and find and remove all related entries in other tables there after removing this entity.
    I have not excercised that myself because i don't have a system to screw
    Make a Database dump prior to your actions and hope nobody is editing pages while you're at work.
    If you have a plain SQL dump you could pick individual datasets from there to rebuild if something goes wrong. You'll only have to note what you changed to be able to revert.
    Just an idea ....
    Make a copy of your page and compare both pages in database. If one is working and the other aint you should be able to find the difference.
    Good Luck
    Andreas

  • Mac Mini Server with Windows installed?

    I have a windows application for a business otherwise all mac OS.  Want to run the windows app on a mac mini server allowing access from multiple workstations.  Desire to not committ entire mac mini server to windows so will need to partition I assume.  Any thoughts?

    You could try virtualizing the windows machine
    Virtual box is free I can't remember if it's free for commercial
    use
    Or VMware or parallels
    You could also try wine it's open source
    And allows running of (some) windows programs on Mac
    I've had mixed results with wine I haven't used it for ages
    Personally I think virtualizing would be the way to go
    Virtualizing would allow you to have snapshots and
    Backups would be somewhat easier
    If your unfamiliar with virtualizing
    It basically runs a compete OS as software on the host machine
    You can virtualize osx server on osx server if you desired
    Or most other OS, Linux, BSD, windows, windows server
    You just need enough grunt hard drive space and ram to host the virtualized OS

  • What is "best practice" to set up and configure a Mac Mini server with dual 1 TB drives, using RAID 1?

    I have been handed a new, out of the box, Mac Mini server.  Has two 1 TB drives in it.  Contractor suggested RAID 1 for the set up.  I have done some research
    and found out that in creating the software RAID, this takes away the recovery partition, so I have been reading up on how to create a recovery "disk" using a thumb drive.  this part of the operation I am comfortable with, but there are other issues/concerns that I have.
    Basically, what is the "best practice" to setup the Mini, configure the RAID and then start the server.  I am assuming the steps would be something like this:
    1) start up the Mini and run through the normal Maverick setup/config - keep it plain and vanilla
    2) grab a copy of the Server app and store it offline in a safe place
    3) perform the RAID configuration / reinstall of OS X Maverick using the recovery tools
    4) copy down and start the server app
    This might be considered a very simplified version of this article (http://support.apple.com/kb/HT4886 - Mac mini server (Late 2012 and Mid 2011): How to install OS X Server on a software RAID volume), with the biggest difference being I grab a copy of the Server App off of the mini before I reinstall, since I did not purchase it from the App store, but rather it came with the mini.
    Is there a best practice /  how-to tutorial somewhere that I can follow/learn from? Am I on the right track or headed for a train wreck?
    thanks in advance

    I think this article will answer your question. Hope this helps: http://wisebyte.blogspot.com/2014/01/best-configuration-for-mac-mini-server.html

Maybe you are looking for

  • Click events are not working properly in Firefox 18

    if some nested html structure and css, click events and event delegation stops working example: http://jsfiddle.net/dmitrismirnov/kSYqd/

  • Dragging images to desktop unpredictable.

    MacPro 3.1 (early 2008) (3) NEC Monitors - all ATI Video Cards. Last week i made the jump from Snow Leopard to Mountain Lion via Clean Install. Other than having to give up a few apps that do not have an upgrade path, everything has been doing remark

  • Support Information:  CSigDict-1938

    I have a client that is getting the following error in Adobe Acrobat Pro 9. Client is using Win XP sp3. Could not find erorr in the Adobe knowledge base or any forums. Creation of this signature could not be completed. Unknown error Support Informati

  • I deleted my icloud backup by accident

    I deleted my icloud backup from my iphone by accident, but I can still see that it shows up on iCloud.com. Anyone know how to get this to show up on my phone again? I lost all my photos when I reset it.

  • Random resetting of smooth scrolling

    Smooth Scrolling is set to "Snap" for all my folio's articles  except for one, the table of contents, which is set to "Both Directions". Every so often after an update this TOC article's smooth scrolling appears to be reset to "Snap" and the only way