Skip to main content

I am in the process of upgrading from RM/Cobol with WOW-Extensions version 10.01 to 12.17. In the past we did a Administrative Installation for the runtime due to it being on a network drive. There is a bug though with the Administrative installation so we're now doing the standard installation and we'll be installing the runtime on up to 125 end-users pcs. My question is what, if any, changes are needed when going from the Administrative Installation to Standard Installation in regards to licensing. Specifically in regards to the license.vlt file.

I am in the process of upgrading from RM/Cobol with WOW-Extensions version 10.01 to 12.17. In the past we did a Administrative Installation for the runtime due to it being on a network drive. There is a bug though with the Administrative installation so we're now doing the standard installation and we'll be installing the runtime on up to 125 end-users pcs. My question is what, if any, changes are needed when going from the Administrative Installation to Standard Installation in regards to licensing. Specifically in regards to the license.vlt file.

<<My question is what, if any, changes are needed when going from the Administrative Installation to Standard Installation in regards to licensing. Specifically in regards to the license.vlt file.>>

First, the Administrative install is supposed to work, so we'd be interested in the problem that you are encountering. In the 12.17 release testing, someone reported a problem but, as we looked at the issue, it suddenly went away. We think that this is some sort of Windows permissions problem. Since the installation is now using the Windows Installer, which is Microsoft technology, we were hoping that Microsoft would support it.

Second, my recommendation is to either download the ISO file from your order or take your downloadable exe file, and place the actual installation on your shared drive.  For the ISO, you simply have to mount the ISO on Windows and then copy the files to the share.  For the exe file, start the exe, it will self-extract to a temporary directory and then start RM-Install. When the opening screen of RM-Install appears, press the Browse button. At that point, you'll be in the temporary directory that the exe was extracted into.  Copy the files into your share, close the Windows Explorer, and terminate the installation.  Finally, on your share, place the license certificates (the .lic files) that you want to install.  Then, your client machines just need to run RM-Install to perform the installation.

Third, if you want RM Install to be more automated, you can create an rm-install.ini file in the share that you can use to preanswer prompts and even make the program be completely silent.  See the rm-install.pdf file. I believe it is one of the documentation files that you can download with your order.

Fourth, if you don't want to bother with RM Install, you can execute the MSI directly on the client machine. Again, I recommend looking at the rm-install.pdf file, which is also on the support website. If you can't find it, just let me know and I'll find a definitive source for you.

Fifth, you should not do anything with the license.vlt file. The installation creates it and will remove it when the last license is removed from it. The .lic files are what you should be using and, if they are placed in the directory with rm-install, it will automatically find them.

Mike Schultz