Client Upgrades

Background: I’m currently running a Windows NT4 Terminal Server environment. I have 3 Notes clients installed. Notes 4.6.4, 5.0.11, and 6.0.2CF1 on each of my Terminal Servers. Each version of notes points to their own Notes Data folder, meaning, if a user is on R4, their data path is M:\notesdata\notes.ini, if the user is an R6 client it is M:\notesdata6\notes.ini.

This is how it was setup when I was put in charge of the Terminal Servers. I am now trying to set these up so I can seemlessly upgrade the clients. Hopefully by just installing the new client on the Terminal Server.

I did some testing though, and was having some problems. I created some test icons for myself. Notes 4, Notes 5, and Notes 6 icons. All the test icons had their INI path going to the same place, which was M:\notesdata\notes.ini. I figured I would create a Notes 4 user, set it up, made sure it worked as Notes 4. Then click the Notes 5 icon and let it “upgrade” the user. Well, it didn’t work as expected. Came back with an error that it wasn’t able to find a file. I THINK it was bookmark.nsf, not sure yet.

Now to get to the point of this post. How WOULD I go about upgrading 500+ users in this environment? Do I have to write a script to cycle through 500+ NOTESDATA directories and add the appropriate files to them?

If you want/need more information about this, please ask as I would REALLY like to get some help on this.

Thanks!