[SDP3][92119b88-7663-4b05-90e4-6704c9d144a4] Windows High Performance Computing diagnostic package

Symptoms
This diagnostic collects information that’s related to Windows High Performance Computing (HPC).
Resolution
When you run the Windows High Performance Computing diagnostic package on an HPC computer that’s experiencing performance issues, the following information is collected.
General information
Collapse this tableExpand this table
DescriptionFile nameBasic system information, including machine name, service pack, computer model, processor name, and processor speed
resultreport.xml
Windows HPC configuration information
Collapse this tableExpand this table
DescriptionFile nameCluster overviewclusteroverview.txtCluster propertyclusterproperty.txtDriverhpcdriver.txtETL tracesdata\logfiles\*.*Grouphpcgroup.txtHostshostsHPC setup logstemp\hpcsetuplogs\*.*HPC test resultshpctest.txtImageimage.txtJob historyjobhistory.txtJob template ACLJobTemplateAcl.txtJob templateJobTemplate.txtMemberMember.txtMetric value historymetricvaluehistory.txtMetric valuemetricvalue.txtNetwork interfacenetworkinterface.txtNode state historynodestatehistory.txtNode templatenodetemplate.txtNodeNode.txtOperations logoperationslog.txtStoragescsistoragearray.txtTest result detailsTestResultDetails.txtTest resulttestresult.txt
Symptoms that are detectedIn addition to collecting the information that’s described earlier in this article, this diagnostic package can detect one or more of the following symptoms:Event log messages: RC_GetEvents

MS10-033: Vulnerabilities in Media Decompression could allow remote code execution

Symptoms
Microsoft has released security bulletin MS10-033. To view the complete security bulletin, visit one of the following Microsoft websites: Home users:
http://www.microsoft.com/security/updates/bulletins/201006.aspx
(http://www.microsoft.com/security/updates/bulletins/201006.aspx)Skip the details: Download the updates for your home computer or laptop from the Microsoft Update website now:
http://update.microsoft.com/microsoftupdate/
(http://update.microsoft.com/microsoftupdate/)IT professionals:
http://www.microsoft.com/technet/security/bulletin/MS10-033.mspx
(http://www.microsoft.com/technet/security/bulletin/MS10-033.mspx)How to obtain help and support for this security updateFor home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support website:
http://support.microsoft.com/common/international.aspx?rdpath=4
(http://support.microsoft.com/common/international.aspx?rdpath=4) North American customers can also obtain instant access to unlimited no-charge email support or to unlimited individual chat support by visiting the following Microsoft website:
http://support.microsoft.com/oas/default.aspx?&prid=7552
(http://support.microsoft.com/oas/default.aspx?&prid=7552) For enterprise customers, support for security updates is available through your usual support contacts.
Resolution
Known issues and more information about this security updateFor more information about this security update and for information about any known issues with specific releases of this software, click the following article number to view the article in the Microsoft Knowledge Base:
979482
(http://support.microsoft.com/kb/979482/)MS10-033: Description of the security update for Asycfilt.dll (COM component): June 8, 2010
975562
(http://support.microsoft.com/kb/975562 /)MS10-033: Description of the security update for Quartz.dll (DirectShow): June 8, 2010
978695
(http://support.microsoft.com/kb/978695/)MS10-033: Description of the security update for Windows Media Format Runtime: June 8, 2010
979332
(http://support.microsoft.com/kb/979332/)MS10-033: Description of the security update for Windows Media Encoder 9: June 8, 2010

Error message when you perform an unattended installation of Windows Server 2008: “Windows could not parse or process unattend answer file [drive:\Windows\Panther\unattend.xml] for pass [oobeSystem]“

Symptoms
When you perform an unattended installation of Windows Server 2008, you receive the following error message:

Windows could not parse or process unattend answer file [drive:\Windows\Panther\unattend.xml] for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].Additionally, the following entry is logged in the %systemroot%\Panther\Unattendgc\Setupact.log file:

[Shell Unattend] Running ‘oobeSystem’ passDateTime, Info [Shell Unattend] WindowsFeatures: Launched ‘”C:\Windows\system32\ie4uinit.exe” -show’ DateTime, Info [Shell Unattend] WindowsFeatures: Launched ‘”C:\Program Files\Windows Mail\WinMail.exe” OCInstallHideOE’ DateTime, Info [Shell Unattend] WindowsFeatures: Launched ‘C:\Windows\system32\unregmp2.exe /ShowWMP /SetShowState’ DateTime, Error [Shell Unattend] WindowsFeatures: Failed to read show/hide command value ‘SOFTWARE\Clients\Media\Windows Media Center\InstallInfo’ ‘HideIconsCommand’ (0×80070002) DateTime, Info [Shell Unattend] Exiting ‘oobeSystem’ pass with status 0x80070002DateTime, Info [oobeldr.exe] [Action Queue] : process exit code = 4DateTime, Error [oobeldr.exe] [Action Queue] : Unattend action failed with exit code 4 DateTime, Info [oobeldr.exe] [Action Queue] : ProcessActionQueue finish (hr = 0x1f2000)DateTime, Error [oobeldr.exe] Execution of unattend GCs failed; hr = 0×0; pResults->hrResult = 0x8030000bDateTime, Info [oobeldr.exe] Successfully completed RunSMIPass for oobeSystem.DateTime, Info [oobeldr.exe] No reboot has been requested for oobeSystem unattend.DateTime, Error [oobeldr.exe] User input error was detected in unattend file. Error: [0x0]DateTime, Info IBS UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure…DateTime, Info IBS UnattendDumpSetting: ——Unattend setting error / warning——DateTime, Info IBS UnattendDumpSetting: Error code = 0x8030000bDateTime, Info IBS UnattendDumpSetting: Pass = oobeSystemDateTime, Info IBS UnattendDumpSetting: Component name = [Microsoft-Windows-Shell-Setup]DateTime, Info IBS UnattendDumpSetting: ——————————————–DateTime, Info IBS UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
Resolution
This problem occurs because you have set a value for the ShowMediaCenter option in the Unattend.xml file.
Notes The ShowMediaCenter option isin the “Microsoft-Windows-Shell-Setup” subsection of the Unattend.xml file. The”Microsoft-Windows-Shell-Setup” subsection is in the”Windows Features” section.This issue can also occur if you specify these settings in an Unattend.xml file, and you are trying to install one of the following operating systems:Windows Vista EnterpriseWindows Vista BusinessWindows Vista Home BasicWindows Vista Starter

Troubleshooting AD Replication error 1722: The RPC server is unavailable

Symptoms
 This article describes the symptoms, cause and resolution for resolving Active Directory replication failing with Win32 error 1722: The RPC server is unavailable.DCPROMO Promotion of a replica DC fails to create an NTDS Settings object on the helper DC with error 1722    
Dialog Title Text:
Active Directory Domain Services Installation Wizard 
Dialog Message text:   
The operation failed because: Active Directory Domain Services could not create the NTDS Settings object for this Active Directory Domain Controller CN=NTDS Settings,CN=<Name of DC being promoted),CN=Servers,CN=<site name>,CN=Sites,CN=Configuration,DC=<forest root domain>  on the remote AD DC <helper DC>.<domain name>.<top level domain>. Ensure the provided network credentials have sufficient permissions. “The RPC server is unavailable.”
DCDIAG reports that the Active Directory Replications test has failed with error 1722: “The RPC Server is unavailable” 

[Replications Check,<DC Name>] A recent replication attempt failed:
            From <source DC> to <destination DC>
            Naming Context: <DN path of directory partition>
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at <date> <time>.
            The last success occurred at <date> <time>.
            <X> failures have occurred since the last success.
            [<dc name>] DsBindWithSpnEx() failed with error 1722,
            The RPC server is unavailable..
            Printing RPC Extended Error Info: 
           <snip>   
      REPADMIN.EXE reports that replication attempt has failed with status 1722 (0x6ba).
REPADMIN commands that commonly cite the -1722 (0x6ba) status include but are not limited to:  
 
·         REPADMIN /REPLSUM
·         REPADMIN /SHOWREPL
·         REPADMIN /SHOWREPS
·         REPADMIN /SYNCALL
Sample output from “REPADMIN /SHOWREPS” and REPADMIN /SYNCALL depicting “The RPC server is unavailable” error is shown below: 

c:\>repadmin /showreps
<site name>\<destination DC>
DC Options: <list of flags>
Site Options: (none)
DC object GUID: <NTDS settings object object GUID>
DC invocationID: <invocation ID string>
==== INBOUND NEIGHBORS ======================================
DC=<DN path for directory partition>
    <site name>\<source DC via RPC
        DC object GUID: <source DCs ntds settings object object guid>
        Last attempt @ <date> <time> failed, result 1722 (0x6ba):
            The RPC server is unavailable.
        <X #> consecutive failure(s).
        Last success @ <date> <time>

Sample output of “REPADMIN /SYNCALL” depicting “The RPC server is unavailable” error is shown below: 
C:\>repadmin /syncall
CALLBACK MESSAGE: Error contacting server <object guid of NTDS Settings object>._msdcs.<forest root domain>.<top level domain> (network error): 1722 (0x6ba):
The RPC server is unavailable.
The “replicate now” command in Active Directory Sites and Services returns “The RPC server is unavailable.”
Right-clicking on the connection object from a source DC and choosing “replicate now” fails with “The RPC server is unavailable.. The on-screen error message is shown below:   
Dialog title text:  
Replicate Now 
Dialog message test: 
The following error occurred during the attempt to synchronize naming context <DNS name of directory partition> from domain controller <source Dc host name> to domain controller <destination DC hostname>:The RPC server is unavailable. This operation will not continue. This condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Web site:http://go.microsoft.com/fwlink/?LinkId=5171
NTDS KCC, NTDS General or Microsoft-Windows-ActiveDirectory_DomainService events with the 1722 status are logged in the directory service event log.
Active Directory events that commonly cite the 1722 status include but are not limited to:
 
Event SourceEvent IDEvent StringMicrosoft-Windows-ActiveDirectory_DomainService1125The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.NTDS KCC1311The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.NTDS KCC1865The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.NTDS KCC1925The attempt to establish a replication link for the following writable directory partition failed.NTDS Replication1960Internal event: The following domain controller received an exception from a remote procedure call (RPC) connection. The operation may have failed.
 
Resolution
RPC is an intermediate layer between the network transport and the application protocol. RPC itself has no special insight into failures but attempts to map lower layer protocol failures into an error at the RPC layer
RPC error 1722 / 0x6ba / RPC_S_SERVER_UNAVAILABLE is logged when a lower layer protocol reports a connectivity failure. The common case is that the abstract TCP CONNECT operation failed. In the context of AD replication, the RPC client on the destination DC was not able to successfully connect to the RPC server on the source DC. Common causes for this are:Link local failureDHCP failureDNS failureWINS failureRouting failure (including blocked ports on firewalls)IPSec / Network authentication failuresResource limitationsHigher layer protocol not runningHigher layer protocol is returning this error

Microsoft Security Advisory: Vulnerability in Windows Kernel could allow elevation of privilege

Symptoms
Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/advisory/979682.mspx
(http://www.microsoft.com/technet/security/advisory/979682.mspx)
Resolution
To fix this problem automatically, click the Fix this problem link under the “Enable this fix” heading. Then, click Run in the File Download dialog box and follow the steps in this wizard.
To undo the fix and restore the original settings, click the Fix this problem link under the “Disable this fix” heading. Then, click Run in the File Download dialog box and follow the steps in this wizard.
Collapse this tableExpand this table
Enable this fixDisable this fix
a.button {background: url(/library/images/support/KBGraphics/PUBLIC/cn/FixItButton.jpg) no-repeat 0 0;width: 139px;height: 56px;display:block;cursor:pointer;}a.button:hover {background-position: bottom right;}Fix this problem
Microsoft Fix it 50364
a.button {background: url(/library/images/support/KBGraphics/PUBLIC/cn/FixItButton.jpg) no-repeat 0 0;width: 139px;height: 56px;display:block;cursor:pointer;}a.button:hover {background-position: bottom right;}Fix this problem
Microsoft Fix it 50367NotesThis wizard may be in English only. However, the automatic fix also works for other language versions of Windows.If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem. Known issues with this security updateThe Fix it solution checks whether if an application is running that is using NTVDM.exe. If an application that is using NTVDM is running, you will receive a message prompting you to close the application before you continue.The Fix it solution does not check whether the Local Group Policy Editor (GPedit.msc) is running.If GPedit.msc is running, you will not receive a message prompting you to close GPedit.msc before you continue. If you run the Fix it solution while GPedit.msc is running, you may experience the following issues: The GPedit.msc user interface may not reflect the DTVDM settings changes that are made by the Fix it solution until you close and then restart GPedit.msc.If you run the Fix it solution whileGPedit.msc UI is running, and then you make additional changes in GPedit.msc without restarting GPedit.msc, the additional changes could overwrite the changes that are made by the Fix it solution. Therefore, the changes that are made by the Fix it solution may not be applied. To avoid these issues, we recommend that you close GPedit.msc before you run the Fix it solution. Note You can use the gpupdate /force command in the Fix it solution make sure that the registry is updated. On some computers, this command may cause the Fix-it solution to take more time to be completed.

SQL Server Questions and Answers, SQL QA