@scottalanmiller best to just replace they are so cheep, but no idea if you can get one in Kiev

Planning a hike today with the boys, or as the older one calls it, a mud walk

My coffee's almost gone already

I am on as well

We are running CRM 2011 on prem and looking to upgrade to both on prem and 365 (I guess both products are now called 365). As always I'm not the official "lead" on the project but it has landed on my platter of things to do.

Was that the ti 99 and the xt expansion unit? That was my first "PC"

Avoiding every site today except ML

Microsoft is no longer providing a USB install guide for HyperV 2016. I did get it working with 2012 for a while but the lab server died a horrible death so waiting for a new server to hit the junk pile

We use Mimecast for our filtering needs. Works with on prem and o365, though we are still on prem right now.

@NerdyDad thats how our colo is. The rent includes security (keycard access to DC, combiantion access to rack), rack, power feed, and Internet. Oh, and basic PDU's. We wanted more advanced PDU's (remote management and monitoring) which we could either lease from them or buy ourselves.

Having just completed our move a couple pointers:

1. Diagram your ideal layout, even if its a "stick Figure" drawing have some sort of guide
2. LENGTH OF POWERCABLES: Our power cables were WAY WAY WAY too long requiring us to do a lot of routing and rerouting, which in turn caused the back of the rack to be somewhat blocked which limits airflow. We are going to be purchasing short (2 and 3ft) lengths and redoing all the power.
3. LENGTH OF NETWORK CABLES: 6ft were too short in some cases, and 10FT were too long. We had to use more cable management which ends up wasting 2U of space. If you can, use some string and a tape measure on your existing racks to get an idea of how much length you'll need.
4. LABEL LABEL LABEL: In an ideal word, you put your stuff in the rack and never come back unless something breaks or its time to move to a new facility. Of course you are going to remember exactly what you did when you installed everything so when you come back 2 years later you remember exactly why that 1 server is in a separate switch port from the others. Take the time now to plan, and when installing label everything you can. This took a big chunk of our move window but will be worth it as I will be able to look and see which server that blue network cables goes to.

@brianlittlejohn That's what I use, I have a coupel Fios routers I picked up and use strictly as a MOCA bridge

There used to be something called Long Range Ethernet designed to provide 10-15Mbit connections over cat-3 phone wire. Doubt you can get much faster over any sort of phone cable. You might be able to use something like this but its expensive:
https://www.amazon.com/StarTech-com-VDSL2-Ethernet-Extender-Single/dp/B002CLKFTG

Moving the companies servers to a colocation facility this Sat. woohoo!

Prepping for our companies big move to colocation on Sat.

Verify that the dimensions of the rack you are getting will hold your equipment!! We are running into an issue with our colocation facility where 2 of our older Dell's rails are deeper that the edge of the mounting rail and that smack right into the PDU's. If you need extended depth be sure to ask for it and GET IT IN WRITING ON THE CONTRACT before you sign.
That having been said, we are using Centrilogic for our colocation facility in Buffalo and they have been very accommodating even with our depth issue. They have 3 data centers in the GTA including Mississauga. I can get you contact info if you want it.

@dafyre My apologies, you are correct ipconfig /flushdns is client cache only.

Windows Server in powershell is Clear-DnsServerCache

@scottalanmiller ipconfig /flushdns should do it I think

Stomach flu has struck Both boys and myself down for the count