3. November 2010 13:32
Today I had a strange problem.
I was at a customer who had both 2003 R2 and 2008 R2 DC's in their domain.
If I created a new GPO on a 2003 DC everything was ok, but if I created the GPO on a 2008 DC the "Administrative Templates" was empty.
It turned out to be because there was created an empty folder called "PolicyDefinitions" on the domain.local\sysvol\domaon.local\policies share.
When the GPMC opens a policy it will look for the ADMX files in "C:\Windows\PolicyDefinitions" execpt for if the "domain.local\sysvol\domaon.local\policies\PolicyDefinitions" folder exists. This is a central store for Policies.
If the "domain.local\sysvol\domaon.local\policies\PolicyDefinitions" folder exists it will load the ADMX files from there but if the folder is empty it will not show anything "Administrative Templates".
To solve the problem I just copied all the files from the "C:\Windows\PolicyDefinitions" folder to the "domain.local\sysvol\domaon.local\policies\PolicyDefinitions" folder.
13. October 2010 11:13
I have seen problems resolving some DNS names at several of our customers after upgrading their DNS servers to Windows Server 2008 R2.
It happens to be a known problem with the "Extension Mechanisms for DNS (EDNS0)" functionality of DNS in Windows Server 2008 R2 and some firewalls.
ENDS0 permits the use of larger User Datagram Protocol (UDP) packet sizes. However, some firewall programs may not permit UDP packets that are larger than 512 bytes. As a result, these DNS packets may be blocked by the firewall.
The resolution to the problem is to run the following command on every Windows Server 2008 R2 DNS server.
dnscmd /config /enableednsprobes 0
Further information can be found in this KB article: http://support.microsoft.com/kb/832223
23. August 2010 23:37
A long time ago i ran into a problem where Windows Server 2008 R2 loses the ability to connect to a network share on a Windows Server 2003.
Microsoft has now finally released a hotfix to the problem (KB2194664).
When the Windows Server 2008 R2 is restarted everything is working as it should. But after a while it can no longer connect to a network drive on a Windows Server 2003 server.
Sometimes I cannot map on the UNC name and sometimes I cannot map on the IP address.
When I cannot map the home drive on the UNC name I will get the following error:
System error 53 has occurred. "The network path was not found"
When I cannot map the home drive using the IP address I will get the following error:
System error 59 has occurred. "An unexpected network error occurred."
Back in January 2010 I started a tread on the MS forum describing the problem. It has now grown to be a large tread with 159 posts and over 16.000 views. More...