LO82432: ANDROID CLIENT MAY NOT BE ABLE TO GET OUT OF BANNED STATE.

APAR status

• Closed as program error.

Error description

• Android client can be banned if the user does not enable the
  Device Administrator when configuring the client. Normally user
  would get out of this state by enabling the Device
  Administrator. If the user instead re-installs or re-configures
  the client then they can get stuck at inital config step.
  Fix allows the device to get past the client upgrade check in
  this scenario and proceed to step that enables Device
  Administrator.
  

Local fix

• Traveler admin can delete the users security record via Traveler
  tell command.
  

Problem summary

• Customer reported one scenario where an Android device may get
  stuck in a banned state.  This appears to happen when the end
  user initially declines to allow the security administrator run
  on the Android device, then later uninstalls and re-installs the
  Traveler client.
  

Problem conclusion

• The Notes Traveler server has been updated to ensure this
  unusual registration path is accepted.
  

Temporary fix

• This fix is included in 8.5.3 UP2 IF8, 9.0.0.1 IF8 and 9.0.1 IF7
  and will be included in any future releases.
  
  For the latest available Notes Traveler maintenance releases see
  this article:
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LOTUS NOTES TRA

• Fixed component ID

  5724E6204

Applicable component levels

• R853 PSY

     UP

• R900 PSY

     UP

• R901 PSY

     UP