Looks like it's removed in the build of 10.8 Server. I've checked if it's available via CLI, but serveradmin doesn't know this bundle identifier which tells us that indeed, DHCPD doesn't exist. I think it's highly questionable to exclude DHCP from OS X Server, while other outdated services return, such as FTP, which is unsecure and obsolete. Maybe Apple adds DHCPD in 10.8.x simply because the integration into the new server app wasn't ready.
I am holding back the upgrade until it becomes clear if DHCP Server is going to exists or not. It is crazy to remove DHCP especially when the addition options/settings are not available in AirPort Extreme and Express, and also in SMB environment, it may be necessary to have it on OS X Server than on network devices.
This does seem like a rather large oversite on Apple's part.
Doesn't look like Apple will be adding Server Admin anytime soon. Upsetting, considering if you use the built-in help in Server.app it'll direct you to put a check in the DHCP service from within Server Admin...
There's this doc on Apple.com:
It says this, rather oblique, statement:
The DHCP service is no longer managed as a separate service in OS X Server. DHCP is used by the NetInstall service to provide startup information to NetInstall and NetBoot clients. It can also used by Internet Sharing (in the Sharing pane of System Preferences) to provide addresses to clients sharing the server's internet connection. Only one of these two services can be used at one time.
If you enabled NAT and DHCP in Server Admin in Lion Server, your configuration will not be preserved when you upgrade to OS X Server (Mountain Lion). You can restore the default NAT and DHCP configuration by disabling then enabling Internet Sharing in System Preferences.
If you enabled DHCP (only) in Lion Server, or you enabled DHCP in Mac OS X Server v10.6, your configuration will be preserved and remain active when you upgrade to OS X Server (Mountain Lion).
Also notice that the Firewall 'service' is gone. They are also deprecating ipfw. So your firewall rules that you already setup remain in place after the upgrade, but you have to use the command-line to edit them:
The Firewall service is no longer managed by OS X Server. Existing Firewall rules remain active after upgrade, but any further firewall configuration must be performed on the command line. For more information, see this article.
I trolled around the internet, and found this useful sounding tool:
So the question really becomes, with all the manual work now required to 'upgrade' to ML Server, why not just go with a Linux Server and do it all manually? The utility of OS X Server has become marginalized.
This is from the OS X Server: Advanced Administration -
If you don’t have a DHCP server, you can set up OS X Server’s DHCP service. For information, see this help topic: DHCP setup overview.
Start or stop DHCP service
You start DHCP service to provide IP addresses to users. You must have at least one subnet created and enabled.
- Open Server Admin and connect to the server.
- Click the triangle at the left of the server.The list of services appears.
- From the expanded Servers list, select DHCP.
- Click the Start DHCP or the Stop Now button (below the Servers list).If you start DHCP and the Firewall service is running, a warning appears asking you to verify that all ports used by DHCP are open. Click OK.
The service runs until you stop it. It restarts when your server is restarted.
On wow. Glad I stumbled across this. The inability to easily manage my DNS is a show stopper. Yes, I could "manually" edit bootpd.plist in the terminal - doesn't scare me at all. But considering the wrench time I've spent in terminal with Lion, and now this "one more thing", I might as well go with a Linux box and be done with it.
Someone who bought ML Server might want to do a review and note this. You can't write a review until you actually purchase the app - which I won't be anytime soon.
Well, then my feedback is "very disappointed". I was looking forward to ML Server fixing some of the bugs we experienced in Lion Server and the new Profile Manager. No I've got two schools that are totally Mac-based with no way to upgrade them until we bring in a separate DHCP solution unless Apple gets their act together and fixes this pronto. I can see a small business getting away with running their DHCP through an Airport Extreme, but if Apple is serious about marketing their server to medium businesses as well, they're going to need to do better.
jgrunewald - spot on really.
Apple have made a big error here, turning a business Server into a toy.
I now have DHCP server running on a Microsoft Windows server - so they have just lost an important Apple infrasturcture server, and had it replaced with a Microsoft server.
I am very dissapointed with Apple for this change and the lack of clarity in the documentation.
Our ony hope is that Apple or a developer creates a DHCP server application.