Domino @ Symetrik Design

Only increminating personal information has been changed. The capitals and all have been left the same.

---

TO..: “IT DEPARTMENT – XXXMYCOMPANYXXXX”
FROM: XXXXXXX
DATE: 30-MAR-2009 09:11
MSG.: 1042041

I HAVE FINALLY MANAGED TO CHANGE MY PASSWORD AFTER MANY ATTEMPTS

THANKYOU

RGDS/XXX
+

I CANNOT USE LOTUS / OUTLOOK BECAUSE MY PASSWORD NEEDS CHANGING.

WHEN I TRY TO CHANGE MY PASSWORD IT SAYS I CANNOT CHANGE MY PASSWORD.

THAT IS R I D I C U L O U S

XXXXXXXXXXX
+

I received this in a Microsoft (not business partner) email invitation to a Microsoft IT Professional Seminar Series

On the agenda was – “Windows Server® 2008 R2 (Codename ‘Windows Server 7′)”

If you’ve ever created a PMR with IBM, you are used to getting the “PMR Updated” notification emails from IBM.

Today, I actually read the text in the notification email and found this:

* Internet access: Log into ESR at
http://www.ibm.com/software/support/probsub.html and update your
Authorized Caller record to indicate you do not want to receive
these update notifications.

* No internet access: Write to esrhelpdesk@us.ibm.com to
inactivate this capability.

NOTE where it says that if you have no Internet access write the the Internet email address.

I wonder if this is only from IBM China or all of IBM.

Have you ever seen this message when opening a mail database? From time to time we see this after an upgrade. Normal Fixup, Compact, Updall, and even template replace will not fix the issue.

However, Compact -D will do the trick.
The -D switch discards any built view indexes

You can try this for B-tree structure is invalid! errors as well.

For good measure you can run Updall -R afterwards to rebuild all the view indexes.

A few months ago, we upgraded all of our Brazilian users to Notes 7.0.3. After we did so, the automated messages generated by their help desk ticket system stopped displaying Portuguese accented characters properly.

When accessing the same message through DWA, the message and accented characters showed up correctly.

We generated a PMR with IBM, who told us to right click within the message, and choose Encoding\Other\Unicode (Auto-Detect) which seemed to fix the isssue.

It appears that the message that is generated by the help desk system is received by Domino via SMTP and when the message is delivered the MIME type is unknown. So this fixes the problem one a one by one basis, but how do you fix it so that the default Encoding is Unicode (Auto-Detect) and/or UTF-8? Read the rest of this entry »

Have you ever seen this error message in your console or statrep.nsf?

I see hundreds in my statrep.nsf all the time.

The cause is that the user with mailbox called filename.nsf has mail rules set to file messages to a folder that doesn’t exist anymore.

I’m sure some of you are reading this and wondering why the @#$@ are you upgrading to R7 instead of R8.02 or R8.5. In short, we are trying to stabilize our 6.5.6 FP3 HF63 servers with the least amount of effort and impact to the users while we run a migration to Exchange.

After applying 3 or 4 hotfixes to 6.5.6 FP3, I have FINALLY convinced my team to upgrade at least the server to 7.0.3 FP1. I spent two month testing and designing a plan to upgrade all of the servers. When they finally got around to seeing how it would be beneficial (due to BES servers crashing and on at least 3 occasions IBM told us to upgrade to Domino 7.03 when we created PMRs) I ran through all the testing procedures.

The one thing I didn’t test, was webmail access on Windows Vista because neither one of my machines is Windows Vista. That happened to be the one thing that broke when we upgraded our servers.

We are using the OpenNTF1.7b mail template which is based on DWA6 (6.5 version). We haven’t upgraded any mail templates because we didn’t want to impact the users in any way.
Read the rest of this entry »

The more I’ve been reading about Exchange 2007 administration, the more it sounds like alot more work (not to mention alot more servers).

I read this blog entry at the Tech Republic Blogs titled “Scripting the remove and disable mailbox attributes in Exchange 2007”

Here’s an excerpt:

The two scenarios can be scripted out in large amounts with normal batch files. A common way to make these scripts is a concatenated formula within an Excel spreadsheet that requires only the username or e-mail address to be added to create the command, which would be copied and pasted to save or run in the Exchange Management Shell.

I do happen to be good with a command line interface and actually enjoy it from time to time as shown in this previous post on my blog about writing a Domino server maintenance script that performs several tasks and a reboot every week in what I call “Preventative Maintenance.”

….but having to use the command line, or run a batch file, and intensifying the process by using Excel just to disable or delete a user sounds asinine.

I’ve just upgraded some of our Domino severs from 6.5.6 FP3 HF63 to 7.0.3 FP1 HF517. I put alot of testing into it so it has been relatively smooth.

I did find that I had some template replication issues, so I went around, deleted every template in our environment except on one isolated 7.0.3 server. I then signed all the templates on that server and used the admin client to create replicas on our hub servers which had also been upgraded to 7.

I had real problems with the following templates: activity.ntf, admin4.ntf, certlog.ntf, dba4.ntf, and webadmin.ntf.

admin4.ntf, certlog.ntf, and dba4.ntf had a bad ACL set, so I couldn’t sign any of them, and the LocalDomainServers group couldn’t replicate. I fixed that and signed the templates and replicated them.

One of them was set to temporarily disable replication, and I fixed that.

All that was left was activity.ntf and webamin.ntf. For some reason, activity.ntf wouldn’t initialize. I had to try several times before I got it working through adminp.

I could never get webadmin.ntf to replicate because the error message that shows up when the temporarily disable replication tickbox is checked kept appearing, but the template did not in fact have that checked.

I starting looking through DDM today, and found that one template and one database generate errors when design runs.

Design error for database ‘help\readme.nsf’: Invalid collection data was detected.
Design error for database ‘dominoblog.ntf’: Invalid collection data was detected.

I looked in R7 admin help, Notes 6 and 7 discussion forums, and google, and “Invalid collection data was detected” appears nowhere.

These are all small things, but wouldn’t expect finicky templates from 7.0.3.