ECSM101 - Epic Client System Manger – Hyperspace 2024/25 Hyperspace Client - ANSWER Hyperspace cannot be installed on a machine that hosts another of Epic's VB6 applications, such as HomeHealth or Analytics, due to resources that would end up being shared by these clients.Am I known? - ANSWER A Workstation Record or LSW must be identified in order for a connection to be successful. This LWS record can be specific to the machine establishing the connection, a generic LWS, or a record shared by multiple connections, depending on the connection being configured.Am I trusted? - ANSWER A fixed key is used to restrict access to the environment and to establish trust. The same fixed key must be defined in the Epic operational database environment as well as in the environment file. 1 / 3
Who Am I? - ANSWER The Epic environment attempts to find an LWS record that matches the one specified by the Client or workstation ID in the connection configuration. If no match is found, a generic LWS can be used if enabled.Where am I going? - ANSWER Destination environments must also be defined in order for a connection to be successful. The connection must provide details such as the hostname of the Epic operational database and the communications port the environment uses. You can define connection information for multiple environments within the same environment file.What is an Administrative Image? - ANSWER You can think of the installation packages (*.msi files) as a collection of compressed files and a database that includes instructions on how to install those files.An Administrative Image will be much larger than the original *.msi, because in an *.msi, the installation files have been decompressed. It is important to keep this large structure together when moving it from one location to another.Why is an Administrative Image Needed? - ANSWER You will install Hyperspace on many servers and workstations in your environment. To 2 / 3
avoid customizing each installation manually, you should create and customize a single package so that, when deployed, it works without further configuration.Can you run Hyperspace on x86 (32-bit) Windows 7? - ANSWER Yes, Hyperspace is technically compatible with 32-bit Windows 7; 32-bit Windows
- is not, however, a Target Platform, and running Hyperspace on this platform
- / 3
caries some risk of running into previously undiscovered issues.How is trust established between an Epic client and the Epic operational database environment? - ANSWER A fixed key will be defined on the client, usually in some type of environment file, and imported into the Epic environment.Why does Epic recommend creating a Hyperspace Administrative Image? - ANSWER Using a script to copy files carries a high chance of failure and would be logged separate from the installation. By creating a customized Hyperspace Administrative Image, an administrator can be sure that all necessary files will be on any client built from that customized image.