In my case, for network distribution, system support has setup a directory and batch file that copies files from the server to the local machine. Most of the my users don't need access to the R> so I have an R:Complied exe that is copied to the user's c:\batch\rbase folder and then a shortcut that is copied to Desktop\Rbase folder which refers to the exe file. A similar process is used for copying the files for R:base. With the corporate program the files don't need a license key to be installed.
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sami Aaron Posted At: Monday, October 31, 2005 11:58 AM Posted To: RB7-L Conversation: [RBG7-L] - Multi-User installation options Subject: [RBG7-L] - Multi-User installation options Near the end of the R:BASE Developers' Conference, Cheryl McClure asked for more information on the easiest way to manage R:BASE version upgrades with multiple users across networks. Since there wasn't time to bring it up during the conference, I told her I'd open a discussion on this topic on the list, to get feedback from other users. In my own experience, I have set up all my multi-user installations of R:BASE version 7.0, 7.1, and 7.5 using the "Server" installation. To do this, the first time I install R:BASE, I change the default drive/folder to be a shared network drive, say, R:\APPS\RBTI\RBG75. By selecting the "Server" installation option, the R:BASE installer will place the required files in my target folder - and NO files will be placed in the local Windows/WINNT or System32 folders. Then, create a desktop shortcut using the "-A" startup option to tell R:BASE where to find the required files. A sample shortcut is: Target: R:\APPS\RBTI\RBG75\RBG75.EXE -A Startup.rmd Start In: G:\DATA\RBDATA This way, if there is a new user or a new computer, the users just have to copy the shortcut to their desktop, enter the license key and activation key once. After that, if there is a bug patch or new build of R:BASE, I can install it once using the "server" installation and pointing to the shared folder, and it is seamless for the end user - the next time they open R:BASE they will be running the new build. The only drawback is if the user needs the R:BASE ODBC files set up - and then you'd want to also install R:BASE on that user's workstation. I have tested this on a couple of networks, including Terminal Server and Citrix configurations, and do not see any speed degradation with the R:BASE program files residing on the server. I'd be interesting in hearing how other developers have managed their network installations. Sami Aaron Software Management Specialists 913-915-1971 [EMAIL PROTECTED]
