Windows WP

With using XP, can I create a indivdual Lotus Notes DB/Welcome screen for each of the indivduals on the same PC? In-other-words, I have 4 users on my new IBM Centre (love it) and I just loaded my Lotus Notes (1st time user) and now set up my welcome page and everything is including recieving mail. What is the process for setting up the other three accounts in each of there XP login?

Subject: Windows WP

If I understand you correctly you are trying to set up a mutli user environment. When installing the client software, select this option (with local admin rights). The switch to the user1 setting and configure the client. Do the same for the other three.

Each user will then have his/her own environment.

Alex

Subject: Roaming User and Multiuser explained

Welcome to Notes. What you are looking to do is called “multi-user”. Here is some information from the help file.GETTING CONNECTED

Sharing a computer with other users

At installation on Windows, Lotus Notes offers two options: “Only for me (Single User Install)” and “Anyone who uses this computer (Multi-User Install).” If you want to share a computer with other users, ask your administrator which computers in your organization have multi-user Notes, or to set up multi-user Notes on a shared computer in your organization if it’s not already available.

To log in to a shared Windows computer when it has been in use by another Notes user, log out of Windows and then log back in.

In the Notes Client 6.01 IBM introduced two new features: roaming user and multiuser. Each of these features has a specific purpose and targeted user. To help you understand both, this article will explain each feature in detail and then explain how your customers can get the most out of each and/or both to achieve greater user mobility.

here is an article about them…

Roaming User and Multiuser explained

In the Notes Client 6.01 IBM introduced two new features: roaming user and multiuser. Each of these features has a specific purpose and targeted user. To help you understand both, this article will explain each feature in detail and then explain how your customers can get the most out of each and/or both to achieve greater user mobility.

The roaming feature is an attribute of the user that allows one user to have the identical Notes information stored on multiple machines . A roaming user can be either a new Notes user who has been registered as roaming or an existing Notes user who has been upgraded to become a roaming user by the Notes Administrator. The target audience for this feature is any user who has more than one system and wishes to have their desktop experience remain consistent across all their machines. For example, someone who has a desktop system in their office and also has their own laptop may want to become a roaming user. By doing so they would have the same experience on both systems. This desktop experience consists of the following items: bookmarks database, contacts database, most user preferences, user dictionary, optionally the user id file, and the user’s private journal if they have one. The only preferences that do not roam are ones that we deemed machine specific (for example fonts do not roam). Also, users may roam between Windows and Mac machines. However, the user dictionary does not roam between platforms. The desktop does not roam nor do any notes.ini variables created by third party apps. The desktop can not roam since it is not a database and also contains machine specific information. We suggest administrators whose users use the desktop should have them use the new gridded bookmarks as their homepage. This is almost identical in look and feel as the desktop, but, since it is contained in the bookmarks file, it roams.

An Administrator should not upgrade a user to roaming if the user will always be using the same machine. This has no value and would use unnecessary disk space on the server. If a roaming user goes to a single user notes client and switches to their roaming id file, it is simply a switch id and does not cause any data to be replicated to that machine. The Administrator has the option of having the user’s id file stored in their roaming NAB. The id file is protected by doubly encrypting it in a profile note in the NAB so that even if someone detaches it they can not use it.

The multiuser feature is an installation type. It is tied to a particular machine and not to a particular user. The target audience for this feature is any machine that has more than one user. When an Administrator installs the Notes Client for multiple users they will need to install the standard Notes Client which is available on the Windows system only (this feature does not support the Administrator or Designer Clients) The multiuser install uses the Windows user profile areas for each user’s private data. Template files and dictionaries are stored in the all users profile area so that each system only needs one copy of these items no matter how many users use this system. The multiuser feature is tied to the user’s Window’s logon. For a new user to use this system they need to log into Windows before starting the Notes Client. This feature is perfect for businesses where many users need to access Notes but have a limited number of machines. An example would be a manufacturing facility where workers would only need limited access to a computer. By having a multiuser Notes client installed on the system each worker could simply walk up to the PC, log off the current user, log into Windows and run the Notes Client. They would have their own private data stored in their profile area.

This feature is also ideal for the job share community where multiple people use the same machine at different times.

This eliminates the need for the workarounds that were necessary in order to have two personal notes configurations on the same machine. This feature was not designed for power users who have their own machines in their offices or their own laptops. If a user is not going to be sharing a system they should not install for multiple users.

By combining the two features you can achieve a more complete solution for mixed use environments. Consider the situation where a user has a personal desktop system but also needs to access Notes from a centrally located machine, (e.g. a lab machine). Combining the two features will result in the perfect solution. If this user is a roaming user, and the lab machine has a multiuser Notes client installed, then this user can simply walk up to the system, log into Windows and start up the Client. Their personal data will be replicated locally and all their bookmarks, contacts, and preferences will be the same as on their personal machine. When an administrator upgrades a user to roaming they can set various clean up options for the user. This clean up setting only applies to a multiuser system. Clean up does not apply to a single user system. An example would be a contractor working at a company for 30 days. The administrator may want to have that person’s personal files cleaned up after a given amount of time. This can also be true of the user who works with highly sensitive data. The administrator may want to have the data cleaned up immediately upon Notes shutdown. The user can also be prompted to have their data cleaned up at Notes client shutdown. Again, this is only relevant on a multiuser system; the user will never get a cleaned up prompt on a single user system. If a user will always be using the same one or two multiuser machines, the administrator will not want them cleaned up each time. Cleaning up every time a user exits the client adds the burden of replication of all their data at every startup of Notes.

You may also want to use the Notes features that uses single sign on with the Windows logon. Look in the help file under “Synchronizing your Windows NT/ 2000 password with your Notes password”.

Finally, Lotus Support has many technotes about “multi-user” and “roaming”.

Subject: RE: Roaming User and Multiuser explained

What do I need to now? Specificlly since I’ve already installed and set my profile up. Do I attempt to reinstall and install as multiuser?