Samsung Australia were kind enough to loan me Galaxy Note 3 to test it’s capabilities with MaaS360. It’s a fantastic smartphone and the screen resolution was amazing.
MaaS360 provides a range of Android device management. Samsung have extended this capability for their devices via Samsung SAFE (Samsung for Enterprise). MaaS360 also has the capabilities to provide remote control of these devices, just like a traditional PC or Mac.
Enrolling a device to MaaS360 is very simple. The administrator can configure all users to enrol in a pre-defined URL, which they can then be authenticated to a companies Active Directory server. The following are a set of screen captures when I enrolled my device.
The Samsung phone would then register to MaaS360 and I could then manage the device. I was then able to distribute the MaaS360 Remote Control application.
The user would install the application as shown in these screen captures:
The MaaS360 administrator can then select to remote control the device as shown:
The user is then prompted on their phone to accept remote control.
After a few seconds, the administrator can view and take control of the device as shown in this video.
MaaS360 is a multi-tenant SaaS based Enterprise Mobility Management (EMM) solution. It not only manages mobile devices (iOS, Android, Windows etc) but also your traditional Windows and Apple Macs (OS X) too. To provide visibility of a companies internal resources such as Active Directory, Exchange, Domino or Blackberry in a secure manner to MaaS360, Fiberlink created the “Cloud Extender” (CE). The Cloud Extender is a small Windows application that you can install on an internal Windows server (physical or virtual machine) as shown in the following diagram:
This article details how I setup the Cloud Extender in our lab running on Softlayer, which consists of Active Directory (x2) and Exchange 2010 server (I tested with the Exchange 2007 Exchange Management Tool and PowerShell options below).
Setting up the Cloud Extender on your internal server
- The setup guide and Cloud Extender Configuration Tool executable is available from the Setup MaaS360 console as shown
- On your nominated intranet server, run the MaaS360_Cloud_Extender.exe and follow the defaults until it is installed.
- Run the Cloud Extender Configuration Tool and select if it’s communicating to the Internet directly or via a proxy. The CE needs communication to *.fiberlink.com and *.maas360.com on ports 80 and 443:
- Select the Services to be configured. You can select various Exchange versions, Lotus Traveller, Blackberry BES, User Authentication (Active Directory or LDAP), User Visibility (Active Directory or LDAP) and Certificate Integration:
- The Cloud Extender Configuration Tool runs a series of prerequisite checks:
- I next configured the Service account to communicate to Active Directory and Exchange. I then tested Authentication:
- I didn’t apply any device managmeent restrictions as shown below:
- The Cloud Extender then completes it’s configuration and it automatically downloads any required components from MaaS360:
- The Cloud Extender has an Automatic Software Update feature which is nice. Finally click Finish.
Cloud Extender from the MaaS360 console
Now login to the MaaS360.com console and select Setup and Cloud Extender. You can see the range of services configured and last communication times.
You can then run a series of tests to ensure the Extender running correctly.
So that’s it! Incredibly easy and I took less than 30 minutes to walk myself through the installation and configuration. If you have any questions, the MaaS360 MDM forum looks a great place look first. Of course, if you would like to try out MaaS360, you can register for a free 30-day trial by going to www.maas360.com/IBM.
Today IBM announced the aquisition closure of Fiberlink Communications. Fiberlink have developed an amazingly simple to use Enterprise Mobility Management (EMM) service. MaaS360 is one of the few MDM products, where you can literally use their MDM product in minutes. A customer can register their details at www.maas360.com for a 30 day trial, and take it for a test drive within minutes. No waiting for sales contacts to contact you first, no migration to other services if you like to use the product after the trial.
I’ve found MaaS360 extremely easy to use. Which is feedback I’ve also heard from clients evaluating other MDM solutions. The MDM in minutes video provides a great overview:
The team at Fiberlink also provide PC and Mac management, which is based on IBM Endpoint Manager (BigFix) technology. So I look forward sharing with you how IBM Endpoint Manager technology will integrate with MaaS360 in the future. I’ll also post my experiences and insights into MaaS360 on this blog too.
IBM Endpoint Manager (IEM) is popular with Managed Service Providers (MSPs) for it’s ability to manage hundreds of thousands of endpoints via a single multi-tennant architecture. IEM provides MSP’s the flexibility for either centralised or delegated administration models.
IBM Endpoint Manager is typically installed in a centralised architecture as show below. A single IEM server is installed at the MSP to manage several clients from one platform. The IEM server may be installed with Distributed Server Architecture (DSA) for larger environments. Some MSP’s prefer to leverage virtualisation technologies for disaster recovery such as VMware Site Recovery Manager (SRM).
IEM can manage thousands of separate customer networks (each with thousands of endpoints), without requiring a VPN connection to each client. This is achieved via IEM relays. A relay is essentially any endpoint but performing some additional responsibilities. IEM can also manage roaming endpoints which may have left those clients and are working at other remote locations (home, hotels etc).
Top Level Relays (MSP Relays)
To manage these endpoints, the MSP will need to separate the IEM server from the public internet via one or more relays. These relays can be designated relay1, relay2, relay3 etc. as extra capacity is required. The suggested guideline is approximately one of these MSP’s will support 1000 child relays, which you can think of is approximately 1000 MSP managed customers.
Including another relay for redundancy is good practice. So for most MSP’s with two top level relays, this could support around 2000 child relays (or managed customers). For the purposes of this.. example, I have called this top level relay relay1.msp.com.
At each customer office that will be managed by the MSP, it’s recommended to install a relay. If you don’t, each endpoint will communicate back directly to the top level relays. So there is additional bandwidth requirements. Each endpoint will most likely need to have command polling enabled. So each endpoint ‘phones home’ on a regular basis.
If you deploy a relay, this can be an existing server already in the DMZ (running a range of Windows, Linux or Unix operating systems). The IEM agent is installed which communicates back to the top level relay called relay1.msp.com. The server relay1.internal.org is promoted as a relay using Fixlet ID 1642 Install IBM Endpoint Manager Relay (Version 9.0.787.0). Check of course for later versions.
Network and DNS Requirements
Ensure you have TCP ports 52311 open at both the MSP and client firewalls. You can check this by performing the following telnet commands:
telnet relay1.msp.com 52311 telnet relaycust1.msp.com 52311
You can also also use a web browser and browsing to the relay’s address and append :52311/relaydiagnostics as shown below:
The MSP should designate the DNS name of the top level relays for client registration purposes (see below). The MSP doesn’t need to define DNS entries for the client relays (such as the name relaycust1.msp.com), although you might simple do this to assist with future network diagnosis.
Endpoints at each of the remote offices need to register back to the MSP’s IEM server. This is not possible via direct communication. It’s achieved by configuring the remote client to register via a nearby relay. In our example above, this is to relay1.internal.org as detailed in this article. The client then registers all the way back to the MSP’s IEM server via the relay servers.
Most MSP’s allocate each client a unique Client Identification (CID) as outlined in this wiki article. They do this so all the endpoints can be easily classified and grouped together. Select Computers, Tools – Manage Properties and create the following cid property:
The cid value can be defined at endpoint registration time via a clientsettings.cfg setting. This number can be allocated from the IEM console, by selecting the server, clicking the right mouse button, then selecting Edit Computer Settings… Then select Add, and enter a setting name of cid and the appropriate number you’ve designated. ie. 0001. Once you’ve clicked ok, it can take a few minutes for this new value to be applied to the endpoint and the results sent back to the IEM console.
You can define separate administrator accounts to only manage those clients endpoints. To do this, create a local account or LDAP role. Then as shown below, only assign computers that match the appropriate cid value. When the user logs back into the IEM console, they will only be able to administer computers with the cid of 0001.
As outlined in this article, circumstances may arise whereby the MSP is required to manage and/or deploy custom content for a specific customer. To avoid all customers TEM Clients downloading and evaluating this custom content, the MSP must create “Custom Sites” and subscribe only the specific customers TEM Clients to that site. Create custom sites for each client and assign computers to them using the following example:
Also note that by default, the IEM Operator accounts you create for each customer cid will have no access to the IBM External sites, such as Patches for Windows, Asset Discovery, Inventory & License, etc, so you will need to give “Reader” access for any of these sites that are required by these customer specific IEM Console Operator accounts.
Running Actions to remote endpoints
With the above IEM architecture in place, the administrator can deploy a patch to a remote endpoint and see it’s progress in realtime. Here is a short five minute video showing a small Microsoft hotfix being applied to a remote server. Remember that this server is isolated at the remote clients network, and has no direct communication to the Internet or central MSP IEM server. All communication is performed via the IEM relays.
You can see how IEM provides a flexible multi-tenant service for Managed Service Providers (MSPs) without complex networking or server requirements.
It was recently reported that a Microsoft Windows and Office vulnerability was already being targeted by criminals. If you search on Google for keywords such a Windows and zero day exploit, it’s interesting to summarise the respective web pages mentions:
- Windows – Approximately 7 Million web pages
- Mac – Approximately 500K web pages
- Linux – Approximately 500K web pages
IBM’s X-Force team publish all new threats via their X-Force Alerts and you’ll see the usual suspects. As outlined in this CRN Article, IBM’s X-Force Team advised that attackers “use a path of least resistance to gain a maximum return on exploits”.
It’s one thing to be notified of these threats, but how do you confidently address them easily within your organisation? This is a particular challenge with thousands of PCs and Macs and a mobile workforce. Some of whom may be travelling for days and not regularly connecting to a corporate network.
The good news is, there are tools that can help. Within hours of vulnerability being identified, IBM’s Endpoint Manager team will package and re-test a published hotfix (or suggested alternative). For example for the Windows and Office vulnerability outlined above, this in in the form of a temporary hot fix. This is then published by IBM in the form of a Fixlet, making this critical fix immediately available for all IBM Endpoint Manager servers and their clients. Each IEM agent then reports to it’s vulnerability status back to the customers IEM console, so you have a realtime view of the number of endpoints effected.
The IEM administrator can “Action this Fixlet” (ie. go ahead and fix those PCs and Servers thanks!), which will dynamically download the hotfix and apply it to tens or hundreds of thousands of endpoints. The administrator can once again view in realtime the remediation status. So at anytime, the IEM administrator report this information to their organisation or security auditors.
In addition to the range of operating system vulnerabilities/patches addressed by IEM, the following is a list of applications managed by the IBM Content Delivery Team include the following (thanks to Peter Tuton for putting together this list):
- Flash Player (including browser plug-ins)
- Shockwave Player
- Remote Desktop
- Internet Explorer
- SQL Server
- Mozilla Firefox
- Nullsoft WinAmp
- Oracle Java Runtime Environment
How is your organisation addressing the Zero Day threat?
IBM Endpoint Manager provides clients with the ability to manage hundreds of thousands of endpoints from a single console. These can be a range of operating system types such as Windows, Linux, Apple Mac OSX and Unix. Oh, don’t forget mobile devices too!
You can install your IEM environment with an relay running in your DMZ, you can also manage your mobile workforce and public cloud resources too. An IEM relay is simply any existing IEM agent thats been given a few more additional tasks. The really provide bandwidth and server scaling benefits and is a proxy between externally managed devices and your internal network.
Your public instances will typically be Windows or Linux operating systems running on your public cloud of choice such as Amazon Web Services (AWS) or IBM Softlayer.
Configuring the IEM Client for Public Internet Instances
Each operating system you wish to manage needs to have the IEM agent installed. IBM offers a range of agents for Windows, Mac OSX, IBM AIX, HP-UX and Solaris. The IEM agent when it’s started, will attempt to register itself back to your IEM server. This will be via details stored within the actionsite.afxm (renamed from the masthead.afxm file). This file is unique to your IEM server and is stored on your IEM server in the Program Files (x86)\BigFix Enterprise\BES Installers\Client directory.
Of course, if you have a public cloud instance the IEM client won’t be able to reach your privately hosted IEM server. You need to provide the client a few additional details so it can ‘phone home’. This will be your relay in the DMZ and it’s DNS name or IP address. These details are stored in the clientsettings.cfg file. The following article provides details on how to configure this, but all it requires is just one or two lines as shown in this example:
Of course, use your DNS server names. The clientsettings.cfg file is used when the IEM client is installed.
Deploying your IEM Clients
You may wish to deploy your IEM clients using the client deployment tool, Active Directory or login script as I detailed here. However for a public cloud environment, some platforms provide image deployment capabilities. Much like VMware’s powerful image template feature, with your cloud provider you will create a ‘gold image’ with your desired operating system, fixes, software and IEM agent installed. You need to follow the instructions in this article so the IEM agent ready to work correctly as new instances are deployed from this image.
Amazon Web Services (AWS)
With AWS, you can create your gold image by creating an instance, shutting it down and selecting Actions – Create Image. You then have an AMI from which you can deploy new Instances as shown below. AWS provide the EC2Config service to also provide Sysprep and other image configuration features.
With Softlayer, you can use the same approach with their Flex Image. Softlayer also provide the ability to execute a script which will be executed on a newly provisioned SoftLayer device, which is another approach to configure client settings if required.
When your instances start for the first time, they will automatically register to the IEM server and be visible in the console. You’ll then be able to provide the following services from your console. This is possible for your private AND public instances !
- Patch Management – Operating System Patches, plus a number of 3rd party applications such as Java, Adobe etc.
- Core Protection – Anti-virus/Anti-malware
- Security and Compliance – security checklists such as CIS, DISA STIG, FDCC and USGCB.
- Software Usage
- Remote Control
If you have IEM baselines enabled, you can then be assured that those endpoints are automatically patched to a minimum level and an appropriate security posture is applied. IBM Endpoint Manager provides per server licensing, so you pay as those instances need to be managed. It would be great to hear from you if you’re managing Windows or Linux instances on AWS or Softlayer.
Buried inside many devices we don’t consider as PCs lurks Windows XP. These are devices like cash registers, vending machines, parking meters and automatic teller machines (ATMs).
Whilst Linux is one alternative, Windows XP has provided the right mix of a reliability, multitasking and wide device support many organisations have needed. This trusty operating system was released back in 2001 and it’s support is finally ending on April 8, 2014. That’s less than 162 days from now!
For your home PC, popping in a Windows 7 DVD and doing an upgrade isn’t a big deal. However for organisations running ‘purpose specific’ devices on XP, this will involve an incredible amount of time and effort.
A recent article by Kevin Casey from Information Week advised that presently “around 75% of ATMs in the U.S. are based on XP”. I recently met with a retailer who advised their cash registers were tuned only for Windows XP. They simply won’t have the CPU and memory resources to run Windows 7. When you consider they have thousands of cash registers that might need to be replaced, it’s a significant outlay. So many organisations are understandably looking for solutions to manage XP for longer if they can.
The good news is that IBM Endpoint Manager (IEM) continues to support the Windows XP operating system. This includes our Core Protection module which provides anti-virus/anti-malware. This capability is critical for ATM’s and cash registers, as hackers being to target these devices. For example, the reported example of malware detected on ATM’s in Mexico running Windows XP.
If you are in the position to upgrade these devices, IBM Endpoint Manager has an operating system deployment capability. This means you can remotely upgrade these endpoints to Windows 7 or Windows 8 (whether that be in-place or bare metal).
IBM Endpoint Manager can protect hundreds of thousands of endpoints, even those connected on very low bandwidth and high latency networks. This capability ensures a bank running IEM can update their ATM’s reliably from a single console. For another financial client SunTrust, this meant their patch cycle times reduced from 2-3 weeks to 2-3 days.
How are you preparing to migrate from Windows XP? How will you support it if you don’t?
Apple’s latest and greatest mobile operating system iOS 7, is now available. From all reports, over 30% of all iOS devices were updated in just 16 hours! I’m still making the adjustment to doing things a little differently than before. I found it ironic that I needed to call on Google to find the answers I needed. For example, like how do I search in iOS 7 or kill running apps. Overall, I do like the new look and feel.
For organisations, Apple has released a range of new Mobile Device Management (MDM) features too. MaaS360 and IBM Endpoint Manager provided same day support for iOS 7 as per previous iOS releases. Since IEM leverages a cloud service to distribute updates for Windows, Mac, Linux and Unix, it can update the product itself to leverage these new services immediately.
There has been a lot of great coverage on iOS 7 MDM from experts such as Jack Madden who has explained the key features and benefits. I noticed that Apple has just updated it’s iPhone in Business web page to reflect iOS 7 too.
The key MDM features of iOS 7 are:
- Open In management - Protect corporate data by controlling which apps and accounts are used to open documents and attachments
- Per app VPN – Configure apps to connect to a VPN when launched
- App Store License management - Companies can assign apps to their users while keeping full ownership and control over app licenses
- New MDM configuration options – see below
- Streamlined MDM enrolment – Devices can be automatically enrolled in MDM during activation
- Enterprise Single Sign-on – Authentication can be done once to a number of applications
I haven’t yet found the ‘definitive list’ of iOS 7 MDM features, so I decided to put one together like I had for Samsung SAFE. So companies and their staff then clearly know what features can be configured and controlled with iOS 7. So here it is, if you have any omissions or corrections please let me know.
There are five new Apple iOS 7 configuration profiles:
- AirPlay – Add Airplay devices and their passwords
- AirPrint – Add Airprint printers
- Font – adding Fonts. Maybe if you have corporate Fonts on devices?
- Single Sign-On Account – Define the SSO account and Kerberos rhelm name
- Web Content Filter – Enable AutoFilter, whitelist bookmarks and blacklist web sites. This article provided more details.
Then there is a range of detailed configuration items listed here:
- Allow fingerprint to unlock device
- Allow Account Modification (Supervised Only)
- Allow Cellular data usage for Apps (Supervised Only)
- Allow Host Pairing (Supervised Only)
- Allow Wifi and Airplane Mode on Locked Screen
- Allow Open Documents from managed to unmanaged apps
- Allow Open Documents from unmanaged to managed apps
- Allow over the air PKI Updates
- Allow Airdrop (Supervised Only)
- Allow Find My Friends (Supervised Only)
- Limit ad tracking (Supervised Only)
- Allow apps to autonomously enter Single App Mode (Supervised Only)
- Allow Find my Friends (Supervised Only)
- Allow Cloud Keychain Sync
- Additional AppLock configuration settings
- Lock Screen
- Allow Access to Control Center
- Allow Notification View in Notification Center
- Allow Today View in Notification Center
As I do more testing with iOS 7, I’ll share my experiences and other applicable news on this blog.
Divide is a container solution for Apple iOS and Android devices. Divide is an app that acts as a workspace, or container, that mimics device capabilities while isolated from the rest of the device. This container solution allows information within Divide to be secured and managed separately from the rest of the device.
The latest release of IBM Endpoint Manager for Mobile Devices can also manage endpoints with Divide containers. So you can have the best of both worlds, managing mobile devices with their native management features or users with corporate services within a container.
You will want to have installed the Divide client on your mobile devices and you can request a trial of their enterprise console here.
I’ve documented the steps to integrate IEM with Divide below:
- Select the Setup and Configuration Wizard and open Setup Enterproid Divide Management Extender. Note that you’ll need to obtain an access token by clicking on the link provided. Enterproid sent me an access token for our companies domain name.
- Select Deploy Management Extender for Enterproid Divide and then select Take Action
- Select the server where this will be installed. I chose the same server as my MDM Management Extender. Ensure this server has TCP port 443 access to api.divide.com
- It takes a number of minutes for the appropriate software to be downloaded automatically from IBM’s cloud service and installed. If you specifically define which computers are members of the MDM site, ensure the Divide plugin is included too (see device type plugin explained here)You’re then ready to select Configure Extenders
- Select the Divide Container as shown. Then enter your Divide domain name and access token. I copied the access token into Notepad just to ensure there wasn’t any incorrect spaces or extra characters.
- Finally select Configure Enterproid Divide Management Extender, then the applicable container device and click OK. It will take a few minutes for the configuration to complete.
Once the configuration was complete all containers from the Divide cloud were displayed in the IEM console as shown (along side other Android and iOS devices which are managed too)
If I selected my iPad with the Divide container installed, I was able to perform a number of container controls:
What was nice, is that I can also define Divide polices from with the IEM console too:
I really like the user interface of the Divide client, which is the most critical factor with any container solution. Some container solutions have the reputation for not being that user friendly, so users end up trying to work their way around how they access their corporate email and applications. Which of course defeats the purpose of providing a container in the first place!
This new capability allows clients to both manage devices via traditional MDM (iOS, Android, Windows, Blackberry) and now a powerful container capability. This is on top of managing Windows, Mac, Linux and Unix from the one console.
If you have any queries, feel free to contact me or post a question to our developerWorks forum.
P.S. Article renamed to reflect Enterproid name change to ‘Divide’ (Oct 2013)
IBM Endpoint Manager for Mobile Devices requires a certificate to manage iOS devices – through Apple’s Push Notification Service (APNS). This APNS certificate allows the Management Extender to establish a secure, trusted channel of communication with the iOS devices. This setup is straightforward and is detailed here. Our MDM evaluators guide provides step by step instructions with screen captures. Contact me if you don’t have a copy.
If you’ve installed IEM to manage some devices, you’ll note that for iOS devices you have to install a self signed certificate first. You can remove the requirement for this by installing a well known or trusted certificate from Verisign, Godaddy, Gotrust etc.
The steps to install IEM with a trusted certificate below. I want to acknowledge the great article by Orb Data which provided me some great info, and explained certificates in PEM format.
- Complete Step 1: Deploy the Management Extender Fixlet and Step 2: Obtain certificate to manage Apple iOS devices to install the Management Extender. Save the final APNS certificate as push.cer and place it in a directory on your IEM server, say D:\ManagementExtender\APNS\push.cer. Now this has the certificate covered for IEM communicating with Apple’s APNS service.
- Now for the certificate for device to IEM server communication, we need to create a certificate request that a certificate authority can process. I was using Godaddy to define a certificate for the domain name mdm.darrylmiles.me. On a Mac I used OpenSSL I would run this command:openssl req -new -newkey rsa:2048 -nodes -keyout yourdomain.key -out yourdomain.csr
For my domain name, I entered: openssl req -new -newkey rsa:2048 -nodes -keyout darrylmiles.me.key -out darrylmiles.me.csr
I was able to the use the command illustrated on Godaddy’s web site here.
The result of this command is two files:
- Now on your certificate authority web site, take the text from within your CSR file (in my case darrylmiles.me.csr) and copy this into appropriate request page:
- Once the certificate request was accepted, I downloaded it as shown:
- The ZIP file contained two files gd_bundle.crt and mdm.darrylmiles.me.crt. Both files contained the certificate information in PEM format, ie.—–BEGIN CERTIFICATE—–
Lots of letters/numbers here…
—–END CERTIFICATE—–I renamed the files as follows:
gd_bundle.crt to gd_bundle.crt
mdm.darrylmiles.me.crt to mdm.darrylmiles.me.cer
- I copied the darrylmiles.me.key, mdm.darrylmiles.me.crt and mdm.darrylmiles.me.cer to the IEM server to a directory called D:\ManagementExtender\Cert\
- I then configured the management extender using these settings:
- That’s it. Once the management extender is configured it’s now ready to accept device enrolments. Here are some screen captures of an iOS device being enrolled:
That’s it. IEM is now setup with a trusted certificate. If you have any queries, feel free to contact me or post a question to our developerWorks forum.