Archive for SNTT

VMWare fusion slowing down bug

Its a Mac related thing, but it was
annoying the hell out of me, so its worth a post.  I use VMWare fusion
to launch an XP client whenever I need to get something windowsy done.
 Recently, it has taken longer and longer to start up going up to
10 minutes just to boot recently.  I tried uninstalling VMWare and
reinstalling, checking disk fragmentation and restored a copy of my version
XP image.  Nada.


Managed to solve it eventually today
(I should of done this ages ago) by reinstalling VMWare tools on the XP
image.  Works a treat again.

Update:  This has not fixed
the problem – something is up here – any vm running on this macbook is
now horribly slow to start and stop….  will let you know when I
find something.

Leave a Comment

Customise ALL the client error messages for Notes

Ok…. Admin people are going to love
this.


A few months ago, I presented
this tip
.  It showed how
to customise some of the more unhelpful errors on the Lotus Notes clients
and make them useful, by replacing the error text that pops up on the client,
with something you put in instead.  Very very nice…..


This involves using desktop policies
to customise the Lotus Notes client error messages.  I present this
as a tip in the Adminblast presentation that I give at many conferences.
 
Bill
and Julian
have helped me out in a big way.
 They have put together a database that calls all the error codes
for the client and outputs them into a database, so you can now customise
ANY error message… and make it useful.    This is release 1,
and we have a few improvements in the planning.  So to use it…


Download the database file from my
resources page
.  Follow the
very simple instructions to output the error code list.


Read Jack Dausmans
excellent article
on how to easily
modify the notes.ini’s on clients using a custom button on your toolbar
(its very very good).


Pick your error – and customise it.

Consider this our Christmas gift to
the administrators, from Bill, Julian and myself.

Leave a Comment

Preventing users from mailing specific groups

Ok, its been a while since I posted
a SNTT, and I was asked this recently, so figured it may be a useful tip
for an admin newbie.  So imagine you are an administrator, and have
to (only ever now and then) deal with pesky end user requests.  Well,
there is a request to prevent any old user from mailing the group that
contains all the users in the domain (or any group for that matter).  Its
a fairly simple process.  

So you have a group that contains all
the users in your domain.  Here it is:


A picture named M2

(em… obviously it would contain users
in the real world – in my domain, I don’t allow users).

Now, create a group that would contain
all the users that will be allowed to mail to the group above.  And
here you go:

A picture named M3

Add all your permitted users to that
group.  Now go back to the group with all the users in it and go into
the document properties.  Click on the key (security) tab and you
will see the following:


A picture named M4

Uncheck the ALL READERS AND ABOVE checkbox
and then we are going to click on the torso icon to the right, and choose
which users can read this group from the directory.


A picture named M5

I have added in the group that will
contain the users permitted to mail to this group, and the admins and localdomainservers
group for management purposes.

Thats pretty much it – now only users
in that group (and admins) can mail to the contents of that large group.
 If you want to permit / deny rights, just add/remove users from the
group.

Comments (10)

Automating the setup wizard on the Lotus Notes client

Its been a while since I posted an SNTT,
and I did some work with this old feature recently, so it was worth a post.
 Many environments automate the installation of the Lotus Notes client
using an installshield tuner or some such, which bypasses all the preference
settings and installs the client silently for the end user (actually this
is done for the administrator, to ensure and easier life, but enough said
about that).  What can also be done is the automation of the
configuration wizard that the users have to go through with the lotus notes
client, after starting it for the first time.  This involves a little
work and planning to get completed, but in larger scale environments, this
is worth it.

All the preference options that can
be chosen on the setup wizard can be pre-populated in a configuration text
file.  This is documented in the ND8 installation guide. Here is an
example:

;Username= [e.g. User Name/OU/O]

;KeyfileName= [e.g. C:\Notes\Data\User.ID]

;;*****Server Details********

;Domino.Name [Domino server name e.g.
MAILSERVER1]


;Domino.Address [IP address of Domino
server]


;Domino.Port=TCPIP

;Domino.Server= [1 to connect to the
server, 0 for no connection]


;*****Internet Accounts********

AdditionalServices=0

;Mail.Incoming.Name= [incoming POP or
IMAP server name]


;Mail.Incoming.Server= [1 for POP or
2for IMAP]


;Mail.Incoming.Protocol=

;Mail.Incoming.Username= [Mail account
user name or login name]


;Mail.Incoming.Password= [Mail account
password]


;Mail.Incoming.SSL= [1 to use SSL; 0
not to use SSL]


;Mail.Outgoing.Name= [Outgoing mail
account name, a friendly name used to refer to these settings]


;Mail.Outgoing.Server= [Outgoing mail
(SMTP) server name]


;Mail.Outgoing.Address= [User's Internet
mail address, such as user@isp.com]


;Mail.InternetDomain= [Internet Mail
domain name such as isp.com]


;Directoy.Name= [Directory account name,
a friendly name used to refer to these settings]


;Directory.Server= [Directory (LDAP)
server name]


;*****Dialup settings********

;NetworkDial.EntryName= [Name of remote
network dialup phone book entry]


;NetworkDial.Phonenumber= [Dial-in number]

;NetworkDial.Username= [Remote network
user name]


;NetworkDial.Password= [Remote network
password]


;NetworkDial.Domain= [Remote network
domain]


;DirectDial.Phonenumber= [Dial-in number]

;DirctDial.Prefix= [Dialup prefix, if
required. For example, 9 to access an outside line.]


;DirectDial.Port= [COM port to which
the modem is connected]


;DirectDial.Modem= [File specification
of modem file]


;*****Proxy Settings********

;Proxy.HTTP= [HTTP proxy server and
port - e.g, proxy.isp.com:8080]


;Proxy.FTP= [FTP proxy server and port
- e.g, proxy.isp.com:8080]


;Proxy.SSL= [SSL proxy server and port
- e.g, proxy.isp.com:8080]


;Proxy.HTTPTunnel= [HTTP Tunneling proxy
server and port - e.g, proxy.isp.com:8080]


;Proxy.SOCKS= [SOCKS proxy server and
port - e.g, proxy.isp.com:8080]


;Proxy.None= [Do not use a proxy for
these hosts or domains]


;Proxy.UseHTTP= [Use the HTTP proxy
server for FTP, Gopher, and SSL security proxies]


;Proxy.Username= [User name if logon
is required]


;Proxy.Password= [User password]

;*****Replication Settings********

;Replication.hreshold= [Transfer outgoing
mail if this number of messages held in local mailbox]


;Replication.Schedule= [Enable replication
schedule]


;*****Instant Messaging Settings********

IM.Server=

IM.Port=1533

IM.ConnectWhen=1

IM.Protocol=0

;IM.ProxyType=

;IM.ProxyServer=

;IM.ProxyPort=

;IM.ServerNameResolve=

;IM.ProxyUsername=

Now, you  don’t need all
of this to automate the installation, just the first fiew lines will do
to prevent users having to click on anything to force the configuration.
 Here is an example of one that does just the basics:


;*****User Details********

;

Username = Paul Mooney/pmooney

KeyfileName=c:\pmooney.id

;

;;*****Server Details********

;

Domino.Name = mailserver/servers/pmooney

;Domino.Address [IP address of Domino server]

Domino.Port=TCPIP

Domino.Server = 1

As you can see, there is not that much
to it.  Now, to force this file to be "read" all you have
to do is save it as a text file (for example, we call it configfile.txt)
and then modify the freshly installed notes.ini (manually or using an install
script) to include the following line:


Configfile=x:\configfile.txt

Now, all the user should have to do
is input their password and click on ok, and then click on ok to the "setup
complete" dialog box.  The work lies in the automation of the
creation of these setup files, but this can be done using batch file exports.
 I even heard of someone creating multiple copies of this file using
the mail merge facility of Microsoft Word!

There you go, nothing too new, but definitely
useful.

Leave a Comment

Agents running in a clustered environment

Here at Admin,
I gave a session on "troubleshooting agents for administrators".
 At the end of the session, I was asked how should you deal with applications
that have scheduled agents running on clustered servers.  So the scenario
is as follows:

You have an application on both servers.
 Scheduled agents exist on both these servers.  You only want
the agent to run once (i.e. not run on both servers).  BUT, you want
the ability for the agent to execute on the other server if needed (i.e.
if the primary server goes down).  There is a View article entitled
  "Failover Support for Background Agents on Clustered
Domino Servers — A Solution for Your Lotus Workflow and Domino Applications"

The basic concept is to use a token
that grants a server permission to run agents.  Agents are enabled
to run on any server, but only one server at a time will have the token.
 The flow chart in Figure 1 delineates the code logic.  Here’s
how the Agent Failover Support solution works:

When an agent is triggered in your application, code that you have added
to the application (provided in the download that accompanies the article)
checks to see whether Agent Failover Support has been enabled (by means
of a checkbox on an administrative setup document also added to your application).

If agent failover is enabled, the code next checks to see whether the server
on which the agent has been triggered (let’s call it the Current server)
is listed in the ClusterServers field in the administrative setup document.
 This field provides a means to restrict agents to certain servers
in the cluster.  If the server is not listed there, the execution
of the agent is terminated.  Now the server checks to see whether
there is a server in the cluster that possesses the token to run agents
(let’s call it the Token server) If there is a Token server, execution
proceeds to step 4; if there is no Token server, execution proceeds to
step 6.

A Token server exists, so the Current server checks to see whether it is
the Token server.  If it is, the Current server runs the agent.  If
the Current server is not the token server, execution proceeds to step
5. The Current server is not the Token server, so the Current server checks
to see whether the Token server is timed out. If the answer is yes (the
Token server is timed out), proceed to step 6.  If the answer is no,
execution of the agent on the Current Server is terminated.  If there
is no Token server, or the Token server is timed out, the Current server
claims the token and runs the agent.


A picture named M2

Leave a Comment

Websphere Portal Server 6.0 Installation. Part 7

Next part now.  If you have completed
the other steps, you should be follow this document to configure single
sign on between domino and Websphere Portal Server.  Go to the
resources
page
for details.

Next part – configuring the HTTP plug
in for Domino/Websphere Portal server (i.e. Using the Domino HTTP task
to surface the portal environment).

Leave a Comment

Websphere Portal Server 6.0 Installation. Part 6

Its been a while since I had something
like this done.  So, part six on the Websphere Portal Server and Domino
integration document is now done.  This section assumes that you have
followed all the other steps.  Now you have to tell Websphere Portal
server to use domino LDAP for security.  Go to my

resources page
for part six.

Enjoy and comments welcome.

Leave a Comment

Customising the error that comes up on the Notes client

After the clustering presentation at
Lotusphere, I was reminded of a tip I totally forgot about by an attendee
(thank you for the email Jason Michels).  It is most definitely worth
a SNTT post.

In a clustering environment, it is typical
to get users to escape out of a database and go back in for failover to
occur correctly.  This is not exactly the case in ND7, but it is a
safe way to go with a load of users if the helpdesk is swamped.  Of
course, the error on screen for the users is not that helpful.  How
many people have seen this
A picture named M2

(known as Error 0807)

or

A picture named M3 ..

(known as Error 0A02)

What can you do?

Leave a Comment

Time Zone patch for Domino/Win2k servers

Bob Warth was good enough to send me
this information for posting.  If you are in the US, or deal with
the US, and have Win2k servers running Domino……. read it!

Hi Paul, not sure how serious you guys
consider the upcoming change to the new
timezone rules for the US, but over here it’s looking like there will be
some
definite pain.  Rob Axelrod is FREAKING OUT over on the Notes forum:

http://www-10.lotus.com/ldd/nd6forum.nsf/0/e579440219fe47f98525725a0061fdba

(and
I don’t blame him.)  At a minimum we’re facing a lot of entries in
C&S and
resource reservations and Sametime that will be an hour off and require
attention, and our hundreds of Blackberry users are already noticing their
handheld calendar doesn’t agree with their Notes calendar on their patched
PC.
RIM says they may have a patch by the end of January. (Could they be thinking
that any patch that arrives before March 11 is soon enough?  Could
they think no
one plans ahead?)

Anyway, setting Notes and Domino to inherit timezone settings from the
OS does
help, and is fine for the Win2003 servers, but Microsoft doesn’t have a
patch
for our remaining 2000 servers.  Or do they?

Leave a Comment

Websphere Portal Server 6.0 Installation. Part 5

Now the pressure is off on the Lotusphere
presentations, I have published
the next section of my "Websphere Portal for Domino admin weenies"
article.  This article covers how to configure your Domino directory
so that LDAP look-ups from WPS will work correctly.  It also outlines
the groups to be created so WPS will behave.  The article can be downloaded
here.
 I have also created a
download/resources
page, which will list the previous steps in one place.  Be sure to
have completed ALL previous steps in advance.

Let me know any thoughts/comments.

Comments (2)