Brian Desmond is on this list, so he can say with authority… But as I remember, within a site, replication is very quick. Outside of a site, except in cases of “emergency replication” (e.g., password changes) the minimum is still 15 minutes.
There are no issues other than the IP address change for DCs. That affects DNS and indirectly, clients trying to locate DCs. From: [email protected] [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Friday, September 11, 2015 3:36 PM To: [email protected] Subject: RE: [NTSysADM] DCs as DHCP Clients Interesting. So even in Azure that’s the default. I just set up the first DC at AWS a few minutes ago and got the warning that the non-static configuration could cause problems for DNS, but I suppose that could be for the obvious problem of the IP address changing. It isn’t that I’m worried about the IP address changing, since there is a reservation in DHCP for the DCs, but I thought it may cause problems other than an IP address change. Not to hijack my own thread, but while setting this up, I found that the lowest inter-site replication interval is still 15 minutes. These are Windows 2012 R2 DCs in domain/forest 2012 R2 functional mode. For some reason I thought it was possible to lower that to 5 minutes now. Thanks. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Michael B. Smith Sent: Friday, September 11, 2015 2:38 PM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] DCs as DHCP Clients I can’t speak to AWS but I do it in Azure. In Azure an IP address isn’t ever released/reassigned until you “Force Stop” a VM which causes the IP, memory and vProcs to be deallocated from the VM. (Azure also has other options – this is just the default.) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Friday, September 11, 2015 2:33 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] DCs as DHCP Clients Has anyone had to run domain controllers as DHCP clients? Someone from another one of our IT groups has provisioned some servers at AWS for Citrix and the proposal is to add a couple of DCs there. He says “All AWS instance should always be DHCP clients”. I think of this as a bad practice, but I would think that if it’s the standard at AWS, then lots of others are doing the same. So even better would be if I could hear from someone who does have DCs at AWS. I have cloned DCs in an isolated test network, which we regularly use for testing. I’ll be connecting those to the DCs I’m building at AWS for testing before even attempting this in production. Even if I have no problems in testing, I am leery to do this in prod. Charlie Sullivan Sr. Windows Systems Administrator
