Generally, a download manager enables downloading of large files or multiples files in one session.Many web browsers, such as Internet Explorer 9, include a download manager.Stand-alone download managers also are available, including the Microsoft Download Manager.

if you do not have a download manager installed, and still want to download the file(s) you've chosen, please note:

You may not be able to download multiple files at the same time.In this case, you will have to download the files individually.(You would have the opportunity to download individual files on the "Thank you for downloading" page after completing your download.)

Files larger than 1 GB may take much longer to download and might not download correctly.

You might not be able to pause the active downloads or resume downloads that have failed.

The Microsoft Download Manager solves these potential problems.It gives you the ability to download multiple files at one time and download large files quickly and reliably.It also allows you to suspend active downloads and resume downloads that have failed.

This update fixes the following issues that may occur when you manage a Microsoft Windows HPC Pack 2008 R2 cluster that contains Windows Azure compute nodes. All HPC Pack 2008 R2 clusters that use Windows Azure nodes should apply this update, even if these issues have not yet been encountered.

Job Scheduling Issues

Job state is incorrect or appears tbe “stuck”. This hotfix provides greater tolerance for network latency and failures communication between HPC services and tWindows Azure.

Job remains in running state with tasks completed or failed

Jobs fail with "parent job cannot be validated" exception

Job completes successfully but marked failed after an HA failover

Jobs remain in running state after database access errors

Job remain in draining state and prevent taking compute nodes offline

Job in running state cannot be cancelled

Cannot cancel jobs when the compute node is running a CPU intensive job

Tasks fail on Windows Azure compute nodes with error message: Exception 'Safe handle has been closed' when creating the task

Crash in admin console when reconnecting tan HA head node with the virtual cluster name

SOA Runtime Issues

When Windows Azure nodes start they fail tsynchronize the SOA service package or application packages from Windows Azure Storage. This issue is more likely toccur in deployments with large number of compute node role instances or a large deployment package tupload. This hotfix makes the synchronization more resilient tfailures on accessing Windows Azure Storage

When session’s broker is running on clustered broker node, SOA message level preemption is enabled and SOA task is preempted the task does not exit as expected. When the task cancel grace period expires, the task is killed by the scheduler. This hotfix resolves the problem by making the task exit gracefully.

When session’s broker is running on clustered broker node, autshrink feature of SOA doesn’t work because the broker fails tmake a task exit. This hotfix resolves the problem by making the task exit gracefully.

This update need to be run on all Compute Nodes, Broker Nodes, Head Nodes, Workstation/Unmanaged Server Nodes, and computers running the HPC Pack Client Utilities.

Perform the following actions before installing the update

Take all compute, workstation and unmanaged server nodes offline and wait for all current jobs to drain

Change Node Template availability policy setting to manual

Stop all existing Windows Azure compute nodes

Close any HPC Cluster Manager and HPC Job Manager applications that are connected to the cluster head node

Backup all HPC databases once all active operations on the cluster have stopped

Applying the update
To start the download, click the Download button next to the appropriate file (KB2816845-x64.exe for the 64-bit version, KB2816845-x86.exe for the 32-bit version) and then:

Click Save to copy the download to your computer.

Close any open HPC Cluster Manager or HPC Job Manager windows.Note: Any open HPC Cluster Manager of HPC Job Managers may unexpectedly quit or show an error message during the update process if left open. This does not affect installation of the update.

Run the download on the headnode using an administrator account, and reboot the headnode.Note: If you have HA headnodes, run the fix on the Active node, move the node to Passive, and after failover occurs run the fix on the new Active node. Do this for all head nodes in the cluster.

Log on interactively, or use clusrun to to deploy the fix to the compute/broker/workstation nodes.

To use clusrun to deploy an HPC Pack 2008 R2 update on clusters that are running Service Pack 2, or higher:

Copy the appropriate version of the update to a shared folder such as \\headnodename\HPCUpdates .

Open an elevated command prompt window and type the appropriate clusrun command for the operating system of the patch, e.g.:
clusrun /nodegroup:ComputeNodes \\headnodname\HPCUpdates\KB2816845-x64.exe -unattend -SystemReboot
clusrun /nodegroup:BrokerNodes \\headnodname\HPCUpdates\KB2816845-x64.exe -unattend -SystemRebootNote: HPC Pack updates, other than Service Packs, do not get automatically applied when you add a new node to the cluster or re-image an existing node. You must either manually/clusrun apply the update after adding/reimaging a node or modify your node template to include a line to install the appropriate updates from a file share on your head node.Note: If the cluster administrator doesn’t have administrative privileges on workstation nodes and unmanaged server node, the clusrun utility may not be able to apply the update. In these cases the update should be performed by the administrator of the workstation and unmanaged servers.

To update workstation nodes and unmanaged server nodes you may need to reboot.

To update computers that run HPC Pack client applications apply the following actions:

Take all compute nodes, workstation nodes, and unmanaged server nodes offline and wait for all current jobs to drain

Change Node Template availability policy setting to manual

Backup all HPC databases

Stop existing Windows Azure compute nodes, you need to redeploy Azure nodes after uninstalling the update. You do not need to delete them if you want to redeploy them in the future.

You can uninstall the update in any order across all types of nodes.

Some updates may apply to more than one piece of HPC Pack software. In order to uninstall those updates, remove them in the following order:

Update for HPC Pack 2008 R2 Services for Excel 2010

Update for HPC Pack 2008 R2 Client Components

Update for HPC Pack 2008 R2 Server Components

Update for HPC Pack 2008 R2 MS-MPI Redistributable Pack

Note: If you don't follow the order, you might not be able to uninstall the update, as some update will have dependence across components

Note: If you have HA headnodes, uninstall the updates on a passive head node, move the node to Active, and then repeat uninstallation on the new passive head node. Do this for all head nodes in the cluster.

Microsoft SQL Server 2008 Management Studio Express is a free, integrated environment for accessing, configuring, managing, administering, and developing all components of SQL Server, as well as combining a broad group of graphical tools and rich script editors that provide access to SQL Server to developers and administrators of all skill levels.

Service Pack 2, the latest service pack for both Windows Server 2008 and Windows Vista, supports new types of hardware and emerging hardware standards, includes all of the updates that have been delivered since SP1, and simplifies deployment, for consumers, developers, and IT professionals.