Spruce
Helix Spruce Product
Hosted Customers β€”

Loading customers…

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

Select a company to load users.
Servers β€”
Name β‡… DNS Hostname β‡… OS β‡… Version β‡… Last Logon β‡… Status β‡… Description β‡… Actions
πŸ–₯︝

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.

PS Forms β€”
πŸ“‹

Select this tab to load PS forms.

Details