I’ve released version 0.3.0 of Carbon. This release contains some minor enhancements, several bug fixes, and backwards-incompatible changes to the following functions:
Set-IisSslFlags
This function was renamed to Enable-IisSsl. Its Enable128BitSsl parameter was renamed to Require128BitSsl.
Configuring client certificates is now a little stricter/clearer. You can no longer specify both AcceptClientCertificates and RequireClientCertificates. Also, if you specify RequireClientCertificates, you must now also supply the RequireSsl switch (before, setting the RequireClientCertificates switch implicitly set the RequireSsl switch).
Set-TrustedHosts
Make sure you’re not calling Set-TrustedHosts with an empty array/value for the Entries parameter. The function now throw an error in that situation. If you need to clear the list of trusted hosts, use Clear-TrustedHosts.
Invoke-PowerShell
If you call Invoke-PowerShell without the x86 switch and PowerShell is 32-bit, you’ll get an error. Under Windows x64, 32-bit PowerShell can’t start the 64-bit instance because Windows redirects all access from C:\Windows\system32 to C:\Windows\SysWOW64. If anyone knows how to get around this, let me know!
Enhancements
- Renamed
Set-IisSslFlagstoEnable-IisSslto better reflect what it does. Also, created parameter sets around client certificate settings so you can’t configure them incorrectly. (Fixes #25: Set-IisSslFlags: Create parameter sets to accurately reflect what flags are allowed to be set simultaneously.) - Added
WhatIfsupport to Install-MsmqMessageQueue. - Created new Clear-TrustedHosts for clearing PowerShell’s trusted hosts list.
Bug Fixes
- Rename Enable-IisSsl/Set-IisSslFlags’s
Enable128BitSslparameter toRequire128BitSsl] (Fix #24 Set-IisSslFlags: Rename the Enable128BitSsl parameter to Require128BitSsl). - Fix issue #19: Install-IisAppPool doesn’t change an existing 32-bit app pool to be a 64-bit app pool.
- Fix issue #33: Install-MsmqMessageQueue: Can wait forever for a queue to get created. It now waits 10 seconds.
- Fix issue #36: Get-PowerShellPath returns the wrong path when running x86 PowerShell on x64 computers.
- Fix issue #37: Invoke-PowerShell should write an error when running as x86 on Windows x64 without the x86 flag (i.e. 32-bit PowerShell can’t launch a 64-bit PowerShell, so throw an error in that situation).
- Fix issue #38: Set-TrustedHosts: passing an empty value for the Entries parameter clears the hosts list. The
Entriesparameter is now required. To clear the trusted hosts list, useClear-TrustedHosts.