Re: Duplicate Computer ADMT Migration
- From: "chriss3 [MVP]" <removethis_christoffer@xxxxxxxx>
- Date: Fri, 19 May 2006 21:39:25 +0200
This is interesting, You may don't have to point the new clients to the WINS
server instead you can have the DNS in AD query the WINS server for name
resolution it can't be solved be DNS.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Resources
"PaulF" <PaulF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:50788E25-154B-4165-9AC8-870D99DB59C7@xxxxxxxxxxxxxxxx
Hi,
I have an NT4 Domain, im currently migrating this to 2003, everything is
working correctly, the trusts are working between the two domains, i can
migrate user accounts and groups without error. However when i come to
migrate a computer account, it works, then reboots, then the client
displays
a system error message stating that a duplicate computer exists on the
network.
The AD Domain and the NT4 Domain are pointing to the same WINS Server, and
DNS is on the AD DC. If i remove the WINS Settings from the client,
everything appears hunky dory, but this is pretty much unaceptable at the
moment as they need that level of resolving during the migration to which
could
take a while at this rate.
Ive tried removing the old computer account from the old NT4 Domain, ive
also tried deleting and also tombstoning the WINS Records from the WINS
Servers for the machine in question.
Has anyone any ideas? is there a better way to do this part, or the
resolver
communication? I did think about moving everything over to DNS before
continuing, but i dont see why the current setup doesnt work.
.
- Prev by Date: Re: changing time zone on DC?
- Next by Date: Re: KCC error 1311 - Windows 2003 network
- Previous by thread: Re: changing time zone on DC?
- Next by thread: Re: Moving servers to new domain....
- Index(es):
Relevant Pages
|
