How To
Summary
This page will give you the base necessary information for opening a ticket relating to Android Secure browser.
Steps
- Account: Account Name
- Issue: Brief description of the issue
- Error: Any error message received
- Details: An in depth description of the issue that you are experiencing.
- What are you trying to do, versus what it is that you are experiencing in our system.
- Are you able to replicate the issue? If so, how?
- T/S: A detailed step by step process of any steps taken to troubleshoot an issue.
- This should include the steps taken as well as the result of these steps.
- Username: Portal username of device being troubleshot
- Device Name: Portal device name of device being troubleshot
- Make/Model: Make and model of device being troubleshot
- OS Version: Operating system version of the device
- Agent version: Version of the MaaS app installed on the device
- MDM Policy: Policy assigned to device being troubleshot or involved in the issue
- Persona Policy: Persona Policy assigned to the device being troubleshot or involved in the issue
- Browser Policy source: Which policy contains the information for the browser policy? MDM? Persona?
- Browser version: Version of the Browser Agent app installed on the device
-
Gateway: Are you using a Gateway? Rover, MaaS, None?
-
Number of affected devices : To determine the impact of the issue.
-
Approx. time of the issue : This will help the R&D team to locate the issue on the logs.
- Permission to Enroll: A Yes or No on whether we have the permission to enroll our test device to your environment
- Enrollment credentials : If the above is Yes, then please provide the test credentials to enroll the test device.
- Replicated?: Has the issue been replicated in another browser?
- Device Logs: Attach device logs from the device being troubleshot or involved in the issue
- Logs must be taken including the time when the issue happened.
- <link to collect Android device logs to be included>
- Browser Logs: Attach Browser logs from the device being troubleshot or involved in the issue
- Logs must be taken including the time when the issue happened.
- <link to collect Android Browser logs to be included>
- Gateway Logs (if applicable) : If you are using a Gateway , attach gateway logs.
- Logs must be taken including the time when the issue happened.
- <link to collect Gateway logs to be included>
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"Component":"MaaS360 Android Browser","Platform":[{"code":"PF003","label":"Android"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
15 March 2019
UID
ibm10871288