Also, the documentation for Windows Server 2003 Service Pack 1 at http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/BookofSP1/658a175c-486a-42ee-b3da-9b56de3d187c.mspx states:
Support for running domain controllers in
virtual machines
On a single physical server that is r
I
wondered that too and checked with Robert who sent my query on to a chap
named Jan Liikamaa. He said:
Unfortunately our product does
not handle different account lockout policies. But I agree that it would be very nice
to be able to specify different set of account lockout
rules
I've looked at using Virtual Server for small sites and it makes sense
to me. The only drawback is that all your eggs are in one basket - lose
the host and you lose everything. The same's true for patching as
you'll need downtime on all of the guest machines when the host is
updated.
One nice
We had a pretty inefficient model for small site deployment, so we
recently revamped it to the one mentioned below. So far, the DC-less
sites have been quite small, no more than 10 users. However, I'd be
comfortable letting that go up as far as 100 or so users - but we do
have very good WAN conn
I'm not an expert on OWA, but as you mentioned in the first part of your
message the DC performs the check against the PDC to see if the password
has been changed. So long as OWA is using a DC to authenticate a user,
which I'm assuming it does, then the DC will handle the PDC check
invisibly.
Th
