Re: NT4 --> 2003 , lmhosts?



well if the clients use LMHOSTS for some reason then this will be a problem
when we start decomissioning the NT4 domain controllers and replace them
with new W2K3 DC's with new names...


"Amanda Wang [MSFT]" <v-amanwa@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:sQXXUriSFHA.4172@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> Thanks for your post.
>
> Based on my experience, it is not difficult to perform an in-place upgrade
> from NT to win2k3. However, backup the system is always the first thing
> before you take any action. In addition, if you have PDC and several BDCs
> in the NT domain. please upgrade PDC to win2k3 first.
>
> With regards to the lmhost, do you mean certain client use lmhost to
> resolve IP and netbios name? If this is the case, domain upgrade will not
> affect the client's lmhost.
>
> Another point is, you can choose interim domain function level when you
> upgrade NT to win2k3. You can perform the following steps to upgrade from
> NT4 domain to Windows 2003 domain:
>
> As a kind reminder, please backup the whole system before you take any
> action.
>
> 1.Install NT 4.0 BDC on the new box.
>
> 2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
>
> 3.Do a full backup of the former PDC and remove it from the network.
>
> 4.Upgrade the new PDC to Windows Server 2003.
> If you want to expand the boot partition, please refer to the following
KB:
>
> 325857 How To Expand the Boot Partition During a Windows Server 2003
Upgrade
> http://support.microsoft.com/?id=325857
>
> 5.Use the Windows Server 2003 Active Directory wizard to turn on the
Active
> Directory service. The Active Directory service imports the existing user
> accounts, groups, and other settings from the PDC.
>
> Please pay attention to the domain function level, the following article
> has introduced the interim level:
> How to raise domain and forest functional levels in Windows Server 2003
> http://support.microsoft.com/kb/322692
>
> 6.Run for a test period.
>
> 7.If desired you can do a clean installation of Windows Server 2003 on the
> former PDC, and bring it online as an Active Directory domain controller.
>
> 8.Transfer all Flexible Single-Master Operation (FSMO) roles to the new
> Windows Server 2003 domain controller.
>
> 9.Verify all directory information has replicated.
>
> 10.Demote the first domain controller to a member server, and remove from
> the domain.
>
> I suggest you check the following KB articles to migrate to Win2k3 from
NT4:
>
> White Paper: Migrating Windows NT Server 4.0 Domains to Windows Server
2003
> Active Directory
> <http://support.microsoft.com/default.aspx?scid=kb;en-us;818623> archived
>
> HTH!
>
> Thanks & Regards
>
> Amanda Wang [MSFT]
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ====================================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================================
>
> --------------------
> >From: "Ziek" <ziek@xxxxxxxxxx>
> >Subject: NT4 --> 2003 , lmhosts?
> >Date: Mon, 25 Apr 2005 06:09:00 -0400
> >Lines: 5
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> >X-RFC2646: Format=Flowed; Original
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> >Message-ID: <#TKXF7XSFHA.3788@xxxxxxxxxxxxxxxxxxxx>
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: ottawa-hs-209-217-83-26.d-ip.magma.ca 209.217.83.26
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:9842
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >I am upgrading a very large NT4 domain to Win2003. Are there any
> >precautions I need to take if this company has made use of Lmhosts files
> on
> >certain machines?
> >
> >
> >
>


.



Relevant Pages

  • Re: Blank Forest Functional Level - Unable to fix
    ... I would start looking very closely at all DCs to verify that the same DC is set for the PDC master. ... I promoted a Windows Server 2003 SP1 server to a domain controller. ... Anyway, you could be running into something odd when raising the forest functional level and even though it isn't required for R2, I will offer a command line mechanism to do it that will kick out an error message that can be used to work out the issue. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT4 and W2K3 Questions
    ... the only in-place upgrade path is to install Windows Server 2003 on the ... This does not have to be your present PDC. ... An AD domain controller for the domain XYZ cannot be contacted, ...
    (microsoft.public.windows.server.general)
  • Migration Approach in NT4 to Win2K3 AD
    ... Promote this NT4 Domain Controller to PDC, which demotes the PDC to a BDC. ... Use the Windows Server 2003 Active Directory wizard to turn on the Active Directory service. ...
    (microsoft.public.win2000.active_directory)
  • Re: Migration to SBS 2003
    ... the PDC to a BDC. ... >Upgrade the new PDC to Windows Server 2003. ... turn on the Active Directory service. ... Active Directory domain controller. ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: migrate from windows nt4 to windows 2003
    ... intend to replace the original NT PDC to a win2k3 DC. ... win2k3 domain, we will set up trusts between the two domains. ... I would like to suggest that we upgrade the NT ... 325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade ...
    (microsoft.public.windows.server.migration)