Virtualization of snow leopard server on a xserv

Hello
I'm looking for someone how have already use virtualization on a xserv.
thanks

We have an xserve + 2 Snow Leoaprd VMs + 2 Win2k3 VM's. It's mostly been used for 10-20 clients, but we're starting to move the rest of our staff on it which adds about 50 more.
We chose vmware because of cost and stability. Parallels requires their server version which costs a lot more money than their desktop, and it didn't seem worth it if we only ran 2-3 VM's.
Vmware also seemed more stable than Parallels5 at the time.
It might be different now, they did not have hypervisor even announced a year ago when we last compared the two.
Message was edited by: InterHmai

Similar Messages

New Snow Leopard Server, Slow Network Accounts

We've installed Snow Leopard Server on our XServe quite a while ago and since then all users who work with network accounts are complaining about serious perfomance issues. These issues are for instance logins which may very well take up to several minutes, or applications like Adobe InDesign which take their time to load files from the users network shares.
Our System consist of:
1 XServe running OS X 10.6.8 Snow Leopard Server
48 iMacs running OS X 10.5
1 Windows Server 2008
The XServe serves as an OpenDirectory and Fileserver, while the Windows Server delivers DNS.
We have created ~500 users and 25 groups in the OpenDirectory. All user files are located in their roaming profiles on the Xserve. Additionaly every user has access to one group folder, which is located on the Xserve as well.
All group folders are Sharepoints and added to the dock of all users in the appropriate group.
I have already checked DNS settings, user accounts, network connectivity in general, network load during peak hours, the ACLs on the group folders....
By now im simply out of ideas what my cause the problem, let alone how to solve it.
Any hints are greatly appreciated.

Are you using any redirections? Redirecting the cache folder from the network home to the /tmp should improve speed. Use this white paper from apple. http://images.apple.com/education/docs/Apple-ClientManagementWhitePaper.pdf The redirections are on page 53.

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Can I use boot camp or other virtualization software with Snow Leopard Server?

Can I use boot camp or other virtualization software with Snow Leopard Server?

Boot Camp is not virtualization; it boots Windows natively on the Mac hardware. So Boot Camp would be irrelevant to running Snow Leopard Server. Parallels and VMWare Fusion both have at least "experimental" support for running Snow Leopard Server in a virtual machine on Mac OS X, though I don't know how robust it is as of this time. You might ask for opinions on the Parallels or VMWare forums.
Regards.

Unable to access gateway and DNS via VPN (L2TP) with Snow Leopard Server

Summary:
After rebooting my VPN server, i am able to establish a VPN (L2TP) connection from outside my private network. I am able to connect (ping, SSH, …) the gateway only until the first client disconnects. Then i can perfectly access all the other computers of the private network, but i cannot access the private IP address of the gateway.
Additionally, during my first VPN connection, my DNS server, which is on the same server, is not working properly with VPN. I can access it with the public IP address of my gateway. I can access it from inside my private network. A port scan indicates me that the port 53 is open, but a dig returns me a timeout.
Configuration:
Cluster of 19 Xserve3.1 - Snow Leopard Server 10.6.2
Private network 192.168.1.0/255.255.255.0 -> domain name: cluster
-> 1 controller, which act as a gateway for the cluster private network, with the following services activated:
DHCP, DNS, firewall (allowing all incoming traffic for each groups for test purposes), NAT, VPN, OpenDirectory, web, software update, AFP, NFS and Xgrid controller.
en0: fixed public IP address -> controller.example.com
en1: 192.168.1.254 -> controller.cluster
-> 18 agents with AFP and Xgrid agent activated:
en1: 192.168.1.x -> nodex.cluster with x between 1 and 18
VPN (L2TP) server distributes IP addresses between 192.168.1.201 and 192.168.1.210 (-> vpn1.cluster to vpn10.cluster). Client informations contain the private network DNS server informations (192.168.1.254, search domain: cluster).
_*Detailed problem description:*_
After rebooting the Xserve, my VPN server works fine except for the DNS. My client receives the correct informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.201
Subnet Mask:
Router: 192.168.1.254
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can ping all the Xserve of my cluster (192.168.1.1 to 18 and 192.168.1.254). If i have a look in Server Admin > Settings > Network, i have three interfaces listed: en0, en1 and ppp0 of family IPv4 with address 192.168.1.254 and DNS name controller.cluster.
The DNS server returns me timeouts when i try to do a dig from my VPN client even if i am able to access it directly from a computer inside or outside my private network.
After i disconnect, i can see in Server Admin that the IP address of my ppp0 interface has switch to my public IP address.
Then i can always establish a VPN (L2TP) connection, but the client receives the following informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.202
Subnet Mask:
Router: (Public IP address of my VPN server)
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can access all the other computers of my network (192.168.1.1 to 192.168.1.18) but when i ping my gateway (192.168.1.254), it returns me timeouts.
I have two "lazy" solutions to this problem: 1) Configure VPN and DNS servers on two differents Xserve, 2) Put the public IP address of my gateway as DNS server address, but none of these solutions are acceptable for me…
Any help is welcome!!!

I would suggest taking a look at:
server admin:vpn:settings:client information:network route definitions.
as I understand your setup it should be something like
192.168.1.0 255.255.255.0 private.
at least as a start. I just got done troubleshooting a similar issue but via two subnets:
http://discussions.apple.com/thread.jspa?threadID=2292827&tstart=0

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!

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.

Where to buy Snow Leopard Server? OEM okay?

All,
I have half a dozen XServe (late 2008 machines) to upgrade from Leopard Server to Snow Leopard Server. I have been investigating how to go about doing this and have a couple of questions:
1) does Apple still sell this software? If so, how the heck to I order it? Searching for Apple software in the Store is an exersize in futility!
2) I've found several suppliers of OEM versions of Snow Leopard Server for impossibly low prices. I have installation media, I simply need the license keys; is this a good route to go?
Thanks for the feedback, everyone!
-Brian

1) does Apple still sell this software? If so, how the heck to I order it? Searching for Apple software in the Store is an exersize in futility!
This is a question a lot of people have. There's no clear answer, other than Apple don't seem to offer it any more.
2) I've found several suppliers of OEM versions of Snow Leopard Server for impossibly low prices. I have installation media, I simply need the license keys; is this a good route to go?
There is no such thing as an OEM version of Snow Leopard Server - or of any Mac OS X System.
Since Apple develop and sell both the software and the hardware, there's no OEM market - it's not like you can buy a Dell or a HP with Mac OS X installed (which would be an OEM version of Mac OS X for Dell or HP).
Therefore, any site offering an OEM version of Mac OS X is absolutely, definitely, 100% a scam.
At best they're reselling older copies (which is questionable), at worst they're a malware farm trying to con you into installing fake software, or charging you for something they can't deliver.

Binding Snow Leopard server OD to Mavericks server OD

Does anyone know if it's possible to setup a Snow Leopard server to bind Open Directory to a new server running Macvericks server?
I have 2 new mac minis running 10.9.4 with server 3.1.2 on them, one as an OD master and the other as a replica. We have a couple of older Xserves still running Snow Leopard server and must keep them that way because of some other software that can't be upgraded.
What we need is those 2 servers to be able to bind (not as a replica as it's not possible) to the master OD mac mini for authentication? I've been able to get the OD process on them to be set to "connect to another directory" then use Directory Utility to try and bind LDAPv3 to the master mini but it says invalid credentials supplied when I type in the proper OD username and password.
Any thoughts?

To work as Master and Replicas, all must be the same version of Server.
You cannot bind as Open Directory Servers (as in combining Open Directories), but you can run Mac OS X 10.6.8 workstations [running 10.6.8 or 10.6.8 Server] off a Mavericks plus Server 3 Open Directory Server. You can have Home Directories on an older Server. You may be able to provide some services off the older Servers. But you cannot keep them as Open Directory Servers on the same Network.
I think you just shut off Open Directory on the 10.6.8 Servers, then use Directory Utility to Bind to the Mac Mini or Replica Server as if they were Workstations.

Snow Leopard Server Software - Mac Mini Copy vs Retail Copy

Hi All,
I recently purchased a mac mini server, with what I thought would be a SL Server license.
I've used the Mac Mini to run a Leopard server whilst our Xserve was out of action.
Now the xserve is back, I was thinking of installing SL on the Xserve and keep the mini running leopard until we migrate over.
When I tried to install SL on the Xserve, it gave me an error. I rang Apple, and the enterprise guy told me this wasn't possible, as the copy that came with the mac mini was hardware specific and just a restore copy of snow leopard server. Bottom line I can't install the Mac Mini version of SL on an Xserve, even though I have paid for a SL license in buying the mac mini!
Does anybody know if there is any real differences between the hardware specific software copy and a retail version. If there isn't I'll install a copy on the mac mini and copy it over to the xserve. I just want to be sure that I'm not getting a downsized version of software!
Thanks.

There are ways to extract the OS from the restore disk so you can use in other system. you will just have to do a little online search. but I think it will be illegal if you care of course... but it would probably be easier to just download a copy from rapidshare or something like that and use your key ..
As far as feature there is none between the restore and retail copy.

Snow Leopard Server with Lion Server for APNS

Hello Everyone,
I'm wanting to keep my Snow Leopard Server (Xserve) setup in place its working great, and cant afford to have any down time on the company network. What I would like to do is setup up an additional Mac Mini with Lion server to handel just the APNS. Is this possiable.
I would be running all of the services, mail, OD, addressbook, caladar, on the Snow leopard server but want to use Lion Server to push out and manage some Lion clients, and iPhone with a second server has anyone done this, can this setup work?
Thanks!
Robert

Hi Robert
"Can you provide the basics for setup?"
Apart from making sure DNS is configured correctly - as always - there's not much else you need to know. Server has to be configured as an OD Master. It does work with the default self-signed certificate although Apple do recommend you purchase one from a CA such as Verisign. I mention Verisign because it's trusted by the US Government. Once you've got your push notification certificate from Apple, enable the relevant option in the Server App. From there create the enrolment profile and key in the relevant url in your IOS device. The rest is fairly obvious. If DNS is not properly configured for your network this part probably will fail.
"Can this all be completed in server admin, or the new server.app?"
AFAIK Server Admin is not involved with APNS.
"Did you just bind Lion Server too Snow Leopard Server, connect to another OD, or replica?"
This was on a publicly accessible server that was its own OD Master. Provided things are configured correctly I can't see why it can't work with an environment that's behind NAT.
"What do I setup after this?"
Apart from making sure DNS is configured properly as well as the tip regarding trusted certificates I can't think of anything else? From what I've seen MDM in Lion Server is very good and what's more quick on the devices I tested. I only tested IOS devices and testing was done 'over the air.' You can still use the ICPU assuming you kept a copy of the download?
HTH?
Tony

Tiger PPC clients with Snow Leopard Server

I installed Snow Leopard Server (10.6.4) on an XServe.
DNS - AFS - DHCP are set up correctly and have been checked several times.
Clients have an AFP automount for network home directory. This share point is set up correctly as well and has been checked by Server's gurus.
Everything is fine for Leopard clients but when it comes to connect to the Server with Tiger clients (PPC 10.4.11) something strange happens :
- the first connection is correct and the home directory mounts normally
- when the user disconnects and tries to connect a second time the folder home directory is not mounted and therefore the user can't have access to his/her home
- although it's possible to mount the folder home directory using the "Connect to server…" command and then choose the user's home directory folder this isn't very handy with young students
I have done extensive researches on Apple's documentation and on the forums but nobody seems to mention such a problem.
Any idea what's wrong ? Already encountered the same issue ?
Any help would be appreciate

We have reported an automount bug which "may" be related to your problem to Apple. Our symptoms occurred in Leopard 10.5.8 and also in Snow Leopard 10.6.2 and resulted in user's seeing a message "You are unable to log in to the user account <account> at this time." This was due to an apparent problem in Mac OS X when reusing a share via automount.
In our case we found that the period of time during which login is denied can be reduced by editing the file /etc/autofs.conf on the Mac and reducing the value of AUTOMOUNT_TIMEOUT.
Hope this helps.

Snow Leopard Server AFP Performance

We have a number of xserves in our school district running 10.5 Leopard Server for Network Home Directories. Performance in the past has often been a major issue. CPU spikes on the servers often slowed things down dramatically.
Recently we upgraded 2 of our servers that had been running poorly to Snow Leopard Server.
What a difference.
CPU average is now BELOW 20%... and I have only seen a handful of spikes... but none of them over say 60% Total CPU utilization.
Anyone else see this dramatic of a difference? Since this played out in 2 of our buildings the same way... we are thinking that something on Snow Leopard Server is dramatically better.
I have since actually loaded even more of our users from 10.5 Servers to a Snow Leopard server and still have not seen a performance issue. Are we crazy lucky.. or are others seeing this as well?

Hi
Everywhere I have installed 10.5 server, they performed bad. Actually the CPU was working overtime.
This has happend on 2 intel Xservers and an old Dual G4 1.25Ghz server. The G4 performed much much better with 10.4 server.
So if you have an old powerPC server, use 10.4 server instead of 10.5

Ultra 320 SCSI card with Snow Leopard Server?

First off, sorry if this is the wrong place for a thread on Snow Leopard server.
I have an older Intel Xserve (xserve1,1) with the Apple-branded Ultra320 SCSI PCI-X card. This isn't a third-party card, this is the one from the Apple Store.
So, are these confirmed to continue to work under 10.6? My server runs 10.4 (I'm skipping 10.5).
Thanks!

Hi
A Beta version is exactly just that. No-one apart from Apple knows for certain what the release version will support. Installing a Beta version of anything on a Production Server would not be a good idea in my view. Although one could risk it if a fully working bootable clone of the current Server was done first prior to installing the Beta (or an update for that matter). Perhaps it's just my cautious nature but I personally would not risk it.
I've been part of the AppleSeed program for 10.6 Server and Client from the outset and am testing both on my laptop.
Tony

Virtualization of snow leopard server on a xserv

Similar Messages

Maybe you are looking for