Alternately, if your networking team cannot stretch the old subnet to your main data center, you could assign the moved servers new IP addresses and then add those addresses to the subnet list and indicate they are in the remote site. Remember, if and IP address is covered by more than one subnet, the more specific subnet is the one that applies.
/jim ----- James Rupprecht IT Architect, Enterprise Systems KU Information Technology Phone: +1 785 864-0116 Skype/Email: [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Friday, December 1, 2017 1:22 PM To: [email protected] Subject: Re: [NTSysADM] Advice: physically moving a site, but not changing AD Site info ... I don't see any issues with doing that. You may want to (once everything is working as expected) add that subnet to the main data center site and do away with the old site. There's no reason to have intersite replication now that the moved DCs have good connectivity to the other DCs. Your remote users at least will have more up to date AD changes, even if they may now suffer from slower overall response from the file server and DCs. On Fri, Dec 1, 2017 at 11:07 AM, Michael Leone <[email protected]<mailto:[email protected]>> wrote: I'm pretty sure I know the answer, but I want to verify. I've got a remote site that is scheduled to be shut down for the day next week, for power issues (don't ask me, I don't own the building ...). Since this site is scheduled to be abandoned next month, the Powers That Be have decided that they want to move the servers out of that site, down to the main data center, on Wed. This means that when the building re-opens on Thu, all the employees who are still at that remote sitewill then log in to the servers across the WAN. <sigh> Now this site is also a Site in AD, with 4 subnets assigned. The servers that are moving are all only in 1 subnet (x.x.16.x), Got all that? So I think if we physically move the servers to the main datacenter, re-configure some switch ports there to be the .16 subnet. And everything should still Just Work ... by which I mean, the folks still out at the remote site can still login in to the domain, and access their file server, pretty much transparently. They're just going to be accessing their files long distance now, instead of locally. I don't need to do any AD or host reconfiguration, right? There is switch reconfigs to do (ports), but that should be on my networking guys, correct? Anything I can tell them to make sure they cover? This is all possible, right? And shouldn't be a big deal, presuming the connectivity all works? I am not a networking guy in any sense ... Thanks for any help. This just dropped into my lap when I came back in today. I thought we had until the end of Feb to prepare for this .... -- Charlie Sullivan Sr. Windows Systems Administrator Boston College 197 Foster St. Room 367 Brighton, MA 02135 617-552-4318
