Re: Adding target domain on source domain's workstation for migration
From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 09/07/04
- Next message: Bob Qin [MSFT]: "RE: Moveuser Migration"
- Previous message: Bob Qin [MSFT]: "RE: DC moving to 2003 Version of Active Directory"
- In reply to: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Next in thread: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Reply: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 07 Sep 2004 07:05:38 GMT
Hi Curtis,
In fact, we can create LMHOSTS files to point the clients to the target
domain and PDC of the target domain. Please refer to the following article
to create a properly formatted Lmhosts file.
How to Write an LMHOSTS File for Domain Validation and Other Name
http://support.microsoft.com/?id=180094
But it is not a recommended solution in Windows Active Directory. If you
use dynamic IP address in your network, you can assign the new DNS and WINS
server to clients using DHCP options.
228803 DHCP Dynamic Updates with DNS
http://support.microsoft.com/?id=228803
323360 How to install and configure a DHCP Server in an Active Directory
domain
http://support.microsoft.com/?id=323360
Hope this helps!
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: Re: Adding target domain on source domain's workstation for
migration
Date: Mon, 6 Sep 2004 16:08:52 +0100
Newsgroups: microsoft.public.windows.server.migration
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
> ====================================
>
>
>
>
- Next message: Bob Qin [MSFT]: "RE: Moveuser Migration"
- Previous message: Bob Qin [MSFT]: "RE: DC moving to 2003 Version of Active Directory"
- In reply to: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Next in thread: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Reply: Curtis Fray: "Re: Adding target domain on source domain's workstation for migration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
