I would have the PDC emulator in the root domain of the forest a phsycal
server. Other DCs will get their time from it at startup.
I would have at least 1 DC in each domain in your forest as a physical
server housing DNS. This way if you ever had to shut down your virtual
enviorment, having a physical DNS server that you can start up before your
virtual servers would significantly speed up the process, especially if
Exchange is involved, there is no reason that these DNS DCs in each domain
can't be the PDC emulator also.
hth
DDS
"Kimpsu" <Kimpsu@xxxxxx> wrote in message
news:39BB322B-3DE1-4B39-B7FF-24D114BF43FA@xxxxxx
Quote:
> But since it is basically paused for that 10 seconds or so, it's clock etc
> don't run for that time. How does it address this issue, or does it sync
> the
> clock after resuming it on the other machine?
>
> Since syncing the clock with the host is not recommended for domain
> controllers anyway, the possible difference in the clock between the DC
> and
> possibly the two Hyper-V hosts the machine is migrated from and to should
> not
> affect the DC, but the DC (and often DNS, perhaps DHCP and WINS too) does
> lose 10 seconds. And I was wondering if it would perhaps sync data with
> other
> DCs wrong after this migration.
>
>
> "Danny Sanders" wrote:
> Quote:
Quote:
>> > Hi!
>> >
>> > I have understood that running active directory domain controllers is
>> > supported by MS when run with their own virtualization solutions. What
>> > I
>> > would like to know is how about when having multiple domain controllers
>> > and
>> > using Hyper-V quick migration? It saves the state of the VM, moves it
>> > to
>> > another host, and then resumes it.
>> >
>> > Does this result in data synchronization issues between domain
>> > controllers?
>>
>>
>> The domain controllers are designed to be able to work and recover from a
>> DC
>> being out for a period of time without affecting replication. This is not
>> any different from rebooting the DC or turning it off over a weekend
>> because
>> the building is having power issues and turning the DC on again on Monday
>> morning.
>>
>>
>> hth
>> DDS
>> "Kimpsu" <Kimpsu@xxxxxx> wrote in message
>> news:5A2062AF-80BE-45F5-8BDB-198EC7A032DD@xxxxxx Quote:
>> > Hi!
>> >
>> > I have understood that running active directory domain controllers is
>> > supported by MS when run with their own virtualization solutions. What
>> > I
>> > would like to know is how about when having multiple domain controllers
>> > and
>> > using Hyper-V quick migration? It saves the state of the VM, moves it
>> > to
>> > another host, and then resumes it.
>> >
>> > Does this result in data synchronization issues between domain
>> > controllers?
>> >
>> > Are there any MS documents or articles discussing this scenario? Best
>> > match
>> > I could find was about Virtual Server 2005, but I am particularly
>> > interested
>> > in the quick migration part of Hyper-V.
>> >
>> > Thank you.
>>