<?xml version="1.0" encoding="iso-8859-1"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>macosxhints.com OS X Server tips</title>
<link>http://hints.macworld.com/index.php?topic=server</link>
<description>Tips and tricks for working with OS X Server, from macosxhints.com</description>
<managingEditor>webteam@macosxhints.com</managingEditor>
<webMaster>webteam@macosxhints.com</webMaster>
<copyright>Copyright 2011 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Wed, 14 Dec 2011 07:30:02 -0800</pubDate>
<language>en-gb</language>
<atom:link href="http://hints.macworld.com/backend/hintsserver.rss" rel="self" type="application/rss+xml" />
<item>
<title>Cannot boot to NetRestore Image</title>
<link>http://hints.macworld.com/article.php?story=20111213085535590</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20111213085535590</guid>
<pubDate>Wed, 14 Dec 2011 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20111213085535590#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>I ran into a problem recently where I was unable to boot into any of the images I had made from any Mac. I have NetRestore and one NetBoot image, but not one of my Macs could get to it. After many failed attempts, I finally tricked it into letting me boot. Here's how.&lt;br&gt;&lt;br&gt;The problem actually has to do with the way that NetBoot filters computers. It used to be that you could turn filtering on and off, but now, it is not so simple. In the Image Properties window, you have the option to either all model types, or just the ones selected from a given list.&lt;br&gt;&lt;br&gt;However, MAC filtering is different, you can't simply say allow all. The default selection is to allow only only those computers with the matching MAC addresses in the list below and deny others. This is what is preventing computers from being able to boot. And unless you are interested in manually entering in every new MAC address, it is impractical.&lt;br&gt;&lt;br&gt;The second option is to deny only those computers in the lis ...</description>
</item>
<item>
<title>10.7: Virtual Hosts and multiple web servers</title>
<link>http://hints.macworld.com/article.php?story=2011101123595425</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2011101123595425</guid>
<pubDate>Thu, 13 Oct 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2011101123595425#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>After a great deal of searching the net for answers I have pieced together what is needed to do a couple of things I have wanted to do for some time now. The first is to have virtual hosts working nicely on 10.7 Lion Server. The second and related item is to have multiple web servers within a LAN accessible from one WAN address.&lt;br&gt;&lt;br&gt;&lt;b&gt;Virtual Hosts&lt;/b&gt;&lt;br&gt;&lt;br&gt;To get this working add the following line to the &lt;em&gt;/etc/apache2/httpd.conf&lt;/em&gt; file and then restart the web service.&lt;br&gt;&lt;br&gt;&lt;tt&gt;NameVirtualHost *:80&lt;/tt&gt;&lt;br&gt;&lt;br&gt;Restarting the web service can be done in the Terminal using:&lt;br&gt;&lt;br&gt;&lt;tt&gt;sudo serveradmin stop web&lt;br&gt;sudo serveradmin start web&lt;/tt&gt;&lt;br&gt;&lt;br&gt;Now you can add virtual hosts through the Server app.&lt;br&gt;&lt;br&gt;&lt;b&gt;Multiple web servers within a LAN accessed from one WAN address.&lt;/b&gt;&lt;br&gt;&lt;br&gt;Set up: The following assumes that you have 3 servers with correctly working DNS and apache services. The 10.10.10.x subnet is used for the examples, change them to w ...</description>
</item>
<item>
<title>10.7: Setting the default timezone for calendars viewed on Wiki Server</title>
<link>http://hints.macworld.com/article.php?story=20110901172926867</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110901172926867</guid>
<pubDate>Thu, 08 Sep 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110901172926867#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>Apple does not seem to have provided a setting to change the default timezone despite the obvious need to be able to do so. This hint is a workaround giving a way of changing the timezone for all users who view the calendar via the web interface.&lt;br&gt;&lt;br&gt;First backup the following file:&lt;br&gt;&lt;br&gt;&lt;em&gt;/usr/share/collabd/coreclient/app/views/projects/calendar.html.erb&lt;/em&gt;&lt;br&gt;&lt;br&gt;You will need root privileges to edit the file; this can be accomplished by:&lt;br&gt;&lt;br&gt;&lt;tt&gt;sudo nano /usr/share/collabd/coreclient/app/views/projects/calendar.html.erb&lt;/tt&gt;&lt;br&gt;&lt;br&gt;Add the following line to the original file below the line &lt;tt&gt;&amp;lt;% content_for(:head) do %&amp;gt;&lt;/tt&gt;:&lt;br&gt;&lt;br&gt;&lt;tt&gt;&amp;lt;meta name=&quot;tzid&quot; content=&quot;Europe/London&quot;&amp;gt;&lt;/tt&gt;&lt;br&gt;&lt;br&gt;Where &quot;Europe/London&quot; is replaced by the desired timezone.&lt;br&gt;&lt;br&gt;The file should now read (in its entirety) ...</description>
</item>
<item>
<title>10.6 Server: Workaround for recurring CalDAV password dialogs on iOS devices</title>
<link>http://hints.macworld.com/article.php?story=20110524024036889</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110524024036889</guid>
<pubDate>Thu, 26 May 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110524024036889#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>Follow these steps to work around an issue that causes recurring password dialogs on iOS devices that are configured to connect to a CalDAV account hosted by Mac OS X Server 10.6.&lt;br&gt;&lt;br&gt;The procedure involves turning off Digest authentication and enabling Basic authentication. Since all passwords will be sent in the clear, make sure that all traffic to the iCal server is encrypted. This can be done either by requiring users to connect via VPN or by using a valid SSL certificate and setting SSL to 'Redirect' in the iCal Service settings in Server Admin. &lt;ul&gt;  &lt;li&gt;    Log in to an administrative user's account on the server and open the Terminal application located in &lt;em&gt;/Applications/Utilities/&lt;/em&gt;.  &lt;/li&gt;  &lt;li&gt;    Type the following command to change to the directory containing the settings for the iCal service:&lt;br&gt;    &lt;tt&gt;cd /private/etc/caldavd&lt;/tt&gt;  &lt;/li&gt;  &lt;li&gt;    Make a copy of the preference file. You will be asked for the administrative user's password after en ...&lt;/li&gt;&lt;/ul&gt;</description>
</item>
<item>
<title>Change iCal Server invitations so they will clear spam assassin</title>
<link>http://hints.macworld.com/article.php?story=20110328134806331</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110328134806331</guid>
<pubDate>Thu, 31 Mar 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110328134806331#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>The default invitations which iCal Server sends may be seen as spam by Spam Assassin (score of 5.8 or so), because of a large picture attachment.&lt;br&gt;&lt;br&gt;The workaround for this I found was to modify the template for the invitation to eliminate the attachment.&lt;br&gt;&lt;br&gt;The templates for iCal Server invitations are located in: &lt;em&gt;/usr/share/caldavd/share/email_templates&lt;/em&gt;.&lt;br&gt;&lt;br&gt;I changed mine so they are straightforward but at least not seen as spam. For example, my invite.html is:&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:120px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;&amp;lt;html&amp;gt;&amp;lt;head&amp;gt;&amp;lt;/head&amp;gt;&amp;lt;body&amp;gt;&amp;lt;p&amp;gt;Event: %(summary)s&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Organizer: %(htmlOrganizer)s&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Location: %(location)s&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Date: %(dateInfo)s %(recurrenceInfo)s&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Time: %(timeInfo)s %(durationInfo)s&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Description: %(desc ...&lt;/pre&gt;&lt;/div&gt;</description>
</item>
<item>
<title>Make event emails sent from 10.6  iCal Server come from actual user</title>
<link>http://hints.macworld.com/article.php?story=2011032813422190</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2011032813422190</guid>
<pubDate>Tue, 29 Mar 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2011032813422190#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>In Server Admin, the iCal settings allow you to specify a single email from which event invitations will come. For a personal calendar though, you really want the email to come from your own email.&lt;br&gt;&lt;br&gt;The script which sends invitations is found at:&lt;br&gt;&lt;br&gt;&lt;em&gt;/usr/share/caldavd/lib/python/twistedcaldav/mail.py&lt;/em&gt;&lt;br&gt;&lt;br&gt;It appears that it tries to find the appropriate email address, but I could not figure out how to make a value ever be present where it was looking.&lt;br&gt;&lt;br&gt;So, I modified the script as shown below.
Change: &lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:120px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt; if organizer.startswith(&quot;mailto:&quot;):  orgEmail = fromAddr = organizer[7:] else:  fromAddr = serverAddress  orgEmail = None cn = calendar.getOrganizerProperty().params().get('CN', (None,))[0]&lt;/pre&gt;&lt;/div&gt;To:  ...</description>
</item>
<item>
<title>10.6 Virtualize machine-specific OS X Server in Fusion</title>
<link>http://hints.macworld.com/article.php?story=20101220034435995</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20101220034435995</guid>
<pubDate>Mon, 20 Dec 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20101220034435995#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;I did all this on a new mid-2010 Mac mini Server (with an external MacBook Air SuperDrive), with OS X Server 10.6.5 (re)installed on the upper drive (*disk1*) and OS X client 10.6.5 (and Fusion, many other apps, etc.) installed on the lower drive (*disk0*): i.e., with the computer used mainly as a client desktop rather than a server; so, virtualizing the server OS might be the most convenient solution, while - if desired - also being able to natively boot into the server (at least as an experiment).&lt;br&gt;&lt;br&gt;So, you want to virtualize a whole hard drive (HD) with OS X Server installed? Or, more simply, if you want to install OS X Server onto an 'ordinary,' file-based Fusion virtual machine (VM), but only have a machine-specific install DVD (which will refuse to install if used to boot the VM), here is what I did.
Part 1: If you want to virtualize a whole dis ...</description>
</item>
<item>
<title>10.6: Exclude Software Update data in Time Machine backups</title>
<link>http://hints.macworld.com/article.php?story=20100524084438338</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100524084438338</guid>
<pubDate>Tue, 25 May 2010 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100524084438338#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Using the Time Machine preference pane, it is not possible to effectively exclude the data for the Software Update service from Time Machine backups on Mac OS X Server 10.6. A method is presented here which will do that.&lt;br&gt;&lt;br&gt;By default the software downloaded from Apple’s servers necessary for the Software Update service is located at &lt;em&gt;/private/var/db/swupd&lt;/em&gt;. When excluding this directory using the Time Machine preference pane the path is changed to &lt;em&gt;/var/db/swupd&lt;/em&gt; (&lt;em&gt;/var&lt;/em&gt; being a symbolic link to &lt;em&gt;/private/var&lt;/em&gt;) and the data is still backed up. [&lt;b&gt;crarko adds:&lt;/b&gt; This is for Snow Leopard Server only.]
To remove the Software Update service data from the backups, follow these steps using an administrative account: &lt;ol&gt;&lt;li&gt;Exclude /private/var/db/swupd or /var/db/swupd in the Time Machine preference pane.&lt;/li&gt;&lt;li&gt;Quit t ...&lt;/li&gt;&lt;/ol&gt;</description>
</item>
<item>
<title>10.6: Stream high-resolution chapter-marked movies</title>
<link>http://hints.macworld.com/article.php?story=20100324045254140</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100324045254140</guid>
<pubDate>Fri, 26 Mar 2010 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100324045254140#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;So here was my problem: I needed to be able to produce high-resolution movies of live screen presentations (PowerPoint as it happens) with audio. And because these presentations were two hours long, people wanted chapter/section marks so they could go directly to the part they were interested in seeing again.&lt;br&gt;&lt;br&gt;We wanted to stream the movies, so that people did not have to download the entire 2GB+ movie. They movies also had to be on a server I could get to, so that we could get the video online quickly.&lt;br&gt;&lt;br&gt;This all proved harder than it sounds, and took me about three weeks to figure out and set up -- it wasn't hard, but it was undocumented and not intuitive. I am providing this information because the online information is either wrong, or it doesn't seem to exist.&lt;br&gt;&lt;br&gt; ...</description>
</item>
<item>
<title>10.6: Avoid a DHCP issue with Dual Band Airport Extreme</title>
<link>http://hints.macworld.com/article.php?story=20100316194851664</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100316194851664</guid>
<pubDate>Thu, 18 Mar 2010 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100316194851664#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;While playing with Snow Leopard Server's various services, I noticed DHCP wasn't working. Actually, it worked at first for my laptop, then it stopped. Then I noticed the iPhones were not able to receive IPs either. I thought it was something with my server, so I drew a network diagram, and it gave me an idea.&lt;br&gt;&lt;br&gt;I have an Internet modem connected to a Netgear router, to which the AirPort Extreme (Dual Band) is connected. My Snow Leopard Server machine is connected via the AirPort, as are all other clients. My drawing showed that when my Server was connected on the 5Ghz side, and the DHCP clients were connected on the 2.4Ghz side, DHCP would not work.&lt;br&gt;&lt;br&gt;I confirmed this by splitting the dual band and connecting server and all clients on the 2.4GHz channel only. Set up this way, DHCP worked great; problem solved! I'm not sure if that makes perfect ...</description>
</item>
<item>
<title>Add Volumes for mount at login directly on OS X Server Mac</title>
<link>http://hints.macworld.com/article.php?story=2010022310494430</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2010022310494430</guid>
<pubDate>Thu, 25 Feb 2010 07:30:02 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=2010022310494430#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>Today I needed to use Workgroup Manager to add a Login Item that Mounts an afp Volume. Apple provides no instructions for doing this while logged in directly on the server; instead this task is done using Workgroup Manager on a client (see &lt;a href=&quot;http://support.apple.com/kb/TA21304&quot;&gt;this Apple support document&lt;/a&gt;). I didn't have my MacBook with me at the time, nor did I want to install the Server Admin Tools on another machine just for this one task.&lt;br&gt;&lt;br&gt;The solution is:&lt;ol&gt;&lt;li&gt;Open Safari and enter the URL in the form of &lt;tt&gt;afp://IP-address-OR-Server-name/Share Point&lt;/tt&gt;&lt;/li&gt;&lt;li&gt;Drag the favicon (next to the URL) onto the Desktop.&lt;/li&gt;&lt;li&gt;Drag the favicon into the System Preferences &amp;raquo; Login &amp;raquo; Items section of Workgroup Manager.&lt;/li&gt;&lt;li&gt;Click Apply Now.&lt;/li&gt;&lt;/ol&gt;Note that you do not need to add &lt;tt&gt;%20&lt;/tt&gt; to any white space when typing the URL in Safari; this will automatically be added when you drag the Favicon to the Desktop. Also, the colon and fo ...</description>
</item>
<item>
<title>10.6 Server: How to get NFS disk serving working properly</title>
<link>http://hints.macworld.com/article.php?story=20100219094419683</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100219094419683</guid>
<pubDate>Tue, 23 Feb 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100219094419683#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;You may be surprised to learn that if you follow the detailed 136 page instructions for setting up an NFS disk server that Apple provides for the OS X server machines, it won't actually work. The problem is the firewall. Unlike the non-server OS, which has an application firewall, the Server OS uses IPFW, which is port-based not application-based.&lt;br&gt;&lt;br&gt;This means every service that takes inbound connections has to have fixed port range assignments so you can tell IPFW which port to open. NFS required the RPC deamon, and by default, RPC takes whatever ports are free at the moment and does not keep them fixed. You need to fix these to specific ports by hand because the GUI won't do it.&lt;br&gt;&lt;br&gt;This can be confusing to diagnose because if you start NFS with the firewall down and then put it up, you find the server continues to work for about 30 minutes, be ...</description>
</item>
<item>
<title>10.6 Server: Set the appropriate Software Update Server</title>
<link>http://hints.macworld.com/article.php?story=20091002190708159</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091002190708159</guid>
<pubDate>Wed, 21 Oct 2009 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091002190708159#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;With Mac OS X Server 10.5 and below, Software Update Server only had one catalog of updates -- thus, you could run a command like this one, and have it point Software Update to your server:
&lt;br&gt;&lt;br&gt;
&lt;tt&gt;defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL &quot;http://Server.local:8088/&quot;&lt;/tt&gt;
&lt;br&gt;&lt;br&gt;
With Mac OS X Server 10.6, Apple has divided the catalog file into three separate catalogs: one for 10.4, one for 10.5, and one for 10.6. Each is a separate URL, and if you set the wrong catalog for the OS, you'll get the (incorrect) message that your software is already up-to-date. Having three separate scripts is a hassle, though, and is prone to error.
&lt;br&gt;&lt;br&gt;
On the &lt;a href=&quot;http://forums.macosxhints.com&quot;&gt;Hints Forums&lt;/a&gt;, users &lt;em&gt;tw&lt;/em&gt; and &lt;em&gt;Hal Itosis&lt;/em&gt; were instrumental in crafting this AppleScript. It checks the OS that you ...</description>
</item>
<item>
<title>Update the Software Update Server without re-downloading</title>
<link>http://hints.macworld.com/article.php?story=2009100210290464</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2009100210290464</guid>
<pubDate>Tue, 20 Oct 2009 07:30:02 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2009100210290464#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>I had the need to update a server that was acting as a Software Update Server. I knew that the machine had the update on it, but was unsure of how to get it to see the locally-hosted update. If you open Terminal and issue this command...

&lt;pre&gt;&lt;code&gt;open /usr/share/swupd/html/index.sucatalog&lt;/code&gt;&lt;/pre&gt;

...then Software Update will launch, looking at the localhost -- no need to re-download the update from Apple.
</description>
</item>
<item>
<title>10.6: Using iCal Group calendars on Snow Leopard Server</title>
<link>http://hints.macworld.com/article.php?story=2009090507094085</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2009090507094085</guid>
<pubDate>Mon, 21 Sep 2009 07:30:02 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2009090507094085#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Snow Leopard's iCal Server changed the location of the Wiki-based calendars, so that &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20080410162942908&quot;&gt;this previous hint&lt;/a&gt; no longer works. Intead of using the path of &lt;tt&gt;/principals/groups/groupname&lt;/tt&gt;, the URL for wiki-based calendars has changed to one of the following:

&lt;pre&gt;&lt;code&gt;https://ical.domain.com:8443/principals/wikis/groupname/
http://ical.domain.com:8008/principals/wikis/groupname/&lt;/code&gt;&lt;/pre&gt;

When you add this in as a URL for an additional account, you can then access this shared calendar, with your changes reflected on the wiki page. You could alternatively create a specific user in workgroup manager to be used as the 'silent' owner of a group calendar, create your calendars, assign delegation to all the real users. But if done in that way, you don't get to see the calendar in the wiki, online.
&lt;br&gt;&lt;br&gt; ...</description>
</item>
<item>
<title>10.5: List service ACLs on Mac OS X 10.5 Server</title>
<link>http://hints.macworld.com/article.php?story=20090710025100899</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090710025100899</guid>
<pubDate>Mon, 20 Jul 2009 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090710025100899#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/105only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Mac OS X lacks a good command line tool for following a Services Access Control List (SACL) tree of users and groups. If you don't want to, or just can't, use the GUI to list users in service ACLs of your Mac OS X server (or managed client), you need to parse the groups/nested groups/users tree one group at a time, using &lt;tt&gt;dscl&lt;/tt&gt;. It's really painful. As an alternative, I've created a script to handle this for sys admins.&lt;br&gt;&lt;br&gt;I won't promise you a killer command line tool with foolproof error and recursion handling, but I still believe I've designed a usable piece of shell script -- even if it looks like it's the worst code I've ever written (which is not true; I've made things way uglier). The source code is too long and messy to be just copy-pasted here; just &lt;a href=&quot;http://www.patpro.net/images/getsacls.sh.gz&quot;&gt;download the getsacls.sh script (4KB)&lt;/a&gt; directly from my mach ...</description>
</item>
<item>
<title>10.5 Server: Force certain folders into managed clients' Docks</title>
<link>http://hints.macworld.com/article.php?story=20090617060513110</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090617060513110</guid>
<pubDate>Wed, 17 Jun 2009 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090617060513110#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/105only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;I have recently discovered a solution to a long-time annoyance of mine with 10.5 server and managed preferences for 10.5/10.4 clients: How to force the Applications and Downloads folders into the Dock.  
&lt;br&gt;&lt;br&gt;
I 'took apart' and examined the &lt;tt&gt;com.apple.dock.plist&lt;/tt&gt; file and found the options for the Applications folder and the Downloads folders. If you simply place these folders into the Workgroup Manager (WGM) area for dock preferences, you end up with a broken downloads folder and an Applications folder that won't show its contents. Instead, when you click on Applications in 10.5, you just get a new window instead of the list of its contents. 
&lt;br&gt;&lt;br&gt;
The secret is to take a &lt;tt&gt;com.apple.dock.plist&lt;/tt&gt; file and take out everything but the entries for Applications and Downloads. Use this file in the Details tab of preferences plists that you can force out -- don't forge ...</description>
</item>
<item>
<title>Upgrade to 10.5 Server without reboot on newest Macs</title>
<link>http://hints.macworld.com/article.php?story=20090305124058230</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090305124058230</guid>
<pubDate>Wed, 11 Mar 2009 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090305124058230#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>This is more observational than hint-like, but it's interesting. This morning we had a customer order a new 2009 Mac mini, and they asked to have it upgraded to Leopard Server.&lt;br&gt;&lt;br&gt;When we put the DVD into the Mac mini slot, we were getting ready to boot from DVD to do the upgrade. However, with this new mini, it no longer requires a reboot. You can install the &lt;em&gt;Leopard Server Install Package&lt;/em&gt; without booting from the DVD. 
</description>
</item>
<item>
<title>Use one Deploy Studio server with images on many servers</title>
<link>http://hints.macworld.com/article.php?story=20090227083540481</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090227083540481</guid>
<pubDate>Tue, 03 Mar 2009 07:30:01 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090227083540481#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>I am jumping on board the &lt;a href=&quot;http://www.deploystudio.com/Home.html&quot;&gt;DeployStudio&lt;/a&gt; train, and with multiple sites to support, I ran into the issue of how to use one master Deploy Studio server, but host the images at each of the sites (especially the WAN locations).
&lt;br&gt;&lt;br&gt;
The solution I came up with was simple. When Deploy Studio wants to mount the images volume (via AFP), I just have a preflight script that mounts the volume based on which location (based on subnet) the computer is being imaged at. For instance, our Deploy Studio is on our fiber network, but our satellite site is on cable. When the computer netboots and DeployStudio Runtime is launched, it connects up to the Deploy Studio server (again, hosted on the fiber network).
&lt;br&gt;&lt;br&gt;
A preflight script will mount the correct AFP mount prior to imaging the computer. We are basing this on our subnets, but your mileage may vary. Hope this helps those other network administrators going through the same struggles ...</description>
</item>
<item>
<title>10.5: Fix cron for LDAP Users in Mac OS X Server 10.5</title>
<link>http://hints.macworld.com/article.php?story=20090119164250363</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090119164250363</guid>
<pubDate>Mon, 26 Jan 2009 07:30:01 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090119164250363#comments</comments>
<dc:subject>OS X Server</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/105only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;To the best I'm able to determine, Mac OS X Server's &lt;tt&gt;cron&lt;/tt&gt; does not recognize &lt;tt&gt;crontabs&lt;/tt&gt; of users who exist in LDAP, nor the flat files (e.g., /etc/passwd). This is because &lt;tt&gt;cron&lt;/tt&gt; starts prior to LDAP, and thus sees the &lt;tt&gt;crontabs&lt;/tt&gt; of such users as &quot;orphans.&quot;  If you log in and re-establish the &lt;tt&gt;crontab&lt;/tt&gt;, all is well ... but a simple reboot shouldn't cause &lt;tt&gt;crontabs&lt;/tt&gt; to become disabled.
&lt;br&gt;&lt;br&gt;
The system cron is a &lt;tt&gt;launchd&lt;/tt&gt; service, and so it's quite difficult to control the order in which it launches. One can make the argument that it's &lt;tt&gt;cron&lt;/tt&gt;'s fault that it doesn't check for LDAP when it starts, but I think that the blame is really Apple's to bear. I spent hours today trying to figure out a graceful way to delay &lt;tt&gt;cron&lt;/tt&gt;'s launch without installing a new &lt;tt&gt;cron&lt;/tt&gt; or hacking things up too badly, all in vain.  
&lt;br&gt; ...</description>
</item>
</channel>
</rss>

