I've been researching this site and others regarding ActiveSync throwing the classic error that Microsoft KB article 817379 is supposed to fix. I've gone through the resolution instructions both in the MS KB article and from Sembee. I'm still getting the error.
We did have this working properly in the past. It was not until last week when we lost a domain controller and I have to rename/rejoin it to the network that this error started coming up. I don't see why this issue would have effected the ActiveSync functionality - unless there's a setting somewhere else that is still pointing to the old DC server name??? Any help is appreciated. Thanks.
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.