Mingcedar

Product: Mingcedar CONTROL

Windows installation and first access | Mingcedar

Run the installer as an administrator. The default root is C:\HQControl; another fixed local drive can be selected if it meets the installer requirements.

Published Updated

<div class="manual-doc-article manual-doc-article-section"><h2 id="windows-install">Windows: Windows installation and first access</h2>

Use the release package for the target system and deployment role. The installer prepares the required database, cache and Python environment.

<div class="doc-card-list doc-tutorial">

<article class="doc-card">

<h3 id="windows-install-item-1">Choose the installation role</h3>

<p>Run the installer as an administrator. The default root is C:\HQControl; another fixed local drive can be selected if it meets the installer requirements.</p>

<ol>

<li>Choose full for a complete host, managed data services and Python on one machine.</li>

<li>database installs PostgreSQL, TimescaleDB and Redis only. host installs the host and Python and uses prepared data services on the same machine.</li>

<li>Use dedicated-node only for an IO runtime with a prepared schema and same-machine PostgreSQL / Redis managed outside the installer. It provides no Web, Alarm, Trend or Python runtime. The client profile installs only client trust and access shortcuts.</li>

<li>Check mode, directory and dependencies before continuing. A mode locked by the installer entry cannot be changed.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="windows-install-item-2">Configure Portal and Screen addresses</h3>

<p>The default Portal uses HTTPS port 8080 and the separate Screen origin uses HTTPS port 8081. Use the endpoints reported by the installation.</p>

<ol>

<li>Choose a host name or IP reachable by every client. Portal and Screen must be different HTTPS origins.</li>

<li>Permit both endpoints for the intended clients and install the trusted certificate on those clients. PostgreSQL and Redis remain private, not client endpoints.</li>

<li>Open the Portal and then an actual runtime screen to verify the Screen endpoint. After changing public addresses, restart as indicated and reopen the browser entry.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="windows-install-item-3">Check installed services</h3>

<p>A complete host contains five runtime services: Web/App, IO, Alarm, Trend and Script.</p>

<ol>

<li>Check the five services, database and Redis in System Status, then inspect the current license on the License page.</li>

<li>Windows service names are HQControl, HQControlIO, HQControlAlarm, HQControlTrend and HQControlScript.</li>

<li>For unready services, check installation and service logs. Check Device connection and Tag values after configuration.</li>

</ol>

</article>

</div>

</div>