fighting for truth, justice, and a kick-butt lotus notes experience.

 
alt

Detlev Poettgen

 

IBM Technote regarding Traveler 9.0.1.18 Feature Run As User and whats in the box in 9.0.1.19 to solve it

 10 September 2017 11:30:00
This week IBM released a new Technote, which explains the "Run as a User" feature introduced with Traveler 9.0.1.18 in detail.
Some customers reported issues after upgrading to 9.0.1.18 or later. The Technote explains how to solve this issues.

You should read the Technote BEFORE upgrading.


IBM Traveler 9.0.1.18 enabled by default a feature that allows Traveler to "Run as a User" instead of as a server. This feature resolves several long standing issues with accessing the user's data as the server ID, including:

          Preventing event notices and automated responses from being sent “from” the Traveler server ID (they are sent “from” the user ID instead)
          Preventing the server ID from being assigned as the owner of the mail profile when there is no owner defined.
          Honoring access controls on the mail file and corporate lookup for the user.

The last point above may cause sync issues for mobile users. If the access controls are inadvertently set to values that restrict individual users, but do not restrict the Traveler server, then users that could sync when running as the Traveler server ID might not be able to sync when running as their user ID.

Note that the Traveler administrator can disable the Run as User feature by setting the notes.ini value NTS_USER_SESSION=false on all Traveler servers and restarting the servers. This may be a quick way of restoring sync capability to the few affected mobile users with restrictive access control settings.
However, it is not recommended because it is a global setting, so all users will lose the benefits of Run as User when it is disabled.


Please, read the Technote!

Link to IBM Technote: How to resolve synchronization issues that start after upgrading to IBM Traveler 9.0.1.18 (or higher)


The Technote discripes a new feature in Traveler 9.0.1.19, which will help to the solve the issue I posted in an earlier Blog entry: Traveler 9.0.1.18 needs Editor access under Maximum Internet Access ACL settings

Image:IBM Technote regarding Traveler 9.0.1.18 Feature Run As User and whats in the box in 9.0.1.19 to solve it


For Traveler 9.0.1.19, this field is reflected in the 'show user' and 'dump user' output in the ACL section:

Mail File Replicas:
  [CN=Tserver/O=Torg, mail/johndoe.nsf] is reachable.
         ACL for John Doe/Torg:  Access=Manager,No access Capabilities=create,update,read,copy Missing Capabilities=delete
          ACL for Tserver/Torg:  Access=Manager Capabilities=create,update,read,delete,copy Missing Capabilities=none

Also, Traveler 9.0.1.19 counts the number of times it has read an ACL with the “Maximum Internet name and password” field set to each of its values, and prints them in the 'systemdump' output in the Statistics section:

          DCA.ACL_InternetLevel.NTS_ACL_EDITOR = 6
          DCA.ACL_InternetLevel.NTS_ACL_NOACCESS = 1

If set to No Access, and another user sends a new email to this user's Inbox, Traveler fails during prime sync.

Symptom: Console message


Traveler: SEVERE John Doe User ID CN=John Dow/O=Torg on device prime sync failed to connect to mail database mail/johndoe.nsf on server CN=Tserver/O=Torg. Either the user or the IBM Traveler server does not have sufficient rights to access this database. Exception Thrown: com.lotus.sync.caf.auth.NTSAuthException: ESM_AUTH_007

If set to Reader, and another user sends a new email to this user's Inbox, Traveler can sync the received document. If the user tries to send a new email (or a reply to the received email) from the device, that fails writing into the user's mail database.

Symptom: Console message


Traveler: SEVERE John Doe Document(null) Subject of 'Re: Dear John Doe' could not be synchronized from the device to the server mail database as ACL permissions for this user insufficient for this create operation.

Likewise, if another user sends an invitation it is synced to the device. However, if the user tries to send an accept notice from the device, that fails trying to write the accept notice into the user's mail database.

Symptom: Console message


Traveler: SEVERE John Doe Document(null) Subject of 'Tentative: Invitation: Doe reunion (Sat 09/02/2017 08:00AM, Deer Park)' could not be synchronized from the device to the server mail database as ACL permissions for this user insufficient for this create operation.

Recommended fix
: For Traveler 9.0.1.18, the user will have to modify his ACL to change the “Maximum Internet name and password” setting to a value of Editor or above.

Traveler 9.0.1.19 includes an enhancement to the Run as User feature which allows Traveler to run as the Traveler server for just those users that have the “Maximum Internet name and password” ACL field set to a value lower than Editor, in order to allow those users to sync without access errors. Thus Traveler will override the Run as User feature on a per-user basis, based solely on the “Maximum Internet name and password” setting for each user. This enhancement is enabled by a new notes.ini setting, NTS_USER_SESSION_OVERRIDE_INTERNET=true, and it is set to true by default.

Symptom: NTSActivity log entry (if the user session is being overridden):


[09/05 11:27:13.287] FINEST PS-7fc9e44e0700 Tom User1 DispatchThreadData.getNotesSessionUser#849 Overriding user session due to ACL settings


If the Run as User function is being overridden for a user, that user will lose the benefits of the Run as User function. To restore those benefits, the user will have to modify his ACL to change the “Maximum Internet name and password” setting to a value of Editor or above.

Traveler caches the user's ACL in memory, for performance reasons. If the user updates the ACL setting, the cache entry should be cleared for that user to ensure the new setting will be recognized by Traveler. The Traveler administrator can clear the user cache entry for a user by issuing Traveler command:

tell traveler clearcache user


The next time the user syncs, the cache entry will be refreshed using the ACL settings at that moment.



As already mentioned in my older post I created a small database QuickFix for Traveler , which will query the mail databases of all Traveler users and shows some consolidated database properties (Size, Quota, Template, ACL, Owner, Soft Deletions, Max. Internet Access, #Documents).
From there you can select the databases with Max. Internet access lower then Editor and it will fix it for you.

If you want to use this database, too - just drop me an Email or leave a comment with your mail address. I will send you the QuickFix for Traveler app.

IBM Traveler 9.0.1.19 available

 6 September 2017 20:37:33
Today IBM released a new Traveler version called 9.0.1.19 (Build: 9.0.1.19 201708291200_20).

Image:IBM Traveler 9.0.1.19 available

9.0.1.19 brings this new changes:
 
 
  • Support for MS SQL Server 2016 Enterprise Edition.
  • Updated APNS Certificates with expiration 8/1/2018.
  • Improvements for the Run as User Feature.

Fixlist:
APAR # Abstract
LO92524 Sync performance impacted if syncing a large repeating calendar event.
LO92525 Reply notice sent from an FYI recipient for a calendar event when processed on a mobile device.
LO92557 Cancelled event may appear ghosted after the cancel on the iOS Native Calendar application.
LO92638 Add invitee from native iOS Calendar application and the recipient may be added twice to the meeting.
LO92645 Error reading some policy documents when Run as User feature is enabled.
LO92713 User unable to sync when sync request is internally routed from an older server to a 9.0.1.18 or later server.
LO92728 DB Connection exception during migration from Derby to an Enterprise database.
LO92783 Android user incorrectly denied access if specific set of administration settings are enabled.
LO92829 Handle comma character in display name for mail sent from an Outlook client.
LO92881 High CPU may be seen on the database server for one particular SQL query.
LO92897 Update APNS Certificates, new expiration is 8/1/2018.







Note: IBM Traveler 9.0.1.19 does not include a database schema update.

You can download the update as usual on IBM FixCentral.

An IBM Traveler 9.0.1.19 full installation package, which will be available by September 18, 2017, can be used to upgrade any previous Traveler server or to install a new environment.


Announcing - Lets Encrypt for Domino - Just Do SSL

 23 August 2017 16:16:43
To enable HTTPS on your website, you need to get a certificate from a public Certificate Authority (CA). Let’s Encrypt is such a CA, which offers free trusted certificates. The only limit is that the certificates expire after 90 days. But you can renew them as often as you like.

There are several clients around to retrieve a certificate from Let’s Encrypt. But none of them offer a consistent way to automate the process, when using Domino as your HTTP-Server. Either the client tool is only available for Linux, or you have to install additional Perl/Python interpreter on your Domino server machine to run scripts. And then there is the Domino properitary keystore format :-(

We at midpoints were looking for a solution to get Let’s Encrypt certificates working together with Domino as close and automated as possible.
So we started the midpoints Let’s Encrypt 4 Domino project for internal use.

Let’s Encrypt for Domino == Let’s Encrypt 4 Domino == LE4D (spoken as lead)


After we got it working, we decided to make the tool available for free, because the Let's Encrypt certs are for free and so midpoints LE4D should be free, too. SSL is important and you should use it.

Yes, you can get  it for free!

Image:Announcing - Lets Encrypt for Domino - Just Do SSL

What midpoints LE4D will do in detail?

The short answer - A lot!

In more details:

- Creates a Let's Encrypt User and Domain Keys
- Creates and puts Let's Encrypt Challenge on your server
- Creates and sends the Signing Request CSR to Let's Encrypt
- Downloads the certificate
- Downloads the Key Chain
- Generates the Domino Key Ring files using the IBM KYRTOOL
- Merges the certificates and chain into the Key Ring
- Backups the generated certificates
- Restarts the HTTP Task
- Periodic Renewal of certificates, when needed

All you will need is our midpoints LE4D template.
Create a new application from the template, create a configuration for your domain and start an agent ( the agent can later be started on a scheduled basis using a program document to renew the certificates).


Interested? Then get your copy of midpoints LE4D today for FREE.

https://www.midpoints.de/LE4D


Ulrich Krause aka eknori and myself digged into the Let's Encrypt API to make LE4D possible. Thank you Ulrich that we together got it working!

And we would like to thank Let's Encrypt and the Let's Encrypt community to provide their great Let's Encrypt Cert service.

Old IBM Apple APNS Push Certificate of Traveler 9.0.1.15 used for Verse expired on 12.08.17

 11 August 2017 12:35:52

If you are still running IBM Traveler version 9.0.1.15, have in mind that the Apple IBM Push Notification Certificates for IBM Verse and ToDo for iOS will expire tomorrow (12th Aug. 2017).

You will may see error messages like this on the console after 12th Aug. 2017:

06.02.2017 11:59:08   Traveler: SEVERE  *system Couldn't send message after 3 retries, Message(Id=692311; Token=8C720F7F9B96D30C184445840EF0D0D925BC8C269618C7523E0B98EE9B61A03E; Payload={"aps":{"badge":14,"content-available":1,"alert":"E-Mail von test.de","sound":"v)"},"LGUID":"2068982","FLAGS":"1001","account":"1"}) Exception Thrown: javax.net.ssl.SSLException: Received fatal alert: internal_error


To solve it you will have two options:

1. Option: Move on to Traveler 9.0.1.18  (Recommended)


2. Option: Stay on 9.0.1.15 (for what ever reason) and only change the P12 certificate files.

You can replace your existing certs and use this three files, which I copied from my Traveler 9.0.1.18 server. The certs are valid until 8th March 2018.

PushAPNSAppleVerseProduction_validto_20180308.zip

Extract the zip-file and copy the three P12-files to your Traveler server: notes_data/traveler/cfg  and restart your Traveler server


You can check, if the Push Notifications are working and how long the certs are valid by executing this command:

tell traveler push cmstatus


It should look like this:

> tell traveler push cmstatus

...
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: No connection for MaaS360 Production to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_MAAS360_PRODUCTION
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: No connection for Third Party Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_THIRD_PARTY_DEVELOPMENT
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: No connection for Third Party Production to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_THIRD_PARTY_PRODUCTION
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: -- Certificate Validity Dates (Fri Aug 11 12:31:24 CEST 2017) --
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: D:\Progs\domino\data\traveler\cfg\PushAPNSAppleToDoProduction.p12 is valid from Mon Feb 06 20:34:55 CET 2017 to Thu Mar 08 20:34:55 CET 2018.
[14B0:002E-0D08] 11.08.2017 12:31:25   Traveler: D:\Progs\domino\data\traveler\cfg\PushAPNSAppleVerseCitrixProduction.p12 is valid from Mon Feb 06 20:38:01 CET 2017 to Thu Mar 08 20:38:01 CET 2018.
[14B0:002E-0D08] 11.08.2017 12:31:26   Traveler: D:\Progs\domino\data\traveler\cfg\PushAPNSAppleVerseIBMProduction.p12 is valid from Mon Feb 06 20:41:08 CET 2017 to Thu Mar 08 20:41:08 CET 2018.
[14B0:002E-0D08] 11.08.2017 12:31:26   Traveler: -- APNS-DelQ --
...


Tesla Model 3 - es wird die Autobranche für immer verändern

 31 Juli 2017 13:23:20
Sehr lesenswerter erster Tesla Model 3 Testbericht:

Image:Tesla Model 3 - es wird die Autobranche für immer verändern


... Ich habe es nur sehr kurz fahren dürfen, aber ich bin so gut wie jedes andere reine Elektrofahrzeug auf dem Automobilmarkt gefahren und kann mit Sicherheit sagen, dass das Model 3 keine Konkurrenz hat.

Doch es ist mehr als das. Obwohl es ein kleiner Viertürer ist und der Markt sich allmählich von dieser Art Fahrzeug entfernt, um sich auf Crossover-Fahrzeuge und SUVs zu konzentrieren, wird niemand in diesem Auto sitzen und es nicht besitzen wollen. Das Model 3 erweckt sofort Begierde, und die Lust auf das Auto bleibt. Das verändert wirklich alles.

Alles, was Tesla jetzt noch machen muss, ist eine halbe Million dieser Autos zu bauen.

via: http://www.businessinsider.de/ich-bin-das-tesla-model-3-gefahren-es-wird-die-autobranche-revolutionieren-2017-7


Wer mich persönlich kennt, dem werde ich vermutlich inzwischen schon mit meiner Begeisterung für Tesla auf die Nerven gehen.
Ich war so verrückt, das ich mein Tesla Model 3 am 31.03.2016 um 10:00 Uhr deutscher Zeit schon vor dem Live-Event ungesehen vorbestellt habe.

Elon Musk beginnt nun 16 Monate später zu liefern und ich werde vermutlich bis in die Mitte 2018 auf mein Model 3 warten. Ich weiß nun, was ich bekommen werde und freue mich darauf.

Image:Tesla Model 3 - es wird die Autobranche für immer verändern

Im Gegensatz zu den deutschen Automobilherstellern hat Tesla eine Vision und setzt diese auch wirklich um. Anstatt auf den Staat zu warten und auf Förderungen zu hoffen, macht Tesla es selbst. Das beste Beispiel ist hier das Tesla eigene Supercharger-Netzwerk, das es schon heute ermöglicht mit seinem Model S oder X auch lange Strecken quer durch Deutschland zu fahren.  

Für mich ist das Tesla Model 3 das iPhone der Automobilindustrie!


Vor 10,5 Jahren wurde ich mit meiner Begeisterung für das erste iPhone von meinen Kollegen sehr belächelt. Die damaligen Marktführer (Nokia, Blackberry, ...) führen inzwischen ein Nischendasein und haben Apple komplett unterschätzt.
Für mich ist die aktuelle Situation und Stimmungslage im Automobilsektor sehr ähnlich wie vor 10 Jahren im Handy-/ Smartphone Umfeld.

Die Zeit ist Reif für Innovationen und die alten Platzhirsche halten zulange fest an Althergebrachtem und finden nicht den Weg aus der Sackgasse.

Ich drücke Tesla die Daumen, das das Hochfahren der Produktion wie geplant funktioniert und die Qualität darunter nicht leidet.
In einem Jahr werde ich hoffentlich in meinem Model 3 sitzen und wir werden sehen, was bis dahin passiert ist. Es wird auf jeden Fall ein spannendes Jahr.

Hash-Tag: #EnttäuschterUndVera***terVolkswagenKunde






Traveler 9.0.1.18 needs Editor access under Maximum Internet Access ACL settings

 13 Juli 2017 15:10:19
A customer called me today, that he has trouble with a few of his Traveler users.
After updating IBM Traveler to v9.0.1.18 users are no longer able to sync and the deletion of these Traveler devices (using the traveler delete command) is not working any more.

When trying to delete the Traveler user using:

tell traveler delete * Detlev Poettgen


He gets this errors on the console:

Traveler: SEVERE  Detlev Poettgen[*] NotesException Notes error: You are not authorized to perform that operation
                          id=4000 occurred trying to access device profiles Exception Thrown: Notes Exception(4000) : Notes error: orized to perform that operation
Traveler: SEVERE  Detlev Poettgen[*] NotesException Notes error: You are not authorized to perform that operation
                         id=4000 occurred trying to access device security profiles Exception Thrown: Notes Exception(4000) : Note not authorized to perform that operation



IBM enabled the Run-as-User function with Traveler 9.0.1.18 and the way Traveler will access the users mail database:


Starting with IBM Traveler 9.0.1.18, the new run as user feature will now be enabled by default. When running as the user, the Traveler server will access the user's mail file as the user ID instead of the server ID.

This feature resolves several long standing issues with accessing the user's mail file as the server ID, including:
  • Honor ACL controls on mail file and corporate lookup for the user.
  • Prevent event notices and automated responses from being sent from the server ID.
  • Prevent the server ID from being assigned as the owner of the mail profile when there is no owner defined.

Important:
For run as user feature to function properly, the Traveler server must be listed as a trusted server in the user's Mail Server document.


So we first checked, if the Traveler server was listed as a Trusted Server in the mail server document.
That was all fine and other users located on the same mail server were able to sync.

So when looking at the ACL of the users mail database, we found really quick the reason:

Image:Traveler 9.0.1.18 needs Editor access under Maximum Internet Access ACL settings

For the users mail database the Maximum Internet name and password access was set to Reader.
After changing it to Editor, the user was able to sync again and a traveler delete command works again.


Update 17.07.2017:


During the last few days I got asked, how you can check, if all your Traveler users are having set Maximum Internetname and password access to Editor.

As far as I know, there is no out-of-the-box solution available from IBM. The Admin-Client will not show this ACL setting in a view and catalog.nsf will not contain this setting.

So I created a small database QuickFix for Traveler , which will query the mail databases of all Traveler users and shows some consolidated database properties (Size, Quota, Template, ACL, Owner, Soft Deletions, Max. Internet Access, #Documents).
From there you can select the databases with Max. Internet access lower then Editor and it will fix it for you.

If you want to use this database, too - just drop me an Email or leave a comment with your mail address. I will send you the QuickFix for Traveler app.





 



IBM Verse for iOS 9.4.0 updated pre-configuration settings

 26 Juni 2017 15:30:05
Last week IBM released a new version 9.4.0 of the IBM Verse for iOS App.

IBM Verse for iOS v9.4.0 had been completely rewritten and was the first feature update since a few months.

Under the hood IBM changed the way to pre-configure the app by an EMM/MDM solution. The Verse app now supports the open AppConfig Community standard to push setting like a server URL or an user name to the app.

Verse for iOS supports custom managed configuration, which allows the MDM administrator to preconfigure many Verse for iOS settings. Any setting defined using the MDM takes precedence over a similar setting or policy defined at the Traveler server.
Setting custom app configuration will vary by the MDM soltution you are using. All MDM providers should support the concept of Apple managed configurations using custom keys and value pairs.

Now it is possible to define most of the user setting within the app and to lock some of these settings. I will post an additional bloentry in a few days, when IBM will have published the AppConfig documentation.

To pre-configure Verse you will need to set in minimum these four settings:
Key Data Type Value  (Example) Comment
appConfigOnly Boolean true       (1*) Will enable the AppConfig Settings within the app and will ignore Maas360 & MobileIron SDK
serverType String onpremises Where is your server located?
onpremises
cloud
choice     (asking user)
serverURL String https://mobile.comp.com/traveler Provide the hostname or a fully qualified URL to your company's Traveler server. Only provide this value if using ‘onpremises’ as the server type.
user String IggyPop Login user id. You should be able to use placeholders depending on your MDM solution



Hint: The key names are case sensitive !!!

(1*)  Depending on your MDM solution you can use "true" / "false"  or "1" / "0" as Boolean Values

Using our own MDM solution midpoints mobile.profiler a simple pre-configuration of Verse for iOS looks like this:

Image:IBM Verse for iOS 9.4.0 updated pre-configuration settings

Thank you at this place to Bill Wimer (IBM) and the Traveler Dev team for the AppConfig integration.
Well done and I will post a few more new settings when the AppConfig documentation will be public.

Update 27.06.2017:
IBM released the AppConfig for Verse documentation yesterday evening. Check out: http://www-01.ibm.com/support/docview.wss?uid=swg27049934


IBM Traveler 9.0.1.18 available bringing one important change

 15 Juni 2017 21:56:11
Today IBM released a new Traveler version called 9.0.1.18 (Build: 9.0.1.18 201706131301_20).

Image:IBM Traveler 9.0.1.18 available bringing one important change

9.0.1.18 brings this new change:
 Traveler Server Run as User

Starting with IBM Traveler 9.0.1.18, the run as user feature will now be enabled by default. When running as the user, the Traveler server will access the user's mail file as the user ID instead of the server ID.

This feature resolves several long standing issues with accessing the user's mail file as the server ID, including:
  • Honor ACL controls on mail file and corporate lookup for the user.
  • Prevent event notices and automated responses from being sent from the server ID.
  • Prevent the server ID from being assigned as the owner of the mail profile when there is no owner defined.

Important: For run as user feature to function properly, the Traveler server must be listed as a trusted server in the user's Mail Server document.

To disable run as user, set this notes.ini parameter: NTS_USER_SESSION=false


Fixlist:
APAR # Abstract
LO90096 Info update continues to be ghosted on mobile device after the event is processed.
LO91797 Empty comments displayed on iOS native Calendar application when event processed in iNotes.
LO91836 Invalid this and future reschedule generated by iOS native Calendar application.
LO91875 Ghosted event not displayed on mobile device.
LO91956 Maill attachment does not sync to mobile device when contains angle brackets < and >.
LO91997 IBM Traveler web administrator may show iOS Verse 9.4 device as not supporting security capabilities.
LO92010 Better handling of special character in mail header fields.
LO92080 Ignore a reply message with out a valid action defined.
LO92085 Hard delete processed notices vs soft delete to prevent from filling up trash folder.
LO92209 Second meeting room may be lost if event updated from mobile device.
LO92210 Unable to turn off iOS Verse application password via Domino policy document setting.
LO92257 Two instances of a previously processed event may show on mobile device if the daylight savings rules change for the time zone.
LO92303 SQL Syntax error adding index TSGUDTSTAMPCREATEIDXSQL9 on DB2.



Note: IBM Traveler 9.0.1.18 does not include a database schema update.

You can download the update as usual on IBM FixCentral.

An IBM Traveler 9.0.1.18 full installation package, which will be available on Passport Advantage on June 21, can be used to upgrade any previous Traveler server or to install a new environment.

Call for Abstracts DNUG Conference 2017 in Berlin

 3 April 2017 14:01:25
Die nächste DNUG Konferenz findet vom 31.05. bis 01.06.2017 in Berlin statt!  

Image:Call for Abstracts DNUG Conference 2017 in Berlin


Wer sich als Referent aktiv einbringen möchte, hat hierzu die Chance einen Abstract einzureichen.
Die einzelnen Tracks werden durch die einzelnen DNUG-Fachgruppen organisiert.

Ich selbst bin gemeinsam mit Jürgen Bischof Mitverantwortlich für die DNUG-Fachgruppe Mobile und würde mich über Abstract zu Mobile-Themen freuen.

Was mir hierbei am Herzen liegt:

Die DNUG ist eine User Group und lebt vom Austausch, der Diskussion und dem Networking untereinander. Daher würde ich mich freuen, wenn nicht nur die üblichen bekannten Sprecher Abstracts einreichen, sondern auch neue Gesichter sich motiviert fühlen, sich einzubringen.
Jeder hat bestimmte Herausforderungen oder Aufgaben bei sich im Unternehmen gemeistert und Lösungen gefunden, die sich im Alltag bewährt haben.
Warum diese nicht teilen und im Rahmen eines DNUG Vortrags vorstellen? Andere stehen in der Regel vor den gleichen Herausforderungen - die DNUG ist die Plattform diese Erfahrungen untereinander auszutauschen.

Wenn jemand also zu Mobile-Themen (IBM Traveler, Enterprise Mobile Device & Application Management, interessante Mobile Inhouse Projekte, Best Practices, ...) einen Vortrag halten oder an einer Diskussionsrunde teilnehmen möchte, kann sich gerne bei mir melden oder einfach Online bis zum 10.04.2017 den Abstract einreichen:

http://dnug.de/dnug44-call-for-abstract/

Wer selbst keinen Vortrag halten will oder kann, aber gerne ein Thema behandelt sehen möchte, kann mir gerne auch einfach einen Themenvorschlag per Mail schicken oder hier einen Kommentar hinterlassen. Ich würde dann schauen, ob wir hierzu einen Referenten in der Community finden.

IBM Traveler 9.0.1.17 fixing the issue introduced with 9.0.1.16

 21 März 2017 17:37:58
Today IBM released a new Traveler version called 9.0.1.17 (Build: 9.0.1.17 201703170414_200).

Image:IBM Traveler 9.0.1.17 fixing the issue introduced with 9.0.1.16

It’s a maintenance release that provides APAR fixes - no new features

Fixlist:

APAR # Abstract
LO90889 Invitee status not correct on mobile device if the invitee response is received in a non-syncing folder.
LO91550 Multiple ghost entries possible if adding invite to event that has outstanding updates pending.
LO91723 User may stop recieving updates to mobile device after mail server restarted and there is no backup mail server.
LO91733 Subject of mail replied to/forwarded from Windows 8 device may display incorrectly.
LO91762 IBM Traveler server may change case of Domino domain to all lower case when sending mail.
LO91770 Subject of new mail sent from Windows 8 device may display incorrectly.
LO91819 User may not be able to sync data to mobile device when the user's mail file name contains special characters.
LO91870 Wipe data option may be greyed out for iOS Verse client.



Note: IBM Traveler 9.0.1.17 does not include a database schema update.

You can download the update as usual on IBM FixCentral.

An IBM Traveler 9.0.1.17 full installation package, which will be available on Passport Advantage on 24th March., can be used to upgrade any previous Traveler server or to install a new environment.


Archive