This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Sep 12, 2016, 4:47 PM
51 Posts

Roaming & User Logon (Clarification)

  • Category: Notes Client
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags:
  • Replies: 7

We are testing roaming with virtual desktops (VDI). To date, our users have been non-roaming. Can someone assist me in understanding how a roaming user would logon to Notes? For example, a user starts a virtual desktop (or from another physical system) and double-clicks the Notes icon. I'm used to seeing the user drop-down, password, and locations fields in the prompt. What is different for roaming users? It needs to be a multi-user installation, right? Is the prompt different? Does it pull the ID from the vault? The only option that seems logical, at least in my current logon prompt, is to choose "Other" from the user list. Problem... this presents a file dialog seeking a local ID file. What am I missing? Thanks in advance.

Update: We're considering non-persistent desktops. Would you setup the Notes clients (where it asks name, home server...) with a dummy user so that the client's actually setup when the desktop session starts for the end-user vs. having to complete setup each time? Maybe my client was installed as single vs. multi-user. Is that why I'm not seeing the option to logon as a roaming user? How can you tell if the Notes client is installed as a single or multi-user?

Also, I found this site (https://www-10.lotus.com/ldd/dominowiki.nsf/dx/notes-8.5-roaming-user-quickstart-guide) that shows a logon screen but mentions a custom setup.txt. I just assumed that the user entered his/her name or selected from list, clicked a roaming button... something. Any help appreciated.

Sep 13, 2016, 8:06 AM
14 Posts
Roaming
A roaming user logs on as normal to the Notes client , the user does not do anything different at logon. The Roaming process is all controlled by the Administrator.
There are two types, you can enable a policy or select users to upgrade using the Roaming tool in the Admin Client.
In order to become roaming the users need to start of the process from a primary workstation, because the Notes client needs to create replicas of Local databases on the Server.
These databases will hold the users preferences so that once you become Roaming and move machine you data will be replicated down to your new instance of Notes.
At this stage the user will have to accept the prompt as shown is the document you referenced.

Roaming will work with ID vault but if you have used to Roaming Tool in the Admin client to upgrade don't choose the option to Roam the users ID file in the local Names.nsf.
It's also possible to use a Setup.txt that can pre-populate the configuration dialog boxes when the users has a new instance.

Hope this helps
Ronan
Sep 13, 2016, 2:45 PM
51 Posts
Re: Roaming

Ronan,

Thanks for your feedback, really appreciate. I'm still a bit confused about logging in normally. The issue could be that the standard client's different (I'm using all clients). Is the user able to type his/her name in the user field of the login dialog? In my client, the list is fixed and and a choice must be made. I located an example (thanks to Mat Newman - see link below) that shows a partial notes.ini (pre-setup) and the configuration file (setup.txt). I'm assuming that the user would click the Notes icon and the notes.ini would initialize then setup/configuration would complete based on the setup.txt file. In short, the user would not see the setup screens and only the password prompt. Interestingly, the Username=%USERNAME% parameter/value seems to use the Windows login ID. If the Windows ID (e.g. shortname) matches a value in the person document (Domino directory), would it pull the ID from vault and prompt user for password? Would be nice...

http://www.matnewman.com/webs/personal/matblog.nsf/dx/easiest-notes-upgrade-ever

[Notes] 
KitType=1 
ConfigFile=S:\Tools\Install\notessetup.txt 
SharedDataDirectory=C:\ProgramData\IBM\Notes\Data\Shared 
InstallType=6 
InstallMode=1 
NotesProgram=c:\Program Files (x86)\IBM\Notes\ 
 

The Configuration File

Username=%USERNAME% 
Domino.Name=theconfigserver/thecompany 
Domino.Address=theconfigserver.thecompany.local 
Domino.Port=TCPIP 
Domino.Server=1 
AdditionalServices=-1 
AdditionalServices.NetworkDial=0 
Replication.Threshold=9999 
Replication.Schedule=0 

Sep 20, 2016, 1:29 PM
14 Posts
Roaming
Hi Michael,
Roaming is not supported for the All client version, you need to be doing your testing with the the Notes Single user or Multiuser installs.
It seems to me that you are trying to do two things at once, automate the config and roaming the users at the same time which will not happen.

Also you never explained what type of Roaming you were testing (policy or roaming tool)

If its a new instance of Notes where you are using a config file to automate the setup , it will not set up Roaming at this time .
Notes needs to already set up before Roaming will kick in , this is because Roaming will need to replicate the local databases to the Server with one exception if you are Roaming using the Policy.

You are essentially just doing an Automated Config.

I think it will work as you were expecting once the users are Roaming . On a user with an existing Notes instance either apply the Roaming  Policy or use the Tool (without Roaming the ID file). Once the Roaming is complete  then do your Auto Config.

The Config. text file will populate the config screen and pull the ID from the Vault once authenticated the Roaming will kick in and replicate down the data from the server.

Sep 13, 2016, 5:08 PM
326 Posts
read this technote

Found this technote that explains what else can be in the config file http://www-01.ibm.com/support/docview.wss?uid=swg21112835  

 

I never used the username parameter but set the keyfilename= to the users correct id file that we set in the users own user directory.     Also we always pointed the Domino.Name to one server and the initial setup resolved it to the correct mail server that was listed on the person doc.

Sep 13, 2016, 6:56 PM
51 Posts
Re: read this technote

Barry,

Thanks for the additional information. Since we're unsure which users will access (could be any of several hundred... accessing these non-persistent virtual desktops), the keyfilename parameter seemed too explicit. Also, I agree re: the one server (our plan, too). The %Username% seemed ideal.

Scenario: John Smith launches his virtual desktop and logs into the Windows domain as "jsmith" (also happens to = shortname in person document). Once in, he double-clicks the Notes icon that points to the stripped down notes.ini and setup.txt. His %Username% (jsmith) is used during startup (setup/config). During this process, jsmith is found in the Domino directory and the ID is fetched from the vault. The user receives the password prompt for user John Smith/TestCo. He logs in and roaming takes over.

This should work. right? Seems so, based on the articles. Thanks in advance team.

Sep 13, 2016, 11:47 PM
326 Posts
Well

Its says

 

I D Vault
Q. Is it possible to automate a new install of Notes 8.5.x (or higher) with no user interaction with the help of ID Vault.
A. Yes. If Username is set to the hierarchical username and the Domino.Name, Domino.Address, and  Domino.Server entries are set appropriately, then Notes will look for the user's ID file in the ID Vault. IMPORTANT NOTE: The key is getting the Username correct for each user and then setting the ConfigFile= value in the notes.ini to point to that user's setup file. Also note that ID Vault requires version 8.5.x (or higher) for the client and server.

 

 

Username needs to be the exactly as it is in the first full name of the person doc.   I guess if you have the heir name in active directory  you can write  a program  that runs in login script that gets the info based on ldapsearch and set a new windows end lets say called usernamehier and use that in the install script.  We did the keyfilename as our %username% concatenated with .id matched the filename and this was also pre setting up the id vault.

Sep 14, 2016, 12:32 AM
51 Posts
Roaming & %Username%

Barry,

Thanks. Will test the %Username% with existing shortnames and see what happens. Great information to start.

Michael


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal