Great news! The Traveler administration database now provides administrators with the option to set default device preferences and security settings. This is awesome news as it does reduce the need for policies in many cases. This is especially important in cases where the Traveler server is located in a different Domino domain than the mail servers.
I am truly stunned what technology can achieve those days. Just discovered that there is now the possibility to display your Google contacts’ birthdays within the Google calendar. Check out the ‘more’ section in this document.
Combine above with the new 8.5.1 feature that allows for calendar feeds to be downloaded for offline use:
Now syncronise your mail file with your mobile device using Traveler. Within a flash you got all your Google Calendar entries replicated to your mobile device using pure Lotus technology.
In case you are planning to upgrade to Lotus Traveler 8.5.1, ensure that you are replacing the index.html file in the <Domino data directory>\domino\html\traveler folder after the upgrade. The new file is provided as index_template.html and is part of the installation.
Without updating the index.html file, mobile users trying to download the updated phone client would still be getting the 8.5 version.
You can confirm that the new index.html page is in place when the Nokia Series 60 entry has been split up into a 3rd Edition and 5th Edition client as shown below.
One of my previous posts describes that there are two different ways policies are applied to traveler users.
When Traveler policies are applied, the content of the settings document is being copied over into a profile document of the user’s mail file.
The Traveler server is using the Traveler’s Cluster Cache database (ntsclcache.nsf) to look-up the location of the user’s mail file.
The following error could be raised when policies can not be applied:
Notes Traveler: SEVERE [SYSADMIN] Internal Error: Debug Data: Error on UpdateProfileFromPolicyError: Database ‘mail/mdemo2.nsf’ on ‘CN=MAIL/O=Organisation’. Error(227 )=Invalid or nonexistent document
There might be an issue with the ntsclcache.nsf. Just open the database, remove the entries for the affected user. Restart the Traveler task and try applying the policies again manually.
In my case the mail file was located on a 7.0.3 server in a different domain, hence I had to issue ‘Tell Traveler Policy Update MDemo2‘
The command syntax for the deletion of users has been extended for version 8.5 of Lotus Traveler.
Use
‘Tell Traveler Delete <Device> <User>‘
instead of using
‘Tell Traveler Delete <User>‘,
whereas Device refers back to the Device ID of the mobile phone. It can be replaced by a * wild card, indicating all devices.
When using the delete command, bear in mind that the name of the user or device must not contain white spaces. Hence the short name of the user has to be used.
It is also important to note that the user to be manually removed from the Traveler database must exist in one of the directories of the Traveler server in order to resolve the short name.
