The new server checks licenses, and authenticates, directly against the current software license repository, so synchronization is no longer required. That said, this will resolve the license expiration inconsistencies that people have been seeing. If there are problems I should be able to fix them quickly. So, if you see problems with your updates or fresh installs (like a missing server) in the next few hours, feel free to drop me a note here on this forum post. This shouldn't adversely effect anyone, and no one should notice any downtime (DNS should have time to propagate while I go eat dinner, and then I'm heading to the data center to perform some upgrades on the old server before putting it back into service as a mirror of the new repo server).īut, because we've been juggling a lot of eggs this week, and I've gotten confused more than once about the order of things needing to happen in order to avoid downtime (it's been a while since I was doing daily server migrations.the skills get a little rusty), so I wouldn't be surprised if something goes wonky with this, as well. Because our week has not been exciting enough with fun new bugs and confusing license problems, I'm moving our software repositories (,, , ) to a new server.
