Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1014
  • Last Modified:

Domain Controller not working After P2V to LAB

Hello,
We have a strange scenario where we P2V'ed a domain controller to an isolated lab environment, after it was successfully migrated, i was able to log in the domain controller using my login name, but can't create any objects, nor can i join computers to that domain in that lab environment.

i seized the RID, PDC, Scheme master and domain naming master roles but still no good.
i'm getting - the directory service was unable to allocate a relative identifier

i'm suspecting that there's a problem with the RID, and saw some information on the web that i should clean all the remaining servers that the domain controller previously connected with (including all the sites) but i fail to understand if it's even related and if so, then why would it solve the problem?

the domain is 2003 native
0
johnnyjonathan
Asked:
johnnyjonathan
1 Solution
 
dphantom9002Commented:
until you clean the metadata of any other references to previous Domain Controllers, you will have problems with any number of AD relatded items including replication, RID generation and so forth.

http://technet.microsoft.com/en-us/library/cc736378(v=WS.10).aspx
0
 
Syed_M_UsmanSystem AdministratorCommented:
Dear,

1) could you please explain more "We have a strange scenario where we P2V'ed a domain controller to an isolated lab environment"

2) "was able to log in the domain controller using my login name, but can't create any objects" ideally only Domain Admin and Administrators users suppose to do this job.

3)"i seized the RID, PDC, Scheme master and domain naming master roles" why you seize the roles and how you have done this task..
YOur problem could be this, are you sure you have seized the roles properly???
what happened if you run below
start:run>cmd>netdom query fsmo
start:run>cmd>repadmin /showrepl
start:run>cmd>dcdiag

seizing roles should be done only when there is no chance that server will come live, many people like to restore systems stat on same hardware....


4) "i should clean all the remaining servers that the domain controller previously connected with (including all the sites)" you dont have to do this task unless you have failed DCPROMO or Faild DC in your network
0
 
johnnyjonathanAuthor Commented:
Thanks, got the idea of adding another DC from your answer!
cleaning up also works but it was easier :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now