Probably (didn't take the time to verify, although removing it from SUG resolved the issue) due to this known issue and may need to be added to the list: http://support.microsoft.com/kb/2894518 I've experienced this on Windows Server 2008 R2 deployments thus far, but taking it out of all deployments and injecting in the reference WIM's. I read it's important for DC's but we decided to go ahead and make it the standard. Just a heads up. -Stephen
