GPOs is what helped us discover that the NT4Emulator setting was still enabled.
We were implementing a new Citrix PS 4.5 farm, and the GPO we had set for the
Citrix OU wouldn't apply to any of the servers. A little digging showed that
the servers saw the domain a NT4 - many head scratches later - I set the
NeutralizeNT4Emulator setting on one of the Citrix servers and the GPO applied
immediately. I - incorrectly - assumed that I could disable the NT4Emulator
setting on the DCs, and all my Win2K and newer member devices would throw a
party and start using Kerberos. Instead, they puked and started throwing fits.
I ran DCDIAG and NETDIAG and both reported everything was fine - time for the
Jim Beam.
~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~
~ <http://www.sunbelt-software.com/product.cfm?id=400> ~
