远程安装.NET 8 SDK：Invoke-Command失效而Enter-PSSession可用的原因

The discrepancy comes down to critical differences in how PowerShell manages remote session context, desktop access, and process lifecycle between non-interactive and interactive sessions. Here's the breakdown:

• Non-interactive sessions lack desktop access:
  The .NET SDK installer (even in quiet mode) may rely on components that require access to the interactive desktop session. Invoke-Command runs in a background non-interactive session (usually Session 0), which doesn't have access to the user's desktop environment. This can cause silent installers to fail without feedback because they can't initialize necessary UI-related subsystems. Enter-PSSession, however, runs in an active interactive user session with full desktop access, letting the installer complete all required steps.

• Session termination kills background processes:
  Invoke-Command creates a temporary remote session that closes immediately after the script block finishes. If the .NET installer spawns background processes (like post-install configuration or cleanup tasks), these get terminated early when the session ends. Enter-PSSession keeps the session alive, so all installer processes can run to completion.

• User profile isn't loaded by default:
  Invoke-Command doesn't load the remote user's profile unless you specify -LoadUserProfile, whereas Enter-PSSession loads it automatically. While the .NET installer doesn't explicitly need profile data, missing environment variables or registry settings from the profile could indirectly cause installation failures in non-interactive mode.

Fixes to Make Invoke-Command Work #

Try these tweaks to get the installation working via Invoke-Command:

1. Load the user profile:
   Use -LoadUserProfile to ensure the installer has access to the full user environment:

   Invoke-Command -ComputerName Server1 -LoadUserProfile {
     c:\temp\dotnet-sdk-8.0.301-win-x64.exe /install /quiet /norestart
   }
   

2. Wait for the installer to finish:
   Use Start-Process with -Wait to prevent the session from closing before the installer (and its background tasks) complete:

   Invoke-Command -ComputerName Server1 {
     Start-Process -FilePath "c:\temp\dotnet-sdk-8.0.301-win-x64.exe" -ArgumentList "/install /quiet /norestart" -Wait -NoNewWindow
   }
   

3. Enable interactive session access:
   If desktop access is mandatory, use session options to enable interactivity (requires appropriate permissions):

   $sessionOpts = New-PSSessionOption -Interactive -EnableNetworkAccess
   Invoke-Command -ComputerName Server1 -SessionOption $sessionOpts {
     c:\temp\dotnet-sdk-8.0.301-win-x64.exe /install /quiet /norestart
   }
   

内容的提问来源于stack exchange，提问作者Rod