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.
Symptom:
After removing a server from the Domino domain, Domino Domain Monitoring (DDM) is still attempting to pull monitoring data from the decommissioned server, even after it has been removed from the collection hierarchy.
Error connecting to server Server/Organisation: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
Unable to replicate with server Server/Organisation: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
Solution:
Open ddm.nsf on the collection server. Select View -> Go to … while holding <SHIFT> and <CTRL>, select the ($vwStatus) view and remove all documents that are referencing the previously removed server.
Restart the event task in issuing ‘tell event quit’ and ‘load event’ on the server console.
Only just realised that IBM has gone through the full trouble in order to not only provide us with an easy way to push location, but also Eclipse preference settings to the client via policy.
While I wouldn’t necessary pronounce that it was worth the wait, while applying the workaround in Lotus Notes and Domino 6 to 8, it’s definitely a feature that has been waited for a long time.
