It probably would have been faster and easier from the command line – but I’m sticking to the interface so far. I decided to use the wizard to change the name of the current server to MAIN.local and set the network interface to these basic details:Įvery time I applied something, that process took too way to long. This will configure Windows XP and any other clients that connect. The first thing I wanted to do with my small example network of Lion (as the server) and Windows XP (as the client) was to setup a basic static IP on the server and run a DHCP (Dynamic Host Configuration Protocol) server on the network.
#Apple server admin tools install
Just install the app and server loads with no issues. Setting up the Server itself couldn’t really be easier. The hardware in this example is just an older Macbook on an enclosed network of a few Windows machines. This server is installed and simply just runs on top of Lion just like any other application you install on a Mac. What I’m using in this case is the Mac Server that is currently available in the App Store for Lion at a price of $49.95. Summary: I take a closer look at Apple’s OS X Server (running on Lion) as it serves data to Microsoft Windows computers on a network. Choosing this sort of solution for an office of OS X machines may be a no-brainer, but, what if you wanted to run a network of Windows computers on this server? Would it stack up well to what Microsoft offers? Does it offer the kinds of things you might expect from a Windows Server? Let’s take a look. In the case of Apple’s Server offering for OS X Lion, this simplicity is never more apparent.
It seems more and more that the main driving forces in the Apple world are focused squarely on simplicity.
0 kommentar(er)
