Since the launch of SimpleMDM, we have seen tremendous use of the service. From small businesses, to schools, to government agencies around the world, SimpleMDM has made iOS device management easy and accessible.
As a result, we have re-branded the product to better suit its capabilities. Although the solution remains powerfully "simple", we wanted a name that can grow beyond simple and we believe DeviceLink will do just that.
To announce the change, we published our first-ever press release. Below is an excerpt with a link to the full thing, and thank you for making DeviceLink such a hit!
Setting itself apart from other MDM offerings, DeviceLink provides unlimited device management with rapid enrollment at no cost. Customers only need a web browser and devices to manage to get started. An organization can literally begin managing devices in minutes – ideal for small businesses.
DeviceLink has been available in limited release for more than nine months as SimpleMDM with customers all over the world. Along with the official launch and based on customer feedback, DeviceLink will now support free and paid app distribution as well as volume purchase codes.
DeviceLink allows for management of bring your own device (BYOD) and company-owned devices, offering three levels of security within a single selection. DeviceLink provides support for iPhone, iPad, and iPod touch with device compliance detection, including passcode requirements, app whitelist/blacklist, as well as remote lock, wipe and password reset. For more information, visit UnwiredRevolution.com/DeviceLink.
Full Press Release: http://www.unwiredrevolution.com/news/
DeviceLink Webpage: http://www.unwiredrevolution.com/devicelink/
I've got an impossible request, but I'm interested if anybody has come across any information that may be helpful; trying the power of crowd sourcing.
iOS and iPad backups: has anybody come across there ANYTHING that provides an automatic backups of iOS/iPads to enterprise backup solutions ? And the it is very important that it is automatic; I can not rely on our customer's iPad users to be involved in the back up procedure.
- I know that there are back up solutions that have an iOS client on the iPad, but typically it requires a manual process for the end user to initate the back up procedure.
- I know that a mac can be set up to act as a back up option (over Wifi) but (typically) this does not 'connect' directly to most enterprise back up solutions (EMC, etc).
- I can think of ways to hook 'this-into-that' and 'bolt-that-on-to-this' but most of these options require ongoing support.
In a perfect world, (working with the options that Apple allow us) I would like a hardware (or VM appliance) that runs an iTunes service continuously for backup services ALONE. This device would connect to the Wifi environment and provide a continuous service to all iPads that connect on to the Wifi network. Each iPad back up would be unique by date/timestamp. And this solution would allow me to restore any back up to the source iPad.
(chirp chirp <- the sound of crickets over the deathly silence)
I was wondering whether it's possible to interact with Profile Manager in an automated way (i.e. as a RESTful web service) to do things such as delete a device (i.e. as part of a de-provisioning workflow, or even do an "Update Info" periodically).
I did a basic search but nothing seemed to jump out.
Hi enterprise iOS community,
Anybody out there using a multi-platform (Android, iOS, Mac OS X, Windows) management/MDM software? Meaning, one application is managing desktops, laptops and handheld mobile devices. If so, please tell me the good and the bad of your chosen management platform.
Thanks in advance,
Jack Madden has written a helpful history of enterprise management improvements in iOS.
"As we gear up for Apple's WWDC in June (with fingers' crossed that we'll get even more enterprise management features in iOS 7), I thought it would be good to take a look at just how far Apple has come over the years when it comes to improving the enterprise management aspects of iOS."
Although it isn't their marketing focus, enterprise iOS is a significant part of engineering. Every major release of iOS has included some features useful only for people like us.
We are happy to announce the successor of the Batch Apple ID Creator AppleScript, "Apple ID Automation Builder," a self-contained app written by the Great iTunes Automator Greg Moore, aka Eight_Quarter_Bit.
Purpose & Features
Deploying a great quantity of iOS devices means creating a great quantity of Apple IDs. This script allows automated Apple ID creation from a spreadsheet. Apple IDs are created without a credit card, which is great for many deployments. There is a "dry run" feature to test the script without actually creating the Apple ID.
Enterprise iOS is hosting a forum for any comments or discussion.
The current version is downloadable here: http://bit.ly/AIDAB ... This file is a disk image (DMG) containing a bundled app.
There is also an RSS feed for when I upload new versions or additional files:
- IMPORTANT: Apple uses a velocity check to prevent too many Apple IDs from a single IP address. You must contact your Apple business representative to request that your IP address is whitelisted for a short time.
- Being AppleScript, this runs only on Macs.
- UI Scripting allows us to script otherwise non-scriptable interfaces. Turn this on in System Preferences > Accessibility and check "Enable access for assistive devices."
- Apple has strong password requirements. Account creation will fail if the passwords are too weak.
About Version 2.0
After many months of work (and almost as many of silence on my end, for which I do apologize) version 2.0 of this script is nearly ready for beta testing. I was never really happy with the version available here, because (as you have all seen) it's incredibly fragile and needy. The level of knowledge needed to fix this version is also high, the internal design ranged from poor to non-existent, and major features were never fully developed.
In short, this version of the script was never intended for public consumption. It was an ugly hack from the get-go, barely "alpha" levels of quality, and really only designed to be used within my department. Heck, I never anticipated it would even leave my machine, much less be used all over the world. I'm glad it has served as a stop-gap in the meantime, but frankly I'm embarrassed to have put you through its numerous quirks. Time to give this guy a well-deserved retirement.
Version 2 is a complete from-the-ground-up redesign. 98% of the code has been freshly written (pretty much only a few portions of the CSV parser made it unscathed from v1,) weighs in at roughly 2500 lines, and the method of operation is completely new. In v2 the script builds the setup process itself, outputting the constructed process into an independent app, rather than relying on brittle, hard-set UI element references. When the ID setup process changes you just use the script's GUI to build a new process -no knowledge of AppleScript required! This also allows for constructing multiple setup processes, for instance one with no payment information and one with a payment method, or one method for operating on the CSV output from a user management system and a second for a different CSV source of user info.
Because v2 constructs the setup process, it is now fully system-language and Apple Store location independent by design. Finally you guys living outside the US can stop having to hack away at the script every time it is updated. I haven't forgotten about you.
Version 2 also outputs and updates three CSV files during operation: one containing the accounts that were created successfully, one with the accounts that encountered some sort of error (which the script is now vastly better at recovering gracefully from,) and one with the accounts that have yet to be run. Accounts that encounter an error report what step they encountered the error on, the time the error occurred, and even tries to record the error reported by Apple. All of these are in standard CSV output, so if something terrible happens and the script explodes in a giant fireball you can just re-launch, open the "pending accounts" CSV that the script was updating as it ran, and pick back up where you left off. Need to re-try the accounts that encountered errors? Just grab the CSV that recorded accounts with errors and pop it right back into the script.
Also planned for the new version is inherent support for being used as a library in a larger project, for those of you who are script-heads and want to work Apple ID creation into a larger workflow. This feature likely won't be ready by the first beta, but the groundwork is laid.
There are lots of little niceties as well, including some pretty icons, boatloads of error checking, a highly verbose GUI that walks you through every step of constructing a sign-up process, support for customizable pauses to avoid tripping Apple's velocity limit if need be, and more.
I hope to put the final spit-and-polish on version 2 beta this weekend, and be able to remove the beta tag within a month. Over the past two days I've successfully run roughly 2000 accounts through it, and just need to touch up a few remaining areas. I will get in contact with Mr. Freimark as soon as I have killed the last few big issues, and see if we can't get a new post put up.
Your patience with v1, as well as your enthusiasm, have been astonishing. I thank you.
Here's too many more automatically created Apple IDs, in the days to come!
Enterprise iOS is hosting a forum for any comments or discussion.
In the recent years we all have seen the many revisions of iOS and with each one comes the famous "my battery is draining because of the upgrade" As we all do as techs and support we look for the usual, such as exchange settings and apps currently running. Recently, I came across a user that is claiming that he is losing battery so rapidly he can't get through a few hours, when on-site to evaluate this claim no such situation exists. So I have decided to start taking action as convincing Apple to swap out the phone may not actually be the answer. Wanted to hear what the communities strategy has been to evaluate, support and explain to a client "it might be you"
[Editor's note: This was originally posted on tekserve.com, but I thought it was useful enough to post here too.]
Apple recently enabled a new security feature for Apple ID accounts called “Two-Step Verification.” This is a form of multi-factor authentication that can help keep your account more secure. I am a huge fan of multi-factor authentication and have enabled it on almost every account that offers it. This post will explain just what the technology is, why it’s helpful, and how to use Apple’s implementation specifically.
What Is Multi-Factor Authentication?
In order to log in to an online service, such as my email, I need to authenticate with the server. When I go to Gmail, for example, Google does not intrinsically know that it’s me trying to connect. I need to first provide the server with proof that I’m the owner of the account before being allowed access to my data. My password is one possible “factor” for authentication. It proves to Google’s server that it is indeed me, and not someone else, who is trying to access my data, and allows me in to see it.
The Register has an article on an important but often overlooked aspect of iPads in business. Users want them working, all the time.
My iPad is more robust than most of the appliances in my kitchen never mind an enterprise data centre... As a result of this turnaround, the role of an IT architect has got even harder, especially in the small- and mid-enterprise sectors where arguably the pace of IT change has never been faster and the lack of IT governance has never been lower
Have you noticed this too?
We use x509 TLS certificates as part of our authentication to activesync. When the certificate renews, the way this works is the profile is removed from the device and re-added with the new credential.
Unfortunately, this means that the activesync account settings are reset to defaults (folders to sync, days, etc) as well as if the user had set the activesync as default account for mail, calendar, contacts.
Under the principle of least surprise, I'd like to force the activesync accounts to be default when provisioning or renewing. I haven't found any way of doing this with the standard AirWatch profile settings, so I was wondering if there's any MDM features I should be asking AirWatch for, or even if there's any custom XML that I can apply.
About This Site
- Comparison of MDM Providers (615,132)
- Complete List of iOS User-Agent Strings (252,072)
- How to get remote viewing/control of the IPAD screen via internet or preferably 3G? (166,498)
- Apple Configurator vs. MDM (120,309)
- Mobile Device Management (80,455)
- Apple Profile Manager (69,289)
- AirWatch (65,148)
- Gartner Magic Quadrant for MDM (2014, 2012, 2011) (64,418)
- Batch Apple ID Creator (63,176)
- iOS Devices (58,539)
Comparison of MDM Providers
Forum topic added by Wymanneq 1 day ago
Story comment by ammararajpoot 1 day ago
Forum topic comment by aroobarajpoot 2 days ago
Forum topic comment by usher.br 3 days ago
Forum topic comment by Juhis 3 days ago
Mobile Management Provider changed by bugfrisch 3 days ago
Story added by Aaron Freimark 4 days ago
Story added by Aaron Freimark 4 days ago
Forum topic comment by swkim 5 days ago
Forum topic comment by usher.br 5 days ago
Forum topic comment by peterjli 5 days ago
Forum topic added by Chrisp55 5 days ago
Forum topic comment by jesselvella 5 days ago
Forum topic comment by andycidau 5 days ago
Forum topic added by shopper150 1 week ago
Mobile Management Provider changed by Rene 1 week ago
Forum topic added by Weeksy 1 week ago