I would like to know if this hotfix can be applied to Server 2008 Enterprise service pack 2. I do NOT have R2. This article doesnt state if it will work. http://support.microsoft.com/kb/978055

On Tue, 10 Aug 2010 17:34:16 +0000, Timbure96 wrote: I would like to know if this hotfix can be applied to Server 2008 Enterprise service pack 2.? I do NOT have R2.? This article doesnt state if it will work. http://support.microsoft.com/kb/978055 According to the article in question it is only valid for R2. Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca

I guess then, the second part is to ask, how can I enable DES encryption on a Windows Server 2008 SP2 (not R2)? Is it even possible? I've looked high and wide and have not found a single answer. Everything refers to R2.

On Tue, 10 Aug 2010 19:06:07 +0000, Timbure96 wrote: I guess then, the second part is to ask, how can I enable DES encryption on a Windows Server 2008 SP2 (not R2)?? Is it even possible? I've looked high and wide and have not found a single answer. Everything refers to R2. In the properties dialog for the user account, on the Account tab, in the Account Options list. Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca

i tested this on myself. In active directory, i checked the box to user DES. Then on my machine (Windows 7) I checked the boxes to use DES encryption. I rebooted and it didnt work.

On Wed, 11 Aug 2010 15:11:17 +0000, Timbure96 wrote: i tested this on myself.? In active directory, i checked the box to user DES.? Then on my machine (Windows 7) I checked the boxes to use DES encryption.? I rebooted and it didnt work. Then you're probably going to need to open a support case with Microsoft. Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca

Ok I just did. I will post the outcome here in case other users are having the same issue.

After applying this hotfix I am still seeing the same issue as described here. I promoted a different domain controller last week and applied this hotfix & everything was ok. However, thats not the case on a newly promoted DC. Anyone have any ideas as to why this patch didnt fix-it? I did remove and reinstall it as well to no avail. Thanks