RE: NT->AD2003 upgrade

Hello,

Thanks for posting!

From the post It appears that this should be a DNS issue. We have several
methods to seamlessly migrate DNS zones from a Windows 2000
server to Windows Server 2003. If the existing DNS zones are AD-integrated,
we can setup the AD-Integrated DNS zones on the new server directly as
these zones have been synchronized via AD replication. If the DNS zones are
primary, use either methods below:

Method 1: Zone Transfer

1.1) Create a secondary zone on the Windows Server 2003 system for the zone
on the existing 2000 DNS server.

1.2) Transfer the zone over to the Windows Server 2003 system

1.3) Change the secondary zone on the Windows Server 2003 system to a
Standard Primary Zone

Method 2. Copy the DNS zone file from the current DNS server:

2.1) Copy the DNS zone file (*.dns) from form the Windows 2000 DNS server
in the following location:

%SystemRoot%\system32\DNS

2.2) Put the *.dns file in the %SystemRoot%\system32\DNS folder on the
Windows Server 2003 system

2.3) Try to create a new primary zone by using the wizard. When you are
asked if you want to crate a new zone file, please select the radio box
"Use this existing file" and specify the file name.

Reference:

814591 HOW TO: Install and Configure DNS Server in Windows Server 2003
http://support.microsoft.com/?id=814591

Hope the information helps.

Best Regards,

Jason Tan

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: "Haim Beyhan" <haimb@xxxxxxxxxx>
| Subject: NT->AD2003 upgrade
| Date: Thu, 2 Mar 2006 17:58:53 +0200
| Lines: 63
| 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: <#Q$I2IhPGHA.1088@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: 192.115.235.2.static.012.net.il 192.115.235.2
| Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.windows.server.migration:22689
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hi,
|
| We're running an upgrade in test lab.
|
| Account domain:
| --------------------
| ACCDC1 (NT 4-PDC)
| ACCDC2 (NT4-BDC)
|
| Resource domain:
| ---------------------
| RESDC1 (NT4-PDC)
| RESDC2 (NT4-BDC)
| SRV1 (Windows 2003 Member)
| SRV2 (Windows 2000 Member-DNS server with 3 different domains. One of the
| domain is the name that I would like to use in AD and it's not secondary
dns
| in this site)
| CLN1 (Windows XP client)
|
| There is a one way trust between the domains.
|
| I have some problems:
|
| When running the AD wizard, I installed also DNS and let the wizard
| configure the dns. Actually I have some hosts on the old DNS server that
I
| will copy them to the new server. All the clients and servers (except the
| ACCDC1) have SRV2 dns server ip on their dns client. I put the ip of the
new
| dns server as a forwarder to the old dns in order for clients/servers to
| find the active directory.
|
| 1. After upgrading ACCDC1 to Windows 2003 and got AD up and running, the
| login script is not running when loging on SRV1 (Win 2003 server). I
don't
| have problems running the login scripts from SRV2 or CLN1.
|
| 2. Is it correct to put a forward ip to old dns for the new dns server?
All
| clients get ip from dhcp and they renew every 3 days.
| Do i have to force them to renew or is there a better way to do this?
|
| 3. I get the following message in the event viewer after loging on from
SRV1
| (windows 2003 machine)
|
| Error 1055
| Windows cannot determine computer name. (The specified domain either does
| not exist or could not be contacted). Group policy processing aborted.
|
| Error 1109
| CN=User1,CN=Users,DC=mydomain,DC=com from a different forest logged onto
| this machine. Cross forest group policy processing is disabled and
loopback
| processing has been enforced in this forest for this user account.
|
| 4. I have also Radius server running on ACCDC1 NT machine (before
upgrade)
| which authenticates Cisco vpn remote users to Cisco PIX. Will Radius work
| after the upgrade. The problem is that I cannot test it in real.
|
|
| What do they mean?
|
|
| Thanks,
|
| Haim Beyhan
|
|
|

.

Relevant Pages

  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 4515 :another copy of zone has been found
    ... running on the old 2000 server. ... I then installed DNS on ... I seem to remember hearing that if you just delete/remove the zone it ... Container), the Configuration Partition, and the Schema Partition. ...
    (microsoft.public.windows.server.dns)
  • Re: Replication between parent child domains
    ... install dns before i run the dcpromo on the melbourne server. ... DNS server will forward any query it can't answer, Checks zone ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication between parent child domains
    ... DNS server will forward any query it can't answer, Checks zone ... DNS Servers) all queries will go to tld DNS server (including Internet ... Stub zones: Stub zones contain a read-only copy with specific records ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)