Annoyances.org
Home » Windows Server 2003 Discussion Forum » Message 1239437050 » Entire Thread Search | Help | Home
  
Windows 2003 std migrate to Windows 2003 R2 problem
Showing all messages in thread #1239437050
Windows Server 2003 Annoyances Discussion Forum


The following are all of the messages in this thread (2 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
Windows 2003 std migrate to Windows 2003 R2 problem
Saturday, April 11, 2009 at 1:04 am
Posted by leiw (1 messages posted)

Hello, I having old Windows 2003 std migrate to new Windows 2003 R2 problem. I was successfully done migration from old std to new R2 2 month ago using join existing domain and then transfer FSMO method. But the new R2 recently had hardware failed. So I used FSMO method transfer back to old std. Now the new R2 hardware repaired and then using FSMO method again transfer to new R2 but it shown following message when join existing domain: The operation failed because: This Active Directory installation requires domain configuration changes, but whether these changes have been made on the domain controller server1.btt.local is undetermined. The installation process has quit. I performed a Dcdiag tool to test FSMO but it has error as follow: Running enterprise tests on : btt.local Starting test: Intersite ......................... btt.local passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. ......................... btt.local failed test FsmoCheck Old Windows 2003 already run ADPre.exe /forestprep and /domainprep, both server are R2 and R2 DNS to old std. I don't know what I can do now ! Please help.

[Reply or follow-up to this message]

Tip: Run a free scan for common Windows errors ad

re: Windows 2003 std migrate to Windows 2003 R2 problem
Thursday, May 7, 2009 at 7:43 am
Posted by appleoddity (2369 messages posted)

The unable to contact PDC error looks like a DNS problem. The machine that you are running the dcdiag on is unable to locate a DNS entry for your domain name. This suggests that your DNS settings are incorrect. They DNS settings need to point to a DNS server that is hosting that domain (probably located on the old server, so the DNS server address on the new server should be set to the IP address of the old server for now).

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows Server 2003 Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.