• Part 1 – Target Application (Build and Deploy)
• Part 2 – Autoscaler (Build)
• Part 3 – Autoscaler (Configure Autoscaling Block)
• Part 4 – Autoscaler (Configure Service Information Store)
• Part 5 – Autoscaler (Configure Rules Store)
• Part 6 – Autoscaler (Run and Monitor)

In Part 1 we’ll build and deploy the Azure application that will be the target of the autoscaling. In Parts 2 – 5 we’ll build and configure the application that performs the autoscaling using the Autoscaling Application Block (WASABi) from the Enterprise Library 5.0 Integration Pack for Windows Azure. Finally in Part 6 we’ll run the autoscaling application and monitor the target application during the autoscaling requests.

Richard led us through various strategies for building hybrid cloud integration solutions with the Microsoft Application Platform. One of the technologies that excited me was StreamInsight which provides complex event processing capabilities. In particular I’m looking forward to getting my hands on StreamInsight Austin which provides StreamInsight-based event processing in Windows Azure.

Slow as Molasses

My Macbook was achieving 30Mb/s downloads via my cable modem but the new Dell was only managing between 1 and 4Mb/s and even then it was patchy. I tried out the main suggested solution which was to configure the wireless adapter settings in the power options in Windows 7. This did not help.

Intel Drivers

I came across a forum suggesting that the Intel drivers rather than those from Dell would solve the problem. I downloaded and installed the Wireless_15.1.1_Ds64.exe file from the Intel Download Centre. It solved the issue and now I am getting 30Mb/s downloads via my Dell.

I’ll be starting a series on Azure and using the Autoscaling Application Block (WASABi) soon. This will be based on the demo I put together for the talk.

My previously blogged about methods for updating multiple iPhones in a household are no longer necessary. The 5.0.1 over the air software update was a manageable 44MB and very kind on my bandwidth (even when downloading it more than once to upgrade each phone over our household wireless).

iOS 5.0.1 Release Notes

• Fixes bugs affecting battery life
• Adds Multitasking Gestures for original iPad
• Resolves bugs with Documents in the Cloud
• Improves voice recognition for Australian users using dictation

Download URL

The iOS 5.0 firmware update file (.ipsw) is available at:

• http://appldnld.apple.com/iPhone4/041-8358.20111012.FFc34/iPhone3,1_5.0_9A334_Restore.ipsw

Update

Updating each iPhone as per my previous post resulted in a strange 3002 error.

I finally managed to solve this by placing the downloaded .ipsw file in the following location on each Mac:

• /Library/iTunes/iPhone Software Updates

Create the folder if it does not exist. Clicking on the update button in the iPhone Summary page in iTunes will update your iPhone. Repeat with each Mac and iPhone combination.

iOS 4.3.5 Release Notes

Fixes a security vulnerability with certificate validation.

Download URL

The iOS 4.3.5 firmware update file (.ipsw) is available at:

• http://appldnld.apple.com/iPhone4/041-1966.20110721.V3Ufe/iPhone3,1_4.3.5_8L1_Restore.ipsw

Update

Update each iPhone as per my previous post.

iOS 4.3.3 Release Notes

This update contains changes to the iOS crowd-sourced location database cache including:

• Reduces the size of the cache
• No longer backs the cache up to iTunes
• Deletes the cache entirely when Location Services is turned off

Download URL

The iOS 4.3.3 firmware update file (.ipsw) is available at:

• http://appldnld.apple.com/iPhone4/041-1011.20110503.q7fGc/iPhone3,1_4.3.3_8J2_Restore.ipsw

Update

Update each iPhone as per my previous post.

I run my MacBook through a 24” Samsung SyncMaster T240 and use the wired keyboard and wired mouse. This gives me a nice desktop setup and when I need to be mobile the 13” form factor is perfect.

Lately I have begun to feel the limits of the stock 2GB RAM and the 160GB HDD. So it is time for an upgrade. This post marks the completion of a 2 part project to upgrade both the RAM and the HDD of my MacBook.

• Part 1 – Upgrade RAM from 2GB to 4GB
• Part 2 – Upgrade HDD from 160GB to 500GB

No Space

Right clicking on Macintosh HD > Get Info showed that I had around 5GB of HDD space left on my MacBook. I bought the replacement drive for this little project over a year ago but had been putting off replacing my HDD – it was finally time …

HDD Specifications

I read a number of reviews and posts on various forums and blogs about what an ideal replacement drive would be. I looked at the prices between 320GB and 500GB HDDs (remember this is over a year ago) and finally settled on finding a HDD with a capacity of 500GB. My logic was that the bigger the drive was, the less likely I would have to do this again during my MacBook’s lifetime.

The next challenge was whether to get a 5400RPM or 7200RPM drive. Again there was heated debate in the forums and on blogs. The two contenders for me were:

• Seagate Momentus 7200.4 500GB SATA 3.0Gb/s, 16MB Cache, 7200RPM
• Western Digital Scorpio Blue 500 GB, SATA 3 Gb/s, 8 MB Cache, 5400 RPM

I liked the fact that the drive in my MacBook was so quiet and wanted to maintain that experience. Western Digital advertised WhisperDrive technology on their Scorpio Blue drives which was meant to yield the quietest 2.5 inch drives on the market. This claim seemed to be held up in the forums and since I was not doing anything seriously IO intensive on the MacBook I decided to go with the 5400RPM Western Digital Scorpio Blue 500GB. I also ensured that the drive was no higher than 9.5mm due to ongoing debates on various forums.

Cloning the HDD

This is the part of the process that kept me from upgrading months ago. The contents of the existing HDD in the MacBook would have to be cloned to the new HDD. I had read a number of blog posts on using the SuperDuper! or Carbon Copy Cloner utilities and it all seemed simple enough – but I was still a little nervous. I finally settled on using Disk Utility which is bundled with Mac OS X and is all you really need for cloning your HDD. A simple and easy to understand post by Daryn Cox got me started.

I mounted my new 500GB HDD into an external USB enclosure. I fired up Disk Utility via Applications > Utilities > Disk Utility and selected the Restore tab. I dragged the icon of the existing Macintosh HD from the left pane into the Source box and the icon of the new external 500GB HDD from the left pane into the Destination box. Ensure that the Erase destination checkbox is checked. Double check that your existing HDD is the source and that the new HDD is the destination before proceeding.

Click the Restore button.

Confirm the erasure of the destination drive by clicking on the Erase button.

Then wait… My estimated time fluctuated between 3 and 6 hours initially but I left it running overnight so I’m not really sure how long it actually took. It is probably better if you don’t use your MacBook while this operation is taking place.

Verify Clone

Once the cloning process has completed you need to verify that the clone was successful. The easiest way to do this is to boot from your new HDD. There are two ways to do this in Mac OS X:

Option1: System Preferences > Startup Disk

Navigate to the Startup Disk section of System Preferences. Select the new external 500GB and click the Restart button.

Confirm the restart by clicking on the Restart button.

Option 2: Option Key at System Boot

Hold down the option key during system boot.

Select the new external 500GB.

Once I had confirmed that my drive had been correctly cloned, it was time to install the new HDD into the MacBook.

Installing the new HDD

Apple provide fairly detailed instructions via their support site on how to upgrade your HDD. See Chapter 3: Boost Your MacBook > Replacing the Hard Disk Drive of the manual for the MacBook 13" Aluminum (Late 2008). I had my cloned HDD, some decent precision screwdrivers this time around and was ready to begin.

Opening up the MacBook

Turn the MacBook over and push down on the door latch to release the access door. Remove the access door and the battery. The battery has a handy tab on it to make lifting it out of the bay easier.

Make sure to ground yourself before touching anything inside your MacBook.

Removing the old HDD

The old HDD should be visible on the bottom left of the MacBook.

Remove the bracket holding the old HDD using a #00 Philips precision screwdriver. I finally found a decent #00 Philips and the experience removing my HDD was much better than when I upgraded my RAM… If the only advice you take away from this is to find a really decent precision screwdriver then you will be halfway there.

Lift the old HDD out of the bay using the clear tab and then gently wiggle the connector off the HDD. Remove the mounting screws using a Torx T6 precision screwdriver. Again I will say it – spend the cash and get a decent screwdriver.

Installing the new HDD

Remove the clear tab from the old HDD and attach to the new HDD. Screw the mounting screws into the new HDD using the Torx T6 screwdriver.

Place the new HDD into the drive bay.

Replace the bracket using the #00 Philips screwdriver.

Closing up the MacBook

Place the battery back into the bay and then replace the access door. Press it down gently until the latch moves to the closed position.

Confirmation

Switch on the MacBook and make sure it boots. Right clicking on Macintosh HD > Get Info now shows my new 500GB HDD and plenty of free space.

Using a proxy

I again used Charles to capture the url of the iOS 4.3.2 firmware update file (.ipsw). I had to enable the SOCKS proxy options this time to capture the traffic successfully.

Enable the SOCKS proxy in Charles by clicking on Proxy > Proxy Settings in the menu and checking the Enable SOCKS proxy checkbox in the Proxies tab.

Also check the Use SOCKS proxy in the Mac OS X tab.

Download URL

The iOS 4.3.2 firmware update file (.ipsw) that iTunes was downloading is clearly visible in Charles:

• http://appldnld.apple.com/iPhone4/041-0662.20110414.byQ84/iPhone3,1_4.3.2_8H7_Restore.ipsw

Update

Update each iPhone as per my previous post.