如何通过PowerShell移除MSMQ消息及日志配额？2008 R2脚本无报错失效

Hey there, I’ve run into this exact issue before—scripts that work perfectly on Windows 10 just won’t take effect on Server 2008 R2, no errors thrown. Let’s break down why this happens and how to fix it.

Why This Happens #

• 32-bit vs 64-bit Registry Redirection: Server 2008 R2 is 64-bit, but if you’re running a 32-bit PowerShell session, your registry writes get redirected to HKLM:\Software\Wow6432Node\Microsoft\MSMQ\... instead of the 64-bit path MSMQ actually reads from.
• MSMQ Service Not Restarted: Changes to MSMQ’s registry settings require a service restart to apply. Windows 10 might handle this more gracefully, but Server 2008 R2 needs a manual restart.
• Insufficient Permissions: Even if you don’t get an error, your script might not have admin rights to modify HKLM registry keys, so the changes silently fail.
• Registry Path/Key Differences: MSMQ’s registry structure was tweaked between Server 2008 R2 and Windows 10, so the keys you’re targeting might not be the right ones for the older OS.

Step-by-Step Fixes #

1. Run the Script in 64-bit PowerShell #

On Server 2008 R2, the default PowerShell shortcut might launch the 32-bit version. Make sure you open the 64-bit one:

• Navigate to C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe and run it (this is the 64-bit instance).
• Then execute your script here.

2. Updated Script with Admin Check & Service Restart #

Here’s a revised script that fixes common issues—adds admin validation, forces registry writes, and restarts MSMQ:

# Check if running as administrator
$currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
if (-not $currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Write-Error "Please run this script as an administrator!"
    exit 1
}

# Set unlimited quota values (max decimal value)
$regPath = "HKLM:\Software\Microsoft\MSMQ\Parameters\MachineCache"
Set-ItemProperty -Path $regPath -Name MachineQuota -Value 4294967295 -Force
Set-ItemProperty -Path $regPath -Name JournalQuota -Value 4294967295 -Force

# Restart MSMQ to apply changes
Restart-Service -Name MSMQ -Force -ErrorAction Stop

Write-Host "MSMQ quota limits removed successfully, service restarted."

3. Verify Registry Changes Manually #

If the script still doesn’t work, check the registry directly to confirm writes:

• Open regedit.exe
• Go to HKLM:\Software\Microsoft\MSMQ\Parameters\MachineCache
• Ensure MachineQuota and JournalQuota are set to 4294967295 (decimal)
• If you only see these keys under HKLM:\Software\Wow6432Node\Microsoft\MSMQ\..., delete them and re-run the script in 64-bit PowerShell.

4. Confirm Changes in MSMQ Settings #

After running the script and restarting the service, verify the limits are gone:

• Open Computer Management → Services and Applications → Message Queuing
• Right-click your server name → Properties → Limits tab
• Check that "Message queue quota" and "Journal quota" show as "Unlimited" (or the max value you set).

Extra Notes #

• Server 2008 R2’s MSMQ is an older version, so some registry behavior differs from Windows 10. Double-check you’re targeting the correct keys for this OS.
• If manual registry edits work but the script doesn’t, the issue is likely with the PowerShell session (32-bit vs 64-bit) or permissions.

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