WINDOWS INSTALLATION

The method used to install the server on Windows depends on the type of system.

Simply execute the downloaded setup executable.

Use Control Panel, Add/Remove Programs, and execute the setup executable.

Right-click the setup executable, and ‘Run As Administrator’.

Use Control Panel, Install Application on Terminal Server, and execute the setup executable.  Later versions refer to "Terminal Server" and "Remote Desktop Services".

Follow the on-screen prompts from the installer to install UnForm to your system.  This will install both the server program and a local client (uf90c.exe) program.  The client program and its associated support files will be installed in both the server directory and in the Windows System directory, enabling a command line launch without a full path, as the Windows System directory is generally included in the PATH environment variable.

This will also install shortcuts to the server manager and documentation, under the Start, Programs, UnForm 9.0 Server menu.  Run the server manager to activate and operate the server.

Windows XP and 2003

UnForm contains components written in .NET 4, which is compatible with systems from Windows 2003/XP and up. Windows 2003 and XP will not have .NET 4 installed by default, so it may be necessary to install it.

Note that prior to 9.0.26, these components were written in .NET 3.5, which would not be installed by default on Windows 2008 and up, requiring an install of the .NET 2/3.5 runtime.

Permissions

Often, a local UnForm client (uf90c.exe) is used to submit jobs to the UnForm server.  When the client connects to the server "localhost", it knows it is running on the same system, and will copy submission files, and when needed retrieve output files, directly to and from the server's "temp" sub-directory.  The installer will attempt to grant the special user "Everyone" full rights to that directory, but if this fails, and administrator can add this access manually.

Client Path Access

The local client is installed in the server folder, and an attempt is also made to copy the uf90c*.* files to the System32 and SysWow64 directories to enable path-free execution.  However, on some systems this does not work for a setup script, so you can take one of several approaches: