cliu
e90ad790a2
New knowledge/r105-verification.md lists the R1.05 functions not available on the test server (not tested) and the read-only steps prepared for the user to verify on the server or in the GUI (eqpdbg, setup_check.ps1, Engineering Module forms) plus the CI-Eng-Sample load decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.5 KiB
3.5 KiB
| name | description |
|---|---|
| installation-security | CI Server R1.05 installation, upgrade and Windows/IT security. Use when the user wants to prepare Windows for CI Server, check whether a machine meets the setup requirements, install, reinstall, upgrade or uninstall CI Server, merge configuration files after an upgrade (automatic merge, jupgutl, upgrade report), apply or extend a licence, install CI Server Remote Connect, set up Vnet/IP drivers or network addresses, apply the IT Security Tool (IT security version 2.0 or 3.0), set up LAPS, check or open firewall ports, manage the CIX_ groups and CIX_PROCESS account, install CI Server next to PRM, or run CI Server on a virtual machine. Sources IM 36K01C10-01EN and IM 36K01C30-01EN (5th editions). |
Installation and security (R1.05)
First written for R1.03 (frozen on branch r1.03), re-checked against the R1.05 manuals
(5th editions, Feb. 2026) and the R1.05 test server on 2026-10-08.
Background: knowledge/manuals/IM36K01C10-01EN.md (Setup) and
knowledge/manuals/IM36K01C30-01EN.md (Security Guide). Known issues:
knowledge/manuals/IM36K01A50-01EN.md (IT Security tool, install path, VMs).
Rules:
- Run the
system-checkskill first. - Installing, upgrading, changing Windows settings or IT security needs an elevated session, changes the machine and often needs restarts: follow the user's chosen way of working and confirm before each step. In prepare only mode, produce a checklist for the user.
- Never copy old setup files over new ones after an upgrade: compare and merge. The R1.05 automatic merge does not cover every file (Setup summary §3).
- Before a reinstall or upgrade, set the startup type of CI Service and VAGW Bossd to
Manual. From R1.04 VAGW Bossd is stopped and started with
vagwstarter.exe(Setup summary §3). - Read paths from the
TLS_*variables: the manuals print the default install paths, which may not be where CI Server is installed (ISS-086). - IT security (IT Security Tool, CIX_ groups, LAPS) is not tested on R1.05 (from docs): the
R1.05 test server runs Windows Server 2025, where the tool is not supported, and it is not
installed. Vnet/IP, the upgrade merge and PRM are not tested either (see
knowledge/r105-verification.md).
| Task | Where | Status |
|---|---|---|
| Check a machine against the setup and security requirements | tasks/setup-check.md |
verified (R1.03; R1.05 checks run one by one) |
| New installation (physical, VM, dual-redundant): order of work, Windows settings, Vnet/IP, install, IT security, licence | Setup summary §2 | from docs |
| Start/stop CI Server and VAGW Bossd, reinstall, upgrade (incl. HAC), extend licence, uninstall | Setup summary §3 | from docs |
Upgrade with automatic merge of configuration files (installer checkbox, jupgutl, merge report and conflict log) |
Setup summary §3 | from docs (files and merge patterns checked on the R1.05 test server) |
| Install CI Server Remote Connect; web ports | Setup summary §2.4 | from docs |
| CI Server and PRM on one computer or connected | Setup summary §4 | from docs |
| Firewall ports for CI Server and drivers | Security Guide summary §3 | from docs (web, DURM, SMDMON, RESTful API ports checked on R1.03 / R1.05) |
| IT Security Tool (version 2.0 / 3.0), user management types, CIX_ groups/accounts, change service account | Security Guide summary §2, §5, §7 | from docs |
| LAPS (linked domain management with IT security 3.0) | Setup summary §2.1.6, Security Guide summary §7 | from docs |