Installing EnSight 10.0 on Windows without admin privileges

The following process will only work with EnSight 10.0.2(c) or later distributions.

EnSight 10.0 relies on a specific version of the the Visual C++ 2008 runtime library, which traditionally requires admin privileges to install. Starting with the EnSight 10.0.2(c), release, CEI changed the version of the runtime to make it possible to install the CEI software suite without installing the runtime. 

This capability is considered to be in 'beta' status for the present. At some point, the stand-alone .exe installer may use this same mechanism, but for now, it is only available via a 'tarball' installation. 

Here are the basic steps to install EnSight 10.0.2(c) on a Windows system without using the stand-alone installer:

1) Download and unpack the 'All platforms' distribution ('.tgz' file).  A tool like 7-zip will be able to unpack the file. The extracted files should start at a directory named 'CEI'.  This directory will become the CEI_HOME directory.

2) Create a sub-directory of CEI named 'bin'.  For all of the other sub-directories of CEI, find the ones with a 'bin' sub-directory.  Copy the files from these bin sub-directories into the 'CEI/bin' directory. For a complete install, the directories should include: reveal30/bin, license8/bin, envideo100/bin, enve40/bin, ensight100gui/bin, ensight100/bin, 
enliten100/bin, ceistl100/bin, ceistl100/bin, apex30jt/bin, apex30/bin, abaqus100/bin. On Linux, the commands:

cd CEI
mkdir bin
cp */bin/* bin

will accomplish this task.

3) Two environmental variables need to be set for EnSight to run from this install on Windows.  Set CEI_HOME to the directory name of the 'CEI' file and add %CEI_HOME%/bin to the current PATH environmental variable. In a Windows cmd shell, these steps would be:

set CEI_HOME=C:\MyTempInst\CEI
set PATH=%CEI_HOME%\bin;%PATH%

4) At this point, you should be able to run our application suite from the command line. This type of installation will not make desktop icons, nor create file associations.

5) An optional step: the size of the distribution can be reduced by removing the files for Linux and OSX, at the expense of the Windows install not being able to create pack-n-go files for those platforms.  In each of the application sub-directories, there will be a 'machines' directory.  One can remove the dirs: apple_10.5  linux_2.6_32 linux_2.6_64 for a Windows only install. Under Linux, the commands would be:

cd CEI
rm -rf */machines/linux_*
rm -rf */machines/apple_*

This will result in an install that only runs on Windows.


One can also take the initial steps using the distributed Windows installer, instead of the tarball distribution. The Windows installer still requires admin privs to install, however once the install has be performed on a system, one should be able to copy the %CEI_HOME% directory to another machine.  Once that is done, one need only update the CEI_HOME and PATH environmental variables as in step (3) above to be able to run EnSight from the command line on another Windows system. 
The initial installation should be to a 64bit Windows machine if you use this method to generate the tree structure.


If, after following these steps, the various CEI tools will not launch on your system, please report your system details to CEI.  If you do have admin access, you can execute the following files on the target machine to fix the install. These files will automatically elevate access as needed when run:


On a 32bit Windows system, you only need to run the two 'win32' files. On a 64bit Windows system, you need to run all four files.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request