You can actually run with only one domain controller in a child partition
and the parent is joined to the domain. On start up the parent will use
cached credentials. You need to set the child DC to start up before any
other children. There are other considerations as well. See Option 4 and
some of the comments in the following blog. http://blogs.msdn.com/virtual_pc_guy...r-dilemma.aspx
It's obviously not an optimum situation and may not be something you want to
put into production. I have done this a few times while testing and for
demos. I've had a child DC with the parent joined to the domain and managed
by SCVVM also running as a child. You have to play with the timing that the
children start up with. You have to do a bit of testing to see how long it
takes the DC to start up then set the children to delay for at least this
long. Depending on your hardware it may take ten minutes or so to get
everything up and running from a cold boot. Updates can be a problem as this
may delay the startup of the DC. I've found it best to update in this
order - child DC first, parent, then the rest of the children.
MS-MVP - Windows Desktop Experience: Systems Administration http://www.vistahelp.ca/phpBB2/
"Shannon" <Shannon@xxxxxx> wrote in message
> It appears that you need your host machines in the domain in order to get
> any use out of SCVMM '08. This is a home configuration and I've only got
> machines to play with and don't want to add a third one as a domain
> controller so here's the scenario I'm considering and will it work?
> Install a domain controller as a VM on host machine B. Add host machine A
> to the domain. Install a domain controller as a VM on host machine A.
> host machine B to the domain.
> In my head it seems like it will work but I'm wondering if I'll have any
> unusual auth problems due to the fact that the host OS will boot long
> the DC VM.