Be aware of a problem when renaming domain controllers
If you have renamed a Windows Server 2008 or Windows Server 2008 R2 domain controller you should be aware of a problem. The problem is that a DFSR object is not renamed to the new name. This does not cause any problems until you remove the domain controller in question and after doing a demote or cleaning it up with metadata cleanup the object will become orphaned. So if you have renamed 2008 or 2008 R2 DCs you should follow the steps in KB2001271 to fix this.
Case of the mysterious issues with UAC in Windows 7 and Windows Server 2008 R2
Solution to have multiple SSL sites on port 443 in IIS
Follow-up to TechEd session WCL326: Five infrastructure changes that will boost performance for the Windows Client
About Author
Andreas Stenhall
I'm Andreas Stenhall and my work passion is the Windows client in combination with Microsoft 365 security and management services. I do consulting, I produce and teach my own courses, I lecture and I present and my formal work title is prinicipal workplace advisor and architect at Coligo in Stockholm, Sweden. I'm also proud to be an Microsoft MVP since 2009. I have presented at BUILD, TechEd in the US and Europe and regional TechDays. Follow me on twitter @AndreasStenhall.