Installing Mavericks is a straight forward process. The following models can be upgraded to Mavericks: iMac: Mid-2007 and up Mac mini: Models from early 2009 and up Mac Pro: Models from 2008 and up MacBook: Late 2008 and up MacBook Air: Models from 2008 and up MacBook Pro: Models from Mid 2007 and up Xserve: Models from early 2009 and up Installing OS X has never been easier. In this article, we’ll look at upgrading a Mac from OS X 10.8 to OS X 10.9 (Mavericks). The first thing you should do is clone your system. The second thing you should do is make sure you have a good backup. The third…
-
-
ARD 3.7
Apple has released the client and server updates for Apple Remote Desktop. Both are now available on the App Store. For official information of the server update, see http://support.apple.com/kb/HT5896?viewlocale=en_US. New features include: Support for OS X Mavericks A shared clipboard which allows automatic copy and paste between local and remote computers Improved support for Mac systems with multiple displays or multiple IP addresses Enhanced multi-observe with gesture support for swiping between screens Output of remote UNIX commands is no longer truncated The client update documentation is at http://support.apple.com/kb/HT5896?viewlocale=en_US&locale=en_US.
-
The Official Apple Mavericks Server 3 Documentation
I’ve written plenty about Mavericks Server 3 here on https://krypted.com/ but way more effort went into the official documentation. There’s lots of nuggets here at: http://help.apple.com/advancedserveradmin/mac/3.0/ Enjoy!
-
Configure the Mail Service in Mavericks Server
Mail is one of the hardest services to manage. Actually, mail is pretty simple in and of itself: there’s protocols people use to access their mail (such as IMAP and POP), protocols used to communicate between mail servers and send mail (SMTP, SMTPS) and then there’s a database of mail and user information. In Mavericks Server, all of these are represented by a single ON button, so it really couldn’t be easier. But then there’s the ecoysystem and the evil spammers. As a systems administrator of a large number of mail servers, I firmly believe that there is a special kind of hell where only spam is served at every…
-
Enable Push Notifications In Mavericks Server
Push Notifications can be used in most every service OS X Mavericks Server (Server 3) can run. Any service that requires Push Notifications will provide the ability to setup APNS during the configuration of the service. But at this point, I usually just set up Push Notifications when I setup a new server. To enable Push Notifications for services, you’ll first need to have a valid AppleID. Once you have an AppleID, open the Server app and then click on the name of the server. At the Overview screen, click on Settings. At the Settings screen for your server, click on the check-box for “Enable Apple push notifications.” At the…
-
OS X 10.9 Mavericks Gives nvram A Delete All Option
A nifty little new option in OS X 10.9 Mavericks is the ability to delete all of the firmware variables you’ve created. This can get helpful if you’ve got a bunch of things that you’ve done to a system and want to remove them all. If you run nvkram followed by a -p option you’ll see all of the configured firmware variables: nvram -p If you run it with a -d you’ll delete the given variables that you define (e.g. boot-args): nvram -d boot-args But, if you run the -c you’ll wipe them all: nvram -c Enjoy!
-
Obtain Information About OS X Server Using serverinfo in Mavericks Server
OS X Mavericks Server (Server 3) comes with the /usr/sbin/serverinfo command (introduced in Mountain Lion Server). The serverinfo command is useful when programmatically obtaining information about the very basic state of an Apple Server. The first option indicates whether the Server app has been downloaded from the app store, which is the –software option: serverinfo --software When used, this option reports the following if the Server.app can be found: This system has server software installed. Or if the software cannot be found, the following is indicated: This system does NOT have server software installed. The –productname option determines the name of the software app: serverinfo --productname If you change the…
-
Use Server Admin Web Modules In Mavericks Server
Since the early days, OS X Server has supported performing the serveradmin commands through a web interface. This interface was accessible at the address of the server followed by a colon and then 311 in a web browser. This feature was disabled by default in Mountain Lion. But fear causes hesitation, and hesitation will cause your worst fears to come true, so we’re going to turn it back on here in Server 3. To enable, use the following command: sudo defaults write /Library/Preferences/com.apple.servermgrd requireUserAgent -bool false Once done, open https://127.0.0.1:311 in a web browser, or replace 127.0.0.1 with the address of the server if accessing from another location. This is…
-
OS X 10.9 Mavericks Makes fdesetup A Bit More Useful
Previously I’ve written a little here and there about using FileVault and more specifically scripting things around Filevault. The fdesetup command that enables FileVault for OS X clients from the command line got a few new options in OS X 10.9 Mavericks. We’ve always been able to enable FileVault using scripts thanks to fdesetup but now Apple’s taken some of the difficulty out of configuring recovery keys. This comes in the form of the changerecovery, haspersonalrecoverykey, hasinstitutionalkey, usingrecoverykey and validate recovery options. These options all revolve around one idea: make it easier to deploy centrally managed keys that can be used to unlock encrypted volumes in the event that such an…
-
New statshares Option in the smbutil command For OS X 10.9 Mavericks
I wrote about using the smbutil for DFS in Lion awhile back. I haven’t needed to write anything else as it hadn’t changed since. But in OS X 10.9 Mavericks, a new option for smbutil appears: statshares. The statshares option has an -m option to look at a mount path for showing the path to the mount (e.g. if the mount is called krypted this should be something like /Volumes/krypted): smbutil statshares -m /Volumes/krypted When run, you see a list of all the attributes OS X tracks for that mount path, including the name of the server, the user ID (octal), how SMB negotiated an authentication, what version of SMB…