End of Day 2 as a Infrastructure Engineer

On Monday, I started a new job.
I had been preparing for the new job by researching DevOps, ITIL and the like.
From the conversations I'd had with my boss, he was very keen on the whole agile methodology and that's where I made an assumption.
I assumed that that would be the method in place. I was wrong.
After two days, I have realised that this is a broken team. Like, properly broken.
The Infrastructure is a mess. It's mis-matched, there is very little resiliency, many single points of failure, there is little-to-no-backup and what little documentation that exists is 5 years old and incomplete.
I have realised there is a lot of work to do. I am starting with network monitoring because there is none. I'm also going to be advocating a who new backup system.

On the plus side, budget doesn't seem to be tightly regulated, or indeed particularly planned.
My boss copied and pasted a PO that a colleague had made in order to fashion me with a workstation. It turns out that order was test rig for a designer.
Its has :

• 8 core Xeon processor
• 32GB of RAM
• 2 120GB SSDs (one M2 straight on the board and a kingston from stores)
• 1TB WD blue

and last but by no means least

• 2 27" HP monitors

They're fucking huge, but I'm rocking 1080 on both sides. :-)

I installed the hyper-V role on the windows 10 pro build that was handed to me on a flash drive (build 1603, so it took most of the date to get updated) and proceeded to get the virtual switch working.
Normally this is a trivial task, but this time around it would not play ball.
After I realised that the virtual adapter disables IPv4 on the NIC, windows 10 once again got an IP leased, but the virtual switch would not allow the guests access to to the external network.I'll tinker with it more tomorrow.

I know, it's been literally ages.