Thanks. As an update, they've decided *not* to move the servers tomorrow, during the downtime at the site. They will stay, and be back up the next day, when the power people get down doing whatever it is that they are doing.
(which means all the users at that site are coming here. And logging in .. to no profile, as their profile is hosted on the server which will be powered off at the remote site. I foresee lots of fun and amusement ...) However, that site will close early next year, so I will have to move the file server and DC. I thought about collapsing down the subnets (and AD sites), but my networking guys don't want to do that, as they still need them for the telecom/VOIP system - don't ask me, I'm not following all that. If we don't change the subnets, then the networking guys have a ton of re-VLANing of ports to do, at the remaining site ... No doubt I will be writing again, when the move actually happens. What I'd really like, is to be able to move the DHCP services off the DC, and onto another server. But that may be scary, too, guess we'll find out ... On Fri, Dec 1, 2017 at 2:21 PM, Charles F Sullivan <[email protected]> wrote: > 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]> 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
