You're welcome! 

>>>-----Original Message-----
>>>From: [EMAIL PROTECTED] 
>>>[mailto:[EMAIL PROTECTED] On Behalf Of Mark Parris
>>>Sent: Friday, May 05, 2006 18:58
>>>To: ActiveDir.org
>>>Subject: Re: [ActiveDir] NT4Emulator Reg Key
>>>
>>>Thanks Jorge.
>>>
>>>I have not done an inplace before, only migrations.
>>>
>>>
>>>Mark
>>>-----Original Message-----
>>>From: "Almeida Pinto, Jorge de" 
>>><[EMAIL PROTECTED]>
>>>Date: Fri, 5 May 2006 17:52:35
>>>To:<[email protected]>
>>>Subject: RE: [ActiveDir] NT4Emulator Reg Key
>>>
>>>As the key says, the NT4Emulator key makes a AD DC behave 
>>>like an NT4 DC. When trying to promote additional DCs or 
>>>using w2k/wxp/w2k3 clients to manage AD you are not able to connect. 
>>>The main reason the NT4Emulator key is to prevent ALL 
>>>w2k/wxp/w2k3 clients and servers swamping down the PDC FSMO 
>>>as that is the first AD DC in the field. Another reason 
>>>could me you want to in place upgrade and see if everything 
>>>goes OK without starting using kerberos already.
>>>As soon as you are satisfied and you have enough AD DCs you 
>>>can remove the NT4Emulator keys from the AD DCs and ALL 
>>>w2k/wxp/w2k3 clients and servers will start using kerberos 
>>>instead of NTLM as soon as they find the AD DCs.
>>>
>>>OK, back to the connecting thing....
>>>To be able to connect and to add additional AD DCs you must 
>>>introduce the NeutralizeNT4Emulator key on the client that 
>>>tries to connect or on the DC you are promoting. For the DC 
>>>you are promoting, make sure you introduce the NT4Emulator 
>>>key (if needed!) otherwise the w2k/wxp/w2k3 clients and 
>>>servers will find that DC and use it!
>>>
>>>Normal? No
>>>Feature of R2? No
>>>You? Who knows... ;-))
>>>
>>>Cheers,
>>>jorge
>>>
>>>>>>-----Original Message-----
>>>>>>From: [EMAIL PROTECTED]
>>>>>>[mailto:[EMAIL PROTECTED] On Behalf Of 
>>>Mark Parris
>>>>>>Sent: Friday, May 05, 2006 16:11
>>>>>>To: ActiveDir.org
>>>>>>Subject: [ActiveDir] NT4Emulator Reg Key
>>>>>>
>>>>>>I am upgrading an NT4.0 domain to Windows 2003R2 and on the PDC I 
>>>>>>have added to the HKLM...Netlogon\parameters the key 
>>>NT4Emulator with 
>>>>>>a value of 1 and then done the inplace upgrade. I now try 
>>>to promote 
>>>>>>in another AD DC and it does not work I get DNS timeout errors 
>>>>>>(0x000005B4 ERROR_TIMEOUT)
>>>>>>
>>>>>>DNS is configured correctly and removing the key and 
>>>rebooting the 
>>>>>>upgraded DC makes the issue go away and I can add new AD DC's.
>>>>>>
>>>>>>Is this normal or is it a new feature of R2?
>>>>>>
>>>>>>Mark
>>>>>>List info   : http://www.activedir.org/List.aspx
>>>>>>List FAQ    : http://www.activedir.org/ListFAQ.aspx
>>>>>>List archive: 
>>>>>>http://www.mail-archive.com/activedir%40mail.activedir.org/
>>>>>>
>>>
>>>
>>>This e-mail and any attachment is for authorised use by the 
>>>intended recipient(s) only. It may contain proprietary 
>>>material, confidential information and/or be subject to 
>>>legal privilege. It should not be copied, disclosed to, 
>>>retained or used by, any other party. If you are not an 
>>>intended recipient then please promptly delete this e-mail 
>>>and any attachment and all copies and inform the sender. Thank you.
>>>List info   : http://www.activedir.org/List.aspx
>>>List FAQ    : http://www.activedir.org/ListFAQ.aspx
>>>List archive: 
>>>http://www.mail-archive.com/activedir%40mail.activedir.org/
>>>
>>>[EMAIL PROTECTED]
>>>Ö«r¯zm§ÿðà šŠV«r¯yÊ&ý§-Š÷Š¾4™¨¥iËb½çb®Šà
>>>

Reply via email to