Re: Adding target domain on source domain's workstation for migration

From: Curtis Fray (curtis.fray_at_Xbssmail.nhs.uk)
Date: 09/06/04


Date: Mon, 6 Sep 2004 16:08:52 +0100

Hi Bob,

Sorry for the delay in replying. I've been away and just got back. Hopefully
you're still monitoring this thread.

Thank you for your ideas. Unfortunatey the NT domain I'm upgrading does not
have a WINS or DNS server. Historically its always depended on HOST and
LMHOST files (hence yet another reason for the migration and fresh start!).
That why I was hoping it may be possible to add the necessary entry in the
host files.

I could set up the necessary servers but would then have to set up all
client machines with the new WINS and DNS server entries. Is it possible to
change these with a logon script maybe to avoid visiting all machines? If so
I could just point them to the new DNS server in the new domain which does
overcome the problem.

Any other thoughts you have on this would be greatly appreciated.

Thanks,

Curtis.

-------------------------------

"Bob Qin [MSFT]" <bobqin@online.microsoft.com> wrote in message
news:e8ucGCziEHA.2816@cpmsftngxa10.phx.gbl...
> Hi Curtis,
>
> Thanks for your posting here.
>
> I would like to recommend that you point your Windows 2003 DC to the NT
> WINS server and createa a secondary zone on Windows NT DNS server for the
> Windows 2003 domain. Then you can keep the clients pointing to the NT DNS
> server.
>
> If the problem still persists, please let me know the detailed error
> message in migration log and I will do further research.
>
> Regards,
> Bob Qin
> 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.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
> From: "Curtis Fray" <curtis.fray@Xbssmail.nhs.uk>
> Subject: Adding target domain on source domain's workstation for
> migration
> Date: Wed, 25 Aug 2004 12:31:08 +0100
> Newsgroups: microsoft.public.windows.server.migration
>
> Hi,
>
> I was having trouble migrating computers across to a new domain until
> I
> found the source workstations need to be able to resolve the full
> domain
> name of the new 2003 domain (ie, abc.com). I can resolve this by
> specifying
> the target domain's DNS server as the source workstations primary DNS
> server. However, due to the amount of workstations I have to do this
> isn't
> really practical. Does anyone know if it's possible to specify the
> full DNS
> domain name in HOST or LMHOST files?
>
> I have already set the target domain's NETBIOS domain name in the
> lmhost
> file of the client machine, but this doesn't appear to be sufficient
> for its
> migration. It seems to require the full DNS domain name.
>
> Thanks,
>
> Curtis.
>
> ====================================
> When replying by email please remove the X
> ====================================
>
>
>
>



Relevant Pages

  • Re: NT4 - ADMT - 2003 & XP Agents
    ... the 2003 DNS Server prior to their migration." ... It looks like the Workstations in the NT Domain could not successfully ... > Please point the Workstation to the DNS Server in the 2003 Domain and test ... > profile on Translate objects screen. ...
    (microsoft.public.windows.server.migration)
  • ADMT
    ... I am new in ADMT. ... Migration Wizard, the DNS of the source domain could not be resolved. ... installed ADMT on target migration domain DC. ... Currently both domain have DNS server running on the DC(pointed back ...
    (microsoft.public.windows.server.migration)
  • Re: Integrated Active Directory DNS?
    ... If the DNS server runs on a member server. ... In my own migration I installed DNS on Win2000 member servers in an NT ... >Integratate zones? ...
    (microsoft.public.win2000.active_directory)
  • Configure 2003 DNS Server for NT4 domains
    ... server 2003 from an NT 4 environment. ... have a large organisation and need to do a phase migration. ... we want to set the DNS server for the abc.nt.dom clients to the 2003 DNS ...
    (microsoft.public.windows.server.dns)
  • Re: DNS/IP resolution issues
    ... > the DHCP server has a limited range of 15 address for wireless laptop ... > no entries (on either machines affected with this issue or not). ... You have no DNS server? ...
    (microsoft.public.windows.server.dns)