NT Domain Migration Problem

Recently, an issue occurred on our NT 4.0 Server that subsequently would not
allow it to boot. An ERD disk was inserted, which unknown to the
administrator, was from Jan 2000. This then caused a time warp to occur
after all of the settings were selected and run. There are about 35 clients
connected on this network. The operating systems range from Windows 98 to XP
Pro.

Once the problem with the server had been recognized, the C:\ drive was
reformatted and NT Server reinstalled. The name of the server was changed
but, the domain name was left in tact. As the client system were booted up
they could not connect to the new server to browse. The NetDom utility was
used but, was not successful. One by one all of the NT 4.0 Workstations and
Windows 2000 client systems were migrated to a Workgroup and then back to
the domain. Much to our dismay this created two new unforseen problems.

The first was that it created two new profiles. An example was in Windows
2000. In C:\Documents and Settings the profile folders for each client, for
exmple "Dale", were present before the incident. Afterward, it was noticed
the that a "Dale.(Domain Name)" and a "Dale.000.(Domain Name)" were created.
This meant that all of the settings, documents, desktop, Outlook eMail
settings, etc. were no longer available to the User. They had to be manually
moved to the new profile.

The second and more distressing problem was the Users rights. They no longer
have rights on there system to even open simple files that are local to
their hard drive. They get an error message that indicates that they do not
had "priviledges" to these items. I tried adding them to the local
Administrator's group on their individual systems but, without success.

I attempted to change the security settings individually on files and found
that it did work however, was very time consuming to go from folder to
folder, highlight all, right-click and change rights on them. I found that
the only thing that seemed to work was to add each user account into the
Domain Admins global group. This was not the way I had envisioned this.
Creating a huge domain security breach just to allow local access to simple
tasks.

Can anyone shed so light on what went wrong and more importantly, how to
repair the damage?

Dale

Hi Dale,

First, I want to know when you try to use the NetDom, what error you get?

I also want to know the following information.

1. How many servers in the network. 1 PDC and ? BDC?
2. Whether the server you formated is the PDC?
3. Why you change the server computer name?
4. You said that:

The name of the server was changed but, the domain name was left in tact.

I don't understand this.

Would you please answer these questions? I will continue to help you.

Thanks for using Microsoft News Group!

Sincerely,

Steven Liu

Microsoft Online Partner Support

MCSE 2000

Get Secure! ¨C www.microsoft.com/security

This posting is provided ¡°as is¡± with no warranties and confers no rights.
--------------------
| Reply-To: "Dale" <IGTeck RemoveThis @hotmail.com>
| From: "Dale" <IGTeck RemoveThis @hotmail.com>
| Subject: NT Domain Migration Problem
| Date: Sat, 30 Aug 2003 09:21:35 -0700
| Lines: 43
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <u6hB6MxbDHA.2372 RemoveThis @TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: adsl-67-122-232-126.dsl.scrm01.pacbell.net
67.122.232.126
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:3066
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Recently, an issue occurred on our NT 4.0 Server that subsequently would
not
| allow it to boot. An ERD disk was inserted, which unknown to the
| administrator, was from Jan 2000. This then caused a time warp to occur
| after all of the settings were selected and run. There are about 35
clients
| connected on this network. The operating systems range from Windows 98 to
XP
| Pro.
|
| Once the problem with the server had been recognized, the C:\ drive was
| reformatted and NT Server reinstalled. The name of the server was changed
| but, the domain name was left in tact. As the client system were booted up
| they could not connect to the new server to browse. The NetDom utility was
| used but, was not successful. One by one all of the NT 4.0 Workstations
and
| Windows 2000 client systems were migrated to a Workgroup and then back to
| the domain. Much to our dismay this created two new unforseen problems.
|
| The first was that it created two new profiles. An example was in Windows
| 2000. In C:\Documents and Settings the profile folders for each client,
for
| exmple "Dale", were present before the incident. Afterward, it was noticed
| the that a "Dale.(Domain Name)" and a "Dale.000.(Domain Name)" were
created.
| This meant that all of the settings, documents, desktop, Outlook eMail
| settings, etc. were no longer available to the User. They had to be
manually
| moved to the new profile.
|
| The second and more distressing problem was the Users rights. They no
longer
| have rights on there system to even open simple files that are local to
| their hard drive. They get an error message that indicates that they do
not
| had "priviledges" to these items. I tried adding them to the local
| Administrator's group on their individual systems but, without success.
|
| I attempted to change the security settings individually on files and
found
| that it did work however, was very time consuming to go from folder to
| folder, highlight all, right-click and change rights on them. I found that
| the only thing that seemed to work was to add each user account into the
| Domain Admins global group. This was not the way I had envisioned this.
| Creating a huge domain security breach just to allow local access to
simple
| tasks.
|
| Can anyone shed so light on what went wrong and more importantly, how to
| repair the damage?
|
| Dale
|
|
|