>This issue doesn't exist when connecting to a Server 2008 R1 server, so it's some R2/Win7 change that did it. >Hoping for an upstream fix soon.
It exists in 2008 R1 also (at least for me). I created this bug because of this issue being present in R1.
>This issue doesn't exist when connecting to a Server 2008 R1 server, so it's some R2/Win7 change that did it. >Hoping for an upstream fix soon.
It exists in 2008 R1 also (at least for me). I created this bug because of this issue being present in R1.