Archive for the 'How-To' Category

Excel automation with Powershell

Powershell is Microsoft’s answer of decent shell scripting on the Windows platform. Equipped with the functions you would expect from VBScript, it behaves as an Unix shell script would. All commands can work from the command line, or as a set of instructions in a file.

Adding to the basic shell functions one would expect, such as file and directory manipulation, reading and writing text files, manipulating strings with regular expressions, Powershell also integrates with .NET 2.0 and higher to communicate with other functions, such as accessing the System.Windows.Forms object to make neat forms equipped with all the controls you would expect in a compiled application, or in this case: manipulating Excel workbooks.

Using Excel together with PowerShell can be very easy. Too bad the documentation is sparse on this topic, and the official documentation makes no mention of a workaround that is needed when using Excel with PowerShell on a machine which is not configured with regional settings set to EN-us. Continue reading ‘Excel automation with Powershell’

Cannot install an update? Try this workaround.

One of many Microsoft patches used the Microsoft Update.exe Package Installer and that got me almost into trouble tonight…

The Update.exe Package Installer relies on Update.inf to check wheither the update, patch or hotfix is suited for the operating system and patch levels of your application.  Normally, this poses no problem, but at times you might have something running which was supported, and then not. Continue reading ‘Cannot install an update? Try this workaround.’

“Access Denied” using Trend Micro Officescan 5.58?

A client uses Trend Micro Officescan 5.58. On Windows Server 2000, this works fine, but on Server 2003 it goes awry. Install does not pose any trouble, but after installation, there was no way for me to log into the Officescan’s control panel. The result was a 403 Forbidden: Access Denied error while calling up http://server/officescan/cgi/cgiChkMasterPwd.exe.

A day later, the client came up with the solution: switch on IIS 5.0 isolation mode in Windows Server 2003’s IIS 6.0:

[photopress:iis_50_isolationmode.gif,full,centered]