This update resolves the following issues that may occur:
In a cluster, you cannot submit a job by using a user account in a domain that does not have a trust relationship with the domain of the cluster.
Note After you apply this update, you can use head node credentials of the domain from the Job Console. Or, you can use runas credentials in a job submission at a command prompt or at a Windows PowerShell prompt.
Under certain heavy workload conditions, the HPC Job Scheduler service may receive a request from a user to cancel a job when the HPC Job Scheduler service is trying to preempt the job automatically. At the same time, the Job Scheduler service incorrectly reports to the user or the client application that the job is canceled. However, the Job Scheduler is requeued and runs again automatically.
Note After you apply this update, the HPC Job Scheduler service processes the events correctly and reports the correct job status to the user or to the client application.
How to obtain this update
The update is available for download from the following Microsoft Download Center website: Download the update package now. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To apply this update, you must be running Windows HPC Server 2008. Additionally, HPC Pack 2008 Service Pack 1 (SP1) must be installed.
To install this update, run this update on the head node.
Note If you have a pair of high-availability head nodes, run this update on the active node, and then run this update on the passive node.
You must restart the computer after you install this update.
Update replacement information
This update does not replace a previously released update.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.