Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Rendom /upload Error

1,957 views
Skip to first unread message

S Sainsbury

unread,
Feb 3, 2009, 9:31:01 AM2/3/09
to
I have a test lab which I am using to test a domain rename.

The domain is simple, its a single domain in a single forest and I am
changing the domain from "site.company.com" to "company.com".

I am following the step by step guide from MS but when I go to to the step
where you upload the xml file to generate the instructions an error appears
as follows...

"Failed to upload Dns Root alias on the DN:
CN=3570e6d7-b70e-422b-86b1-5c51bd91c4ba,
CN=Partitions,CN=Configuration,DC=site,DC=company,DC=com, on host "ServerFQDN"
000021A2: SvcErr: DSID-030A09F3, problem 5001 (BUSY), data 0:
The requested resource is in use."

I have searched online and followed various recommendations such as
clearning meta data etc, to no avail.

The domain controllers are clones of the original and the test lab includes
two DC's (with fsmo) one Exchange Server, Member servers and PC's. 1 domain
controller in the live infrastructure is not present in the test lab, but it
is simply an additional server and does not hold any roles.

A previous test worked without issue, however it did not include an exchange
server.

Can anyone help with this?

Meinolf Weber [MVP-DS]

unread,
Feb 3, 2009, 9:52:33 AM2/3/09
to

Hello S,

All domain controllers have to be online as far as i know, so this can be
the reason, because you said one is not in the test lab available. SO either
i would cleanup the AD database in the test lab or also create it in the lab.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Jorge Silva

unread,
Feb 3, 2009, 12:36:24 PM2/3/09
to
Hi
-Is exchange installed on a DC "This isn't supported"?
-Ho is the "3570e6d7-b70e-422b-86b1-5c51bd91c4ba"

http://www.msexchange.org/tutorials/Domain-Rename.html
--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup


This posting is provided "AS IS" with no warranties, and confers no rights.

"S Sainsbury" <SSain...@discussions.microsoft.com> wrote in message
news:C9A6956C-4560-4919...@microsoft.com...

S Sainsbury

unread,
Feb 3, 2009, 12:41:02 PM2/3/09
to
I have seen that mentioned on other posts, however the MS instructions say
you can do a rename with offline DC's. The original test lab where the
procedure worked had only 1 out of 3 domain controllers present and that
seemed to work.

However I removed the offline DC's from active directory in the test lab and
ran the meta data cleanup to remove all trace but the same error was returned
when I tried the rename.

I have now restored the test lab to its original state and have tried again
but still no joy.

Unfortunately I have to do a live rename a.s.a.p in order to create new sub
domains for other sites joining our network and im loathed to do that without
a successful test.

Thanks for your help.

Meinolf Weber [MVP-DS]

unread,
Feb 4, 2009, 2:50:25 AM2/4/09
to

Meinolf Weber [MVP-DS]

unread,
Feb 4, 2009, 2:52:03 AM2/4/09
to

S Sainsbury

unread,
Feb 4, 2009, 6:20:05 AM2/4/09
to
Thanks for your help.

I had a look through the various articles but dont think they apply as they
relate to processes that are further along the rename procedure.

Im aware of the exchange fixup tool, however I am not at that point in the
process as yet as that procedure is performed after the initial domain rename
as far as im aware.

Exchange is installed on a dedicated member server.

I am only at the point of doing rendom /upload

Im going to try doing a clone of the missing domain controller to see if
that changes the situation when in the test lab.

S Sainsbury

unread,
Feb 11, 2009, 11:41:00 AM2/11/09
to
I managed to resolve this issue and the cause was quite simple but not obvious.

Because this was a virtual test lab the virtual domain controller still had
details of the physical servers NIC and this NIC had the various AD bindings.

Removing the non present NIC resolved the issue, I suspect this may be a
consideration for others attempting a virutal lab.

Jorge Silva

unread,
Feb 11, 2009, 1:32:46 PM2/11/09
to
Glad that you solved.
Thanks for the feedback.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"S Sainsbury" <SSain...@discussions.microsoft.com> wrote in message

news:3C70CD12-A820-4BF6...@microsoft.com...

0 new messages