Spruce
Helix Spruce Product
Spruce Fleet Dashboard β€”
Last refreshed: β€” SQL ok: β€” Errors: β€”
Hosted Customers β€”

Loading customers…

Users β€”
Display Name β‡… Username β‡… Last Logon β‡… Expires β‡… Status β‡… Pwd Last Set β‡…
πŸ‘€

Select a company to load users.
Software Download

Download software packages for a customer's installed Spruce version directly from the ECI Version Service.

Database Query

Run a read-only SELECT against a customer database. Use a template or type your query, then Prepare to add WITH (NOLOCK) and row limits before running. Results are capped at 500 rows.

RDS broker sessions β€”

Lists every active session from Get-RDUserSession on each connection broker. Passive HA nodes return no rows; the active broker returns all sessions.

User Session host ID State Collection / name Idle Logon Actions

Open this tab or press Refresh to load sessions from RDCBs.
Servers β€”
Name β‡… OS β‡… Version β‡… Last Logon β‡… Status β‡…
πŸ–₯︝

Select this tab to load servers.
Net-new customer install

Starts AWS_NewInstall_NetNew.ps1 on the WinRM orchestrator (detached). Poll shows the last lines of stdout/stderr from the orchestrator temp folder. SiteID must contain the NSID substring.

Stdout (tail)
β€”
Stderr (tail)
β€”
Customer setup

Modular steps that mirror AWS_NewInstall_NetNew.ps1 after the monolith was split. Each step calls the WinRM orchestrator independently (same SiteID / NSID / product as shared context below). Use Resolve POD context (cache) once per browser session to avoid repeating the expensive Get-PODEnvironment / Get-PODInfo work on every step (omit the checkbox to force a full resolve each time). Optional Run AD prep then folders runs both in order when you want one click without retyping.

Shared context

Used by every step. Fill once, then run any step (or the combined action at the bottom).

1Customer AD prep

OU, security group, RDS users (NSID-1 …), service account. Synchronous WinRM run. DCS for non-sandbox: HELIX_SPRUCE_POD_DCS on Helix.

2Create customer folders

DFS / file layout after AD prep. The orchestrator resolves POD context, then runs an ECiHostingTools layout cmdlet if one exists; otherwise Helix uses a built-in layout (physical folders under the POD cloud drive and New-DfsnFolder when a namespace parent can be resolved). Override with the optional cmdlet field if your HostingTools export uses a different name.

3More steps

Additional install phases will appear here as they are split from AWS_NewInstall_NetNew.ps1.

Event Log Capture

Select one or more RDS servers below. Choose a time window, then start capture. Results appear below when the job finishes β€” download a ZIP per host.

RDS Servers β€” select one or more targets
PS Forms β€”
πŸ“‹

Select this tab to load PS forms.

Customer Data
β€”
Site ID NetSuite ID POD Crystal User Vendor User Updated
Loading…
PS Data Review

Customer

β€”

Site ID

β€”

AD Users

β€”

Concurrent Seats

Spruce API URL

RCWS URL

Database Name

β€”

SQL Server

β€”

System Type

Server

β€”

Details