Domain rename under Windows Server 2008 R2

Posted on 2010-04-02
Medium Priority
Last Modified: 2012-08-13
What does the message "Failed to prepare pdc.olddomain.local : 5" mean when running "rendom /prepare" ?

This is the setup: There are several servers, all running as VMs under server 2008 R2 hosted hyper-V. All servers are running. There are two DCs (called pdc and bdc).

This is what I did:

on PDC, I created new forward lookup zone for newdomain.co.uk

I created another 2k8R2 server for the "control station" and added the Remote Server Admin Tools feature.

on the control station, copied Rendom.exe, Repadmin.exe, Dfsutil.exe, and Gpfixup.exe to a temporary folder, but running rendom from that folder gets "unable to load resource string 1067", so I followed the advice in http://is.gd/baa03 and run rendom by "c:\windows\system32\rendom ..."

"rendom /list" produces the expected xml file which I edited, changing three instances of "olddomain.local" to "newdomain.co.uk" and one (NetBIOS) of OLDDOMAIN to NEWDOMAIN.

"rendom /showforest" shows changes are correct and complete.

"rendom /upload" creates a dclist.xml which correctly contains both domain controllers

"rendom /prepare" then returns "Failed to prepare pdc.olddomain.local : 5". Retrying produces the same result again

I tried "c:\windows\system32\repadmin.exe /bind pdc.olddomain.local" (and bdc) as suggested by http://is.gd/baa03 - both succeed, but have no beneficial effect.

I do note that p.1055 of Minasi's "Mastering Windows Server 2008 R2" includes in prerequisites the need for a stand-alone DFS server which we don't have. But I haven't seen that prerequisite anywhere else including on Technet, so I'm far from sure that we need it.

So what am I meant to do with the rather unhelpful "Failed to prepare pdc.olddomain.local : 5"
Question by:peterpanic
  • 3
  • 2
LVL 49

Expert Comment

ID: 29490380
usually Error 5 is Access is Denied.

run net helpmsg 5 and you will see

did you run the cmd as administrator ?

Author Comment

ID: 29502348
Yes, logged in as, and therefore (presumably) running as, administrator.
LVL 49

Expert Comment

ID: 29502423
right click on command prompt and run-as administrator

Author Comment

ID: 29538853
Yes, I have tried running cmd.exe as administrator. No change - it still fails with identical results.

Accepted Solution

peterpanic earned 0 total points
ID: 32871928
I've given up and rebuilt the domain members from scratch

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
I’m willing to make a bet that your organization stores sensitive data in your Windows File Servers; files and folders that you really don’t want making it into the wrong hands.
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question