Cisco Systems MaaS360 manual Shows the flow of this process

Page 24

Figure 16 Binding Policies to User Groups

With the example configuration shown above, users that belong to BYOD_Employee_Access will get Full_Access_policy pushed to their devices. User will see two profiles installed by ISE and two or three from the MDM. The server will install the MDM payload during the on-boarding process. After that profile has been installed, the device will be issued a check-in request via APNS or GCM. When the device responds to the push notice, it will connect to the MDM where any additional profiles are installed.

Figure 17 shows the flow of this process.

24Integrating Fiberlink MaaS360 with Cisco Identity Services Engine

Image 24

Contents Revised August 6 Page Page Fiberlink MaaS360 Capabilities and Features OverviewCapability Features Fiberlink MaaS360-Key Capabilities Deployment Models Getting Fiberlink MaaS360 Ready for ISE Import MDM Certificate to ISEExporting the MDM Site Certificate with Internet Explorer Grant ISE Access to the Fiberlink MaaS360 API Manage Administrator Account Add Account Add MDM Server to ISE Configure the MDM API on ISE Verify Connectivity to MDM Message ExplanationReview MDM Dictionaries Enterprise Integration DMZFiberlink MaaS360 Cloud Extender Download Cloud Extender Installation Wizard Active Directory/LDAP Integration AD Group Memberships Ownership User Group Restrictions MDM Profiles Create Policies Shows the flow of this process Mobile Client Application-Fiberlink MaaS360 Agent MDM APNS/GCNDevice Ownership User Experience MDM On-boardingMDM Enrollment MDM Enrollment-Terms of Acceptance Enterprise Application Store Pass Code ComplexityInstallation of Maas360 Application Corporate Data Data at-RestCorporate Wipe Forced CoA from ISEVerify Device Compliance End User PortalISE Compliance versus MDM Compliance Action Type Options Device Compliance/Restrictions Device Scanning IntervalsPINLockStatus Manually Updating the MDM ServerManage Lost/Stolen Devices Jailbroken or Rooted devicesRegisterStatus Application Distribution Cisco Applications Jabber, etc Conclusion Disclaimer