Realtek HD Audio 2.40 Treiber verfügbar

Hi,

der Realtek HD Audio 2.40 Treiber wurde zum Download bereit gestellt!

Change-Log:

  1. Vista/Windows 7 WHQL Supporting: ALC882, ALC883, ALC885, ALC888, ALC889, ALC892, ALC861VD, ALC660, ALC662, ALC663, ALC665, ALC260, ALC262,ALC267, ALC268, ALC269, ALC270, ALC272, ALC273, ALC887,ALC670, ALC275, ALC680
  2. Windows 2000/XP WHQL Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC889, ALC892, ALC861VC, ALC861VD, ALC660, ALC662, ALC663, ALC665, ALC260, ALC262, ALC267,ALC268, ALC269, ALC270, ALC272, ALC273, ALC887,ALC670, ALC275, ALC680
  3. HDMI Device WHQL Support: ATI HDMI Devices
  4. OS Supporting: Microsoft Windows XP, Widnows2000, Windows Server 2003, Vista, Windows Server 2008, Windows7 – x86/x64
  5. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
  6. Add/Fix
    1.) Driver:
    1. Customizations.

Realtek HD Audio 2.40

Na dann, Viel Spass beim selber Testen!
CU

Advertisements

E-Book: 50 Windows 7 Tips und Tricks

Hi,

Vasu Jain von Windowsvj.com hat freies E-Book mit 50 Windows 7 Tips und Tricks veröffentlicht. Das E-Book ist zwar in Englisch aber enthält einige Tweaks, Informationen und viele Screenshots zu diversen Funktionen von Windows 7.

image
Download: 6MB

Na dann Viel Spass beim selber Testen!
CU

Windows 7/Server2008 R2: Hotfix für Stop-Fehlermeldungen bei großen SATA HDDs

Hi,

laut Microsoft kann es offenbar zu Problemen kommen, wenn Windows 7 oder Windows Server 2008 R2 aus dem Standby oder Ruhezustand (S1- oder S3-Status) aufgeweckt werden. Auf manchen Systemen erscheint dann eine der folgenden Stop-Fehlermeldung.

  • STOP 0x0000007A
  • STOP 0x00000077
  • STOP 0x000000F4
Der Hotfix KB977178 steht aber zum Download bereit, der das Problem beheben soll.
Hotfixes nicht präventiv einspielen, sondern nur wenn man auch das dazugehörige Problem hat!
Das Problem scheint aber nur aufzutreten, wenn sehr große SATA Festplatten verbaut sind, von 1 Terabyte Kapazität oder mehr. Der SATA-Treiber setzt voraus, dass die Festplatten nach 10 Sekunden wieder vollständig betriebsbereit sind. Bei großen SATA-Platten kann dieser Zeitraum aber zu kurz sein.
Na dann, Viel Spass beim selber Testen!
CU

Virenscanner: Empfehlungen für Windows und Auschlusslisten für DCs, SQL, Sharepoint, Exchange und Lync

Hi,

Microsoft hat im KB Artikel 822158 Empfehlungen gegeben, wie man Anti Virenscanner für die Windows Betriebssysteme Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 2000, Windows XP, Windows Vista, und Windows 7 konfiguriert und welche Dateien, Ordner und Prozesse man auf Auschlusslisten setzen sollte.

For computers that are running Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 2000, Windows XP, Windows Vista, or Windows 7

Do not scan the following files and folders. These files are not at risk of infection. If you scan these files, serious performance problems may occur because of file locking. Where a specific set of files is identified by name, exclude only those files instead of the whole folder. Sometimes, the whole folder must be excluded. Do not exclude any one of these based on the file name extension. For example, do not exclude all files that have a .dit extension. Microsoft has no control over other files that may use the same extensions as the following files:

Microsoft Windows Update or Automatic Update related files

  • The Windows Update or Automatic Update database file. This file is located in the following folder:%windir%\SoftwareDistribution\DatastoreExclude the Datastore.edb file.
  • The transaction log files. These files are located in the following folder:%windir%\SoftwareDistribution\Datastore\LogsExclude the following files:
    • Edb*.log
      Note The wildcard character indicates that there may be several files.
    • Res1.log. The file is named Edbres00001.jrs for Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2.
    • Res2.log. The file is named Edbres00002.jrs for Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2.
    • Edb.chk
    • Tmp.edb
    • The following files in the %windir%\security path should be added to the exclusions list:
      • *.edb
      • *.sdb
      • *.log
      • *.chk

      Note If these files are not excluded, security databases are typically corrupted, and Group Policy cannot be applied when you scan the folder. The wildcard character indicates that there may be several files. Specifically, you must exclude the following files:

      • Edb.chk
      • Edb.log
      • *.log
      • Security.sdb in the <drive>:\windows\security\database folder
  • Group Policy related files
  • Group Policy user registry information. These files are located in the following folder:%allusersprofile%\Exclude the following file: NTUser.pol
  • Group Policy client settings file. These files are located in the following folder:%Systemroot%\system32\GroupPolicy\Exclude the following file: registry.pol
For Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, and Windows 2000 domain controllers

Because domain controllers provide an important service to clients, the risk of disruption of their activities from malicious code from a virus must be minimized. Antivirus software is the generally accepted way to lessen the risk of virus infection. Install and configure antivirus software so that the risk to the domain controller is reduced as much as possible and so that performance is affected as little as possible. The following list contains recommendations to help you configure and install antivirus software on a Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, or on a Windows 2000 domain controller:
Warning We recommend that you apply the following specified configuration to a test configuration to make sure that in your specific environment it does not introduce unexpected factors or compromise the stability of the system. The risk from too much scanning is that files are inappropriately flagged as having been changed. This results in too much replication in Active Directory. If testing verifies that replication is not affected by the following recommendations, you can apply the antivirus software to the production environment.
Note Specific recommendations from antivirus software vendors may supersede the recommendations in the article.

  • Antivirus software must be installed on all domain controllers in the enterprise. Ideally, try to install such software on all other server and client systems that have to interact with the domain controllers. It is optimal to catch the virus at the earliest point, such as at the firewall or at the client system where the virus is first introduced. This prevents the virus from ever reaching the infrastructure systems that the clients depend on.
  • Use a version of antivirus software that is designed to work with Active Directory domain controllers and that uses the correct Application Programming Interfaces (APIs) to access files on the server. Older versions of most vendor software inappropriately change file metadata as it is scanned. This causes the File Replication Service engine to recognize a file change and therefore schedule the file for replication. Newer versions prevent this problem. For more information, click the following article number to view the article in the Microsoft Knowledge Base:815263 (http://support.microsoft.com/kb/815263/ ) Antivirus, backup, and disk optimization programs that are compatible with the File Replication service
  • Do not use a domain controller to browse the Web or to perform any other activities that may introduce malicious code.
  • When you can, do not use the domain controller as a file sharing server. Virus scanning software must be run against all files in those shares, and this can put an unsatisfactory load on the processor and the memory resources of the server
  • Do not put Active Directory or FRS database and log files on NTFS file system compressed volumes.
    For more information, click the following article number to view the article in the Microsoft Knowledge Base:318116 (http://support.microsoft.com/kb/318116/ ) Issues with Jet Databases on compressed drives
  • Do not scan the following files and folders. These files are not at risk of infection, and if you include them, this may cause serious performance problems because of file locking. Where a specific set of files is identified by name, exclude only those files instead of the whole folder. Sometimes, the whole folder must be excluded. Do not exclude any of these based on the file-name extension. For example, do not exclude all files that have a .dit extension. Microsoft has no control over other files that may use the same extension as those shown here.
    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756(http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

    • Active Directory and Active Directory-related files:
      • Main NTDS database files. The location of these files is specified in the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\DSA Database FileThe default location is %windir%\ntds. Exclude the following files:Ntds.dit
        Ntds.pat
      • Active Directory transaction log files. The location of these files is specified in the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\Database Log Files PathThe default location is %windir%\ntds. Exclude the following files:EDB*.log (The wildcard character indicates that there may be several files.)
        Res1.log (The file is named Edbres00001.jrs for Windows Server 2008, and Windows Server 2008 R2.)
        Res2.log (The file is named Edbres00001.jrs for Windows Server 2008, and Windows Server 2008 R2.)
        Ntds.patNote Windows Server 2003 no longer uses the Ntds.pat file.
      • The NTDS Working folder that is specified in the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\DSA Working DirectoryExclude the following files:Temp.edb
        Edb.chk
    • SYSVOL files:
      • The File Replication Service (FRS) Working folder that is specified in the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Working DirectoryExclude the following files:FRS Working Dir\jet\sys\edb.chk
        FRS Working Dir\jet\ntfrs.jdb
        FRS Working Dir\jet\log\*.log
      • The FRS Database Log files that are located in the following registry key:HKEY_LOCAL_MACHINE\system\currentcontrolset\services\NtFrs\Parameters\DB Log File DirectoryThe default location is %windir%\ntfrs. Exclude the following files:FRS Working Dir\jet\log\*.log (if the registry key is not set)
        FRS Working Dir\jet\log\edbres00001.jrs (Windows Server 2008, and Windows Server 2008 R2)
        FRS Working Dir\jet\log\edbres00002.jrs (Windows Server 2008, and Windows Server 2008 R2)
        DB Log File Directory\log\*.log (if the registry key is set)
      • The Staging folder that is specified in the following registry key and all the Staging folder’s sub-folders:HKEY_LOCAL_MACHINE\system\currentcontrolset\services\NtFrs\Parameters\Replica Sets\GUID\Replica Set StageThe current location of the Staging folder and all its sub-folders is the file system reparse target of the replica set staging folders. Staging defaults to the following location:
        %systemroot%\sysvol\staging areas
        The current location of the SYSVOL\SYSVOL folder and all its sub-folders is the file system reparse target of the replica set root. The SYSVOL\SYSVOL folder defaults to the following location:
        %systemroot%\sysvol\sysvol
      • The FRS Preinstall folder that is in the following location:Replica_root\DO_NOT_REMOVE_NtFrs_PreInstall_DirectoryThe Preinstall folder is always open when FRS is running.

      In summary, the targeted and excluded list of folders for a SYSVOL tree that is placed in its default location would look similar to the following:

      1. %systemroot%\sysvol                                                  Exclude
      2. %systemroot%\sysvol\domain                                           Scan
      3. %systemroot%\sysvol\domain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory  Exclude
      4. %systemroot%\sysvol\domain\Policies                                  Scan
      5. %systemroot%\sysvol\domain\Scripts                                   Scan
      6. %systemroot%\sysvol\staging                                          Exclude
      7. %systemroot%\sysvol\staging areas                                    Exclude
      8. %systemroot%\sysvol\sysvol                                           Exclude

      If any one of these folders or files have been moved or placed in a different location, scan or exclude the equivalent element.

    • DFSThe same resources that are excluded for a SYSVOL replica set must also be excluded when FRS is used to replicate shares that are mapped to the DFS root and link targets on Windows Server 2008-based, Windows Server 2003-based, or Windows 2000-based member computers or domain controllers.
    • DHCPBy default, DHCP files that should be excluded are present in the following folder on the server:%systemroot%\System32\DHCPNoteYou should exclude all files and subfolders that exist in this folder.The location of DHCP files can be changed. To determine the current location of the DHCP files on the server, check the DatabasePath, DhcpLogFilePath, and BackupDatabasePath parameters under the following registry subkey:

      HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\DHCPServer\Parameters

For Windows Server 2008, Windows Server 2003, and Windows 2000 domain controllers
  • DNS: You should exclude all files and subfolders that exist in the following folder:%systemroot%\system32\dns
  • WINS: You should exclude all files and subfolders that exist in the following folder:%systemroot%\system32\wins

File-Level Antivirus Scanning on Exchange 2010

Guidelines for choosing antivirus software to run on the computers that are running SQL Server

Anti-Virus Exclusions for Windows Server 2008 or Windows Server 2008 R2 based computer that has Hyper-V Role installed

Certain folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in SharePoint

Specifying Antivirus Scanning Exclusions for Lync Server 2010

Na dann, Viel Spass beim selber Testen!
CU

Windows 7: RDS Remote Apps nutzen

Hi,

seit Windows Server 2008 gibt es ja schon die möglich remote nur einzelne Anwendungen zu starten, per Terminal Services Remote Apps, die ja jetzt in Windows Server 2008 R2 in Remote Desktop Serives RemoteApps umbenannt wurden. Daür wird RAIL (Remote Applications Integrated Locally) genutzt, was dafür sorgt, dass die Anwendungen dabei nahtlos mit dem eigenen Desktop seamless dargestellt werden. Die Remoteanwendungen (»RemoteApps«) erscheinen also in einem eigenen Fenster
und nicht innerhalb eines Remotedesktop Fensters. Im Hintergrund wird für den Benutzer transparent eine RDP Sitzung gestartet und die ausgewählt Anwendung geöffnet. Auch Dialogfelder und sogar Symbole im Infobereich der Taskleiste erscheinen in diesem Fall genauso, als würde es sich um eine lokale Anwendung handeln.

Mit wenigen Anpassungen kann aber auch Windows 7 in den Enterprise und Ultimate Versionen dazu verwenden, RemoteApps bereitzustellen. Andere Windows-Versionen können zwar über den Remote Desktop Client auf einzelne remote bereitgestellte Anwendungen zugreifen, aber die Bereitstellung selbst erfordert entweder Windows
7 Enterprise/Ultimate oder einen Remote Desktop Session Host (Terminalserver).
Dazu sind folgende Schritte nötig:

  1. Unter Start, Ausführen “regedit” eingeben und starten (Registrierungseditor als Administrator).
  2. Navigieren zum Zweig “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
    NT\CurrentVersion\Terminal Server\TSAppAllowList”
  3. Doppelklicken des Eintrag´s “fDisabledAllowList” und dem Eintrag den Wert 1
    zuweisen (heißt wirklich fDisabledAllowList “f” am Namensanfang ist kein Druckfehler). Durch diese Änderung wird Windows 7 autorisiert, sämtliche Anwendungen als RemoteApps bereit zustellen!

windows7_rds_remote_apps01

Als nächstes wechselt man zu dem Computer, von dem man aus remote auf Anwendungen zugreifen will. Man erzeugt auf diesem Rechner eine neue RDP-Datei:

  1. Entweder unter Unter Start, Ausführen “mstsc” eingeben oder im Startmenü den Remotedesktopclient (unter Zubehör) starten
  2. Konfigurieren der übrigen Einstellungen wie IP-Adresse oder Hostname, Sicherheitseinstellungen usw. bereits beschrieben, als würden Sie eine
    reguläre Remotedesktopverbindung einrichten wollen.
  3. Im RDP Client auf “Optionen” klicken und auf der Registerkarte Allgemein auf die Schaltfläche “Speichern unter”. Speichern der Einstellungen unter einem Namen wie z.B. “Remoteanwendung x.rdp” auf dem Desktop
  4. Anpassen des Inhalts der RDP-Datei erweitern, mit der rechten Maustaste anklicken und Kontextmenü “Öffnen mit” wählen. unbedingt das Kontrollkästchen “Dateityp immer mit dem ausgewählten Programm öffnen” Deaktivieren!
  5. auf den Pfeil am rechten Ende der Kategorie “Andere Programme” klicken und 
    Editor auswählen, Der Inhalt der RDP-Datei wird nun im Editor angezeigt (Liste von Textanweisungen)
  6. Hinzufügen z.B. der folgenden Zeilen
    alternate shell:s:%windir%\System32\cmd.exe
    remoteapplicationprogram:s:%windir%\System32\cmd.exe
    remoteapplicationcmdline:s:
    remoteapplicationname:s:Remotekonsole auf Rechner X
    remoteapplicationicon:s:
    oder
    alternate shell:s:%programfiles%\Internet Explorer\iexplore.exe
    remoteapplicationprogram:s:%programfiles%\Internet Explorer\iexplore.exe
    remoteapplicationcmdline:s:
    remoteapplicationname:s:Internet Explorer Remote auf Rechner X
    remoteapplicationicon:s:
  7. Suchen des bereits existierenden Eintrag remoteapplicationmode:i:0 und ändern in des Wert´s von 0 auf 1

windows7_rds_remote_apps02

Na dann, Viel Spass beim selber Testen!
CU

Windows 7 / Server 2008 R2: Hotfix für Windows Media Player 12 Problem mit Videobild flackern

Hi,

unter Windows 7 und Windows  Server 2008 R2 behebt ein Hotfix von Microsoft die Probleme mit mit Videobild flackern des Windows Media Player 12. Der KB Artikel 975806 gibt darüber Auskunft:

You have a computer that is running Windows 7 or Windows Server 2008 R2. You configure Windows Media Player 12 to display subtitles when you play a DVD. However, the video image flickers every time that a new line of subtitle is displayed.

This problem occurs because of an issue in the way that the Enhanced Video Renderer (EVR) handles subtitle notifications.

Na dann, Viel Spass beim selber Testen!
CU

Windows Vista / Server 2008: Hotfix für Black Screen Problem beim starten

Hi,

falls Windows Vista oder Windows Server 2008 mit installiertem SP1 und SP2 beim Hochfahren mit einem Black Screen stehen bleiben, kann dafür ein Hotfix von Microsoft installiert werden. Der KB Artikel 977675 gibt darüber Auskunft:

When you start a computer that is running Windows Vista or Windows Server 2008, it stops responding at a black screen early in the startup process.

The issue occurs because of a deadlock between a thread in Windows NT File System driver (Ntfs.sys) and a thread in the Autochk.exe program.

Na dann, Viel Spass beim selber Testen!
CU