Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1

• Known issue 1

  Symptoms
  
  A new Ethernet Network Interface Card (NIC) that has default settings may replace the previous NIC and cause network issues. Any custom settings on the previous NIC persist in the registry but aren't used.
  
  Resolution
  
  To fix this issue, run the following VBS script. Copy and paste this script into Notepad, and then save the file with a .vbs extension.
  
  Instructions
  
  Before you run the script, make sure that you back up the following registry key and subkeys:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI
  
  This script can be run on physical or virtual computers at any of the following times:
   
  • Immediately before installing the Convenience Rollup.
  • Immediately after installing the Convenience Rollup but before restarting the following update installation.
  • After installing Convenience Rollup 3125574 and after restarting even though the computer is in a problem state. In this situation, another restart will be required after the script is run.
  
  Note The script also includes binary version checks around PCI.SYS file.
   
  Script

  Dim strPciFileVersion
  Dim WindirFilePath

  set WshShell = WScript.CreateObject("WScript.Shell")
  WindirFilePath = WshShell.ExpandEnvironmentStrings("%WinDir%")
     
  Dim fs
  Set fs = CreateObject("Scripting.FileSystemObject")
     
  strPciFileVersion = fs.getfileversion(WindirFilePath & "\\system32\\drivers\\pci.sys")
  Dim strAryFileVersion1

  strAryFileVersion1 = Split(strPciFileVersion, ".")

  If (strAryFileVersion1(0) = 6 And strAryFileVersion1(1) = 1 And strAryFileVersion1(2) = 7601) Then
                  If (strAryFileVersion1(3) < 17630 Or (strAryFileVersion1(3) > 20000 And strAryFileVersion1(3) < 21744)) Then
                                 
                                  Const HKEY_LOCAL_MACHINE = &H80000002
                                  Dim oReg : Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")
                                  Dim oShell : Set oShell = CreateObject("WScript.Shell")
                                  Dim sPath, aSub, sKey, aSubToo, sKeyToo, dwValue, Result, SaveResult
                                  Dim NotDeleted
                                 
                                  NotDeleted = 0
                                 
                                  ' Get all keys within sPath
                                  sPath = "SYSTEM\CurrentControlSet\Enum\PCI"
                                  oReg.EnumKey HKEY_LOCAL_MACHINE, sPath, aSub
                                 
                                  ' Loop through each key
                                  For Each sKey In aSub
                                                  ' Get all subkeys within the key 'sKey'
                                                  oReg.EnumKey HKEY_LOCAL_MACHINE, sPath & "\" & sKey, aSubToo
                                                  For Each sKeyToo In aSubToo
                                                    Result = oReg.DeleteKey(HKEY_LOCAL_MACHINE, sPath & "\" & sKey & "\" & sKeyToo & "\" & "\Device Parameters" & "\SlotPersistentInfo")
                                                    ' Allow failure only if key never existed
                                                    If (Result = 1) Or (Result > 2) Then
                                                                  NotDeleted = 1
                                                                  SaveResult = Result
                                                    End If
                                                  Next
                                  Next
                                 
                                  If (NotDeleted > 0) Then
                                    Wscript.Echo "SlotPersistentInfo keys still exist under HKLM\System\CurrentControlSet\Enum\PCI\<deviceid>\<subdeviceid>\Device Parameters.  Please delete all manually and then install the updates. Result = " & Result
                                  End If
                  Else
                                  WScript.Echo "Your system is ready to install the updates"
                  End If     
  Else
                                  WScript.Echo "Your system is ready to install the updates"
  End If

• Known issue 2

  Symptoms
  
  After you install this rollup, virtualized applications in Microsoft Application Virtualization (App-V) versions 4.5, 4.6, and 5.0 may have problems loading. When these problems occur, you may receive an error message that resembles the following:
  Launching MyApp 100%
  Note In this error message, MyApp represents the name of the App-V application.
  
  
  Depending on the scenario, the virtualized app may freeze after it starts, or the app may not start at all.
  
  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 How to back up and restore the registry in Windows
  
  Resolution
  
  To fix this known issue, configure the TermSrvReadyEvent registry entry on the computer on which the Microsoft Application Virtualization Client is installed.
  
  For Microsoft Application Virtualization 5.0
  • Registry Key: HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions
    Value name: 93 (or any unique value)
    Type: REG_SZ
    Data: TermSrvReadyEvent
    
    
    Example
    For example, type the following command at an elevated command prompt to add the entry to a system that is running Application Virtualization 5.0:
    reg add HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions /v 93 /t REG_SZ /d TermSrvReadyEvent
  For Microsoft Application Virtualization 4.6
  • For all supported x86-based systems
    
    Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
    Value name: 95 (or any unique value)
    Type: REG_SZ
    Data: TermSrvReadyEvent
    
    Example
    For example, type the following command at an elevated command prompt to add the entry to an x86-based system that is running Application Virtualization 4.6:
    reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent
  • For all supported x64-based systems
    
    Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
    Value name: 95 (or any unique value)
    Type: REG_SZ
    Data: TermSrvReadyEvent
    
    Example
    For example, type the following command at an elevated command prompt to add the entry to an x64-based system that is running Application Virtualization 4.6:
    reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent

• Known issue 3

  Symptoms
  
  After you install this rollup, if outgoing NTLM traffic is blocked by using the following group policy setting:
  Policies\Windows Settings\Security Settings\Local Policies\SecurityOptions\Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers
  Group Policy object (GPO) backup operations will fail with both Group Policy Management Console (GPMC) as well as PowerShell with the following error message:
  A directory Service error has occurred
  Additionally, gpmgmt.log will log the following errors:
  [XXX.XXX] DateTime [WARNING] LdapConnectServer: ldap_bind_s failed with 0x80072095
  
  Resolution
  
  1. You can use a Windows 8.1 or newer operating system to perform the GPO Backups instead.
  
  -OR-
  
  2. To fix this known issue, configure an exception for Windows 7 and Windows Server 2008 R2 Systems doing GPO Backup operations, in order to enable outgoing NTLM authentication:
  • Configure an exception through GPO (for example: ldap/contoso.com)
    Policies\Windows Settings\Security Settings\Local Policies\SecurityOptions\Network Security: Restrict NTLM: Add remote server exceptions
  • Configure an exception through the registry (for example: ldap/contoso.com)
    HKLM\System\CurrentControlSet\Control\LSA\MSV1_0\<ClientAllowedNTLMServers>

• Known issue 4

  Symptoms
  
  After you install this rollup, in some cases, you may notice that the robocopy mirroring (/MIR) command is not working as expected. It is observed that instead of only copying modified files from Source to Destination, robocopy is also copying the files that were not modified.
  
  Command where the issue is observed:
  Robocopy <source> <destination> /MIR [<options>]
  
  Resolution
  
  To fix this issue, you are advised to use archive attribute based mirroring. In this mode, robocopy mirroring makes sure to only copy files that were modified in Source and skip the rest.
  
  Command for archive attribute based mirroring:
  Robocopy <source> <destination> /MIR /A /M [<options>]
  Note In first pass, it will still copy all the files. However, in subsequent runs, it will only copy the files that were modified.
   

• Known issue 5

  Symptoms
  
  32-bit applications can't change local Group Policy in 64-bit version of Windows 7 SP1 and Windows Server 2008 R2 SP1.
  
  Resolution
  
  To fix this issue, uninstall the update KB3125574.

This update replaces the previously released update 2614451 and 2800422.