Uh Clem's Admin World

My previous post mentioned some issues (read bugs) I encountered with DWA8 Contact List.   Here are the details (btw... I'm using 8.0.2 Domino and mail template):

1) The biggest user complaint is that it does not support selecting a group name to start a group chat.  The "chat" option is greyed out.  Tech Support did say this is a bug and they will get me an SPR.  In the meantime they offered a workaround to open a 1-to-1 chat then invite others.  Yeah....right.
2)  The DWA8 Contact List does not support nested public groups.  Oh you will get the names of the users in the sub-groups, but they won't be in alphabetical order.  It will list the users of the first sub-group first, then the second sub-group, and so on.  This is quite confusing for the user when the list are long.
3) The up/down scroll of the contact list is much slower than DWA7's Contact List.  It will pause for several seconds when retrieving the next part of the list.

I am now 60% complete on my client roll out.  This is a one month project to upgrade all users from their 7.x  Notes & DWA to 8.0.2.  The mix is about 1/3 full client and 2/3 DWA clients with under 1000 users in 16 cities.  I must say my rollout is going quite smoothly (knock on wood).

For the DWA upgrades it is a simple convert task that is scheduled on the server to run overnight.  I feed it a file that has a list of the mail files to be converted.  For the full clients I am using the upgrade by email feature built into the Domino directory.  I simply point them to the upgrade image on their local file server.  

I decided to roll out the 8.0.2 standard client using the notes.ini setting "enable_early_authentication=0" instead of the 8.0.2 CCH1.  There was no way to get users from 7.x to 8.0.2CCH1 in one step.

Issues So Far
The full client has had very few issues.  The biggest issue is slowness on laptops with only 512mb RAM, which we plan to address through various means.  Also when the new mail file design is replicated locally, the user may get some errors if they are accessing their local mail file while the design is replicating.

The DWA issues have been mostly about Sametime IM issues.  This is mainly due to the fact that by default DWA users will get the DWA Contact List which has very few IM features, and some bugs.   Instead I have switched the DWA users to use the Sametime Connect for Browsers, which is more stable and has more features (like group chat).   This setting is in the server config doc under the DWA tab in the "Instant Messaging" and disable "Prefer DWA8 Contact List".

As I roll out the Notes 8.0.2 client to users they are discovering the great feature of the user info pop-up when you hover over a name in the Sametime contact list.   Some are discovering their own info is wrong, so we are getting requests all of a sudden to update user's contact info in the Notes directory.   I did not anticipate this unexpected user need.

Some of the user contact info we updated a day ago, but the new info was not appearing in the ST contact list pop-ups.  A user can right-click on a name and select "Refresh Person Info" to force the update.  But my question is why hasn't the server performed the update after a day?  What is the trigger for the server to refresh all this info on its own?   Is it a ST server restart, or what?

Got an email from IBM Tech Support with a link to their ftp site to download the Notes 8.0.2 client CCH1 hotfix.  This hotfix supposedly fixes the hang on startup and maybe a few other SPR's I blogged about.

Bad news is that you will have to contact tech support to get it.

So my testing of DWA 8.0.2 has gone pretty well, and I'm moving forward with deployment.   I blogged about a bug with nested groups in the Sametime Contact List here.

But I have run into another bug that might be a little more troubling for the user.    Apparently the use of the up/down keys to navigate the inbox do not work if you have both the preview pane open, and logged into Sametime.   THIS one is going to be really annoying to my users.  I didn't think this was a common method for inbox navigation.  I would have guessed that users would use the mouse more.  But I've been given feedback that the up/down keys are used quite a lot.  Go figure.

This bug has been reported as SPR XMXL6XCA5D.   They could not give me a timetable as to when they were going to address this bug.  If you want this fixed sooner rather than later open a PMR with tech support and subscribe to this SPR, and tell them this is impacting your users.   This will give higher weight to the SPR, and maybe they will address it sooner.

Since I never saw any posting of an 8.0.2 "Revised" client they told me about 3 weeks ago I decided to call them.   The latest word is a Cumulative Client Hotfix (CCH1) is scheduled to be released this Friday (10 Oct).  The CCH will be a download that you will install over top the 8.0.2 install.   They were not sure whether it will be posted on the Passport Advantage website, or whether you have to call tech support and request it.

So this means you can not go straight to the hotfix for now.  You will have to install/upgrade to 8.0.2, then apply the hotfix.   I will have to investigate the Smart Upgrade option for this one.

I upgraded a handful of DWA users this week as a pilot for my company-wide upgrade to 8.0.2.   Some of the users complained that the names in their IM contact list were not sorted in some of the groups.  It turns out that those groups happened to be nested groups.  The DWA IM contact list will show the first sub-group sorted, THEN the second sub-group sorted beneith the first.   If there are multiple groups in the top-level group, the name list looks a mess.

Also if the group is nested 3 levels deep the group doesn't even expand in the contact list, and there is no "+" next to the group to expand it.

IBM tech support referred me to technote 1223002 which says DWA 6.5 doesn't support nested groups, but they said it is still not fixed.

So for now my only option is to tell my users to use the sub-groups explicitly.

Does your company allow employee photos in their corporate directory?  If so, how do you get it past your human resources department?  My HR department feels it would be too risky.  They think it would open us up to law suit if an internal candidate claimed they did not get a job based on their published photo.

Also, does anyone have any input on how prevalent this practice is?