Preparing the network installation
Before you start the installation in a network area, you should have finished some preliminaries.
Establish prerequisites for the use of the automatic update function
Please note the additional requirements for using the Automatic Update Function.
Create an installation directory inside your network
The existence of an installation directory is a precondition for later use of the !
Create a directory on the server and copy the complete contents of the installation package into this installation directory.
All workstations must have at least read permission for the installation directory - define access rights if necessary.
Determine the network directory and data directories
During installation, a network directory for and some (subordinated) data directories are created on the server PC. Clients will get a local program directory and access shared data in the data directories on the server. Also, some files in the directory are shared, e.g. he , which centrally controls the layout of (printed) output.
The installation suggests default directories.
- Decide in which network directory the server installation should take place.
You have to ensure that all clients have 'read' and 'write'-permission for this installation directory on the server PC!
The server installation includes:
A) One directory for Central settings (with shared files) and
B) Data directory(s) - default: \User Data - e.g. as a subdirectory of the Central Settings directory, which holds the shared data.In the \User Data directory, the following subdirectories are automatically created during installation:
\User Data\Libraries
\User Data\Sample Data
\User Data\Projects
\User Data\System templates
These directories are then displayed in their own areas in the
- Create a network drive (if not done yet) on each client PC, which is mapped to the directory you determined in 1. A), e.g. P:\ on the client is mapped to D:\SOFTWARE\ORCA AVA on the server.
Of course, you can execute the mapping of the network drive, when you access the clients for the initial installation, however, in every case: before you run the installation on the client PC.
Please note:
- For the installation First workstation and network directory some files are installed into the directory (1.A) and into the data directories (1.B). You have to run the installation of exclusively - this means:
The application must not be run on any other network client during installation. This is valid for the initial installation, for updates and maintenance installations. (It is generally recommended to close all other programs - before installing.) - do not install into (no data either) - therefore they do not have be run exclusively.
- During the initial installation, you must access each workstation in order to install the application from there. Updates can later be installed automatically on the individual workstations - see Automatic update function.
- If you are using a system for software deployment/rollout:
- The update for has to be run just one time explicitly. Therefore, it should not be part of your deployment/roll out routine. Only the updates for are part of the deployment/roll out.
For the installation of ORCA AVA, specific software components are required.
If you start the installation using the Setup.exe or Update.exe or from within ORCA SOLUTIONS, these components will be installed automatically.
If you use the Msi package InstallOrca.msi with your rollout software, you must ensure that these components are installed before you start the (update) installation. You can also call these components with a silent installation parameter in a batch file, for example, "vcredist_x64.exe /q"; unless a different silent parameter is specified for the software component.
Microsoft Windows Desktop |
You can find the installation file in the directory: \ISSetupPrerequisites\{83261F85-EB7A-4F82-887F-F96B051FC656} of the installation package or in the installation directory: |
Microsoft Windows Desktop |
You can find the installation file in the directory: \ISSetupPrerequisites\{61296F22-77F7-4721-9E28-203533D0A17D} of the installation package or in the installation directory: |
Microsoft ASP .NET Core 8.0.11 - Shared Framework (x64) |
You can find the installation file in the directory: \ISSetupPrerequisites\{8AF67105-977E-486D-9AC4-DB0D6B96F00F} of the installation package or in the installation directory: |
Microsoft ASP .NET Core 8.0.11 - Shared Framework (x86) |
You can find the installation file in the directory: \ISSetupPrerequisites\{BCFF0072-5F65-4619-86A9-76666C34C87D} of the installation package or in the installation directory: |
.NET Framework 4.8 |
You can find the installation file in the directory: \ISSetupPrerequisites\{AA221105-04C0-4298-BBBD-47A1456ED2E1} of the installation package or in the installation directory: ndp48-x86-x64-allos-enu.exe |
Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.34.31931 |
You can find the installation file in the directory: \ISSetupPrerequisites\{237BF186-A2AF-48C2-BFC9-0AA2DA3829DD} of the installation package or in the installation directory: |
Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.34.31931 |
You can find the installation file in the directory: \ISSetupPrerequisites\{72AAD3AB-420C-41F0-9BE5-D854C4037DEF} of the installation package or in the installation directory: |
Microsoft Edge WebView2 Runtime x64 |
You can find the installation file in the directory: \ISSetupPrerequisites\{7C442069-A3CD-4344-9E4A-4E9A13EDD3F9} of the installation package or in the installation directory: MicrosoftEdgeWebView2RuntimeInstallerX64.exe |
