Previously the stage indices reflected logical milestones but not the order they fire in. Run-ShopfloorSetup posted idx=1 (start) and idx=4 (PPKG) - but 09-Setup-Keyence (inside per-type loop) ran BETWEEN them and posted idx=5/6. The dashboard then "regressed" from 6 back to 4 when PPKG fired, making it look stuck at the per-type-complete card. New numbering matches actual execution order: 1 - WinPE: PESetup / WIM apply (startnet.cmd) 2 - Run-ShopfloorSetup: starting (Run-ShopfloorSetup.ps1) 3 - 09-Setup-<Type>: starting (per-type) 4 - 09-Setup-<Type>: complete (per-type) 5 - Run-ShopfloorSetup: PPKG enrollment (Run-ShopfloorSetup.ps1) 6 - Run-ShopfloorSetup: handoff to Monitor (Run-ShopfloorSetup.ps1) 7 - Monitor-IntuneProgress: Intune Device ID captured services/imaging_status.py rewind threshold reverts to stage_index <= 1 now that WinPE startnet posts idx=1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
186 lines
8.4 KiB
PowerShell
186 lines
8.4 KiB
PowerShell
# 09-Setup-CMM.ps1 - CMM type setup (runs during shopfloor-setup phase).
|
|
#
|
|
# At imaging time the tsgwp00525 SFLD share is NOT yet reachable - Azure DSC
|
|
# has not provisioned the share credentials that early. So we install from a
|
|
# WinPE-staged local copy at C:\CMM-Install (put there by startnet.cmd when
|
|
# the tech picks pc-type=CMM). Ongoing enforcement is handled by GE-Enforce
|
|
# (registered separately in Run-ShopfloorSetup.ps1) reading cmm/manifest.json
|
|
# from the tsgwp00525 share.
|
|
#
|
|
# Sequence:
|
|
# 1. Enable .NET Framework 3.5 (PC-DMIS 2016 prereq on Win10/11 where 3.5
|
|
# is an off-by-default optional feature).
|
|
# 2. Run Install-FromManifest against C:\CMM-Install\cmm-manifest.json.
|
|
# 2.5. Grant BUILTIN\Users Modify on PC-DMIS install dirs (Hexagon-documented
|
|
# approach for non-admin runtime).
|
|
# 3. Delete C:\CMM-Install to reclaim the ~2 GB of bootstrap installers.
|
|
#
|
|
# Library lookup: the imaging-time install uses the common Install-FromManifest
|
|
# library at ..\common\lib\Install-FromManifest.ps1 (relative to $PSScriptRoot).
|
|
#
|
|
# Log: C:\Logs\CMM\09-Setup-CMM.log (stdout from this script) plus the
|
|
# install-time log at C:\Logs\CMM\install.log written by Install-FromManifest.
|
|
|
|
$ErrorActionPreference = 'Continue'
|
|
|
|
$stagingRoot = 'C:\CMM-Install'
|
|
$stagingMani = Join-Path $stagingRoot 'cmm-manifest.json'
|
|
$libSource = Join-Path $PSScriptRoot '..\common\lib\Install-FromManifest.ps1'
|
|
|
|
$logDir = 'C:\Logs\CMM'
|
|
$logFile = Join-Path $logDir 'install.log'
|
|
$transcriptLog = Join-Path $logDir '09-Setup-CMM.log'
|
|
|
|
if (-not (Test-Path $logDir)) {
|
|
New-Item -Path $logDir -ItemType Directory -Force | Out-Null
|
|
}
|
|
|
|
# Independent transcript in addition to whatever Run-ShopfloorSetup.ps1 is
|
|
# capturing at the top level. Lets a tech open C:\Logs\CMM\09-Setup-CMM.log
|
|
# and see the entire CMM-type setup run without scrolling through the
|
|
# monolithic shopfloor-setup.log.
|
|
try { Start-Transcript -Path $transcriptLog -Append -Force | Out-Null } catch {}
|
|
|
|
function Write-CMMLog {
|
|
param([string]$Message, [string]$Level = 'INFO')
|
|
$stamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
|
|
Write-Host "[$stamp] [$Level] $Message"
|
|
}
|
|
|
|
Write-CMMLog "================================================================"
|
|
Write-CMMLog "=== CMM Setup (imaging-time) session start (PID $PID) ==="
|
|
Write-CMMLog "Running as: $([System.Security.Principal.WindowsIdentity]::GetCurrent().Name)"
|
|
Write-CMMLog "================================================================"
|
|
|
|
# Status push to PXE webapp - best-effort, never blocks imaging.
|
|
$pxeStatusLib = Join-Path $PSScriptRoot '..\Shopfloor\lib\Send-PxeStatus.ps1'
|
|
if (Test-Path $pxeStatusLib) {
|
|
try { . $pxeStatusLib; Send-PxeStatus -Stage '09-Setup-CMM: starting' -StageIndex 3 -StageTotal 8 } catch { }
|
|
}
|
|
|
|
# Diagnostic dump - knowing WHY the script took a branch is half the battle.
|
|
Write-CMMLog "Script root: $PSScriptRoot"
|
|
foreach ($file in @('pc-type.txt','pc-subtype.txt','machine-number.txt')) {
|
|
$path = "C:\Enrollment\$file"
|
|
if (Test-Path -LiteralPath $path) {
|
|
$content = (Get-Content -LiteralPath $path -First 1 -ErrorAction SilentlyContinue).Trim()
|
|
Write-CMMLog " $file = $content"
|
|
} else {
|
|
Write-CMMLog " $file = (not present)"
|
|
}
|
|
}
|
|
if (Test-Path $stagingRoot) {
|
|
$bootstrapFiles = @(Get-ChildItem -LiteralPath $stagingRoot -File -ErrorAction SilentlyContinue)
|
|
Write-CMMLog "Bootstrap staging: $stagingRoot ($($bootstrapFiles.Count) files)"
|
|
foreach ($f in $bootstrapFiles) {
|
|
Write-CMMLog " - $($f.Name) ($([math]::Round($f.Length/1MB)) MB)"
|
|
}
|
|
} else {
|
|
Write-CMMLog "Bootstrap staging: $stagingRoot (DOES NOT EXIST - startnet.cmd did not stage it)" "ERROR"
|
|
}
|
|
|
|
# ============================================================================
|
|
# Step 1: Enable .NET Framework 3.5
|
|
# ============================================================================
|
|
# PC-DMIS 2016 lists .NET 3.5 as a prereq for some older components. On Win10/
|
|
# Win11 it's an optional Windows feature that is OFF by default. Enable-
|
|
# WindowsOptionalFeature pulls the payload from Windows Update when the PC
|
|
# has internet; sources from the installed Windows image otherwise. Idempotent
|
|
# (no-op if already enabled). We swallow failures because if internet and
|
|
# media are both unavailable this becomes a known gap rather than an imaging
|
|
# blocker - we'd still rather try to install PC-DMIS and surface the real
|
|
# failure in its log.
|
|
Write-CMMLog "Checking .NET Framework 3.5 state..."
|
|
try {
|
|
$netfx = Get-WindowsOptionalFeature -Online -FeatureName 'NetFx3' -ErrorAction Stop
|
|
if ($netfx.State -eq 'Enabled') {
|
|
Write-CMMLog " .NET 3.5 already enabled"
|
|
} else {
|
|
Write-CMMLog " .NET 3.5 state is $($netfx.State) - enabling now (may take a minute)..."
|
|
$result = Enable-WindowsOptionalFeature -Online -FeatureName 'NetFx3' -All -NoRestart -ErrorAction Stop
|
|
Write-CMMLog " Enable-WindowsOptionalFeature RestartNeeded=$($result.RestartNeeded)"
|
|
}
|
|
} catch {
|
|
Write-CMMLog " Failed to enable .NET 3.5: $_" "WARN"
|
|
Write-CMMLog " Continuing anyway - PC-DMIS installers will surface any hard dependency."
|
|
}
|
|
|
|
# ============================================================================
|
|
# Step 2: Install apps from the WinPE-staged bootstrap at C:\CMM-Install
|
|
# ============================================================================
|
|
if (-not (Test-Path $stagingRoot)) {
|
|
Write-CMMLog "$stagingRoot does not exist - startnet.cmd did not stage CMM installers" "ERROR"
|
|
Write-CMMLog "Skipping install. The logon enforcer will pick up from the share when SFLD creds are available."
|
|
}
|
|
elseif (-not (Test-Path $stagingMani)) {
|
|
Write-CMMLog "$stagingMani missing - staging directory is incomplete" "ERROR"
|
|
}
|
|
elseif (-not (Test-Path $libSource)) {
|
|
Write-CMMLog "Shared library not found at $libSource" "ERROR"
|
|
}
|
|
else {
|
|
Write-CMMLog "Running Install-FromManifest against $stagingRoot"
|
|
& $libSource -ManifestPath $stagingMani -InstallerRoot $stagingRoot -LogFile $logFile
|
|
$rc = $LASTEXITCODE
|
|
Write-CMMLog "Install-FromManifest returned $rc"
|
|
}
|
|
|
|
# ============================================================================
|
|
# Step 2.5: Grant Users write access to PC-DMIS install directories
|
|
# ============================================================================
|
|
# PC-DMIS writes settings, probe configs, and measurement data to its own
|
|
# install directory at runtime. Without Modify permission for BUILTIN\Users,
|
|
# non-admin accounts get a UAC elevation prompt on every launch. Granting
|
|
# the ACL here is the Hexagon-documented approach for non-admin deployment
|
|
# and avoids the need for a first-run-as-admin (which hits a license dialog
|
|
# and can't be automated silently).
|
|
$pcdmisDirs = @(
|
|
'C:\Program Files\Hexagon\PC-DMIS 2016.0 64-bit',
|
|
'C:\Program Files\Hexagon\PC-DMIS 2019 R2 64-bit',
|
|
'C:\ProgramData\Hexagon',
|
|
'C:\Program Files (x86)\General Electric\goCMM',
|
|
'C:\Program Files\DODA'
|
|
)
|
|
foreach ($dir in $pcdmisDirs) {
|
|
if (-not (Test-Path -LiteralPath $dir)) {
|
|
Write-CMMLog "PC-DMIS dir not found: $dir - skipping ACL"
|
|
continue
|
|
}
|
|
try {
|
|
$acl = Get-Acl -LiteralPath $dir
|
|
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule(
|
|
'BUILTIN\Users',
|
|
'Modify',
|
|
'ContainerInherit,ObjectInherit',
|
|
'None',
|
|
'Allow'
|
|
)
|
|
$acl.AddAccessRule($rule)
|
|
Set-Acl -LiteralPath $dir -AclObject $acl -ErrorAction Stop
|
|
Write-CMMLog "Granted BUILTIN\Users Modify on $dir"
|
|
} catch {
|
|
Write-CMMLog "Failed to set ACL on $dir : $_" "WARN"
|
|
}
|
|
}
|
|
|
|
# ============================================================================
|
|
# Step 3: Clean up the bootstrap staging dir
|
|
# ============================================================================
|
|
# ~2 GB reclaimed. From here on, GE-Enforce takes over from the tsgwp00525
|
|
# share for ongoing updates.
|
|
if (Test-Path $stagingRoot) {
|
|
Write-CMMLog "Deleting bootstrap staging at $stagingRoot"
|
|
try {
|
|
Remove-Item -LiteralPath $stagingRoot -Recurse -Force -ErrorAction Stop
|
|
Write-CMMLog "Bootstrap cleanup complete"
|
|
} catch {
|
|
Write-CMMLog "Failed to delete $stagingRoot : $_" "WARN"
|
|
}
|
|
}
|
|
|
|
if (Get-Command Send-PxeStatus -ErrorAction SilentlyContinue) {
|
|
Send-PxeStatus -Stage '09-Setup-CMM: complete' -StageIndex 4 -StageTotal 8
|
|
}
|
|
Write-CMMLog "=== CMM Setup Complete ==="
|
|
try { Stop-Transcript | Out-Null } catch {}
|