Professional Documents
Culture Documents
Simio Installation Notes
Simio Installation Notes
The Simio Release Notes and the Simio Reference Guide are both available using the links on
Simio’s Support Ribbon. Or you can find them in the install folder (by default \Program
Files\Simio).
If you have difficulties during download or installation, you can go to the Simio User Forum
which is a searchable on-line knowledgebase and your connection to thousands of other Simio
users. See the first topic to become a Simio Insider and get full forum access. You can also
contact Simio support at support@simio.com.
However, Simio only requires .NET Client Profile. You can download the Client Profile via a
Standalone Installer or Web Installer. The Standalone version is a larger download, while the
Web version requires an internet connection during installation. It may also be installed by
doing a Windows Update, depending upon your particular system configuration.
First create a new directory on your desktop called DirectXInstall. When you have downloaded
directx_mar2009_redist.exe, double click to open it. When prompted, choose the DirectXInstall
directory on your desktop as the location to extract the contents of the archive. Now, go into
the DirectXInstall directory, and double click on DXSETUP.exe. This should install the proper
DirectX components onto your machine.
Once DXSETUP.exe is finished, you can delete both the new directory on your desktop and
directx_mar2009_redist.exe.
Step 3 – If you have not already installed Simio, you can now install the Simio software itself
by starting setup.exe from the downloaded Simio zip file.
Simio can be activated with a command-line argument. So after deploying the image, one can
run a post-deployment step that looks something like this:
C:\Program Files\Simio\Simio.exe -authenticate:THIS-ISMY-AUTH-KEY
Simio will set the "errorlevel" value to 0 if the authentication is successful, or 1 if not. Note that
in order to authenticate, Simio must be able to connect to the internet to access our
authentication web service.
The authentication is based on the machine name, so this post-deployment step would have to
run after each computer has been given its final unique name. This implies that if a particular
machine needs to be re-deployed, it would need to be given the same machine name as before,
otherwise the re-authentication process would consume another valid authentication from the
key.