Implementing Remote Access
The remote access functionality allows the computers to be accessed remotely from your 4biz instance. In this sense, we use the Virtual Network Computing (VNC) protocol resources through the Apache Guacamole - a web-based remote access gateway - to make this operation feasible. In addition to being able to remotely access a configuration item, all sessions are saved and made available to the CI information. This ensures better control over the actions taken by providing a reliable and auditable environment.
This functionality is an add-on to Configuration Management and depends on the inventory process to make viable remote access to a CI.
Having the inventory process defined and functional using the 4biz Inventory;
Having inventoried the configuration items;
- Install the GuaCD using the official documentation or download the container provided by 4biz. It is not necessary to install the guacamole-client, since 4biz only uses the Guacamole daemon, that is, the GuaCD;
- After installation, set up the logs;
3. Download the (.jar) video encoder (in the partner portal downloads center) - which compiles the videos from the sessions;
4. Copy the video encoder to the server;
5. Perform the configuration by replacing the variables with the information of your server;
6. Set directory for recording videos (eg.: /mp4);
🖊 Nota: Video Recording:
After the remote access session ends, the generated video enters a compilation queue and, then made available on the platform. The time of compilation will depend on the time of the session, in addition, the beginning of the compilation is linked to the cron routine defined in the remote access connection.
7. In the configuration item that will be accessed remotely (eg.: Windows Computer), install a remote access client with VNC protocol support (eg.: TightVNC) and set an access password. Save this password as it will be used in the next step;
8. Perform the registration of Remote Access connections in your instance according to the document.
With GuaCD service active and communicable, the next step is to remotely access the configured CI.
