At first glance, Apple Push Notification services seem pretty darn complicated. Luckily, we’re all about demystifying technical things here at Bushel. So let’s take a moment to look at what happens when an Apple Push Notification transaction occurs. In this example, we’re going to look at using our tool to send some command to a device, like enforce a passcode policy. Now, you send this passcode enforcement in what is known as a profile. That’s just a way of saying some code that tells the device to enforce a passcode policy. That transaction of sending the profile might seem like it’s as simple as just send the code from the…

You can do some pretty simple testing to Apple’s APNS of ports and network communications using strategies I’ve outlined in the past with tcpdump, trace route, telnet, curl, stroke and of course ping. These are classic ways to test connectivity to servers. However, netcat has a few interesting things you can do with it; namely actually run a port super-quickly to test traffic between subnets, forcing scans of ipv6 traffic, debugging sockets, keeping connections alive, parodying through SOCKS 4 and 5 and just checking for daemons that are listening rather than actually sending data to them. Learn To Test Connectivity to Apple Push Notification Services Here…

Apple’s Device Enrollment Program (DEP) allows organizations to automatically setup large numbers of devices without lifting a finger. Well, per device at least. What we mean by this is that if you use a Mobile Device Management (MDM) solution, such as Bushel, you will be able to configure that solution to configure your devices automatically once they’re on a wireless network. Each of your coworkers, students or employees can take the wrapper of their own device, log into the wireless network and have the device setup mail, apps and apply security settings! Cool, right?!?! Learn More About DEP Here…

Last year, I did the Electric Run last year in Minneapolis. This year it’s at the Minnesota State Fairgrounds, rather than around a lake. June 6th from 9:30pm on. Should be a great time. Hope to see ya’ there!

Here at Bushel, we code all winter. And sometimes, we take our phone outside during the winter. Luckily, we’re usually holding it in our hand. But sometimes, you need both hands (like when you’re shoveling some snow). When the temperature of an iOS device -4º or above 113º F the device shuts off, and Apple has yet again protected you (this time from the elements). Learn More About iOS Devices and Temperature Here…

(Guest post by Allister Banks) We’re several years in to Apple distributing its installer through its (formerly with the ‘Mac’ prefix) App Store, which if you right-click the bundle you can show package contents, and then navigate to the packages involved in the install as part of an Electronic Software Distribution image(or InstallESD.dmg for short.) Guidance remains the same, however, regarding getting the proper version of the OS to reinstall on your computer – in almost all cases, the newest hardware will only be supported by a ‘forked‘ version of the operating system. That means the process outlined here on Rich Trouton’s DerFlounder blog is still 100% applicable if you…

To install wget on a Mac, first make sure you have Xcode installed. Then, create a place to do your installation from: mkdir ~/Desktop/wgetinstall; cd ~/Desktop/wgetinstall Then, curl it down from the gnu.org ftp servers: curl -O http://ftp.gnu.org/gnu/wget/wget-1.14.tar.gz Next, extract the tar file: tar xvf ~/Desktop/wgetinstall/wget-1.14.tar.gz Then cd into the wget directory: cd wget-1.14 And then let’s config: ./configure --with-ssl=openssl Then a standard make: make Then a typical make install: make install Now let’s make sure we know where it went: type -a wget And now let’s test wget —version And to test downloading: wget http://www.apple.com Then, clean up after your installer: rm -rf ~/Desktop/wgetinstall