While the standard shutdown /r /m \\remotePC command works for basic remote restarts, Windows doesn't natively support remote safe mode booting through conventional commands. This creates challenges for sysadmins needing to troubleshoot problematic systems.

The most reliable method involves modifying the boot configuration database (BCD) registry hive remotely:

# PowerShell script for remote safe mode boot
$computer = "RemotePCName"
$regKey = "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Option"
$regValue = "OptionValue"

Invoke-Command -ComputerName $computer -ScriptBlock {
    Set-ItemProperty -Path ("Registry::" + $using:regKey) -Name $using:regValue -Value 1 -Force
    & bcdedit /set {default} safeboot network
    Restart-Computer -Force
}

For environments where PowerShell remoting isn't enabled, WMI provides another option:

wmic /node:RemotePCName process call create "cmd.exe /c bcdedit /set {default} safeboot network & shutdown /r /t 0"

• Requires administrator privileges on target machine
• Network connectivity must be maintained during restart
• Always test in non-production environments first
• Create System Restore point before making changes

After completing troubleshooting, disable safe mode boot:

bcdedit /deletevalue {default} safeboot

Remotely managing Windows machines is a common task for sysadmins and developers, but booting into Safe Mode with Networking presents unique challenges. While the shutdown command allows remote reboots, Windows doesn't natively support direct Safe Mode initiation through standard remote commands.

One effective method involves modifying the boot configuration in the registry:

Invoke-Command -ComputerName REMOTE_PC -ScriptBlock {
    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SafeBoot" -Name "AlternateShell" -Value "cmd.exe"
    Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" -Name "AutoAdminLogon" -Value "1"
    shutdown /r /t 0
}

For more control, you can use BCDEdit through PowerShell remoting:

$session = New-PSSession -ComputerName REMOTE_PC
Invoke-Command -Session $session -ScriptBlock {
    bcdedit /set {current} safeboot network
    Restart-Computer -Force
}

Remember to reset after troubleshooting:

Invoke-Command -ComputerName REMOTE_PC -ScriptBlock {
    bcdedit /deletevalue {current} safeboot
}

Windows Management Instrumentation provides another approach:

$comp = Get-WmiObject -Class Win32_OperatingSystem -ComputerName REMOTE_PC
$comp.Win32Shutdown(0)  # Normal reboot
# Then use scheduled task to set Safe Mode flag before next boot

• Ensure proper permissions (Admin rights on remote machine)
• Network connectivity must be established before Safe Mode boot
• Always test in non-production environments first
• Document the changes made for easy reversal