Re: Inplace Upgrade

Dump a list of your workstations, and then have a script loop through that
list and remotely update the DNS settings:
http://www.microsoft.com/technet/scriptcenter/scripts/network/client/modify/nwmovb20.mspx?mfr=true

--
Hunter

"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BA4D1770-C387-4502-8F52-E3B5DFEE31A2@xxxxxxxxxxxxxxxx
I found an article if I use the NT4EMulator in the registry before the
inplace upgrade on the PDC server. Then it will hide the AD information
and
will make the 2003 DC act like NT4 server. So basically if XP or win2000
login to the network will not see DC on the network and it will login
similar
when it was NT 4.0 environment. The reason I want to do it because it will
take a long time to track down the pc. I am trying to avoid the long delay
login before I change the DNS setting on each pc.
I really appreciate for giving information.

Thx.

"Danny Sanders" wrote:

NT 4.0 clients and earlier will WINS. XP and Win 2k clients MUST use a
DNS
server set up for the AD domain, if not there will be long log in times,
most everything to do with AD will not work, like group policy etc.

I would devise a plan to get your clients pointed to the right DNS server
before going to AD.

hth
DDS W 2k MVP MCSE


"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:48A9F8AE-283F-4579-8552-60CA58B13E56@xxxxxxxxxxxxxxxx
The environment is NT 4.0 PDC after upgrading the PDC to the Windows
2003
DC,
do I have to right away change the DNS settings for the workstation to
the
internal DNS that points to the AD DNS. The clients all have the
Workstation
using static Ip and Static dns and DHCP server is not available.

Will the existing NT workstation and Windows xp clients able to resolve
the
AD DC using the existing Wins from the PDC environment. I am planning
to
run
the DC in mixed mode environment where both the NT and 2003 server will
allow
authentication. The reason I cannot change the DNS settings on clients
because there are so many and we don't know the exact locations.

I really apprecaite for your help...





.

Relevant Pages

  • Re: cant connect using conect computer command
    ... What DNS settings are you changing on the clients? ... Windows Small Business Server ... > on the server i can see the files and in iis the default webpage is all ...
    (microsoft.public.windows.server.sbs)
  • Re: error trying to join domain
    ... Check the DNS settings on the problem workstation - it should be using the ... domain's DNS server for name resolution and no others. ... > I can ping the server name with no problem, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Slow login to a Win 2003 domain
    ... >>> of user logins at the clients. ... >>> the personal settings. ... > Check out your DNS settings. ... Your server should be configured to point ...
    (microsoft.public.windows.server.general)
  • Re: XP Pro cannot join AD Domain
    ... You DNS settings on the clients must be pointed to the DNS server hosting ... > When i try to join domain I get: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cannot browse DCs
    ... What's about the DNS settings from your clients? ... Did you change them to the new DNS server and also check all the server DNS settings? ... admin password does not give any joy. ...
    (microsoft.public.windows.server.active_directory)
Loading