Just a tad frustrating in that we suspect MS has a hand in this and yet no true solutions. Worse is that MS hasn't even mentioned the issue one way or another and we all know that they surf sites like bytes.com and others as a means of Bug hunting (IMHO a good practice as the bugs tend to show up in the forums long before they are reported to MS).
One day, we'll all be in a perfect happy place where OS runs as it's supposed to!
RESOLVED! Evidently this is a known issue and a hotfix exists to resolve it. i have only been able to test it with 1 client but i appears to have worked.
Comment