Is PHP part of Leopard Server?

I am about to install a PHP program called Jomscocial which is a community program for a website that is hosted on my server, am I correct in thinking that PHP is standard on the server etc.

There is a php environment present within Mac OS X Server 10.5, yes.
Do check your software for what php extensions might be required. There are a few php extensions around that Mac OS X Server lacks, which means you'll potentially be rebuilding php for your box. The folks over at TopicDesk have a few documents, including one covering how to [add GD2 to php on Leopard Server|http://downloads.topicdesk.com/docs/AddingGD2_to_PHP_on_OS_X_Server_10_5Leopard.pdf]
Also be cautious around Internet-facing php installations in general, as packages based on that are common security targets; your servers will be attacked. (Not may be attacked. Will be.) Stay current, and stay paranoid.

Similar Messages

Alex on Leopard Server

Hi,
Does Alex come as part of Leopard Server. I'm looking at using Leopard Server and wold need Alex. I couldn't find it any where in any of the documents.
Kind regards,
Dave.

Alex? That's a software package that neither I nor the apropos command (on Leopard client) are familiar with, but -- if the source code is available, and if it works on Solaris or Linux or BSD or such -- it'll probably port over. Got a URL or a spot more detail?

PHP 4 on Mac Leopard Server

Hi there.
I would like to know, if it is possible to run PHP 4 on a Leopard Server. I have a website, that have problems running PHP 5, but runs perfectly under PHP 4.
Is there a way, to change it to PHP 4?
Thanx

I've found this info on another forum.
Maybe you can use it somehow:
PHP4 comes pre-installed from Apple. But it doesn't come pre-enabled.
You need to edit /etc/httpd/httpd.conf and uncomment two lines;
#LoadModule php4_module libexec/httpd/libphp4.so
#AddModule mod_php4.c
then restart Apache in Personal Web Sharing in System Preferences/Sharing/Services tab.
The Entropy PHP module (http://www.entropy.ch/software/macosx/php/) uses an extra .conf file (/usr/local/php5/entropy-php.conf) which essentially just contains the LoadModule and AddModule lines for PHP 5.
Of course, if you uncomment the PHP 4 lines in httpd.conf, then Apache tries to run both 4 and 5 and gets confused. You've to edit entropy-php.conf to point to PHP 4 instead. That's probably an ugly hack, however.

Anybody know a guide to revert Snow Leopard Server from php 5.3.1 to 5.2.x

I need to build a membership database for where I work. I had it working fine on my personal mac, but wanted to host it on a dedicated computer, so last week I went out and bought a Snow Leopard server.
The biggest issue I've come across is that Snow Leopard ships with php 5.3.1 installed and the Drupal / Civicrm system I'm using will only accept php 5.3.0. and apparently php 5.2.x is a much more stable / less buggy build. So I've been trying to figure out how to remove the installed php and downgrade to a previous build.
I should also point out that while I can do fairly limited things in Terminal, I am by no means a pro. I
am looking for something like the entropy build, rather than trying to figure out how to configure the whole thing myself -- if that makes sense.
Message was edited by: Flakesobran

You really have two options here.
Your SonicWall Firewall has a built-in VPN server, so you could configure that, point your remote client to the SonicWall's address and you're set - the remote machine will be given an address in your internal (192.168.2.x) LAN and will be able to communicate with all the other machines on the LAN.
The other option is to configure the VPN server on your Mini, in which case you'll need to configure port forwarding on the SonicWall so that the VPN traffic (the UDP ports listed above) are passed through to the server.
The advantage of running on the Mac is that it's automatically tied into the directory system on your Mac, so any user in your Mac's directory will be able to establish a VPN connection. The downside is that it's a little more complex to setup due to the port forwarding requirements.
In either case, once the VPN connection is established your remote Mac will be able to communicate with any machine on the LAN (the Mini, other clients, printers, etc.). The only thing that won't work will be auto-discovery (e.g. Bonjour), so VPN-based servers won't appear in your Finder's sidebar, for example. To overcome this you'll need to make sure your LAN DNS is working properly or know the IP address of each machine on your LAN.

Snow Leopard vs Snow Leopard Server (part 2)

How can it be determined if a machine is a Mac OS X server edition with some degree of certainty?
This is somewhat related to previous discussion titled "Snow Leopard vs Snow Leopard Server". I'm remotely logged into a machine that runs OS X 10.6.6 and acts as an office file server; yet the folder 'Server' under '/Applications' (e.g. /Applications/Server) that should contain some useful server administration tools does not exist on this machine.
Further, if this machine turns out to be a 'workstation' rather then a server, are there any licensing issues that would prevent installation of server administration tools to it (as referenced in http://en.wikipedia.org/wiki/MacOS_XServer)?
Thanks.

If you're using Screen Sharing, then look at About This Mac in the Apple menu. You'll see either Mac OS X, or Mac OS X Server there. If you're at the shell, then one of the ways you can identify the software is with the system_profiler command, in the software section.
And no; it's expected to have the software installed on a client you're managing the server from. If you want to know details, check the fine print with the package.

Where can I buy Snow Leopard Server?

Hi,
I need to find Snow Leopard Server to install Freehand in a new iMac 27" with Mountain Lion on Parallels 8.
I've seen SL Server in SMARTSHOP: http://enqurrvbpoii.lowcostoem.com/browse/search/?q=SNOW+LEOPARD+SERVER in an OEM download version to $79,95
Is it a reliable site?. Do you know a better site for this?
Many thanks in advance.

$20 - USA & Canada: Call 800-MY-APPLE and ask for part number MC588Z/A:
[click on image to enlarge]
Be sure to download the Snow Leopard patch for Freehand from the Adobe site.
http://forums.macrumors.com/showthread.php?t=1365439

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

Need help sorting a 'self-populating' plist file (vpn on mac leopard server - 10.6.8)

i recently configured my mac snow leopard server using terminal and had it successfully working.
i could vpn internally and externally to my server at its location.
i one day started getting the message
     "The connection has failed. Please verify your settings and try again"
i did as the message said and everything remained the same;
- server IP
- shared secret
- username and password
- public IP address
- com.apple.ppp.l2tp.plist stil, configured correctly
on a mission i thought id configure it the normal way by entering the data into the server admin panel and tried flicking the VPN service on and it wouldnt work, i was also getting an error saying it could not launch the com.apple.ppp.l2tp plist.
upon investigation i found out that i had installed (but not running) iVPN... so i uninstalled this...
still i could not get a VPN connection so i checked the com.apple.RemoteAccessServers.plist and noticed it had doubled in size (originally 4kb and now 8kb).
i thought this was a mistake and deleted it knowing it would self create a new fresh plist file.... HOWEVER it constantly populates the info twice as shown below:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ActiveServers</key>
    <array>
        <string>com.apple.ppp.l2tp</string>
    </array>
    <key>Globals</key>
    <dict>
        <key>PSKeyAccount</key>
        <string>vpn_0649d87c2f06</string>
    </dict>
    <key>Servers</key>
    <dict>
        <key>com.apple.ppp.l2tp</key>
        <dict>
            <key>DNS</key>
            <dict>
                <key>OfferedSearchDomains</key>
                <array>
                    <string>8.8.8.8</string>
                    <string>8.8.4.4</string>
                </array>
                <key>OfferedServerAddresses</key>
                <array>
                    <string>192.168.0.248</string>
                </array>
            </dict>
            <key>EAP</key>
            <dict>
                <key>KerberosServicePrincipalName</key>
                <string>vpn/[email protected]</string>
            </dict>
            <key>IPSec</key>
            <dict>
                <key>AuthenticationMethod</key>
                <string>SharedSecret</string>
                <key>IdentifierVerification</key>
                <string>None</string>
                <key>LocalCertificate</key>
                <data>
                </data>
                <key>LocalIdentifier</key>
                <string></string>
                <key>RemoteIdentifier</key>
                <string></string>
                <key>SharedSecret</key>
                <string>com.apple.ppp.l2tp</string>
                <key>SharedSecretEncryption</key>
                <string>Keychain</string>
            </dict>
            <key>IPv4</key>
            <dict>
                <key>ConfigMethod</key>
                <string>Manual</string>
                <key>DestAddressRanges</key>
                <array>
                    <string>192.168.0.230</string>
                    <string>192.168.0.240</string>
                </array>
                <key>OfferedRouteAddresses</key>
                <array/>
                <key>OfferedRouteMasks</key>
                <array/>
                <key>OfferedRouteTypes</key>
                <array/>
            </dict>
            <key>Interface</key>
            <dict>
                <key>SubType</key>
                <string>L2TP</string>
                <key>Type</key>
                <string>PPP</string>
            </dict>
            <key>L2TP</key>
            <dict>
                <key>Transport</key>
                <string>IPSec</string>
            </dict>
            <key>PPP</key>
            <dict>
                <key>ACSPEnabled</key>
                <integer>1</integer>
                <key>AuthenticatorACLPlugins</key>
                <array>
                    <string>DSACL</string>
                </array>
                <key>AuthenticatorEAPPlugins</key>
                <array>
                    <string>EAP-KRB</string>
                </array>
                <key>AuthenticatorPlugins</key>
                <array>
                    <string>DSAuth</string>
                </array>
                <key>AuthenticatorProtocol</key>
                <array>
                    <string>MSCHAP2</string>
                </array>
                <key>DisconnectOnIdle</key>
                <integer>1</integer>
                <key>DisconnectOnIdleTimer</key>
                <integer>7200</integer>
                <key>IPCPCompressionVJ</key>
                <integer>0</integer>
                <key>LCPEchoEnabled</key>
                <integer>1</integer>
                <key>LCPEchoFailure</key>
                <integer>5</integer>
                <key>LCPEchoInterval</key>
                <integer>60</integer>
                <key>Logfile</key>
                <string>/var/log/ppp/vpnd.log</string>
                <key>VerboseLogging</key>
                <integer>1</integer>
            </dict>
            <key>Radius</key>
            <dict>
                <key>Servers</key>
                <array>
                    <dict>
                        <key>Address</key>
                        <string>1.1.1.1</string>
                        <key>SharedSecret</key>
                        <string>1</string>
                    </dict>
                    <dict>
                        <key>Address</key>
                        <string>2.2.2.2</string>
                        <key>SharedSecret</key>
                        <string>2</string>
                    </dict>
                </array>
            </dict>
            <key>Server</key>
            <dict>
                <key>LoadBalancingAddress</key>
                <string>1.2.3.4</string>
                <key>LoadBalancingEnabled</key>
                <integer>0</integer>
                <key>Logfile</key>
                <string>/var/log/ppp/vpnd.log</string>
                <key>MaximumSessions</key>
                <integer>128</integer>
                <key>VerboseLogging</key>
                <integer>1</integer>
            </dict>
        </dict>
        <key>com.apple.ppp.pptp</key>
        <dict>
            <key>DNS</key>
            <dict>
                <key>OfferedSearchDomains</key>
                <array>
                    <string>8.8.8.8</string>
                    <string>8.8.4.4</string>
                </array>
                <key>OfferedServerAddresses</key>
                <array>
                    <string>192.168.0.248</string>
                </array>
            </dict>
            <key>EAP</key>
            <dict>
                <key>KerberosServicePrincipalName</key>
                <string>vpn/[email protected]</string>
            </dict>
            <key>IPv4</key>
            <dict>
                <key>ConfigMethod</key>
                <string>Manual</string>
                <key>DestAddressRanges</key>
                <array/>
                <key>OfferedRouteAddresses</key>
                <array/>
                <key>OfferedRouteMasks</key>
                <array/>
                <key>OfferedRouteTypes</key>
                <array/>
            </dict>
            <key>Interface</key>
            <dict>
                <key>SubType</key>
                <string>PPTP</string>
                <key>Type</key>
                <string>PPP</string>
            </dict>
            <key>PPP</key>
            <dict>
                <key>ACSPEnabled</key>
                <integer>1</integer>
                <key>AuthenticatorACLPlugins</key>
                <array>
                    <string>DSACL</string>
                </array>
                <key>AuthenticatorEAPPlugins</key>
                <array>
                    <string>EAP-RSA</string>
                </array>
                <key>AuthenticatorPlugins</key>
                <array>
                    <string>DSAuth</string>
                </array>
                <key>AuthenticatorProtocol</key>
                <array>
                    <string>MSCHAP2</string>
                </array>
                <key>CCPEnabled</key>
                <integer>1</integer>
                <key>CCPProtocols</key>
                <array>
                    <string>MPPE</string>
                </array>
                <key>DisconnectOnIdle</key>
                <integer>1</integer>
                <key>DisconnectOnIdleTimer</key>
                <integer>7200</integer>
                <key>IPCPCompressionVJ</key>
                <integer>0</integer>
                <key>LCPEchoEnabled</key>
                <integer>1</integer>
                <key>LCPEchoFailure</key>
                <integer>5</integer>
                <key>LCPEchoInterval</key>
                <integer>60</integer>
                <key>Logfile</key>
                <string>/var/log/ppp/vpnd.log</string>
                <key>MPPEKeySize128</key>
                <integer>1</integer>
                <key>MPPEKeySize40</key>
                <integer>0</integer>
                <key>VerboseLogging</key>
                <integer>1</integer>
            </dict>
            <key>Radius</key>
            <dict>
                <key>Servers</key>
                <array>
                    <dict>
                        <key>Address</key>
                        <string>1.1.1.1</string>
                        <key>SharedSecret</key>
                        <string>1</string>
                    </dict>
                    <dict>
                        <key>Address</key>
                        <string>2.2.2.2</string>
                        <key>SharedSecret</key>
                        <string>2</string>
                    </dict>
                </array>
            </dict>
            <key>Server</key>
            <dict>
                <key>Logfile</key>
                <string>/var/log/ppp/vpnd.log</string>
                <key>MaximumSessions</key>
                <integer>128</integer>
                <key>VerboseLogging</key>
                <integer>1</integer>
            </dict>
        </dict>
    </dict>
</dict>
</plist>
Thinking i was half clever i thought id do a restore to when i first set the server up... not successful
Secondly i wiped the drive with zero data and did a fresh install... still not successful.
There must be a way to fix this BS error!
my source for the original setup was here: http://dreaming-artemis.com/2011/07/18/setting-up-vpn-on-the-imac-osx-snow-leopa rd-10-6-8/
Thanks in advance
TMC

I would think you could copy them over using rsync, which is part of the OS X server package. If you're not familiar with rsync there is a tutorial here:
http://everythinglinux.org/rsync/
Skip the stuff about installing and configuring rsync and just go to the part about using it to copy files between servers.

I've got Snow Leopard Server, but don't need the server functions. What to do?

This is somewhat complicated, so please bear with me. My Mac Pro was running OS X 10.5 and required updating. But we have legacy Power PC apps (mainly FreeHand) that we want to continue using, even though Mountain Lion doesn't support them.
As a solution, I'm going to run Snow Leopard Server in emulation on Parallels 8 Desktop. I would rather have used plain old Snow Leopard instead of the server version, but Apple's EULA only allows 10.6 Server to run in emulation.
So, I got Snow Leopard Server and have used it to upgrade 10.5. Eventually, (once I get everything working properly), I'll upgrade that to Mountain Lion and use SL Server in Parallels emulation to run the old Mac apps we can't do without.
But I've run into a problem I didn't anticipate: I don't have a clue about running a server.
I'm having trouble setting it up so the other Mac user in my department can access a shared folder. Also, I want the login window to display the list of users, but that option is grayed out.
What I'd like to do is strip out all the server functions and just run as if 10.6.8 was a standard version of Snow Leopard, which I'm familiar with. If that's not practical, please explain how to get sharing to work since that's the main problem.
I've tried turning off the services listed in the Server Preferences (iCal, Mail, etc.) but that hasn't fixed the problems. I think there may be server functions running that I haven't found preventing me from fixing the problems. Or it could be something else entirely (as I said, no clue).

DON'T MAKE A MOUNTAIN (lion?) OUT OF A MOLEHILL!
Several points in response to your post, in chronological order, not necessarily in order of importance:
• It was a common Urban Myth that Snow Leopard (client's) EULA prohibited its virtualization in Lion or Mt. Lion on a Mac! That myth has been largely debunked in the last 18 months.
Here are detailed instructions on how to install Snow Leopard client into Parallels 7 or 8:
http://forums.macrumors.com/showthread.php?t=1365439
That being said, and being the author of the aforementioned thread, I STRONGLY recommend that, where possible, you use Snow Leopard Server in favor of Snow Leopard client. This will side step some later corruption problems that can arise from the improper use and shutting down of this Parallels partition.
Historically, this thread was written when Apple sold Snow Leopard Server for $499+ or ceased sales altogether. Now, Apple has rendered the (now diminishing) debate over the EULA moot, by its recent release of Snow Leopard Server to the US & Canadian community for $20; leaving those who cannot purchase SLS (or get someone to purchase it for them) to continue to follow the instructions in my thread (or asking me to purchase SLS for them and forward it to them; my preferred course of action!).
• I ALWAYS recommend that data files be stored on the real Mac's HDs and NOT in a virtualized world. This is easy to accomplish and establishes a backup regimine (Time Machine, etc.) that will protect the users data. Lost applications are easily restored from their installer discs.
• In practice I find that using SLS in Parallels 8 is the same as using SL client in Parallels. I have even removed the Server apps from the Dock so as to not be confused by them.
So, your solution is to establish a "shared folder" on the hard drive of the Mac that is hosting Parallels. When in SLS in Parallels you will have access to your shared folder, ironically through Parallels' "Shared Folders" feature that is now present in Mac OS Guest installs on version 8 (see the "Shared Folders" SERVER on the right side of the screenshot, below).
When using Freehand MX or other PowerPC apps, save your data files into your shared folder through access to it by Parallels' Shared Folders. Other users on your network will have access to the SAME data files, through their customary use of file sharing to access your shared folder from your Mac's hard drive.
IGNORE the Server applications in the Applications folder...
Freehand MX running in Snow Leopard Server installed into Parallels 8 for use in Lion or Mt. Lion:
[click on image to enlarge]
Postscript: your post was so easy to follow!

Where can I find info on how to install and run Snow Leopard Server as virtual machine inside Mountain Lion

Where can I find info on how to install and run Snow Leopard Server as virtual machine inside Mountain Lion

Here is the short answer:
Installing Snow Leopard Server into Parallels 10 for DUMMIES:
http://forums.macrumors.com/showpost.php?p=17285039&postcount=564

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.

Mac Mini 2009 vs Leopard Server

Hi all...
I am hoping to get to the bottom of this asap, as I am looking forward to just getting on with things.
The issue is installation of Mac OS X Leopard Server 10.4 on a Mac Mini (Early 2009)
First of all.... Yes I have read the *Article HT3479* http://support.apple.com/kb/HT3479 and yes it allows you too boot your mini, however....
When you go through the installation process and are entering your information, there are several key steps missing from the interview[Server Assistant]. The main question missing is, "What type of installation" Standard, workgroup or advanced.
Another key set of questions missing is Network Setup.
So suffice to say the HT3479 does not address the issue i am experiencing.
Here are the methods I have attempted to use to install Server on this mini...
HT3479. {The result is that I can not run Server Preferences... Apparently the computer is in advanced mode and can not be reverted to standard}
The above method has been tried in the following examples...
* Install Mac OS X Client (10.5.6 from client disk)
+ Apply updates (at the time it was pre 10.5.7 so up to and including all updates to that time10.5.6)
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
* Install Mac OS X Client (10.5.6 from client disk)
+ Don't apply updates
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
I tried the above methods several times having no success
I contacted Apple support where I was asked to just try it again! and was told that nobody else was having these issues.
Great... 60Gb download capped reached so I had to wait for this month to continue.
10.5.7 update was released recently, so i thought I may be in luck.
So this month I have tried the above methods several times with the same outcomes.
In desperation I tried the following method...
Boot the Mac Mini in Target Disk Mode and running installation from an iMac targeting the disk in the mac mini. {The result is that during Boot up and Shut down verbose mode is invoked and there are numerous error messages in the log files, secondly I am experiencing several issues with DNS names etc.... won't accept SERVERNAME.local}
Anyway, this method gave me the most joy but still far from ideal.
Seemingly unfair it let me glimpse what leopard server can do, and yes i like what i see, but I really need to be able to install leopard server normally and have no issues.
*Hardware Configuration*.
Mac Mini (Early 2009) A1283 (2.0\1X1G\120\SD\AP\BT)
Upgraded RAM from 1GB to 4 GB (yes it works fine, full hardware test performed)
Upgraded HDD from 120GB to 320GB 7200 rpm (Caviar Black)
Samsung 22" monitor
Apple Keyboard (Aluminium with keypad) A1243
Apple Mightymouse A1152
Network
ADSL modem PPPOE
Apple Airport Extreme
Wired direct from rear of AEBS to Mac Mini
AEBS setup in DHCP, but reserved IP address for Mac Mini's Mac Address
Software
Mac OS X Server Version 10.5.4 [0Z691-6214-A] (Full retail version)
Mac OS X 10.5.6 Disk version 1.0 [2Z691-6344-A]
I am sure that others are experiencing the same issue, as many have listed similar issues to the above, however many are open ended with no resolution. I hope that if a solution is found or it is determined that there is an issue that news can be posted by apple so others are better informed before investing money in both products hoping to achieve a working network server.

I recently purchased a Mac Mini 320 GB model and OS X Server (Leopard). Before I purchased them I asked a couple of the Genius guys if I could run OS X Server normally on one of the new 320GB Minis? And the concensus among several Apple Store employees, was that yes, there should be no problem whatsoever...
So I bought the pair, and went through the install process numerous times, and was never able to get the standard installation until I resorted to dire measures which I have outlined below.
I tried to boot from OS X Server 10.5.4 on several machines at the Apple Store, and it does not boot any of the new machines (as of 2009.06.02). The normal install (use the os x server disk to boot) works perfect on an iMac 2.4GHz machine, and on a G4 Mirrored Drive machine, and on both of these machines the process is simple. Pop in the os x server disk, go get a sandwich, come back, answer a few questions, you are up and running, and life is great. It doesn't get any better...
The problem with the newer machines is that you must install the standard os x, get all the updates, insert os x server disk, and install os x server. The unfortunate part is that by the time you install OS X Server several items have already been set, OS X Server senses this and skips about 17 screens that allow for {"standard", "workgroup", "enterprise"} setup, and goes right into the "enterprise" mode.
One of the big conveniences with the standard setup is that quite a few things are created for you. Once you use the "standard" setup you can promote the installation to the "enterprise" mode by opening it with "Server Admin" which provides infinitely more control, but using "standard" setup to start with simplifies life considerably.
If you figure out how to do the "standard" install bear in mind that when it asks you for your administrative user account info it really wants :
name : Directory Admin
shortname : diradmin
password : astrongpassword
This will allow you to go from LOCAL to LDAPv3/127.0.0.1 when using Workgroup Manager
When it asks if you want add more users you can add one user, the "Local Admin" :
name : Local Admin
shortname : localadmin
password : astrongpassword (you will have to reset this password after you login as diradmin)
You can reset the "Local Admin" password via "System Preferences ---> Accounts"
and you can create the other users via the Workgroup Manager ---> LDAPv3/127.0.0.1 domain once you get DNS and Open Directory working.
if you use "standard" or "enterprise" the first thing to setup is DNS, everything else depends on DNS being configured correctly. "standard" really shines here because it won't let you screw up DNS.
You will need private DNS even if you have a provider handle public DNS for you.
If you are using standard you will be asked for, and can enter something like the following :
domain : crystal-palace.mac.private
machine : crystal-palace
if you are doing the "enterprise" mode you will also have to enter crystal-palace.mac.private in one more field,
Each machine will have a fixed PRIVATE IP address in the form of "192.168.1.n" and a "Computer Name" that was unique within the ZONE (the group of machines) via "System Preferences ---> Sharing".
Once you switch to the "enterprise" mode you can add more machines (using the "Computer Name" above) with their respective private ip addresses.
If you are using the "enterprise" mode, You want to setup Open Directory initially as "standalone", once that is working promote it to "Directory Master" via the "Settings" Tab. If you are using the "standard" mode, the Open Directory is setup automatically as "Directory Master" but there doesn't seem to be any way to add to the DNS, I think you have to use "Directory Utility" to do this. But if you've gotten this far it is easier to promote the setup mode to "enterprise" with "Server Admin".
I have a 1TB drive partitioned into 8 logical drives , the first seven standard partitions are named BUP_1 through BUP_7 and are provide 93 GB each. They are setup as test drives. The last partition is named TM_1 which is used for Time Machine backups and it provides close to 280 GB of backup storage.
On the first partition, I installed OS X 10.5.7 along with some basic applications that I normally use. I then created a dmg installer that I saved to TM_1 using disk utility and used that to install the image on the remaining six partitions (BUP_2 ... BUP_7).
The seven standard partitions then have OS X 10.5.7, which I basically use as test drives. It is here that I attempted different things trying to get this to be a simple deal. If one attempt didn't work I moved on to the next partition...
The BUP_n already have USERNAME setup as localadmin, not admin CHECK step ( 4 ) below. Also note that the dscl commands all have a dot following them.
Steps that worked for me, that allowed me to select the setup mode for os x server.
( 1 ) Boot mac into single user mode by holding down (CMD-S) during startup until you see text scrolling on the screen.
if the text on the screen stops, and you don't get the "root # " cursor, you may have to hit return once in order to get it. Once you get the root cursor you will need to enter the following commands very carefully. On the paths you can type part of the path and hit tab for auto completion. Everything is case sensitive...
NOTICE that USERNAME needs to be substituted with the correct shortname from step ( 4 ) in steps ( 6 ), ( 7 ) and ( 8 )
( 2 ) $ mount -uw /
( 3 ) $ /bin/launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist &
( 4 ) $ dscl . -list /Users
( 5 ) $ rm -R /Library/Preferences/
( 6 ) $ rm -R /Users/USERNAME/
( 7 ) $ dscl . -delete /Users/USERNAME
( 8 ) $ dscl . -delete /Groups/admin GroupMembership USERNAME
( 9 ) $ rm /var/db/.AppleSetupDone
( 10 ) $ rm -R /var/db/dslocal
( 11 ) $ mkdir -p /var/db/dslocal/nodes
( 12 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
( 13 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
( 14 ) $ passwd
( 15 A) $ shutdown -h now (if you want to reboot outside of single user mode)
OR
( 15 B) $ exit (if you want to continue booting in single user mode)
I think that to make this an easy install, there should be a small script from Apple that you can run once OS X, and OS X Server are installed, and updated, that reset everything to pristine, so that after running the script everything that needs to be removed, or reset is done so that you can go through the normal 17 screens that allow for simple setup of OS X Server, just like if you had been able to boot from the OS X Server disk.
The answer I got from Apple Support is that when new machines come out it takes a while to get the correct drivers and release an installer disk for OS X Server. The unfortunate part is that there is no simple way to allow the installer to select which mode they need for the particular installation. They are forced to take the "enterprise" mode...
I am not SURE whether the steps I have outlined above cover everything, that is why I am suggesting that if would be far more accurate if Apple provided an installer script when they have NON_BOOTABLE versions of OS X Server Installer.
After three weeks and about 150 hours worth of work, I finally gave up and took the Mac Mini and OS X Server back and bought another iMac 24. Whenever a newer version OS X Server that is bootable on the newer machines comes out, I will get it another shot...
The guy I dealt with at the Apple Store kept saying, it works, you're just not installing it correctly. He also said "I've installed OS X Server on a Mini". But everytime I asked him, "Was it a new new Mini?" and he would respond, "Well, NO!". I also asked him "Were you able to boot the Mini from the the disk ?", he responded "YES!"
I ran into some other issues, for example one night I shutdown the server, and the next morning none of the passwords would work, not even the root password. So I came up with the following, hope this helps.
PROBLEM :
This morning for some reason the Mac Mini would not allow me to log in, neither as the Local Admin, nor as the System Admin. The database containing the login info must have become corrupted.
FIRST LEVEL REPAIR ATTEMPT
I started the machine using the Apple Install DVD, holding the "C" key to force the CD to boot
Once the installer screen came up, hit return and select :
( 1 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Permissions
( 2 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Disk
( 3 ) Quit out of Disk Utility...
( 4 ) Menu Utilities -> Reset Password
( a ) Reset the password for the root user
( b ) Reset the password for the local admin user.
( 5 ) Quit out of Reset Password...
( 2 ) Menu Utilities -> Startup Disk
( 6 ) Select the correct disk to use for re-start.
( 7 ) Re-Start
( 8 ) I tried this several times, but could never get the new passwords to work after re-booting.
There must have still been some corruption in the database.
SECOND LEVEL REPAIR ATTEMPT
( 10 ) reboot and to hold the CMD-S to boot into the single user mode.
At the root prompt, type in the following commands. I might have to hit return, if there is a white cursor that appears to be hung up waiting for input, just hit return, then you should see the root prompt.
First try :
( 11 ) root # fsck -f
( 12 ) root # mount -uw
( 13 ) root # passwd
( 14 ) root # exit
( 15 ) when the login dialog appears try to login as root
( 16 ) if you can login, go to :
( a ) System Preferences -> Accounts and reset the password for the Local User in question.
ELSE
( b ) Go to step ( 20 ) below
THIRD LEVEL REPAIR ATTEMPT
This is the command set to reset the local DB on the server
20. $ reboot and to hold the CMD-S to boot into the single user mode.
21. $ mount -uw /
22. $ mv /var/db/dslocal /var/db/dslocal.old
23. $ mkdir -p /var/db/dslocal/nodes
24. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
25. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
26. $ passwd
FOURTH LEVEL REPAIR ATTEMPT
( 31 ) Shutdown the machine with the problem( we will call it the pm for problem machine)
( 32 ) attach a firewire cable to the pm on one end
( 33 ) attach the other end of the firewire cable to a good machine (call it gm)
In my case the gm uses firewire 400, and the pm uses firewire 800, so I had to get a cable that had firewire 400 on one end, and firewire 800 on the other,
( 34 ) start up the pm while holding down the "T" key until you see a large image floating around the pm screen. This put the pm into the "TARGET" mode, now it will behave like a drive, and you should see the drive on your gm desktop.
( 35 ) You can now copy anything you need from the pm to the gm.
( 36 ) Make sure you BACKUP anything and everything you want from the pm to the gm
( 37 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X SERVER :
At this point, if nothing else has worked you will have to erase the drive and
( a ) re-install OS X, and
( b ) re-install OS X Server on the pm
( 38 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X :
At this point, if nothing else has worked, from the Install DVD you can
( a ) Archive and re-install OS X on the pm
Another interesting thing that has happened several times now, is that I always install standard OS X on the first partition of the disk, and OS X Server on a different partition, and after installing OS X Server the machine would no longer boot from the standard OS X partition. This has happened like four different times, not sure what could be causing this problem. Booting from the install disk and running Disk Utilities to repair the disk (which comes back OK), and repair permissions always comes back with an internal error,and cannot be completed.
I have no clue what could be happening. I always had to reformat the drive and instal OS X all over again.
I have no clue what could be causing this to happen ?

Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

MySQL installation in Snow Leopard Server appears to be broken?

I tried
sudo gem install mysql -- --with-mysql-config=/usr/bin/mysql_config
and it failed.
The mkmf.log said (in part):
"gcc -o conftest -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DXOPENSOURCE -DDARWIN_CSOURCE -I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common conftest.c -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch x86_64 -pipe -L/usr/lib -lmysqlclient -lz -lm -lruby -pipe -L/usr/lib -lmysqlclient -lz -lm -lpthread -ldl "
ld: library not found for -lmysqlclient
collect2: ld returned 1 exit status
checked program was:
/* begin */
1: /top/
2: int main() { return 0; }
3: int t() { mysqlsslset(); return 0; }
/* end */
So, I checked mysql_config:
Usage: /usr/bin/mysql_config [OPTIONS]
Options:
--cflags [-I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT]
--include [-I/usr/include]
--libs [-pipe -L/usr/lib -lmysqlclient -lz -lm]
--libs_r [-pipe -L/usr/lib -lmysqlclient_r -lz -lm]
--socket [/var/mysql/mysql.sock]
--port [0]
--version [5.0.91]
--libmysqld-libs [-pipe -L/usr/lib -lmysqld -lz -lm]
Note that mysql_config appears to have been compiled with an assumption that /usr/lib
would contain a -lmysqlclient shared library.
Which assumption fails on my Snow Leopard Server installation:
minisvr:~ root# ls -la /usr/lib/mysql
ls: /usr/lib/mysql: No such file or directory
Now, I'm reasonably certain that I have done nothing to cause this library to be missing;
as I am also reasonably certain that the mysql_config found in /usr/bin is one shipped by
Apple (as opposed to one I could have picked up somewhere else).
Can anyone else out there verify: does Apple ship /usr/bin/mysql_config?
If so, does it supply linker options like -L/usr/lib -lmysqlclient?
If that also is true, does your /usr/lib actually contain an Apple-supplied libmysqlclient.*?
Now, assuming that my installation is reasonably close to what Apple actually shipped,
what should I do about it? Would I be better off to go find a source distribution,
and build and install mysql, foregoing the Apple-supplied integration with
management tools (e.g., using Server Manager to start/stop and monitor logfiles)?
What do other users of mysql on Mac OS X Server do?
Thanks,
Tommy K

I tried
sudo gem install mysql -- --with-mysql-config=/usr/bin/mysql_config
and it failed.
The mkmf.log said (in part):
"gcc -o conftest -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DXOPENSOURCE -DDARWIN_CSOURCE -I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common conftest.c -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch x86_64 -pipe -L/usr/lib -lmysqlclient -lz -lm -lruby -pipe -L/usr/lib -lmysqlclient -lz -lm -lpthread -ldl "
ld: library not found for -lmysqlclient
collect2: ld returned 1 exit status
checked program was:
/* begin */
1: /top/
2: int main() { return 0; }
3: int t() { mysqlsslset(); return 0; }
/* end */
So, I checked mysql_config:
Usage: /usr/bin/mysql_config [OPTIONS]
Options:
--cflags [-I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT]
--include [-I/usr/include]
--libs [-pipe -L/usr/lib -lmysqlclient -lz -lm]
--libs_r [-pipe -L/usr/lib -lmysqlclient_r -lz -lm]
--socket [/var/mysql/mysql.sock]
--port [0]
--version [5.0.91]
--libmysqld-libs [-pipe -L/usr/lib -lmysqld -lz -lm]
Note that mysql_config appears to have been compiled with an assumption that /usr/lib
would contain a -lmysqlclient shared library.
Which assumption fails on my Snow Leopard Server installation:
minisvr:~ root# ls -la /usr/lib/mysql
ls: /usr/lib/mysql: No such file or directory
Now, I'm reasonably certain that I have done nothing to cause this library to be missing;
as I am also reasonably certain that the mysql_config found in /usr/bin is one shipped by
Apple (as opposed to one I could have picked up somewhere else).
Can anyone else out there verify: does Apple ship /usr/bin/mysql_config?
If so, does it supply linker options like -L/usr/lib -lmysqlclient?
If that also is true, does your /usr/lib actually contain an Apple-supplied libmysqlclient.*?
Now, assuming that my installation is reasonably close to what Apple actually shipped,
what should I do about it? Would I be better off to go find a source distribution,
and build and install mysql, foregoing the Apple-supplied integration with
management tools (e.g., using Server Manager to start/stop and monitor logfiles)?
What do other users of mysql on Mac OS X Server do?
Thanks,
Tommy K

Is PHP part of Leopard Server?

Similar Messages

Maybe you are looking for