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.
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.
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.
The second option is to deny only those computers in the list below and allow all others. It would be easy to select the second option, however, Lion Server has a bug that prevents you from selecting Deny Only if the list is empty. If you simply select it and save, it reverts to the default allow only option.
To get around this bug, enter in a MAC address of 00:00:00:00:00:00 and then select the Deny Only option. Save the changes and now all of your computers should be able to boot to any images you have.
Note: you'll have to make this change for every image.
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.
To get this working add the following line to the /etc/apache2/httpd.conf file and then restart the web service.
Restarting the web service can be done in the Terminal using:
sudo serveradmin stop web
sudo serveradmin start web
Now you can add virtual hosts through the Server app.
Multiple web servers within a LAN accessed from one WAN address.
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 whatever configuration you are using.
Set up a NAT rule on your router/modem to point port 80 through to, for example, 10.10.10.200 (or the address of the primary apache service that will redirect domains to their correct machine):
first.domain.com = 10.10.10.200
second.domain.com = 10.10.10.201
third.domain.com = 10.10.10.202
DNS on the primary machine should be set up as follows:
ZONE - domain.com
machine record server1.domain.com. points to 10.10.10.200
machine record server2.domain.com. points to 10.10.10.201
machine record server3.domain.com. points to 10.10.10.202
alias record first.domain.com. points to server1.domain.com.
alias record second.domain.com. points to server2.domain.com.
alias record third.domain.com point to server2.domain.com.
External DNS needs to be set up that points first.domain.com, second.domain.com and third.domain.com to your external IP address where your web server is located such as 210.55.102.xx (remember this can take up to 48 hours to become live).
Once this is done you can start adding the .conf files to the /etc/apache2/sites folder to do the redirecting.
You can name the files as you like so long as they have the .conf extension.
1st File I will call 0000_any_80_first.domain.com.conf it needs the following in it to do the redirect to the correct machine:
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.
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.
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.
Log in to an administrative user's account on the server and open the Terminal application located in /Applications/Utilities/.
Type the following command to change to the directory containing the settings for the iCal service: cd /private/etc/caldavd
Make a copy of the preference file. You will be asked for the administrative user's password after entering this line: sudo caldavd.plist caldavd.plist.backup
Use the nano editor to edit the preference file: sudo nano caldavd.plist
You can use the arrow keys to navigate around the contents of the preference file. First, enable Basic authentication. Go past the line that reads <key>Authentication</key>, past <key>Basic</key>, stop at <key>Enabled</key> and change <false/> to <true/> on the next line.
Turn off Digest authentication by going past <key>Digest</key> and stop at <key>Enabled</key> and change <false/> to <true/> on the next line.
Press Ctrl+X to exit the editor, press Y to save changes, and press the Enter key to confirm the file name.
In Server Admin, stop the iCal service and start it again.
If you need to revert your changes. Issue the following command in the Terminal application:
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).
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.
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.
By default the software downloaded from Apple’s servers necessary for the Software Update service is located at /private/var/db/swupd. When excluding this directory using the Time Machine preference pane the path is changed to /var/db/swupd (/var being a symbolic link to /private/var) and the data is still backed up.
[crarko adds: This is for Snow Leopard Server only.]
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.
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.
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.
[robg adds: I have reproduced most, but not all, of the linked page in the remainder of this hint, just in case the original site vanishes. However, I suggest you read it on the linked site if possible, because (a) it includes screenshots and (b) the information may be updated at some point in the future.]
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.
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.
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 sense to the IP specialists, but I almost think this is a bug with the Dual Band implementation.
[robg adds: I can't confirm this one, but I'd be interested in comments from others using Server and Dual Band AirPort to see if this is a general issue or not.]