Initializing PowerShell framework and VMware PowerCLI modules in the background.
-This usually takes 5-10 seconds. You will be redirected automatically.
-Checking PowerCLI version...
-
"
-} else {
- $LogoHtmlInjection = ""
-}
-
-# --- PRE-FLIGHT ENVIRONMENT CHECKS (PowerShell host + PowerCLI module) -----
-# Purely informational for the PowerShell host itself -- the script has no hard PS version
-# requirement beyond what PowerCLI already demands to load in the first place -- but this has
-# repeatedly been the first thing worth checking when troubleshooting a cryptic PowerCLI failure,
-# so it's captured up front rather than only reconstructable after the fact from scattered clues.
-Write-DebugLog "[+] Host PowerShell: $($PSVersionTable.PSVersion) ($($PSVersionTable.PSEdition)) on $(if ($PSVersionTable.Platform) { $PSVersionTable.Platform } else { 'Win32NT (Windows PowerShell)' })"
-
-try {
- $powerCliInstalled = Get-Module -ListAvailable -Name VMware.VimAutomation.Core
- if ($null -eq $powerCliInstalled) {
- Write-DebugLog "[-] CRITICAL: VMware PowerCLI module is missing."
- Write-Terminal "ERROR: VMware PowerCLI module is missing. Please install it to use MTAT." "Red"
- try {
- $wshell = New-Object -ComObject Wscript.Shell
- [void]$wshell.Popup("CRITICAL ERROR: VMware PowerCLI module is missing. Please install it to use MTAT.", 10, "MTAT Error", 16)
- } catch {}
- exit
- }
- $powerCliVersion = ($powerCliInstalled | Sort-Object Version -Descending | Select-Object -First 1).Version
- Write-DebugLog "[+] PowerCLI validated successfully (VMware.VimAutomation.Core version $powerCliVersion)."
-
- # Non-blocking on purpose: exact PowerCLI/vCenter compatibility boundaries aren't something this
- # tool can verify with confidence, so this only flags a version old enough that it's clearly
- # worth a look -- not a hard requirement that could incorrectly block a perfectly fine install.
- # Directly motivated by a real troubleshooting session where "Sequence contains no elements"
- # from Get-VM turned out to be an unrelated malformed VM, but an outdated PowerCLI was a
- # reasonable first suspect that's now worth ruling in/out immediately instead of mid-investigation.
- if ($null -ne $powerCliVersion -and $powerCliVersion.Major -lt 12) {
- Write-DebugLog "[!] WARNING: Installed PowerCLI ($powerCliVersion) is quite old. Memory Tiering itself requires vSphere 8.0 Update 3+, and an outdated PowerCLI is a common source of cryptic errors against newer vCenter/ESXi builds. If anything looks wrong, try: Update-Module VMware.PowerCLI -Force"
- }
-
- # -InvalidCertificateAction Ignore is a deliberate tradeoff, not an oversight: most vSphere
- # environments run vCenter/ESXi with self-signed certificates, and refusing those by default
- # would break this tool's core "just connect and assess" workflow for the majority of users.
- # This does mean TLS certificate validation is skipped for every vCenter connection made in this
- # session (a MITM risk on whatever network path this tool's traffic takes) -- acceptable for an
- # internal assessment tool, but worth knowing if this is ever deployed somewhere that matters.
- Set-PowerCLIConfiguration -Scope Session -DefaultVIServerMode Multiple -InvalidCertificateAction Ignore -ParticipateInCEIP $false -Confirm:$false | Out-Null
-} catch {
- Write-DebugLog "[-] Pre-flight initialization failed: $(Get-FullExceptionText $_)"
-}
-
-# --- BACKGROUND VERSION-CHECK JOB (best-effort, non-blocking) --------------
-# PowerCLI only -- an outdated PowerCLI is a real, recurring source of cryptic errors against
-# newer vCenter/ESXi builds (see Add-KnownIssueHints below), so knowing a newer one exists has
-# concrete value. The host PowerShell version is purely informational either way (nothing in this
-# tool requires PS7+), so it isn't checked or displayed here to avoid the added complexity/noise
-# for no real benefit.
-# Kicked off now so it runs concurrently with the rest of startup, before the HTTP listener/UI
-# are even up -- by the time a browser reaches the splash screen and starts polling, this is
-# often already finished or close to it. Runs in a separate PowerShell process (Start-Job), so
-# even if the lookup hangs, it can never delay or block the engine coming up. Environments with no
-# internet egress (common on isolated vSphere management networks) simply time out below, and the
-# UI shows "unable to check" -- this is expected and never treated as an error.
-$currentPowerCliVersionString = if ($null -ne $powerCliVersion) { $powerCliVersion.ToString() } else { "Unknown" }
-
-$global:LatestVersionInfo = [PSCustomObject]@{
- CurrentPowerCli = $currentPowerCliVersionString
- LatestPowerCli = $null
- Status = "checking"
-}
-
-$versionCheckJob = $null
-$versionCheckJobStartTime = Get-Date
-try {
- $versionCheckJob = Start-Job -ScriptBlock {
- $jobResult = [PSCustomObject]@{
- LatestPowerCli = $null
- }
-
- try {
- $module = Find-Module -Name VMware.PowerCLI -Repository PSGallery -ErrorAction Stop
- if ($module) {
- $jobResult.LatestPowerCli = $module.Version.ToString()
- }
- } catch {
- # Best-effort: no internet, DNS failure, corporate proxy blocking egress, PSGallery
- # being unreachable, etc. are all expected, normal outcomes here -- not logged as errors.
- }
-
- return $jobResult
- }
- Write-DebugLog "[+] Background version-check job started (PID job id $($versionCheckJob.Id))."
-} catch {
- Write-DebugLog "[-] Could not start background version-check job (non-fatal): $(Get-FullExceptionText $_)"
- $global:LatestVersionInfo.Status = "done"
-}
-
-function Update-VersionCheckJobStatus {
- # Non-blocking: only acts if the job already finished, or has been running long enough that
- # it's not worth waiting on any longer. Safe to call frequently from the request loop.
- if ($null -eq $script:versionCheckJob) { return }
-
- if ($script:versionCheckJob.State -in @('Completed', 'Failed', 'Stopped')) {
- try {
- $jobResult = Receive-Job -Job $script:versionCheckJob -ErrorAction Stop
- if ($jobResult) {
- $global:LatestVersionInfo.LatestPowerCli = $jobResult.LatestPowerCli
- }
- Write-DebugLog "[+] Background version-check finished. Latest PowerCLI: $($jobResult.LatestPowerCli)"
- } catch {
- Write-DebugLog "[-] Background version-check job ended without usable results (non-fatal): $(Get-FullExceptionText $_)"
- } finally {
- try { Remove-Job -Job $script:versionCheckJob -Force -ErrorAction SilentlyContinue } catch {}
- $script:versionCheckJob = $null
- $global:LatestVersionInfo.Status = "done"
- }
- } elseif (((Get-Date) - $script:versionCheckJobStartTime).TotalSeconds -gt 15) {
- Write-DebugLog "[!] Background version-check exceeded 15s without finishing -- giving up (likely no internet egress from this host)."
- try { Stop-Job -Job $script:versionCheckJob -ErrorAction SilentlyContinue } catch {}
- try { Remove-Job -Job $script:versionCheckJob -Force -ErrorAction SilentlyContinue } catch {}
- $script:versionCheckJob = $null
- $global:LatestVersionInfo.Status = "done"
- }
-}
-
-$url = "http://127.0.0.1:$targetPort/"
-$listener = New-Object System.Net.HttpListener
-$listener.Prefixes.Add($url)
-
-try {
- $listener.Start()
- Write-DebugLog "[+] HTTP daemon bound to network port $targetPort successfully."
-} catch {
- Write-DebugLog "[-] CRITICAL: Port $targetPort bind failed. $(Get-FullExceptionText $_)"
- exit
-}
-
-Write-Terminal "===========================================================" "Cyan"
-Write-Terminal "[*] Engine is LIVE and ready!" "Green"
-Write-Terminal "[*] Launching MTAT interface in your default web browser..." "Green"
-Write-Terminal " (If it does not open automatically, browse to: $url)" "Yellow"
-Write-Terminal "===========================================================" "Cyan"
-Write-Terminal "Please leave this window open while using the tool. Press Ctrl+C to exit." "DarkGray"
-
-# ==========================================
-# --- LITERAL FRONT-END INTERFACE (HTML5) --
-# ==========================================
-$htmlContent = @'
-
-
-
-
-
-
-