Problem with client initial setup for new/old ID vaulted users

HCL Domino Domino Forum
1

We are seeing problems with new or old (roaming) users and 8.5.1 FP2 as their client when they do the initial setup:

Background:

All our users are roaming users and all users are vaulted with their IDs.

When we do the initial setup of the client running Lotus Notes 8.5.1 FP2, users are not prompted for their passwords, but they are presented with a file browse dialog box instead.

If we do the same initial setup for users with the 8.5.1 FP1 or the older 8.5.1 we do not have this problem.

Does anybody have the same issue?

Every hint highly appreciated,

Thanks

Uwe

P.S. I know it’s really a fresh FixPack :wink:

However, I consider this a real show stopper.

2

Subject: More details for the 8.5.1 FP2 ID vault client setup problem

We have more details:

The problem for not prompting the ID vaulted user during the initial client setup only occurs in:

  • Windows XP

The workaround (see postsin this forum) to enter

the IP address of the domino server for the initial contact did not work. Just for the record.

If you do the same initial setup for vaulted users in 8.5.1FP2 on

  • Windows 7/64 or

  • Windows 7/32,

then we do not see any problems. It just works.

We did not expect this. Worth mentioning.

OS is always the english version in our case.

Because Windows XP is still rolled out, this needs further investigation. I’ll keep you posted.

We reverted back to 8.5.1FP1 - but we would prefer 8.5.1FP2: FP2 fixed the German umlaut problem for us (focus switch in full client to plugin pane versus Alt-Ctrl-S for German umlaut ß (szlig)).

Uwe

3

Subject: Problem solved…

Looks like we ran into an issue regarding initial setup settings in Notes.ini in our XP setup.We had a bunch of settings predefined for the initial client setup. Unfortunately this old mechanism conflicts with the current Notes 8.5.1 FPn clients.

The only initial variable that we put into the

clients multi-user setup is now:

Domino.Name=someDominoServerName

So this seems to stop the problem.

Here is the TechNote for this ConfigFile= setting mechanism:

http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21112835

Hope this helps,

Uwe