After my secondment as a Business Analyst, I’ve had a couple of jobs that have been a delight – both to do with Microsoft Platform Websites. The first was to review a ground up implementation of an online channel of a mainframe application, the other is a short knowledge transfer using Commerce Server 2002. I’ve worked on similar jobs before – when a suite of software is bought and it takes a while to use all of the features.

In this case it was an MSIB 2.5 implementation and after it went in Microsoft Content Management Server got all of the attention. Of course, since then Sharepoint Portal Server has come to the fore (for a number of good reasons) and Windows Server 2003 is the server of choice. To remind me of the details, and to “feel the pain” I’ve been building a Commerce Server 2002 platform over the last few days. I decided to add it in to the domain I built earlier to pass my Windows 2000 Admin exam, as the client in question is running on Windows 2000 kit.

My goodness, how long has it taken. I’d hoped to clear this in a couple of days, and here I am still building the thing four days later. The slowest part was the prerequisites and for me this is my first lesson learned. I’m clearly a bit rusty when it comes to my toolkit, and I need to get my cds and dvds together with my platform servers and applications. Downloading Visual Studio over the vpn took over 12 hours, not quite broadband in my book. And I made one or two mistakes in the Virtual Machine config, again totally mucking up the disk sizing and making it too small to get things like service packs on properly. Although installs of server applications can be diverted to a second drive, the primary volume needs to be big enough for service pack deployment and crash dump handling.

Although the time taken has been a bit of added stress before my client visit on Monday, it has been excellent reminder training for me.