Issue with CSS-Exchange script update function caused automatic script updates to fail

[Guest The_Exchange_Team]

This blog post is to draw your attention to an issue that we had with one of our script update functions that we use in several of our scripts to perform automatic script updates. All the scripts that are using the broken function are provided on our CSS-Exchange repository on GitHub (the most prominent one is the Exchange Server HealthChecker).

 

If you run one of them manually or via scheduled task with the bad version released between April 6th and 18th 2023 the automatic update does no longer work and as a result, you must download the latest release manually to make sure that the automatic update logic continues to work.

 

You’ll find something like this being logged to the log file generated, if the script that you run is affected by the issue mentioned in this article:

 

Unable to check for updates: System.Management.Automation.ParameterBindingException: A positional parameter cannot be found that accepts argument '

https://github.com/microsoft/CSS-Exchange/releases/latest/download/ScriptVersions.csv'.

 

Not all CSS-Exchange scripts use this function, so here is a table of those that do. To download the latest version of a script, just click on the name on the releases page or below table to start the download.

 

Affected scripts where the automatic update was temporarily broken:

 

No.	Script name
1	HealthChecker.ps1
2	Update-Engines.ps1
3	MonitorExchangeAuthCertificate.ps1
4	SourceSideValidations.ps1
5	Troubleshoot-ModernSearch.ps1
6	CVE-2023-23397.ps1
7	ExchangeExtendedProtectionManagement.ps1
8	SetupAssist.ps1
9	VSSTester.ps1

 

Affected script versions (those will not auto-update):

 

• 23.04.04.1055
  
• 23.04.05.1708
  
• 23.04.14.1557
  
• 23.04.17.1957
  
• 23.04.18.0737
  

 

Fixed script versions (auto-update works again):

 

• 23.04.19.1501 (or later)
  

 

If you experience any other issue with the script or what to provide feedback (e.g., suggesting a new feature or improvement to an existing one), please let us know. You can reach out to us via email (ExToolsFeedback@microsoft.com) or by opening an issue on GitHub (this is the best way to track issues).

 

The Exchange Server Team

 

Continue reading...