Snow Leopard Server Question

Does anyone know if I can use Snow Leopard Server with Windows clients? I would like to use it for backup of user folders and for a Wiki.

Does anyone know if I can use Snow Leopard Server with Windows clients?
Of course you can.

Similar Messages

Transfer Snow Leopard to Snow Leopard server question..

Just wondering, if I use TimeMachine backup(Snow Leopard), and trandfer system to Snow Leopard server, is it working? My point is according to my understanding, Snow Leopard server doesn't have iLife. what will happen with my iPhoto iMove,etc...after transfering...
Thanks

hi taylor,
Your photos, music, videos are all kept in your 'home folder.' You can move your home folder from your old computer (or time machine backup drive) using migration assistant. The only thing you need to check is 'user accounts.'
Migrating the home folder from the old computer would be faster then using the time machine backup.
You will also need to install ilife, you would want to install ilife from an ilife install disk.
What are you running server on? usually a servers is not used as your work computer. It's usually a separate computer dictated to sharing resources.
it's also important to note time machine dose not back up many of the services you can host on server.

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.

Moving accounts from Snow Leopard Macs to Mac mini with Snow Leopard Server

I got my brand spanking new Mac mini today with Snow Leopard Server! So far, we (at home) were managing our accounts on individual iMacs and a MacBook Pro. While I will be getting into the innards of account migration, management etc. I thought I'd post a quick question here; Currently I have an iMac with three user accounts on it (wife and two kids). I also have my own personal MacBook Pro with my account (the only Admin account) on it. We'll soon be getting another iMac for our daughter (who currently has an account on the existing iMac). My idea in getting the Mac mini was to move to and centrally manage all the user accounts in the household on the Mac mini server. What is the best way to accomplish this? What is the best way to move the existing accounts on to the server?
Additionally, I'll be looking into connecting the two stationary iMacs with Powerline Ethernet (where one runs Ethernet over existing electrical wires in the walls). My other option would be to rely on wireless network (I don't think this would be a good idea for if I am going to be placing the user accounts on the server and there needs to be a constant on, reliable connection between the server and the client computers as they will be talking to each other a lot!). Any thoughts on Powerline? (I am not looking forward to installing Ethernet cabling behind walls :o))
What say the wise men of Mactopia?!
Thanks,
Kenneth.
P.S. I had earlier accidentally posted this in the corresponding section of Mac OS X instead of the Mac OS X Server forum.

Ok so the esiest way to explain this is to tell you what i just went through.
I have 3 user accounts. All the accounts are network Users meaning that there home folder are kept on the server. I was having a problem with Time Machine giving me error 41 and error 11. After scratching my head for 2 days I ended up copying (Drag-n-Drop) the Home Folders to an External Hard Drive. I then proceeded to erase both of the internal hard drives on the mac mini and did a fresh local install of the Server OS.
Everything was fine at that point. Now this is where Snow Leopard stopped being nice.
I went and Created the user account again using WGM. I let WGW create the home folder and the 9 folder inside. I made sure the short names were the same and the passwords were the same as they were previously.
However, once i Copied files from the external drive to the home folders the permissions copied as well, Which i guess should be expected. So now at this point apparently the UID's of the newly created users wasn't the same as they were before the clean install. I have multiple instances of root listed in the ACL for several folders and also had several instances of System listed sporadically.
Now, This isn't to say that you can't drag n drop because now That I have it all squared away and everything is now working ok, I would probably still drag n drop the home folder off to an external disk, but only because I now know what to do to clean things up.
if you drag and drop be sure to use the CHOWN command and theCHMOD commands afterwards. Take a look at this MacFixIt article: http://reviews.cnet.com/8301-13727_7-20013630-263.html?tag=mncol;title
If you copy your local imac users to the home directory on the server you may want to follow the steps on the URL I gave plus you will most likely also have to do the following. In a nutshell you are going to use the chmod command to strip all the ACL Permissions then you are going to use the chown command to re-specify the correct owner and the correct permissions for the network user.
!) Go into ServerAdmin and click on Sharing
2) Go to the users folder you are using and select the user you are going to work with.
3) Click on the Permissions option
4) click on the +sign at the bottom (this will open the users & groups list to the right)
5) Drag the current user from the users list to the owner permissions line under posix section
5a) Click Save
6) Click on the Gear button at the bottom
7) Check the box for Owner Name and Owner Permissions.
8) Uncheck the box for Access Control List then click ok
Once you've gone through that rigmarole you can go back into ServerAdmin and fix the permissions for public and Sites folder which should only take a minute or so.
So the moral of this story and as I found out when i ended up calling Enterprise support is that the act of dragging and dropping user home directories from one server to another, or as in your case, from a local machine to a the server isn't anything that apple recommends or supports. you might want to read through the man pages for "Ditto" or so apple tells me, but honestly now that you know, the steps above aren't all that bad. It's true Knowing IS half the battle!
have Fun!
P.S. FWIW If you run into problems and have to call Enterprise Support be prepared for them to tell you to refer to the user Guides. So reading those would be to your advantage even though they aren't the easiest things to understand unlike apple's consumer products user guides

Lion server or Snow Leopard Server?

From a quick check of postings here, my question of whether to use Lion Server or Snow Leopard server on a Mac Mini for a small office, looks to be "stay away from Lion server" Snow Leopard server just works and is easier to support.
Most of these posts are from 2011, has anything changed where someone can say Lion is now a much better server choice now than considering Snow Leopard Server?
It seems that most posters feel Lion server is a real step backwards, is this the case?
Thanks in advance - Lewis

Which services have been removed or depreicated?
You have to bear in mind that 'removed' or 'deprecated' only really means 'no longer bundled and supported by Apple'. Just because Mac OS X Lion Server doesn't ship with a foobar server that doesn't mean you can't download and install your own foobar server. It just won't be integrated into the Server Admin apps.
For example, Lion Server no longer ships MySQL Server. So download and install your own copy. It's not like the GUI apps gave you any control over the MySQL anyway, other than starting it up and controlling the network ports.
Likewise for print server. Some of the advanced print features such as quotas have been removed from the GUI, but you can implement them yourself.
Likewise with QuickTime Streaming Server, where the functionality is little more than a web service.
What features that have been enhanced?
Lion Server has simplified the setup of a server for small workgroups with simple requirements. If that's you then the whole experience may be enhanced since you're not swamped with a slew of options that you don't understand, or need.
I think a lot of people were also stymied by Snow Leopard Server because they expected the GUI apps to cover all the options, which was never the case.
So my original point stands. There is pretty much nothing you cannot do in Lion Server than you could do in Snow Leopard Server, it's just that it might not be supported by the GUI. Most serious server admins eschew Server Admin.app anyway since even Snow Leopard Server's admin app doesn't cover all the capabilities of some of the services, so you end up driving it via the command line anyway.

How do I upgrade Snow Leopard Server to Mountain Lion (client)?

I have a Mac Mini Server edition (2010) with Snow Leopard Server (10.6.8) pre-installed. I don't like the interface of Server edition because 1) I don't need the server functions and 2) I prefer client OS's easier (less powerful I know) interface to do sharing, logging in, configuring.... etc.
(I know I should've bought the non-server version with a DVD drive but I can't take it back now.)
My question is, what's the easiest way of changing it to a 'client OS', preferably to the latest Mountain Lion? From forum posts it seems downgrading from 'server' to 'client' will definitely require a fresh install. That's fine. I can move all my personal files to the second HDD in the Mini and do a fresh install of OS on the first HDD.
I can see 'Mountain Lion' upgrade in the App Store, but it doesn't say if it's server or client. I am assuming it's a server upgrade?? What will happen if I purchase it for £13.99 in App Store? Or is there an alternative way?
I have a USB Apple optical drive. I have a USB thumbdrive too for storing the OS image if required. Thank you. Any tips will be appreciated.

Not_So wrote:
I went to the AppStore and as I was running Snow Leopard Server it prompted me to purchase Lion Server which I didn't want.
Luckily, I wasn't asked to purchase the 'Server' when I upgraded from SLS to Mountain Lion via the AppStore. I think your particular problem was mentioned in some other posts where the upgrade path to Lion became an infinite loop (hmmm... ). But that's all in the past now. Glad it all worked.

Using ms office 2008 for mac home & student edition with snow leopard serv

Hi all,
I have a very particular question.
I have a new small business starting up and we want to make full use of leopard and snow leopard server in our infrastructure. We also want to use os x for all our client machines.
We want to use ms office 2008 for mac as our main offfice software but i believe we don't need all the uses or festures of the business edtion and i need to seek good advice and clarity on this.
We won't ever use any microsoft exchange servers but instead willl use the apple mail servers and all the other apple server services.
My question is, based on the fact that we will have an all apple mac os x backend and client frontend but want to use the ms office for mac as our business software, and also based on the fact that we wont use the "Build your Brand clip art, Build your skills by lynda.com, the Remote Desktop for mac 2, the Microsoft Exchange Server Support and the Microsoft Windows sharepoint services support, do we really need to go for the business edition? Can we not just use the home and student edition and get the same functionality using everything else apart form what we listed as we wont need these?
The other question is, the Entourage 2008, Web services Edition, will this work with an apple backend instead of ms exchange server?
Kind regards and thanks for your wise advice,
Neil Watson

Thanks, Kurt--I understand now.
One reason I was alarmed was that evidently when the tech installed Office 2008, something went awry with either the key installer or the key code, because when I finished the first two updates (12.1 and 12.2), I tried to open Entourage to see if the problem I'd been having was resolved. Instead of opening, Office gave me a message that my product key was invalid! I did find the product key, and called the tech, who will come by to see what's wrong (he's an honest guy, so I'm sure it's a legitimate error of some kind, not a pirated copy). But the thought of installing two pages of updates and maybe running into the same glitch every time made me blanch. So I'm glad to know that Microsoft is still doing Service Packs for 2008!

DNS Configured-Best Practice on Snow Leopard Server?

How many of you configure and run DNS on your Snow Leopard server as a best practice, even if that server is not the primary DNS server on the network, and you are not using Open Directory? Is configuring DNS a best practice if your server has a FQDN name? Does it run better?
I had an Apple engineer once tell me (this is back in the Tiger Server days) that the servers just run better when DNS is configured correctly, even if all you are doing is file sharing. Is there some truth to that?
I'd like to hear from you either way, whether you're an advocate for configuring DNS in such an environment, or if you're not.
Thanks.

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Installing Snow Leopard server (10.6.0) over Snow Leopard 10.6.2

I need to convert my Mac Pro to run Snow Leopard Server. I have the DVDs.
The installer tells me I cannot perform the upgrade because the OS on the machine
is more recent than the one on the DVD. I guess I have to downgrade to Snow Leopard 10.6.0
before I can install the server OS. I do not want to reformat my hard disk, because I want to
keep the data there. How can I accomplish what I want to do.

server questions should be asked in the server forum
http://discussions.apple.com/category.jspa?categoryID=264
assuming your mac pro did not come with 10.6.2 preinstalled you can reinstall 10.6.0 on it in the usual manner. boot from the snow leopard 10.6.0 install dvd (insert the dvd, reboot and hold "c" at the chime). and follow the instructions. this will preserve your data and applications. but as with any system install you should have a full backup before doing it.

Problems deleting pdf's generated from files off of Snow Leopard Server

The small design studio I work at has just upgraded from G5's running 10.4 Tiger, working off Tiger Server, to new iMacs running 10.6 Snow Leopard and a Mac Mini Server, on Snow Leopard Server.
Normal working practice is to open files off the server across the network, making changes and saving them back down. Most of the time, a pdf will be generated from the file to send to the client when copy changes have been made, then saving down the pdf file to the iMac to email to the client.
The issue is now that when the pdf has been emailed, attempting to delete it brings up a warning window that 'You do not have sufficient accesses privileges to delete the file' and this then has to be done by selecting secure empty trash.
We are all registered users on the Mac Mini Server and this was not an issue we had when using Tiger.
Could anyone suggest any setting changes that would be required to get around this issue?
As a note, all the work files were originally on a older G4 being used as a sever and were copied to the new Mac Mini Server, that was set up as a new machine and was not done via transfer files.
Thanks
Ben

Hello Ben,
I'm very sorry, but this is not the correct forum in which to post your question! Universal Access is the facility for ensuring that all Mac users can benefit fully from their machines, regardless of disability.
Try Snow Leopard Server—Installation, Setup and Migration instead!
Cheers,
Archie

Making Snow Leopard Server services accessible through Time Capsule

Sorry, this will be a fairly long explanation. I think this is the right forum but the question kind of spans several component elements.
During the setup of Snow Leopard Server I let it configure the Time Capsule for services that it is providing, which I want to make available to both the local network and to computers coming in from the Internet. However, there seem to be some conflicts between Time Capsule ports and Snow Leopard ones.
First my set-up: I have Verizon FIOS and have set up my Actiontech Router into bridge mode to the Time Capsule so that the Time Capsule grabs the public IP address. The Snow Leopard Server has a dedicated private IP from the Time Capsule through the DHCP reservation. I have a dynamic DNS setup which consistently points to the public IP address assigned to the Time Capsule. After starting services on Snow Leopard Server, I can see the port mappings created on the Time Capsule by the server allocated to the server's dedicated private IP address. However, the File Sharing (AFP, SMB) entry can't be enabled because the ports used for those services conflict with the ports opened by the Time Capsule to enable backups from client Time Machines (TCP Ports 548, 139). Therefore, any external access to those ports are going to the Time Capsule and not routed to the Snow Leopard Server.
Two questions:
1. Should I map the DNS hostname to the Time Capsule on the Hostnames screen on AirPort utility? While this will enable remote access to the Time Capsule (so that if my client computers are outside coming from the Internet), will this mess up remote access to the Snow Leopard Server?
2. How do I get around the problem of the port conflicts between what Time Machine needs to get to the Time Capsule for backups versus enabling the ports for AFP and SMB on the server?

I actually found an Apple support tip and am posting it here to answer the question:
http://support.apple.com/kb/TS2963
Bottom line: you can't have both devices doing file sharing unless you set up VPN access.

Nslookup Snow Leopard Server DNS problems

I have a mac mini that I'm trying to turn into a snow leopard server. Attached to the mac mini I have three external hard drives which act as back ups to our mac book pro laptops. I have installed the server software and downloaded all the updates and I can see the drives on the server and I can acess the external drives and backup to them with out a problem. The issue that I have is that when I run nslookup I get an error message which tells me that it can't find my name and that I need to rerun so software commands.
I'm also unable to run either dns or podcast producer which was the main reason for buying the server software. I have a static ip address and believe I have configured everything correctly but I just can't seem to sort out the DNS and problems.
Any thoughts - thanks
Russell

This is the Discussions > Mac OS X v10.6 Snow Leopard > Installation and Setup forum. Your questions involve Mac OS Server, which is a different OS product. Thus, you will get better results posting to the Apple - Support - Discussions - Mac OS X Server forums.

Snow Leopard Server and FCServer

Hi.
I'm running FCServer on an iMac, and I'm currently looking for the best solution for giving co-workers outside of our office network remote access to our FCS database. The main purpose for this is for remote users to screen and download episode segments and movies from our database.
I was initially thinking VPN would be the only solution, but then I saw Snow Leopard Server has 'Mobile Access Server' built right into the OS, which appears designed to help users avoid having to use a VPN.
Before I go out and buy SLS for the company, I want to be sure it will work. Am I correct that Snow Leopard Server, and the built-in Mobile Access Server, will allow users outside of our network remote access to our FCSrvr database?
Any help would be greatly appreciated. And if this question is better suited for a different forum please let me know as well.
Thank you!

Hmmm... Thanks for the replies.
I posted this question in the OS X Server forum and got this response:
+"I haven't used Final Cut Server, but I'm pretty sure the Mobile Access Server wouldn't work with it. MAS works with plain HTTP, and the Address Book, iCal, and Mail (SMTP and IMAP) services; but FCServer is only partly HTTP-based, and I don't think even the HTTP part will work due to how MAS authenticates HTTP clients. Also, you might be thinking about using MAS as the same computer as FCServer, and it won't work that way -- MAS needs to be on a separate (internet-facing) computer from the actual origin server (which should be firewalled from the internet).+
+I'd go back to thinking about VPN... "+
Can anyone offer any more insight into this for me? I'm just an audio/video post-production guy, so this is all a little outside of my training.
Any help would be greatly appreciated. Thanks!

Configure DNS on Snow Leopard Server for Web Hosting

Hi Everyone,
I put together an article on my blog about Snow Leopard DNS setup for web hosting. http://www.mkahn.com/?p=279
I'll be revising it over the next few weeks to make it more informative based around feedback. Let me know if you have any questions or trouble setting up DNS on Snow Leopard Server for web hosting.

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

Creating a versatile DNS and redirection service on Snow Leopard Server

For the few of us who use Snow Leopard Server as a main DNS for our small network, the following is a workflow that I would like to share with the board for creating redirection services to not just sites found on the locally hosted apache but also external sites.
+IF you are adding a second domain name, the reverse domain lookup will not appear and you will need to add a Machine/A record with the fully qualified domain "domainname.com." (don't forget the . at the end) into the new zone and it will point to the "server" Machine/A record ip address.+
*DNS Portion* : (ServerAdmin > DNS > Zones >
Add Zone > Primary > Create a fully Qualified Domain name and dns "server" in the Machine / A Record
Create the (add Record > Alias/ CNAME) subdomain pointing to the server.domainname.com e.g. (library)
*Web / Apache Portion :*
Create a new site (ServerAdmin > Web > Sites > Plus button)
With General > host name exactly as spelled in above subdomain in full (library.domainname.com)
Select Web Folder where the site is hosted
If you are creating a redirection, create a folder on the server, add an index.php (with the script below)
Add Alias with the same subdomain as number 2
_PHP script :_
<?php
$location = "http://example.net";
header("Location: ".$location, "301 Moved Permanently");
?>
// Edit the "http://example.net" to which ever e.g. "http://apple.com"
_Alternatively you can also mask the page with :_
<html>
<head>
<title>Same Title As Your Homepage</title>
<script type="text/javascript">
function changeTitle()
if (top.frames['main'].document.title)
top.document.title=top.frames['main'].document.title;
</script>
</head>
<frameset>
<frame name="main" src="http://actual-url.anotherhost.com/page.html"scrolling="auto" target="main" ONLOAD="changeTitle();">
<noframes>
<body>
Place a suitable message here for people with browsers that can't read frames.
</body>
</noframes>
</frameset>
</html>

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Snow Leopard Server Question

Similar Messages

Maybe you are looking for