This hotfix resolves the following issues.
Note If you use network monitoring tools to troubleshoot this issue, you can see many Lightweight Directory Access Protocol (LDAP) queries that are checking the object type of group members in the domain. These LDAP queries originate from the computers that received GPP through item-level targeting.
Note To determine whether you are experiencing this issue, run the netstat -ano command at a command prompt to look for connections to port 389.
The netstat -ano command returns output that resembles the following:
If you run this command again after some time (or if you run the gpupdate /force command) you will notice that the number of open ports grows.
To temporarily work around this issue, restart the computer. This action resolves the problem temporarily as it will close the open ports.
Issue 2
When you apply GPP by using item level targeting for security groups, you notice the SVCHOST instance running the Group Policy Service is leaking virtual memory.
Issue 1
Assume that you have a client computer in a domain environment. The computer is running one of the following operating systems:- Windows Vista
- Windows 7
- Windows Server 2008 R2
Note If you use network monitoring tools to troubleshoot this issue, you can see many Lightweight Directory Access Protocol (LDAP) queries that are checking the object type of group members in the domain. These LDAP queries originate from the computers that received GPP through item-level targeting.
Issue 2
When you apply GPP by using item level targeting for security groups, local ports are leaked in an OPEN_WAIT state. After some time, the nonpaged pool is depleted and the computer stops responding.Note To determine whether you are experiencing this issue, run the netstat -ano command at a command prompt to look for connections to port 389.
The netstat -ano command returns output that resembles the following:
TCP 172.22.244.52:49186 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49227 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49258 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49284 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49300 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49315 172.22.244.50:389 CLOSE_WAIT 968 TCP 172.22.244.52:49331 172.22.244.50:389 CLOSE_WAIT 968
If you run this command again after some time (or if you run the gpupdate /force command) you will notice that the number of open ports grows.
To temporarily work around this issue, restart the computer. This action resolves the problem temporarily as it will close the open ports.
Issue 2
When you apply GPP by using item level targeting for security groups, you notice the SVCHOST instance running the Group Policy Service is leaking virtual memory.