Hence the "if at all possible" in my query :-)
-----Original Message----- From: Michael Leone [mailto:[email protected]] Sent: Friday, October 02, 2009 9:29 AM To: NT System Admin Issues Subject: Re: Seizing roles in a parent/child domain On Fri, Oct 2, 2009 at 12:18 PM, Free, Bob <[email protected]> wrote: > Correct. I assume you are aware you should always transfer if at all > possible vs seize? Actually, not in this scenario. I have created a virtual domain using ESX, and have 1 DC for the parent, and 1 DC for the child, in this virtual domain. The DCs are virtual. There are no FSMO role holders to transfer from, as the FSMO role holders are all physical servers in my production environment. In effect, I am emulating a D/R situation, where all I have are virtual DCs, that hold no roles. I need to seize all roles, so the domains become functional. Then I can continue on with my testing, etc. When I'm done and seized all roles, and cleaned out the metadata, I should end up with a virtual copy of my parent/child domain config, which I can then test upgrading, etc. Like creating a test lab version of my production environment. Yes, I would transfer if I could. :-) ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
