Posts mit dem Label Window Server 2008 R2 werden angezeigt. Alle Posts anzeigen
Posts mit dem Label Window Server 2008 R2 werden angezeigt. Alle Posts anzeigen

Donnerstag, 19. April 2012

WinSxS-Ordner von Windows 7 und Server 2008 R2 verkleinern

Nach der erfolgreichen Installation eines Service Packs in Windows 7 lässt sich ein Teil des vom WinSxS-Ordner belegten Speichers zurück gewinnen. Der folgende Befehl führt dazu, dass die Service Pack-Sicherungsdateien entfernt werden:


dism /Online /Cleanup-Image /spsuperseded

Der Befehl sollte in der Eingabeaufforderung mit Administrationsrechten ausgeführt werden.

Vorsicht: Nach Ausführung des Befehls ist die Deinstallation des Service Packs nicht mehr möglich!

Dienstag, 16. August 2011

Recommended post W2K8R2 SP1 Clustering and Hyper-V Hotfixes


One of the visitors of this blog asked the question if we could publish a list of recommended post Windows Server 2008 R2 SP1 hotfixes related to either Clustering or Hyper-V. Well here it is!
For a complete overview of what was rolled-up in SP1 take a look at the Excel sheet (Updates in Win7 and WS08R2 SP1.xls) which can be found on here.
Note I. Microsoft will release hotfixes if a issue occurs that needs to fixed before releasing a roll-up update or a service pack. However, the hotfix in question is intended to correct only the problem that is described in the article. Apply the hotfix only to systems that are experiencing the problem that is described in the articles. The hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
Note II. Updates can be applicable to Windows Server 2008 R2 (RTM) and/or Windows Server 2008 R2 SP1.



TitleTypeRequiredIC Version
KB976932: Windows 7 en Windows Server 2008 R2 Service Pack 1 Service PackYes6.1.7601.17514
KB2446607: You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 if the computer is a failover cluster nodeCluster HotfixYes, only applicable to described situation
KB2462576: The NFS share cannot be brought online in Windows Server 2008 R2 when you try to create the NFS share as a cluster resource on a third-party storage diskCluster Hotfix Yes, only applicable to described situation
KB2485543: You cannot access or mount a Windows Server 2008 R2-based NFS share after a failover if the NFS share uses Krb5 or Krb5i authenticationCluster Hotfix Yes, only applicable to described situation
KB2494162: The Cluster service stops unexpectedly on a Windows Server 2008 R2 failover cluster node when you perform multiple backup operations in parallel on a cluster shared volumeCluster Hotfix Yes, only applicable to described situation
KB2485986: An update is available for Hyper-V Best Practices Analyzer for Windows Server 2008 R2Hyper-V HotfixYes, only applicable to described situation
KB2519946: Timeout Detection and Recovery (TDR) randomly occurs in a virtual machine that uses the RemoteFX feature in Windows Server 2008 R2Hyper-V HotfixYes, only applicable to described situation
KB2520235: "0x0000009E" Stop error when you add an extra storage disk to a failover cluster in Windows Server 2008 R2Cluster Hotfix Yes, only applicable to described situation
KB2517329: Performance decreases in Windows Server 2008 R2 when the Hyper-V role is installed on a computer that uses Intel Westmere or Sandy Bridge processorsHyper-V HotfixYes, only applicable to described situation
KB2460971: MPIO failover fails on a computer that is running Windows Server 2008 R2Cluster Hotfix Yes, only applicable to described situation
KB2494036: A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2Cluster Hotfix Yes, only applicable to described situation 
KB2523676: GPU is not accessed leads to some VMs that use the RemoteFX feature to not start in Windows Server 2008 R2 SP1Hyper-V HotfixYes, only applicable to described situation 
KB2521348: A virtual machine online backup fails in Windows Server 2008 R2 when the SAN policy is set to "Offline All"Hyper-V HotfixYes, only applicable to described situation 
KB2494016: Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected accessCluster Hotfix Yes, only applicable to described situation 
KB2531907: Validate SCSI Device Vital Product Data (VPD) test fails after you install Windows Server 2008 R2 SP1Cluster Hotfix Yes, only applicable to described situation 
KB2512715: Validate Operating System Installation Option test may identify Windows Server 2008 R2 Server Core installation type incorrectly in Windows 7 or in Windows Server 2008 R2Windows UpdateYes, only applicable to described situation 
KB2525835: MS11-047: Vulnerability in Microsoft Hyper-V could cause denial of service: June 14, 2011Security BulletinYes 
KB2549448: Cluster service still uses the default time-out value after you configure the regroup time-out setting in Windows Server 2008 R2Cluster Hotfix Yes, only applicable to described situation 
KB2549472: Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2Cluster Hotfix Yes, only applicable to described situation 
KB2552040: A Windows Server 2008 R2 failover cluster loses quorum when an asymmetric communication failure occursCluster Hotfix Yes, only applicable to described situation 
KB2496034: Cluster service stops when an error occurs in the registry replication process of a failover cluster in Windows Server 2008 R2 or in Windows Server 2008Cluster Hotfix Yes, only applicable to described situation 
KB2550569: "0×20001" Stop error when you start a Linux VM in Windows Server 2008 R2 SP1Hyper-V HotfixYes, only applicable to described situation 
KB2580360: A heap memory leak occurs when an application or service queries the MSCluster_Resource WMI class in Windows Server 2008 R2Cluster HotfixYes, only applicable to described situation
KB2582281: Slow failover operation if no router exists between the cluster and an application serverCluster HotfixYes, only applicable to described situation
KB2575625: Cluster service initiates a failover after a delay of about 80 seconds when you shutdown the active node in Windows Server 2008 R2Cluster HotfixYes, only applicable to described situation 
KB2578113: The Cluster service takes about 30 seconds to fail over IPv6 IP addresses in Windows Server 2008 R2Cluster HotfixYes, only applicable to described situation 
KB2579052: New registration entries are added to the Persistent Reservation table when the physical disk resource that is associated with the CSV is taken offline on a Windows Server 2008 R2-based Failover ClusterCluster HotfixYes, only applicable to described situation 
KB2550886: A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop workingCluster HotfixYes, only applicable to described situation 
KB2550894: Cluster service leaks memory when the service handles state change notifications in Windows Server 2008 R2Cluster HotfixYes, only applicable to described situation 
KB2547551: Hyper-V Export function consumes all available memory in Windows Server 2008 or in Windows Server 2008 R2 Hyper-V HotfixYes, only applicable to described situation 
KB2550894: Cluster service leaks memory when the service handles state change notifications in Windows Server 2008 R2 or Windows Server 2008 NEW!Hyper-V HotfixYes, only applicable to described situation 
The information is gathered from a number of places. First of all the from the monthly or two-monthly “released knowledge base articles” that we publish on this blog which can be found here: February, March, April, May-Juneand July-August (yet to be unpublished). Besides these overviews I used these websites for layout and checks: “List of Hyper-V Packages Updated After the Release of Windows Server 2008 R2 Service Pack 1 (SP1)” and “List of Cluster Hotfixes for Windows Server 2008 R2”.

Sonntag, 20. März 2011

Windows Server 2008 R2 auf DL380 G7 – Event-ID 37–Die Geschwindigkeit des Prozessors “xx” in der Gruppe “0” wird durch die Systemfirmware begrenzt

Ich hatte bei einem HP DL380 G7 das Problem, das im Eventlog unter “System” mehrere Warnungen auftauchten, die den folgenden Inhalt hatten:

  • "Die Geschwindigkeit des Prozessors “xx” in der Gruppe “0” wird durch die Systemfirmware begrenzt. Seit dem letzten Bericht befindet sich der Prozessor seit 0 Sekunden in diesem Status mit verminderter Leistung.

Quelle war “Kernel-Processor-Power”, Ereignis-ID 37. Die Firmware des Systems ist aktuell, das BIOS ebenfalls.

BIOS-Einstellung-DL380G7-PowerManagement-01Die Ursache des Problems war eine Einstellung im BIOS des Systems:

Unter Power Management Options –> Advanced Power Management Options –> Minimum Processor Idle Power State" gibt es mehrere Einstellungen. Die Einstellung stand auf “C3 State” und muss umgestellt werden auf “No C-states”.

BIOS-Einstellung-DL380G7-PowerManagement-02

Nach dem setzen der Einstellung erschien keine weitere Warnung mehr im Eventlog.

Donnerstag, 17. März 2011

Install the Active Directory Schema Snap-In

You can use this procedure to first register the dynamic-link library (DLL) that is required for the Active Directory Schema snap-in. You can then add the snap-in to Microsoft Management Console (MMC).

Membership in Domain Admins, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at http://go.microsoft.com/fwlink/?LinkId=83477.

To install the Active Directory Schema snap-in

  1. Open an elevated command prompt. Click Start, type command prompt, and then right-click Command Promptwhen it appears in the Start menu. Next, click Run as administrator. When the command prompt opens, type the following command, and then press ENTER:

    regsvr32 schmmgmt.dll
    TipTip
    Although the regsvr32 command shows that it is a 32-bit based command, it does run properly in the 64-bit versions of the supported operating systems (see Applies To near the start of this topic).

    If you do not run the command from an elevated command prompt or if you do not have the appropriate permissions, the following error message appears

    The module ‘schmmgmt.dll’ was loaded but the call to DllRegisterServer failed with error code 0x80040201.

    If you see this error message, check the group memberships of the user account that you are using to ensure that the user account is a member of the Schema Admins group. Also, ensure also that you run the command from an elevated command prompt.

  2. Click Start, click Run, type mmc, and then click OK.

  3. On the File menu, click Add/Remove Snap-in.

  4. Under Available snap-ins, click Active Directory Schema, click Add, and then click OK.

  5. To save this console, on the File menu, click Save.

  6. In the Save As dialog box, do one of the following:

    • To place the snap-in in the Administrative Tools folder, in File name, type a name for the snap-in, and then click Save.

    • To save the snap-in to a location other than the Administrative Tools folder, in Save in, navigate to a location for the snap-in. In File name, type a name for the snap-in, and then click Save.

Montag, 29. November 2010

Unexpected error refreshing Server Manager-errors 0x800706BE and 1601 on Window Server 2008 R2


On certain Windows Server 2008 R2 machines you may experience the Server Manager being unable to open Roles and/or Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE). You may also find that there is also Error 1601 in the Event Log.

Introduction

On certain Windows Server 2008 R2 machines you may experience theServer Manager being unable to open Roles and/or Features in the MMC.  The error it usually comes back with is Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE). 
Server Manager 0x800706BE Error
Certain people have also reported finding that there is also an error being logged in the event log – Error 1601.  Various reasons lead us to believe that this is an issue related to file corruption.  More specifically, file corruption caused by failed Windows Updates.
Server Manager Error 1601
If your Server Manager is crashing and you’re unable to add Roles or Features this article will talk you through a number of steps which may help you resolve the issue.

Step 1 – Download & Install System Update Readiness Tool (KB947821)

The first step in trying to diagnose this is to download and install KB947821 on the server which is having the problem with System Manager and generating the 0x800706BE refresh error.  You can download it from http://support.microsoft.com/kb/947821
The System Update Readiness Tool, runs a onetime scan for inconsistencies that might prevent future servicing operations. This scan typically takes less than 15 minutes to run. However, the tool might take significantly longer on some computers. The Windows Update progress bar is notupdated during the scan, and progress seems to stop at 60% complete for some time. This behavior is expected. The scan is still running and you should not cancel the update.  If you are prompted to restart your computer, do so.

Step 2 – Analyze KB947821 output log file

After you install KB947821 on your computer, you need to inspect the output log file it left behind.  You can find the file in: C:\Windows\Logs\CBS\CheckSUR.log
The log should show what files have been detected as corrupt or missing from/in the C:\windows\servicing\packages folder.  For instance, on our test machine they were shown as:
2010-10-07 09:30:43, Info                  CBS    Failed to get session package state for package: Package_3_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2010-10-07 09:30:43, Info                  CBS    Failed to get session package state for package: Package_2_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
You might also want to have a look at the CheckSUR.persist.log. In our case it looked like this:
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20593
Package Version 7.0
2010-04-14 09:56

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum  Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 72
 Found 1 errors
  CBS MUM Corrupt Total count: 1

Unavailable repair files:
 servicing\packages\Package_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat

(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache
We also checked the servermanager.log and found that the CbsUpdateState.bin file in the C:\Windows\system32\ServerManager\Cache\ folder is missing.
4652: 2010-10-14 17:43:53.856 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
4652: 2010-10-14 17:43:53.965 [CBS]                       IsCacheStillGood: False.
4652: 2010-10-14 17:44:13.356 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800706be (-2147023170)
4652: 2010-10-14 17:44:13.419 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery()
at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery()
at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType)
at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

Step 3 – Copy missing or corrupt files

In order to perform this step, you’ll need access to a machine which has a working ServerManager.  Copy the files listed as corrupted/missing from C:\windows\servicing\packages on the working machine to the server which is exhibiting the HRESULT 0x800706BE error.  You may need to change the ownership of the files on the destination machine to your user account as well as give yourself write permissions on the files before Windows allows you to overwrite them.
Once done, start Server Manager and see if that fixes the error.  To be doubly sure, check the contents of the C:\Windows\system32\ServerManager\Cache folder – there should be two files there: CbsUpdateInfo.bin and CbsUpdateState.bin.  If these files still don’t exist after ServerManager starts you haven’t completely fixed the 0x800706BE error.
Server Manager CbsUpdateInfo.bin CbsUpdateState.bin

Step 4 – Copy all files in C:\windows\servicing\packages folder

If you’re still unable to get Server Manager started, it means that there may be other problems and we need to overwrite all the packages in the C:\windows\servicing\packages folder.  The first step we need to do is take ownership of all the files.  To do this, launch a Command Prompt as an Administrator, and I mean right click the Command Prompt icon and select Run As Administrator.  At the command prompt execute:
takeown /F c:\Windows\Servicing\Packages /D y /R
The takeown command will give you ownership of the files, but you still need to give yourself write access to the files in order to change them.  In the same command prompt window execute the following command: (replace username with your username)
cacls c:\Windows\Servicing\Packages /E /T /C /G "username":F
Now copy all the files from the C:\windows\servicing\packages folder on a working server.  Make sure that the source server has been patched to the same level and has the same roles/features installed as the destination server.

Step 5 – Start Server Manager and check Cache folder

Try starting Server Manager and check if you’re still getting the error.  In all our tests, the above steps have been able to resolve 99% of all Server Manger problems related to error 0x800706BE and 1601.  Jus to be on the safe side, check the contents of the C:\Windows\system32\ServerManager\Cache folder and see that the two .bin files are now visible.

Conclusion

This article has demonstrated a quick and easy way to solve the errors associated with ServerManager and the 0x800706BE and 1601 errors that it exhibits when trying to install Roles or Features.  If the problem is not resolved by applying Microsoft KB947821, we have shown a reliable way to fix the 0x800706BE and 1601 errors by copying all files in C:\windows\servicing\packages from anther working Windows Server 2008 R2 server.

References

System Update Readiness Tool (KB947821)
http://support.microsoft.com/kb/947821
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779%28WS.10%29.aspx

Rename Onedrive Business root folder

Rename Onedrive Business root folder Here is what I remember: In the Office 365 web admin pages, change the organization name to a shorte...