I'm currently working on a SharePoint development project and I'm trying to build my development environment. All of our servers are Server 2012 R2 (which I love). For the virtualization, Hyper-V 2012 R2 is in place (which I don't love so much; I'm a VMware person, but I try to keep an open mind.) The client that I work for (internal) has a System Admin who has been reluctant up to this point to allow me any type of domain access to the environment so that I can construct my servers and apps as needed. I respect that because I've only been with them a few months and people's level of comfortability varies.
Here's my challenge. I was trying to determine a way that I could have "isolated" domain admin access without threatening their production environment. My first thought was that if a child domain was constructed (my DEV section given an OU of DEV), then I thought it would be possible to limit my domain admin access to that child domain specifically. I thought that it would not be forced to inherit access permissions from the parent. When I submitted that idea, I was informed that even in a child domain, I wouldn't have permissions on the hypervisor; as they're in the parent and they don't have any additional hypervisor boxes.
I'm not sure that I'm following his logic here. He may be correct but it sounds like we're talking about two separate things. Rather than lose any more sleep trying to untangle my confusion, I decided to put the question to you....
Is it possible to establish a child domain within a Windows Server 2012 R2 forest (which is on Hyper-V 2012 R2) and not have admin access to the parent domain?
I thank you in advance for your help in this. I feel like it's Monday and my brain is Jello. I apologize for the noob question.