This document describes the minimum configuration requirements when installing the SAFE X3 management console on Microsoft Windows.
Category | Configuration requirements |
---|
Operating system | - Microsoft Windows 2016
- Microsoft Windows 2012 and 2012 R2 32-bit or 64-bit.
- Microsoft Windows 7, 8 and 8.1 32-bit or 64-bit, 10.
- Starter, Home, RT, Phone, CE, Mobile and Embedded Microsoft Windows versions are not supported.
|
Computer | - Industry-standard server or virtual machine:
- Intel® Xeon®, AMD OPTERON™ or EPYC™
- Standard PC:
- Intel Pentium/Celeron/Centrino/i3/i5/i7 1.6GHz (or >) or AMD Athlon recommended.
|
RAM | - 1 GB required for the SAFE X3 Console.
|
Disk space | - 100 MB required for the SAFE X3 Console.
- An additional 50 MB is required as temporary space under the user profile for standard use.
- To use the remote import functionality, additional temporary disk space is needed under the user profile to store a compressed archive. Its size will depend on the associated data volume, it may be several Gigabytes.
|
.Net Framework | Microsoft .Net Framework version 4.6.- You need to manually install the latest update of the .Net Framework 4.6 package.
- Since Windows 8 and Windows Server 2012, .Net Framework 4.6 is now a Feature on Demand. The administrator only needs to enable the .Net Framework 4.6 feature.
|
Pre-requisites during the configuration | - Windows target servers: The distant user used by the console for configuration operations on the target server must be authorized to open a session as a service.
- Unix target servers: The distant user used by the console for configuration operations on the target server must have access and modification rights on the files installed through the adinstall.sh procedure.
- Oracle database: To configure the Oracle database, the distant user used by the console must have the SYSDBA rights (usually by being part of the dba group under a target server such as Unix, or the ORA_DBA group on a target server such as Microsoft Windows).
Caution: As the console uses VBS scripts, avoid blocking the execution of these scripts on target servers such as Microsoft Windows. |