02/08/2010

Display Cancelled Meetings - Perhaps it's not what you think....

Category  
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

One of the new features in Lotus Notes 8 was a new preference setting in your Calendar that would allow Notes to process meeting cancellations automatically for you, and allow you to specify if you want the cancelled meetings "removed from calendar", or "shown as cancelled in calendar" after Notes automatically processed them:

A picture named M2

As soon as I saw this, I (like many others) assumed that with this setting on and configured to "show as cancelled in calendar" I get to see those cancelled meetings in my calendar forever, or until I decide to remove them from there. I know now that this was not the intent of IBM-Lotus programmers when they put this in. Help file is very unhelpful in this case, as it does not really explain anything, and it just restates the obvious:

A picture named M3

The article "Keep your Inbox cleaner - set preferences for meeting invitations (Lotus Notes 8.x Tips)" by Julia Brown on IBM's developerWorks made me realise what this feature is all about.

First, you have to decide if you want Notes to automatically process meeting cancellation notices for you (new in Notes 8), or if you want to continue with the pre-8 functionality, that is manually process each cancellation by opening cancellation notice delivered to your Inbox. By default, automatic processing is turned off unless your administrator changed that through the policy document. After enabling autoprocessing of meeting cancellation notices, you get two choices that are otherwise grayed out:

1. Remove from Calendar - when you pick this option, the cancellation notice will not appear in your Inbox folder at all because as soon as router delivers it to your mailbox, it will be processed and the meeting document will be removed from your calendar. The caveat with this is that you will never know "what hit you...". You'll look at your calendar at one point, and you'll says to yourself: "Geeee, I could swear I had a meeting at 1 pm today, what the heck happened to it?" You may even decide to call your HelpDesk to tell them "I think Notes sucks because it keeps deleting my meetings from my calendar...."

2. Show as cancelled in calendar -  when you pick this option, the cancellation notice will appear in your Inbox folder, and the cancelled meeting will also appear in your calendar (although router processed the cancellation notice as soon as it was delivered to your mailbox), but ONLY until you either opened the cancellation notice in your Inbox (including displaying it in preview pane), or opened the cancelled meeting document in your calendar. As soon as you do that, Notes removes the cancelled meeting form your calendar. And this is where the confusion sets in. It removes it to keep your calendar "less cluttered". It was never intended to keep it in there indefinitely, therefore you cannot say that this is broken and needs to be fixed. How is this different then from not having autoprocessing of meeting cancellation notices turned on? The main goal here is to free up your time  in the "free time lookup" database so that people can see you as available in the time slot originally occupied by the cancelled meeting. Even if you did not get a chance to acknowledge the cancellation notice yet (perhaps you are away for a few days), people trying to invite you to a different meeting scheduled on the same date and at the same time as the cancelled meeting, will not see you as available. After cancellation notice was processed by the router, cancelled meetings show in your calendar in different colour with a different icon until you actually opened the cancellation notice in my Inbox, or opened the cancelled meeting document in my calendar at which point they will be removed:

[ screen shot]

The fact that cancelled meeting document disappears from the calendar after user opened the cancellation notice or the cancelled meeting document does not sit well with some of our users. It looks like some people outside our organization did not like that either (see "Cancelled Meeting does not Show up in Calendar - IBM's Answer" post on Notes 8 forum by Shawn J Kiser.) Here's IBM's position on this:

"The associated SPR (KWSR7LZQ2G) has been closed as "No Plans to fix in this release". Another SPR (MSTR7LDLCW) describes the same symptoms, against v8.5. The status of SPR (MSTR7LDLCW) is currently "Closed/enhancement request". Thusly, feature development is treating this issue as an enhancement request: We are adding further customer reports of this issue to SPR (MSTR7LDLCW) -- so the customer impact is reflected in the weighting. If weight increases sufficiently, as a result of any additional customer reports, the issue may be reconsidered for an upcoming maintenance or feature release"

I suppose all this makes sense if you keep in mind that the main objective of this feature was to free up your time in the "free time lookup" database so that people can see you as available even if you did not get a chance to process the cancellation notice yet.

01/22/2010

IMAP session info no longer displayed or logged with LOG_SESSIONS=1

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

In previous releases, LOG_SESSIONS=1 would produce session info output for all IMAP client connections to the server on the server console and log it in log.nsf:

example:
"12/22/2000 09:26:01 AM  IMAP Server: Jane Doe/University of Windsor logged in from 117.27.50.17"

I was just made aware that this is no longer happening in Domino 8.5.1. This may be related to SPR # DSAN7XH3LD (which my previous blog post is about) or not,  since this relates to IMAP while the SPR deals with Notes client connections.

01/12/2010

LOG_SESSIONS=2 does not write to log.nsf anymore

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

Starting with Domino 8.5.1, LOG_SESSIONS parameter in notes.ini can be set to "2" to include additional information (text in bold) about Lotus Notes sessions with Domino server.

01/12/2010 09:35:45 AM Opened session for 'John Smith/University of Windsor' (Release 8.0.2) SessId 06BE22DB Ip '177.52.15.83' 'Auth' 'C'


Before 8.5.1, setting it to "2" did the same thing as setting it to "1", that is displayed the session info on the server console, AND logged this same information to log.nsf.

01/12/2009 09:35:45 AM Opened session for 'John Smith/University of Windsor' (Release 8.0.2)


It appears that with Domino 8.5.1 and  LOG_SESSIONS=2 in notes.ini, this information no longer gets logged into log.nsf although you can still see it on the server console. Setting  LOG_SESSIONS=1 still works properly, ie. the info shows up on the server console and inside the log.nsf.

IBM Technical Support confirmed that they are aware of this issue:

Lotus Notes SPR # DSAN7XH3LD                                            
Session information not written to Misc. Events in log.nsf after upgrade to 8.5.1 using Log_Sessions=2

12/11/2009

I love this error message :)

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 


A picture named M2

lol

11/27/2009

HEAT killed Lotus Notes password prompt!

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

A very strange thing happened after we upgraded our call tracking software HEAT (FrontRange Solutions) to the more recent version 9. Anyone who had Lotus Notes installed prior to the HEAT upgrade, have noticed that their Notes password prompt got replaced with a box that looks just like text input box that LotusScript code can produce. So we went form this:

A picture named M2

...and this:

A picture named M3

... to this:

A picture named M4

I don't think there was any doubt in anyone's mind what the culprit was, but since HEAT is someone's pet project here, this issue was being down played and was labelled as "limited scope". Our HEAT admin sure took his time in trying to pursue the vendor for a solution to this problem (of course downgraidng HEAT was out of the question), and after weeks of not much happening we got the word that there is no solution but we have workaouround: un-istall Lotus Notes, and re-install Lotus Notes. Apparently vendor of HEAT was not very co-operating in trying to get to the bottom of this. At one point (as we were told) they even said that it's not their problem and that we should contact the IBM... Shortly after, my colleague discovered this strange file that appeared in ../lotus/notes folder around the time HEAT was upgraded:

A picture named M5

When he renamed it and moved it to a different folder, his Notes password prompt came back from the dead. Unfortunately, this did not work for me or our HEAT admin. So few more weeks went by, it looked more and more like the only hope we have is that wonderful workround suggested by FrontRange tech support. It was yesterday, that I took some time to search the Web for the HeatSetLotusPassword string. Did not find much there, Google returned only two hits - two posts on the HEAT related forums that included more questions than answers. Searching though my Windows registry also did not yield any results. There was only one more place to check: notes.ini. As I was making my way up starting from the last line, I then came across this:

EXTMGR_ADDINS=HeatSetLotusPassword,extpwd



A picture named M6

How did we not see this coming? Needless to say, removing this line (or commenting it out), took care of the problem and after restarting Lotus Notes, my password prompt was back.

07/06/2009

FOLLOW-UP: QueryDragDrop and PostDragDrop bug in Notes 8 Standard

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

This is a follow-up to my blog entry from Nov 7, 2008:
QueryDragDrop and PostDragDrop bug in Notes 8 Standard

Recently, I opened a new PMR to find out if this issue has been resolved by IBM-Lotus developers, and this is what I got in response:

"SPR CJON7L73CK (NotesUIDatabase.Documents method returns incorrect information.) has been closed. Apparently there are no plans to fix this issue."

This does not seem to be the case, however. I did the same test in Lotus Notes 8.5 today that I did back in Nov 08 with Notes 8.0.1 when I blogged about this issue. I used the same "PostDragDrop Bug Sample Mailfile" that is available on my blog in downloads section. I discovered that the issue has been resolved and the number of documents reported by NotesUIDatabase.Documents is now correct. Perhaps IBM developers have no plans to address this in the 8.0.x code stream..., but in 8.5 it is working as it should.

06/16/2009

DAOS rocks!

Category  
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

Just recently we implemented DAOS on our three clustered mail servers, and our lone mail archive server. The implementation went without any problems, and the outcome is really amazing. Here's why...

As a real life example of the difference that DAOS makes, let's examine the mail file size of one of our typical users. This user, just like others here, has his mail file replica on each of the three clustered servers. Yesterday, there were 18,740 documents (many with attachments) in each replica. While the replicas on servers ZEUS and VENUS were already converted to ODS 51 (required for DAOS), I noticed that the replica on server TRITON was still using ODS 43, hence DAOS did not do its magic here (see fig.1).

Mail file size on ZEUS was 1,354 MB with 97.5 of space used (ie. 2.5 % white space).
Mail file size on VENUS was 1,345 MB with 97.8 of space used (ie. 2.2 % white space).
Mail file size on TRITON was 3,156 MB with 99.2 of space used (ie. 0.8 % white space).

Do you see the difference? 1.3 GB on a server with DAOS versus 3.1 GB on a server without DAOS. Just by converting the mail file replica on TRITON to ODS 51 and enabling DAOS on it (compact -c), I brought the size down to 1.3 GB (see fig2). I just recovered 1.8 GB of disk space from one mail file.


Fig 1. DAOS at work on ZEUS and VENUS mail file replica (ODS 51), but not TRITON (ODS 43)
A picture named M2

Fig. 2 DAOS at work on all three replicas of the mail file after the replica
on TRITON has been converted to ODS 51

A picture named M3

How was this possible? This user had a lot of attachments stored in his mail file, that were also stored in other user's mail files. When DAOS went thought that mail file, it stripped duplicated attachments from the documents and replaced them with pointers to those same files that DAOS already stripped form other mail files and stored in one central location on the server.

Overall, we recovered about 200 GB of storage space on each clustered server after implementing DAOS. 3 x 200 GB, that's 600 GB of space back to the pool.

Now, the mail archive server. We have about 2,700 users with mail files. Each user has a replica on each of the three mail servers in the cluster. Any mail file that exceeds 400 MB, is eventually included in scheduled server-side archiving to a dedicated mail archive server called HADES. As you can imagine, HADES needs a lot of storage space to accommodate all these archives, especially because we do not have mail file quotas in place and users are allowed to keep anything they want in their mailboxes. Before we implemented DAOS on HADES, the server was using 1.7 TB of space on our SAN for mail file archives. After we implemented DAOS on all mail archives on HADES, we recovered 600 GB (thanks Patrick...) of storage space on that partition. That's more that 1/3 of the space previously used to store these files.

And here is the final proof that DAOS is just amazing. Take good look at the pictures below. This is Chris, our SAN and backup administrator. The first picture was taken just before DAOS was implemented. The second picture was taken after DAOS was running. What a difference!

Fig. 3 Chris before DAOS.
A picture named M4

Fig. 3 Chris after DAOS.
A picture named M5

06/10/2009

Google plots Exchange escape with Outlook plug-in

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

http://news.cnet.com/8301-17939_109-10260879-2.html?tag=newsLatestHeadlinesArea.0

"CIOs invited by Google to a press event in San Francisco were naturally bullish on Google's version of cloud computing, and downplayed any concerns about security, reliability or the loss of a competitive advantage when it comes to giving up control of their IT."

04/13/2009

Complexity or Domino?

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

Worth reading, especially for IT Managers:
http://www.wissel.net/blog/d6plinks/SHWL-7QYDNV

04/08/2009

Creating links to files on the network drives

Category
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

I've been asked by my colleagues if there is a way to insert a link into a Lotus Notes document that points to a file stored somewhere on the network drive. Once this link is clicked by a reader of the Notes document, the file (for example a Microsoft Word document), that this link points to will be opened.

I found two ways of accomplishing this. One involves turning selected text within a document into a "hotspot", specifically a "Link hotspot of the type URL". The other method involves creating Windows shortcut (.lnk file) and attaching it to your document.

Method 1
Create a URL link hotspot

When you hear the term URL, you probably think of an address of a Web site/page (a file accessed remotely though the HTTP protocol) But in this context, the term "URL" means an address of a file that you want to link to using one of many available protocols. Please note that URL consists of two parts: protocol + path to your file. You should also know that in Lotus Notes, the following protocols are allowed inside the URL hotspots:

http://
https://
ftp://
notes://
file://

To create your hotspot that links to a document, we will use "file://" protocol.

1. Make sure your document is in edit mode.
2. Select the text to act as a link.
3. Click Create > Hotspot > Link Hotspot.
4. Select "URL" for the link type.
5. Type in the full URL to your file in the "Value" field. See URL examples below.

URL Example 1
The file "test.doc" is located in a folder called "temp" that in turn is inside a folder called "consult" on a network drive mapped as "M:" on everyone's computers. The path to this file is "M:\consult\temp\test.doc".

You would use the following URL for your hotspot:
A picture named M2

A picture named M3

URL Example 2
Since network drive letter mappings may differ between computers on the same network, it is safer to use a different method for specifying the file path. The same file used in example above, is stored on a Novell server called ALPHA. When it comes to drive mappings, "M:" actually points to a folder called "common" that is stored on a partition also called "COMMON" on that server. Those names are not case sensitive, I just used lower case for the folder name and upper case for the partition name to distinguish them from each other.

You would use the following URL:
A picture named M4

A picture named M5

NOTE: This is applicable to both Novell and Microsoft networks, although I only tested it on our Novell network with Notes 8.


Your Notes document will look like this:

A picture named M6




Method 2
Create Windows shortcut (.lnk file) and attach it to your Notes document

1. Open Windows Explorer and browse to a folder where your file is stored.
2. Right click on your file and select "Create Shortcut" from the menu. You will see that Windows created a new file. If the original file was called "test.doc", your shortcut will be called "Shortcut to test.doc" in Windows XP, or "test.doc - shortcut" in Windows Vista.  Note that Windows hides the file extension ".lnk" which is appended to the shortcut file name.

A picture named M7
A picture named M8

If you wish, you can rename your shortcut file and take out the "Shortcut to" prefix (Win XP) or "-shortcut" appendix (Win Vista).

A picture named M9
 
3. Attach the shortcut file created in step 2 in one of the three possible ways:
a) drag and drop shortcut into your Notes document, or...
b) copy shortcut to the clipboard, switch to Notes document and paste it from the clipboard, or...
c) use File > attach from Notes' menu and browse to the shortcut file

Your Notes document will look like this:

A picture named M10

RSS FEEDS

Browse By Day

Photo Albums

Me

bodek@uwindsor.ca
519-253-3000 x2801

BodekSept2006Small.jpg

Home Improvements

Powered By

Domino BlogSphere
Version 3.0.1 Beta 6