IS this a DNS issue?

[Aze Isa]

-- Hi,
I have been receiving errors event ID: 4004; as well as ntfrs 13504, 13506,
13555, 13567.

But on one DC, when I go to command prompt and browse to the documents and
settings folder,
I get :
ADMINI~1~SER
Administrator.Server3

Why has the ~ appeared?
And the Domain name is not Server3, rather CONSARCDG.

On another DC, I have the correct one :
Administrator.CONSARCDG

Server3 does not exist on this domain which is the only domain we have.
By the way: does an error in DNS Event 5504 : he DNS server encountered an
invalid domain name in a packet from 66.197.0.3. The packet is rejected.

What is happening?
I would have sent you the DCDIAGS and the NETDIAGS logs but it is large.



Regards,
Aze Isa
email address: (e-mail address removed)

 

[Michael Johnston [MSFT]]

Potentially. Make sure that all machines in the AD point to the AD DNS server only. Make sure that the DNS server has the
forward lookup zone that matches that of the AD domain name and that this zone allows dynamic udpates. Open the
netlogon.dns file found in winnt\system32\config. Verify that each entry in this log exists in the DNS zone. The most important
key here is to make sure that the servers and clients do not point at any other DNS servers that are not part of your AD domain.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Aze Isa]

Hi Michael [Johnston], all machines point to this DNS server. It has the
forward lookup zone which matches the domain name and dynamic updates.
Nothing in the netlogon.dns to suggest that it's incorrect.

But this is what bugs me, which I think is the first thing I should
resolve. WHy do when I go to command prompt, I got:
C:\Documents and Settings\Administrator.Server3

the Domain name is not Server3, rather CONSARCDG.

Shouldn't I be seeing
C:\Documents and Settings\Administrator.CONSARCDG instead?

On another DC, I have the correct one :
C:\Documents and Settings\Administrator.CONSARCDG

Please help


--

Potentially. Make sure that all machines in the AD point to the AD DNS

server only. Make sure that the DNS server has the

forward lookup zone that matches that of the AD domain name and that this

zone allows dynamic udpates. Open the

netlogon.dns file found in winnt\system32\config. Verify that each entry

in this log exists in the DNS zone. The most important

key here is to make sure that the servers and clients do not point at any

other DNS servers that are not part of your AD domain.

Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the

terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from

 

[Ace Fekay [MVP]]

In

Hi Michael [Johnston], all machines point to this DNS server. It has
the forward lookup zone which matches the domain name and dynamic
updates. Nothing in the netlogon.dns to suggest that it's incorrect.

But this is what bugs me, which I think is the first thing I should
resolve. WHy do when I go to command prompt, I got:
C:\Documents and Settings\Administrator.Server3

the Domain name is not Server3, rather CONSARCDG.

Shouldn't I be seeing
C:\Documents and Settings\Administrator.CONSARCDG instead?

On another DC, I have the correct one :
C:\Documents and Settings\Administrator.CONSARCDG

Please help

That is really not a DNS issue. It's normal for the servername to be the
suffix of your profile, after all, that;s the server name. If the domain
name popped up, probably due to an upgrade?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

This servername is SERVER-2, not SERVER3. So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

--

"Ace Fekay [MVP]"
message In

Hi Michael [Johnston], all machines point to this DNS server. It has
the forward lookup zone which matches the domain name and dynamic
updates. Nothing in the netlogon.dns to suggest that it's incorrect.

But this is what bugs me, which I think is the first thing I should
resolve. WHy do when I go to command prompt, I got:
C:\Documents and Settings\Administrator.Server3

the Domain name is not Server3, rather CONSARCDG.

Shouldn't I be seeing
C:\Documents and Settings\Administrator.CONSARCDG instead?

On another DC, I have the correct one :
C:\Documents and Settings\Administrator.CONSARCDG

Please help

That is really not a DNS issue. It's normal for the servername to be the
suffix of your profile, after all, that;s the server name. If the domain
name popped up, probably due to an upgrade?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

This servername is SERVER-2, not SERVER3.

I was just reciting what you posted when I mentioned server3.

So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

Then not really sure. Maybe the machine was renamed after installation?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

This server-2 has never been renamed since its first installation from
scratch.
I was addressing this problem because I suspect that replication stopped and
ntfrs errors were showing. Although, it was replicating fine initially.
The system is Windows 2000 Advanced Server SP4 on SERVER-2

Any ideas?

--

"Ace Fekay [MVP]"
message

This servername is SERVER-2, not SERVER3.

I was just reciting what you posted when I mentioned server3.

So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

Then not really sure. Maybe the machine was renamed after installation?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

Sorry for the word "suspect". It's not meant to be there. The replication
had stopped completely.

--

This server-2 has never been renamed since its first installation from
scratch.
I was addressing this problem because I suspect that replication stopped and
ntfrs errors were showing. Although, it was replicating fine initially.
The system is Windows 2000 Advanced Server SP4 on SERVER-2

Any ideas?

--

"Ace Fekay [MVP]"
message

This servername is SERVER-2, not SERVER3.

I was just reciting what you posted when I mentioned server3.

So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

Then not really sure. Maybe the machine was renamed after installation?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

I think we got off track with that profile folder name, which has NOTHING to
do with replication problems that you are now stating that is occuring.

Now you are saying there are replication issues?
Event ID 4004 :
http://www.eventid.net/display.asp?eventid=4004&source=

I'm assuming this is occuring at boot time. This can occur if your zones are
AD Integrated. This means the zone is stored in the actual physical AD
database and not as a text file in the system32\dns folder, where Primary
and secondary zone files are kept as text files (.dns files). The error
normally occurs at startup due to the AD database has not quite finished
intializing when the Netlogon service attempts to register the data into the
zone. If you want to fix that and you have two DNS servers that are both DCs
and both have AD Integrated zones, follow that article:
=========================
If you have 2 DC/DNS servers, to avoid this error, make sure you have the
following under IP properties:
DC1:
First DNS address points to DC2.
Second DNS address points to itself.
DC2:
First DNS address points to DC1.
Second DNS address points to itself.
=========================

This will ensure that it is registering into the other DC/DNS first and not
itself.

As far as these errors:
13504, 13506, 13555, 13567.
They are replication errors, which are usually based on some other aspect,
more than likely in your case DNS. The 5504 error is normally based on a bad
forwarder. You can change the forwarder. Use 4.2.2.2, which is proven to
work.

If you followed Michael's suggestions to ENSURE that all internal machines
(DCs and clients) only point to your internal DNS ONLY, many errors will go
away in respect to AD (including replication). If you are using an ISP's
DFNS server in your IP properties, then many many many errors WILL occur.

If the above is clean, for I don;'t know since I do not of your
configuration, then my only other suggestion for replication is that the SRV
records do not exist (not registering?) or are corrupted. If you are using
SP4, and if you have a SINGLE LABEL AD DNS DOMAIN NAME, then I can see why
the errors are occuring.

Do us a favor and let us know of your configuration by posting:

1. An unedited ipconfig /all
2. The actual AD DNS domain name as it shows up in the ADUC console.
3. Updates set to at least yes?
4. What forwarder are you using.

This info will give us a 98% shot at giving you the answer after posting it,
otherwise at this point we will be guessing. Please try not to edit the
ipconfig, or that leads to guessing too.

Thanks


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Sorry for the word "suspect". It's not meant to be there. The replication
had stopped completely.

--

This server-2 has never been renamed since its first installation from
scratch.
I was addressing this problem because I suspect that replication stopped and
ntfrs errors were showing. Although, it was replicating fine initially.
The system is Windows 2000 Advanced Server SP4 on SERVER-2

Any ideas?

--

"Ace Fekay [MVP]"
message

This servername is SERVER-2, not SERVER3.

I was just reciting what you posted when I mentioned server3.

So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

Then not really sure. Maybe the machine was renamed after installation?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

Hi, Ace,

1. Please find below the IPCONFIG/ALL unedited.
2. Also, the AD DNS name in the ADUC is CONSARCDG (single label- I'm
afraid).
3. Updates set to dynamic updates (yes).
4. There are no forwarders set. This had never been set to anything and
replication was fine. Anything to upset this?
5.By the way BDC is a domain controller and not an NT4 machine. SERVER-2 is
with address 192.0.0.2 and BDC is 192.0.0.6 . Michael's advice was already
implemented way before your last posting.
6. You mentioned that if I were using SP4 (yes), and if I have a single
label AD DNS domai name (yes), then you can see why the errors are
occurring.
Since both conditions are met, what are occurring, and what to do next ?
Thanx ,
Aze



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : SERVER-2
Primary DNS Suffix . . . . . . . : CONSARCDG
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : CONSARCDG

Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 Network Connection
Physical Address. . . . . . . . . : 00-B0-D0-FC-47-D2

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.0.0.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.0.0.9

DNS Servers . . . . . . . . . . . : 192.0.0.6
192.0.0.2
----------------------------
--

"Ace Fekay [MVP]"
message I think we got off track with that profile folder name, which has NOTHING to
do with replication problems that you are now stating that is occuring.

Now you are saying there are replication issues?
Event ID 4004 :
http://www.eventid.net/display.asp?eventid=4004&source=

I'm assuming this is occuring at boot time. This can occur if your zones are
AD Integrated. This means the zone is stored in the actual physical AD
database and not as a text file in the system32\dns folder, where Primary
and secondary zone files are kept as text files (.dns files). The error
normally occurs at startup due to the AD database has not quite finished
intializing when the Netlogon service attempts to register the data into the
zone. If you want to fix that and you have two DNS servers that are both DCs
and both have AD Integrated zones, follow that article:
=========================
If you have 2 DC/DNS servers, to avoid this error, make sure you have the
following under IP properties:
DC1:
First DNS address points to DC2.
Second DNS address points to itself.
DC2:
First DNS address points to DC1.
Second DNS address points to itself.
=========================

This will ensure that it is registering into the other DC/DNS first and not
itself.

As far as these errors:
13504, 13506, 13555, 13567.
They are replication errors, which are usually based on some other aspect,
more than likely in your case DNS. The 5504 error is normally based on a bad
forwarder. You can change the forwarder. Use 4.2.2.2, which is proven to
work.

If you followed Michael's suggestions to ENSURE that all internal machines
(DCs and clients) only point to your internal DNS ONLY, many errors will go
away in respect to AD (including replication). If you are using an ISP's
DFNS server in your IP properties, then many many many errors WILL occur.

If the above is clean, for I don;'t know since I do not of your
configuration, then my only other suggestion for replication is that the SRV
records do not exist (not registering?) or are corrupted. If you are using
SP4, and if you have a SINGLE LABEL AD DNS DOMAIN NAME, then I can see why
the errors are occuring.

Do us a favor and let us know of your configuration by posting:

1. An unedited ipconfig /all
2. The actual AD DNS domain name as it shows up in the ADUC console.
3. Updates set to at least yes?
4. What forwarder are you using.

This info will give us a 98% shot at giving you the answer after posting it,
otherwise at this point we will be guessing. Please try not to edit the
ipconfig, or that leads to guessing too.

Thanks


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Sorry for the word "suspect". It's not meant to be there. The replication
had stopped completely.

--

This server-2 has never been renamed since its first installation from
scratch.
I was addressing this problem because I suspect that replication stopped and
ntfrs errors were showing. Although, it was replicating fine initially.
The system is Windows 2000 Advanced Server SP4 on SERVER-2

Any ideas?

--

"Ace Fekay [MVP]"
message

This servername is SERVER-2, not SERVER3.

I was just reciting what you posted when I mentioned server3.

So where did this come from?
This has not been upgraded from NT4 box. It was installed direct [fresh]
from the w2K CD (Advanced Server 2000).

Then not really sure. Maybe the machine was renamed after installation?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Kevin D. Goodknecht [MVP]]

In

Hi, Ace,

1. Please find below the IPCONFIG/ALL unedited.
2. Also, the AD DNS name in the ADUC is CONSARCDG (single label- I'm
afraid).
3. Updates set to dynamic updates (yes).
4. There are no forwarders set. This had never been set to anything
and replication was fine. Anything to upset this?
5.By the way BDC is a domain controller and not an NT4 machine.
SERVER-2 is with address 192.0.0.2 and BDC is 192.0.0.6 . Michael's
advice was already implemented way before your last posting.
6. You mentioned that if I were using SP4 (yes), and if I have a
single label AD DNS domai name (yes), then you can see why the errors
are occurring.
Since both conditions are met, what are occurring, and what to do
next ? Thanx ,
Aze



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : SERVER-2
Primary DNS Suffix . . . . . . . : CONSARCDG
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : CONSARCDG

Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 Network
Connection Physical Address. . . . . . . . . : 00-B0-D0-FC-47-D2

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.0.0.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.0.0.9

DNS Servers . . . . . . . . . . . : 192.0.0.6
192.0.0.2

This will help you use regedt32 to add the entries from this
article.300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

 

[Ace Fekay [MVP]]

In

This will help you use regedt32 to add the entries from this
article.300684 - Information About Configuring Windows 2000 for
Domains with Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

OUCH. Had a feeling is was a single label name issue. Hope no XP clients.
They have problems with DNS resolution of single label names. Unfortunately,
the best way is to reinstall the system with the correct name and all this
goes away.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

Ouch indeed. Lots and lots of XP clients.
Any ideas on preserving users and profiles while reinstalling the system?

To change the Domain name:
I think I have some idea to do this (bar the screams I'll hear from other
users).
Demote BDC, install NT4 (SP6a) as domain controller. Then demote SERVER-2.
NT4 box seize to become PDC. Disconnect BDC and SERVER-2.
Promote NT4 to Windows 2000, changing to CONSARCDG.COM. Promote SERVER-2 and
BDC to CONSARCDG.COM, Take NT4 out (dcpromo).
The sequence sounds dubious. Any help?

--

"Ace Fekay [MVP]"
message In

This will help you use regedt32 to add the entries from this
article.300684 - Information About Configuring Windows 2000 for
Domains with Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

OUCH. Had a feeling is was a single label name issue. Hope no XP clients.
They have problems with DNS resolution of single label names. Unfortunately,
the best way is to reinstall the system with the correct name and all this
goes away.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Kevin D. Goodknecht [MVP]]

In

Ouch indeed. Lots and lots of XP clients.
Any ideas on preserving users and profiles while reinstalling the
system?

To change the Domain name:
I think I have some idea to do this (bar the screams I'll hear from
other users).
Demote BDC, install NT4 (SP6a) as domain controller. Then demote
SERVER-2. NT4 box seize to become PDC. Disconnect BDC and SERVER-2.
Promote NT4 to Windows 2000, changing to CONSARCDG.COM. Promote
SERVER-2 and BDC to CONSARCDG.COM, Take NT4 out (dcpromo).
The sequence sounds dubious. Any help?

That is pretty much the sequence, actually the is a KB article wrote that
tells you exactly how to do this.
292541 - How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;292541&FR=1

 

[Aze Isa]

Hi guys, before doing this, I am going to try something which I did before,
and was successful.Although in the long run, I agree that the single label
name cannot be sustained. I'll keep you posted as well.

This will take some time though.

--

In

Ouch indeed. Lots and lots of XP clients.
Any ideas on preserving users and profiles while reinstalling the
system?

To change the Domain name:
I think I have some idea to do this (bar the screams I'll hear from
other users).
Demote BDC, install NT4 (SP6a) as domain controller. Then demote
SERVER-2. NT4 box seize to become PDC. Disconnect BDC and SERVER-2.
Promote NT4 to Windows 2000, changing to CONSARCDG.COM. Promote
SERVER-2 and BDC to CONSARCDG.COM, Take NT4 out (dcpromo).
The sequence sounds dubious. Any help?

That is pretty much the sequence, actually the is a KB article wrote that
tells you exactly how to do this.
292541 - How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;292541&FR=1

 

[Ace Fekay [MVP]]

In

Hi guys, before doing this, I am going to try something which I did
before, and was successful.Although in the long run, I agree that the
single label name cannot be sustained. I'll keep you posted as well.

This will take some time though.

--

In

That is pretty much the sequence, actually the is a KB article wrote
that tells you exactly how to do this.
292541 - How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;292541&FR=1

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================

You could install a brand new domain from scratch on an extra server. Then
use the ADMT tool to migrate all the user accounts, groups and machines.
During machine account migration, it will translate the security settings so
the users can continue to use their old profiles. Works like a charm. Then
kill the old server or demote it, then add it in as a replica DC in the new
domain, and either retire the other server, or just keep it online.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

Hi Ace,
I don't mean to question your know-how. But have you done this ? Because
this sounds downright risky, what with hundreds of users who requires it
days and nights. If you really have, then can you send me a detailed proc?
Or is that too much to ask.

Again,
lots of apologies for asking this sort of questions.
Aze

--

"Ace Fekay [MVP]"
message In

Hi guys, before doing this, I am going to try something which I did
before, and was successful.Although in the long run, I agree that the
single label name cannot be sustained. I'll keep you posted as well.

This will take some time though.

--

In

That is pretty much the sequence, actually the is a KB article wrote
that tells you exactly how to do this.
292541 - How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;292541&FR=1

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================

You could install a brand new domain from scratch on an extra server. Then
use the ADMT tool to migrate all the user accounts, groups and machines.
During machine account migration, it will translate the security settings so
the users can continue to use their old profiles. Works like a charm. Then
kill the old server or demote it, then add it in as a replica DC in the new
domain, and either retire the other server, or just keep it online.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

Read below...

Hi Ace,
I don't mean to question your know-how. But have you done this ?

Yes, many times.

Because
this sounds downright risky, what with hundreds of users who requires it
days and nights. If you really have, then can you send me a detailed proc?
Or is that too much to ask.

I don;t have it detailed in doc, just in my head. But you can read up on the
ADMT tool and how it works and use that as the basis to make it happen. Use
ADMT v2.0. If reluctant or not sure, I would highly recommend to hire a
competent consultant that can prove to you he/she has done this in the past
and knows what they are doing.

Active Directory Migration Tool Overview:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/downloads/admtool.asp

Download details Active Directory Migration Tool v.2.0:
http://microsoft.com/downloads/deta...b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

Domain Migration Cookbook - Index and Cover:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.asp

260871 - HOW TO Set Up ADMT for Windows NT 4.0 to Windows 2000 Migration
(this also works for W2k to W2k or W2k to W2k3 or W2k3 to W2k3)
http://support.microsoft.com/default.aspx?scid=KB;en-us;260871&

325851 - HOW TO Set Up ADMT for a Windows NT 4.0-to-Windows .NET Server
Migration:
http://support.microsoft.com/default.aspx?scid=KB;en-us;325851&


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Aze Isa]

That's excellent news. Will follow up what is here then.
By the way I'll be away on urgent errands, and i'll be back early January
next year. Merry Xmas and a great new year.

--

"Ace Fekay [MVP]"
message Read below...

Hi Ace,
I don't mean to question your know-how. But have you done this ?

Yes, many times.

Because
this sounds downright risky, what with hundreds of users who requires it
days and nights. If you really have, then can you send me a detailed proc?
Or is that too much to ask.

I don;t have it detailed in doc, just in my head. But you can read up on the
ADMT tool and how it works and use that as the basis to make it happen. Use
ADMT v2.0. If reluctant or not sure, I would highly recommend to hire a
competent consultant that can prove to you he/she has done this in the past
and knows what they are doing.

Active Directory Migration Tool Overview:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/downloads/admtool.asp

Download details Active Directory Migration Tool v.2.0:
http://microsoft.com/downloads/deta...b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

Domain Migration Cookbook - Index and Cover:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.asp

260871 - HOW TO Set Up ADMT for Windows NT 4.0 to Windows 2000 Migration
(this also works for W2k to W2k or W2k to W2k3 or W2k3 to W2k3)
http://support.microsoft.com/default.aspx?scid=KB;en-us;260871&

325851 - HOW TO Set Up ADMT for a Windows NT 4.0-to-Windows .NET Server
Migration:
http://support.microsoft.com/default.aspx?scid=KB;en-us;325851&


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

That's excellent news. Will follow up what is here then.
By the way I'll be away on urgent errands, and i'll be back early January
next year. Merry Xmas and a great new year.

--

Thanks, and the same to you and your family!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory