Basically,...you are just plain screwed.
You can go against Corp Policy and create a whole new Domain in a whole new
Forest,...start from scratch and do what you want with it,...but that may
not be good for your future employment.
The other approach, ...that probably won't get you fired,... is to go
"above" the Corp IT Staff to the people that they have to answer to and
present your complaints to them.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Mr. JYC" <(E-Mail Removed)> wrote in message
news:9E831B5A-B2DA-4FAA-AF70-(E-Mail Removed)...
> Hello,
>
> What options are there if we are a child domain and we want to control the
> child domain independently from the parent i.e. blocking domain wide
> policies, controlling our own child domain, OUs, and GPOs, and blocking
> the
> ability for the parent to manage objects in the child domain? We have a
> situation where we are convinced that the administrators of the parent
> domain
> don't really know what they are doing. Consequently, we want to
> administer
> our child domain more effectively than the parent.
> --
> Thank you for your help!
> JYC