Windows Server

csamuels

we have a small business currently hosting a nt 4.0 domain with 4.0 PDC & BDC, 2000 member servers, and 2003 member servers. Our clients are 98, 2000, xp. We decided to try to perform an in place upgrade of our domain to 2003. Our old domain name was FS_IMAGE and we want to change it to fmfic.com

Here's the actions we performed.

1. Imaged the PDC for fail-safe.

2. Shutdown the BDC.

3. Upgraded the PDC to Server 2003

4. Dcpromo'd the old PDC as forest root
4a. FQDN for the domain was set to fmfic.com
4b. Set function level as Windows 2000 interim
4c. Allowed pre Windows 2000 permissions
4d. Let dcpromo install and configure DNS

5. Login to a 2000 and xp workstation
5a. The domain in system properties network id tab was automatically changed to fmfic.com

5b. Ctrl Alt Del info still showed user as FS_IMAGE\user

5c. We can still access our main application server hosted on a 2k3 member server.

6. We reboot the application server to recogize the domain change.
6a. Domain name auto changed after login just like the wksts

7. We can no longer access shares on our applaication server.

7a. Access is denied using old and new credentials. fs_image\user, fmfic.com\user, user@fmfic.com, user.

environmental varable userdomain is still set to old domain name

I checked AD's Users & computers. All users and computers were there. I tried resetting the imagergt computer account in AD and rebooting the server but same results. I tried bringing the BDC back online; same results.

Locally on the server, the domain doesn't show for a location when trying to set user permissions. However, in AD on a DC, the domain would show.

Sooooooo, what went wrong here? We're thinking maybe we should have kept our old domain name when we dcpromo'd our upgraded server and then performed a domain name change. But our old domain name could have caused conflict or error because it contains a underscore, FS_IMAGE.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1