- First move the Final Cut application to the trash (it’s in the /Applications folder).
- From your home folder, go to ~/Library/Application Support and move the Final Cut folder in there into the trash.
- From Library/Preferences in your home folder, put com.apple.FinalCut.plist, com.apple.FinalCut.LSSharedFileList and com.apple.FinalCut.UserDestinations.plist in the trash.
- Finally, trash com.apple.FinalCut directory from ~/Library/Caches.
sudo scutil --set HostName YosemiteSam.krypted.comThen the ComputerName:
sudo scutil --set ComputerName YosemiteSam.krypted.comAnd finally, the LocalHostName:
sudo scutil --set LocalHostName YosemiteSamNow check changeip:
sudo changeip -checkhostnameThe changeip command should output something similar to the following:
Primary address = 192.168.210.201 Current HostName = YosemiteSam.krypted.com DNS HostName = YosemiteSam.krypted.com The names match. There is nothing to change. dirserv:success = "success"f you don’t see the success and that the names match, you might have some DNS work to do next, according to whether you will be hosting DNS on this server as well. If you will be hosting your own DNS on the Profile Manager server, then the server’s DNS setting should be set to the IP address of the Server. To manage DNS, start the DNS service and configure as shown previously: Provided your DNS is configured properly then changeip should work. If you’re hosting DNS on an Active Directory integrated DNS server or some other box then just make sure you have a forward and reverse record for the hostname/IP in question. Profile Manager is built atop the web service, APNS and Open Directory. Next, click on the Web service and just hit start. While not required for Profile Manager to function, it can be helpful. We’re not going to configure anything else with this service in this article so as not to accidentally break Profile Manager. Do not click on anything while waiting for the service to start. While the indicator light can go away early, note that the Web service isn’t fully started until the path to the default websites is shown (the correct entry, as seen here, should be /Library/Server/Web/Data/Sites/Default) and a View Server Website link is shown at the bottom of the screen. If you touch anything too early then you’re gonna’ mess something up, so while I know it’s difficult to do so, be patient (honestly, it takes less than a minute, wait for it, wait for it, there!). Once the Web service is started and good, click on the View Server Web Site link at the bottom and verify that the Welcome to OS X Server page loads. Setting Up Profile Manager Provided the Welcome to OS X Server page loads, click on the Profile Manager service. Here, click on the Configure button. At the first screen of the Configure Device Management assistant, click on Next. Assuming the computer is not yet an Open Directory master or Replica, and assuming you wish to setup a new Open Directory Master, click on Create a new Open Directory domain at the Configure Network Users and Groups screen. Then click on Next. At the Directory Administrator screen, provide the username and password you’d like the Open Directory administrative account to have (note, this is going to be an Open Directory Master, so this example diradmin account will be used to authenticate to Workgroup Manager if we want to make changes to the Open Directory users, groups, computers or computer groups from there). Once you’re done entering the correct information, click Next. At the Organization Information screen, enter your information (e.g. name of Organization and administrator’s email address). Keep in mind that this information will be in your certificate (and your CSR if you submit that for a non-self-signed certificate) that is used to protect both Profile Manager and Open Directory communications. Click Next. At the Confirm Settings screen, make sure the information that will be used to configure Open Directory is setup correctly. Then click Set Up (as I’ve put a nifty red circle next to – although it probably doesn’t help you find it if it’s the only button, right?). The Open Directory master is then created. At the Organization Information screen, enter the name of the contact information for an administrator and click on the Next button. Even if you’re tying this thing into something like Active Directory, this is going to be a necessary step (unless of course you’re already running Open Directory on the system). Once Open Directory is setup you will be prompted to provide the information for an SSL Certificate. At the Organization Information screen, enter your information and click Next. At the Configure an SSL Certificate screen, choose a certificate and click Next. This can be the certificate provided when Open Directory is initially configured, which is self-signed, or you can select a certificate that you have installed using a CSR from a 3rd party provider. At this point, if you’re using a 3rd party Code Signing certificate you will want to have installed it as well. Choose a certificate from the Certificate: drop-down list and then click on Next. If using a self-signed certificate you will be prompted that the certificate isn’t signed by a 3rd party. Click Next if this is satisfactory. If you do not already have a push certificate installed for the system, you will then be prompted to enter the credentials for an Apple Push Notification Service (APNS) certificate. This can be any valid AppleID. It is best to use an institutional AppleID (e.g. firstname.lastname@example.org) rather than a private one (e.g. email@example.com). Once you have entered a valid AppleID username and password, click Next. Provided everything is working, you’ll then be prompted that the system meets the Profile Manager requirements. Click on the Finish button to complete the assistant. When the assistant closes, you will be back at the Profile Manager screen in the Server application. Here, check the box for Sign Configuration Profiles. The Code Signing Certificate screen then appears. Here, choose the certificate from the Certificate field. Unless you’re using a 3rd party certificate there should only be one certificate in the list. Choose it and then click on OK. If you are using a 3rd party certificate then you can import it here, using the Import… selection. If you host all of your services on the one server (Mail, Calendars, VPN, etc) then leave the box checked for Include configuration for services; otherwise uncheck it. One of the upgrades in Profile Manager 2.2 is the ability to distribute objects from the App Store Volume Purchase Program through Profile Manager. To use this option, first sign up on the VPP site. Once done, you will receive a token file. Using the token file, check the box for “Distribute apps and books from the Volume Purchase Program” and then use the Choose button to select the token file. Now that everything you need is in place, click on the ON button to start the service and wait for it to finish starting (happens pretty quickly). Once started, click on the Open Profile Manager link and the login page opens. Administrators can login to Profile Manager to setup profiles and manage devices. The URL for this (for YosemiteSam.krypted.com) is https://YosemiteSam.krypted.com/profilemanager. Use the Everyone profile to automatically configure profiles for services installed on the server if you want them deployed to all users. Use custom created profiles for everything else. Also, under the Restrictions section for the everyone group, you can choose what to allow all users to do, or whether to restrict access to certain Profile Manager features to certain users. These include access to My Devices (where users enroll in the system), device lock (so users can lock their own devices if they loose them) and device wipe. You can also allow users to automatically enroll via DEP and Configurator using this screen. Enrolling Into Profile Manager To enroll devices for management, use the URL https://YosemiteSam.krypted.com/MyDevices (replacing the hostname with your own). Click on the Profiles tab to bring up a list of profiles that can be installed manually. From Profiles, click or tap the Enroll button. The profile is downloaded and when prompted to install the profile, click Continue. Then click Install if installing using a certificate not already trusted. Once enrolled, click on the Profile in the Profiles System Preference pane to see the settings being deployed. You can then wipe or lock the device from the My Devices portal. Management profiles from the MDM server are then used. Devices can opt out from management at any time. If you’re looking for more information on moving Managed Preferences (MCX) from Open Directory to a profile-based policy management environment, review this article and note that there are new options in dscl for removing all managed preferences and working with profiles in Mavericks (10.9) and Yosemite (10.10). If there are any problems when you’re first getting started, an option is always to run the wipeDB.sh script that resets the Profile Manager (aka, devicemgr) database. This can be done by running the following command:
sudo /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB.shAutomating Enrollment & Random Management Tips The two profiles needed to setup a client on the server are accessible from the web interface of the Server app. Saving these two profiles to a Mac OS X computer then allows you to automatically enroll devices into Profile Manager using Apple Configurator, as shown in this previous article. When setting up profiles, note that the username and other objects that are dynamically populated can be replaced through a form of variable expansion using payload variables in Profile Manager. For more on doing so, see this article. Note: As the database hasn’t really changed, see this article for more information on backing up and reindexing the Profile Manager database. Device Management Once you’ve got devices enrolled, those devices can easily be managed from a central location. The first thing we’re going to do is force a passcode on a device. Click on Devices in the Profile Manager sidebar. Click on a device in Profile Manager’s admin portal, located at https:///profilemanager (in this case https://YosemiteSam.krypted.com/profilemanager). Here, you can see:
- General Information: the type of computer, capacity of the drive, version of OS X, build version, serial number of the system and the currently logged in user.
- Details: UDID, Ethernet MAC, Wi-Fi MAC, Model, Last Checkin Time, Available disk space, whether Do Not Disturb is enabled and whether the Personal Hotspot is enabled.
- Security information: If FileVault is enabled, whether a Personal Recovery is set and whether an Institutional Recovery Key has been installed.
- Restrictions, whether any restrictions have been deployed to the device from Profile Manager.
- Installed Apps: A list of all the apps installed (packages, App Store, Drivers, via MDM, etc).
- In Device Groups: What groups are running on the system.
- Certificates: A list of each certificate installed on the computer.
Profile Manager simplifies deploying, configuring, and managing them all. It’s one place where you control everything: You can create profiles to set up user accounts for mail, calendar, contacts, and messages; configure system settings; enforce restrictions; set PIN and password policies; and more. Because it’s integrated with the Apple Push Notification service, Profile Manager can send out updated configurations over the air, automatically. And it includes web-based administration, so you can manage your server from any modern web browser. Profile Manager even gives users access to a self-service web portal where they can download and install new configuration profiles, as well as clear passcodes and remotely lock or wipe their Mac, iPhone, or iPad if it’s lost or stolen.For the money, Profile Manager is an awesome tool. Apps such as Casper MDM, AirWatch, Zenprise, MaaS360, etc all have far more options, but aren’t as easy to install and nor do they come at such a low price point. Profile Manager is a great option if all of the tasks you need to perform are available within the tool. If not, then it’s worth a look, if only as a means to learn more about the third party tools you’ll ultimately end up using. One thing I can say for it is that Profile Manager is a little faster and seems much more stable (in fact, Apple has now published scalability numbers, which they have rarely done in the past). You can also implement newer features with it, including Books distribution, Gatekeeper, DEP and Messages.
sudo xcrun ccThis is an interactive command line environment so in order to script it you’d need to use expect to feed in the correct parameters.
ipconfig getifaddr en0Same thing, but setting and echoing a variable:
ip=`ipconfig getifaddr en0` ; echo $ipView the subnet mask of en0:
ipconfig getoption en0 subnet_maskView the dns server for en0:
ipconfig getoption en0 domain_name_serverGet information about how en0 got its dhcp on:
ipconfig getpacket en1View some network info:
ifconfig en0Set en0 to have an ip address of 10.10.10.10 and a subnet mask of 255.255.255.0:
ifconfig en0 inet 10.10.10.10 netmask 255.255.255.0Show a list of locations on the computer:
networksetup -listlocationsObtain the active location the system is using:
networksetup -getcurrentlocationCreate a network location called Work and populate it with information from the active network connection:
networksetup -createlocation Work populateDelete a network location called Work:
networksetup -deletelocation WorkSwitch the active location to a location called Work:
networksetup -switchlocation WorkSwitch the active location to a location called Work, but also show the GUID of that location so we can make scripties with it laters:
scselect WorkList all of the network interfaces on the system:
networksetup -listallnetworkservicesRename the network service called Ethernet to the word Wired:
networksetup -renamenetworkservice Ethernet WiredDisable a network interface:
networksetup -setnetworkserviceenabled offChange the order of your network services:
networksetup -ordernetworkservices “Wi-Fi” “USB Ethernet”Set the interface called Wi-Fi to obtain it if it isn’t already
networksetup -setdhcp Wi-FiRenew dhcp leases:
ipconfig set en1 BOOTP && ipconfig set en1 DHCP ifconfig en1 down && ifconfig en1 upRenew a dhcp lease in a script:
echo "add State:/Network/Interface/en0/RefreshConfiguration temporary" | sudo scutilConfigure a manual static ip address:
networksetup -setmanual Wi-Fi 10.0.0.2 255.255.255.0 10.0.0.1Configure the dns servers for a given network interface:
networksetup -setdnsservers Wi-Fi 10.0.0.2 10.0.0.3Obtain the dns servers used on the Wi-Fi interface:
networksetup -getdnsservers Wi-FiStop the application layer firewall:
launchctl unload /System/Library/LaunchAgents/com.apple.alf.useragent.plist launchctl unload /System/Library/LaunchDaemons/com.apple.alf.agent.plistStart the application layer firewall:
launchctl load /System/Library/LaunchDaemons/com.apple.alf.agent.plist launchctl load /System/Library/LaunchAgents/com.apple.alf.useragent.plistAllow an app to communicate outside the system through the application layer firewall:
socketfilterfw -t “/Applications/FileMaker Pro/FileMaker Pro.app/Contents/MacOS/FileMaker Pro”See the routing table of a Mac:
netstat -nrAdd a route so that traffic for 10.0.0.0/32 communicates over the 10.0.9.2 network interface:
route -n add 10.0.0.0/32 10.0.9.2Log bonjour traffic at the packet level:
sudo killall -USR2 mDNSResponderStop Bonjour:
launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plistStart Bojour:
launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plistPut a delay in your pings:
ping -i 5 192.168.210.1Ping the hostname 5 times and then stop the ping:
ping -c 5 google.comFlood ping the host:
ping -f localhostSet the packet size during your ping:
ping -s 100 google.comCustomize the source IP during your ping:
ping -S 10.10.10.11 google.comView disk performance:
iostat -d disk0Get information about the airport connection on your system:
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport -IScan the available Wireless networks:
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport -sTrace the path packets go through:
traceroute google.comTrace the routes without looking up names:
traceroute -n google.comTrace a route in debug mode:
traceroute -d google.comView information on all sockets:
netstat -atView network information for ipv6:
netstat -ltView per protocol network statistics:
netstat -sView the statistics for a specific network protocol:
netstat -p igmpShow statistics for network interfaces:
netstat -iView network information as it happens (requires ntop to be installed):
ntopScan port 80 of www.google.com
/System/Library/CoreServices/Applications/Network\ Utility.app/Contents/Resources/stroke www.google.com 80 80Port scan krypted.com stealthily:
nmap -sS -O krypted.com/24Establish a network connection with www.apple.com:
nc -v www.apple.com 80Establish a network connection with gateway.push.apple.com over port 2195
/usr/bin/nc -v -w 15 gateway.push.apple.com 2195Establish a network connection with feedback.push.apple.com only allowing ipv4
/usr/bin/nc -v -4 feedback.push.apple.com 2196Setup a network listener on port 2196 for testing:
/usr/bin/nc -l 2196Capture some packets:
tcpdump -nSCapture all the packets:
tcpdump -nnvvXSCapture the packets for a given port:
tcpdump -nnvvXs 548Capture all the packets for a given port going to a given destination of 10.0.0.48:
tcpdump -nnvvXs 548 dst 10.0.0.48Capture the packets as above but dump to a pcap file:
tcpdump -nnvvXs 548 dst 10.0.0.48 -w /tmp/myfile.pcapRead tcpdump (cap) files and try to make them human readable:
tcpdump -qns 0 -A -r /var/tmp/capture.pcapWhat binaries have what ports and in what states are those ports:
lsof -n -i4TCPMake an alias for looking at what has a listener open, called ports:
alias ports='lsof -n -i4TCP | grep LISTEN'Report back the name of the system:
hostnameFlush the dns cache:
dscacheutil -flushcacheClear your arp cache:
arp -adView how the Server app interprets your network settings:
serveradmin settings networkWhitelist the ip address 10.10.10.2:
/Applications/Server.app/Contents/ServerRoot/usr/libexec/afctl -w 10.10.10.2Finally, the script network_info.sh shows information about a Macs network configuration. Both active and inactive network interfaces are listed, in the order that they are used by the OS and with a lot of details (MAC-address, interface name, router, subnet mask etc.).
Stroke got moved, so dug this up and am reprinting with the latest and greatest location.
Network Utility has a port scanner – it’s built in and really easy to use. Sure, stroke isn’t nmap, but it’s not trying to be… Since Network Utility is distributed with every copy of Mac OS X it stands to reason that every copy of Mac OS X has the ability to scan a port without using a GUI tool. Enter one of the best named tools in Mac OS X, stroke. Stroke is the command line back-end to the Port Scan tab of Network Utility. To use stroke, you will need to cd into the Network Utility application bundle and then cd into Contents and then Resources.
Once you are at “/System/Library/CoreServices/Applications/Network Utility.app/Contents/Resources”, you will need to provide stroke with an IP address (or name), followed by the first port to scan and then the last (or the same number twice if your range is only one IP address. For example, if you want to port scan port 80 on your own system you could use the following:
./stroke 127.0.0.1 80 80
But you shouldn’t just stroke yourself (sorry, couldn’t help it). You should also stroke others (Clarence Carter be damned!). So if you want to port scan www.google.com for port 80 the following would achieve such a lofty goal:
./stroke www.google.com 80 80
Because the name www.google.com has to resolve, you’re actually able to check whether a DNS error occurs and whether you can communicate over port 80 to the host in one command. If you want to make a copy of stroke into a directory and then add it to your environment variable’s PATH you can then use it without needing to change your working directory.
sudo launchctl unload -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plistOnce restarted, you may need to remove the files in /var/vm as that is where the swap files are stored. To do so, rm the contents of /var/vm:
rm /var/vm/swapfile*You should also be able to get rid of the sleepimage file in that directory if needed. Since this is supposed to be a temporary or troubleshooting measure, to turn swapping back on:
sudo launchctl load -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist