Daniel Nashed 15 November 2016 19:14:58Traveler 188.8.131.52 has been released with some important fixes and also changes. The Release documentation has some interesting details.
Here is the extract from the release documentation with some comments.
"Device wipe is no longer an option for iOS 10.x devices as support was dropped by Apple. You can still use the Wipe Traveler Data option."
For security reasons Apple disabled wipe over ActiveSync which is understandable. Before that change every server could wipe any device connected via ActiveSync.
With this Apple side change Traveler could not delete the device any more and the status from the device was not interpreted correctly by the server.
Traveler does now check if the device still supports the wipe (running iOS earlier than 10.x) and does only allow the Data Wipe over ActiveSync if the full wipe is not supported on the device.
"Yellow status message if the IBM Traveler server is not listed as a Trusted Server for an end user's mail server. This is required for future security and feature enhancements planned for 2017. The status message will include information about how to correct."
Sounds like IBM is planning a bigger change in 2017 for Traveler. I am curious what this higher security requirements are needed for. Trusted Servers are a quite high requirement which allow the Traveler servers to fully authenticate as any user on the mail server. It's much higher than just granting manager access to an individual mailfile.
I have removed the Trusted Servers entry on my mail-server but I did not yet see the warning.
"Database schema updates to improve data integrity.
Tablerepair tell command to support the above schema updates. A warning message will be displayed at startup if any of the schema updates were not applied with instructions to run the tablerepair command. The server will continue to function properly if no action taken.
NOTE: IBM Traveler 184.108.40.206 does include a database schema update. Action may be required if you manually manage your database schema (this is not common). If you use auto schema updates (default behavior) there is no action required. See Updating the Enterprise Database for more information (http://www.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/UpdatingTheEnterpriseDatabase.dita)"
So this is an important information. This new version requires a schema change. If you are running stand-alone that should not cause any issues.
If you have automatic schema update enabled the schema update should also happen automatically.
And if you are switching from manual schema update to automatic schema update you should be careful. There is one ARPA fixed for DB2 and you should be aware of the default schema name differences for manual and automatic schema configuration.
I guess with this schema change the issue has been discovered and the fix is that the NTS parameter with the schema name will be automatically set.
(See -> http://www.ibm.com/support/docview.wss?uid=swg1LO90497 for details).
The fix-list contains some other important fixes! Check the fixlist link below for details.
My server is already updated but I had not much time to test.
IBM Traveler Fixes 220.127.116.11
IBM Traveler 18.104.22.168 Server Release Documentation
- Comments