- #OS X SERVER 10.7 MAC OS X#
- #OS X SERVER 10.7 INSTALL#
- #OS X SERVER 10.7 UPDATE#
- #OS X SERVER 10.7 TRIAL#
- #OS X SERVER 10.7 DOWNLOAD#
Create and edit the config and startup files in these locations:/opt/local/etc/samba3/smb.confThis needs to be customized for your specific circumstances.
#OS X SERVER 10.7 INSTALL#
Install samba3 (in Terminal type "sudo port install samba3")ĥ.
#OS X SERVER 10.7 DOWNLOAD#
Download XCode Command Line Tools (in Preferences of XCode - requires Developer ID)ģ.
#OS X SERVER 10.7 MAC OS X#
Steps to install and configure samba3 replacement for Apple Mac OS X Server 10.7.x SMB services.ġ.
#OS X SERVER 10.7 UPDATE#
Please feel free to add or update in the comments. There are likely some flaws, and it is probably missing some details and options. In hopes that I can give someone a head start for doing this if they need to, I've cobbled together a recipe from various sources. Unfortunately setup isn't well documented, takes a while, and has no GUI tool (SharePoints I miss you!). I have found that replacing the Apple supplied services with the open source Samba version (dropped by Apple in Mac OS X Lion for apparent licensing issues) has solved these problems, and provided faster performance. All of these were working fine with Mac OS X Server 10.5.8 when a string of hardware failures required replacement with the current version, which is working well for the Mac OS X clients. These problems were supposedly solved in 10.7.3, but my particular issues seem to still be there in several cases (Windows XP name browsing not working, Guest access not working, performance issues, dropped connections), and may be related to the Windows XP (versus Windows Vista/7) clients I'm dealing with. the thing is that this is the first time that I've had to do seriously low-level shit (building a large xserve infrastructure with customized management and deployment tools) and it's like running into a concrete wall headfirst every time a new task comes down the pipe.I have had nothing but trouble with SMB (Windows Sharing) services in Mac OS X Server 10.7. Typically I'm a linux engineer, but I've been OSX on the desktop since the developer previews and the server I've had running at home for a while and I've done contract server set up on versions going back to jaguar. hdiutil and networksetup are 2 prime examples.Īnother thing I forgot to bring up is ipmitool which mostly works unless you try to do serial-over-lan (sol) connections it's completely unusable and you have to go to sourceforge and build your own ipmitool to do that stuff. In many cases, apple has provided their own tools that completely replace the standard toolset.
#OS X SERVER 10.7 TRIAL#
The only way I was able to figure out which gets used where is by trial and error. the user-specified one ("Ethernet 2") and the bsd name ("en1"), but the docs call them both the servicename. There's no consistency in the docs about what they mean by "Service Name" which is what they call the "interface." However, there are 2 names for the interface. `networksetup` in the instance of the LOM and the network port bonding. Who knows whether they'll continue to support ALL of the non-home user features of server like OpenDirectory. Now, they're bundling OSX Server into OSX Lion. and now, 10.6.6 doesn't properly image using System Image Utility ()
You can't configure which port to use for management from the CLI (the docs say you can, but it doesn't work), it renames your interface when you bond network interfaces by appending " Configuration" to the name, which doesn't happen in the gui. I've been running into issues with their commandline admin utilities -they don't give access to everything that you can do with the GUI.
The xserves weren't even that great, but they were the right form factor.Īpple's been seriously fucking up with regard to the enterprise lately. MacMinis are not suitable for this as they don't have enough CPU/RAM. MacPros are not an option as they are not enterprise ready (single PSU, no management port, they're HUGE and must be de-"racked" in order to swap drives, etc). I don't know how apple expects large content producers to encode high-volumes of videos for them without the xserves. Apple has no real interest in the enterprise market.Ĭontent providers for apple MUST provide video files in Apple ProRes fileformat which is ONLY able to be encoded using apple's tools which only run in OSX.