We start to deploy RODCs at one of our clients and in the pilot we’ve discovered, that even though the LOGONSERVER is the local RODC, the general logonscript runs from a remote writeable DC. We can see this on the logonscreen, as the general logonscript shows its status. Now I suspect, that this might be due to the fact that most of our DCs are still Windows 2003 and the forest/domain level is also Windows 2003 (see the Known RODC issues page from Technet) The well-known KB944043 has been deployed on all Windows 2003 domain controllers and XP client PCs. Now we plan to set up a test user that would only have a very basic logonscript to see if that would run from the local RODC. How could we track from which DC this basic logonscript runs? Thanks in advance!