Accessing R6 server with an R5 client

Hi,I’ve a basic question. Will there be any problem of an R5 client accessing an R6 server? If so, can anybody brief out? I also need to know about the active directory synchronization of Windows 2000 with the domino directory in R6. In the sense, if i change my windows password, it should immediately reflect in the addressbook people document, thereby effecting single sign on. Plz, help.

Best Regards,

Hopkins

Subject: Accessing R6 server with an R5 client.

Hi Anthony,

  1. R5 Client, 6 Server.

No Issues here, just DON’T upgrade the design of the users mail database (the ND6 design doesn’t look quite right in an R5 client). I’ve had to do this on occasion for the past 12 months and have not had any issues. Loads of clients with ND6 servers who have yet to upgrade their users.

  1. Single sign-on for windows.

As long as the client install on the workstation included the “Single Sign on” service for windows, there will be no problem with windows and notes passwords synchronising. A recommendation though - change the password through Notes, rather than “Three-fingered-salute” → “Change password”, as the Notes option in my experience seems to be flawless.

Regards,

Mat.

Subject: Accessing R6 server with an R5 client.

You might be able to do that if- The database(s) the client needs to access isn’t converted/upgraded to ND6 design (i.e. isn’t using any new ND6 features etc)

  • The database(s) the client needs to access has the R5 ODS. Don’t remember the version number for the ODS, though.

but I would recommend upgrading the clients first before upgrading the server(s). It will minimize the problems/issues. Read more in the Administration Help about upgrading issues.

Regarding the AD-synch: I have no idea - have never explored this new feature/function with ND6. Maybe someone else know the answer…

hth

Subject: RE: Accessing R6 server with an R5 client.

Kenneth.

  1. The ODS on the DOMINO SERVER, has nothing to do with how the Notes Client will access the server based database. This is not the case though with “local” access (ie, file system) to a database with a different ODS. Please don’t confuse the two.

FYI - Server (ND 6.5 on Notes01/notesweb) replica of this DB is ODS 43, MY LOCAL replica (using Notes 5 Client) is ODS 41. That also leads me on to…

  1. Your recommendation regarding the order of upgrade, is this based on your own extensive experience?

I would suggest that the order of an upgrade would be on a case-by-case basis.

Please be careful with answering posts in this forum, there recently has been a large number of posts from self-confessed “Newbies”, we want them to enjoy the best groupware product on the market, not confuse them by providing advice that may not necessarily be correct.

Regards.

Mat

Subject: RE: Accessing R6 server with an R5 client.

Hello Mat,thank you for the response. So you mean to say there won’t be problem accessing the R6 server with an R5 client, until and unless i don’t do any design upgrade and also compact databases. is that right? And what about the synchronization of the windows active directory with the domino directory. Like if i change the password at any of the end, say if it is for the windows login or thru’ notes client, i need to synchronize them and pave way for single sign on. So if you’ve any documentation and if you can clearly supplement me with the flow as to what has to be carried out, it would be of great help to me. Awaiting your reply.

Best Regards,

Anthony.

Subject: RE: Accessing R6 server with an R5 client.

Hi Anthony,

“there won’t be problem accessing the R6 server with an R5 client, until and unless i don’t do any design upgrade and also compact databases.”

Compacting the databases on the server is inconsequential - it’s the design replace that will make things look ugly. Compacting will just change the SERVERS ODS.

“And what about the synchronization of the windows active directory with the domino directory.”

As mentioned, changing the password through Notes (File->Security → User Security, then “Change password”) works 100% of the time in changing both the Notes.ID and the Windows password. I can’t say the same for “Ctrl+Alt+Delete”, “Change Password” as this has been a little flaky in my experience.

Just a side Note:

The Domino Directory ONLY stores the users Internet password, not the password to “log into” the notes client.

Notes security is not the “Username/Password stored in a server-based database” model used by Microsoft. The Notes.ID file that the user has access to is encrypted with a password, which is what the user enters when the Notes client starts. When you enter your password when Notes starts, you have not, at that point, even touched a server. The ID file contains security certificates, which are unlocked when the correct password is entered, and those certificates are exchanged with the server to establish a trust relationship between the client and server.

Also, if the user changes the Notes password using the Notes client, the administrator can configure the server to synchronise the Notes password (stored in the ID file) and the Internet password (Stored in the person document in the Domino Directory).

So changing a password using the Notes option, ensures that a users Notes, Windows and Internet password will always be synchronised.

HTH

Regards,

Mat

Subject: Great explanation Mat. This is a hard one to explain to some people.

Subject: Thanks Bill - It would be pretty bad if I couldn’t explain stuff like this :slight_smile:

Subject: RE: Accessing R6 server with an R5 client.

Dear All

After working for notes since 4.51, i agree with Matt.

I to, have R6 servers and r5 servers with a mixture of R6(mine!) & R5 clients(users!). However, from the initial problems i had accessing old archive databases on CD, see my postings!, and talking extensively with Lotus, I have upgraded my main servers first.

A server of higher version will “know” what has happened in the past and hence can interpret an old clients, or servers requests… logical really. If you upgraded your clients first, and then the client requested a function which the old version of server knew nowt about problems could arise.

In my view I’d upgrade the servers first, but not any design changes , and then the clients, once complete design upgrades can occur. I’d also advise doing this on a non-production server to ensure any special databases you have designed work, before going live.

Kind regards

Rod