8
aaxa
8y

Today I investigated how one could build a Windows 10 VM.
We have an Azure subscription in our company (which is expensive enough), which gives me access to their new interface where it looked like I could build a Windows 10 VM. I was so happy that MS actually made this feature for developers, until I got redirected to the MSDN front-page telling me that you would need ANOTHER FUCKING SUBSCRIPTION to do that. This is fucked up. You pay for access to Office 365, then you pay for Azure and THEN you pay for MSDN just to pay for another Windows 10 license so you can test a simple Azure feature on Windows 10. How about nope.

Comments
  • 1
    Ever since MSDN dropped Universal, it's been a train wreck for knowing what is available under license and what isn't. We ran into a similar problem with Hyper-V VM usage on bare metal WS2012-R2 machines and ended up spending close to $50K for proper licensing.
  • 1
    @JuniorMini Yep, it's just insane. We've just had a Microsoft Audit this weekend. I'm already prepared to work overtime.
  • 0
    @aaxa Yeah, we had ours at the end of November. Our sys admins were pulling 60-70 hour weeks with no OT to get everything licensed properly.

    I expect that in 2 years we will be back to square 1 again. lol
  • 0
    and you wonder why people suggest unix as a replacement
  • 1
    I'm in the process of trying to roll out a custom VM image on Azure. Holy fuck. The documentation is confusing, all over the place and missing the most important steps.

    Actual Azure Doc quote:
    "To do this you will need to setup a reverse proxy moon connection with extra flump.

    Now you've done that...."

    Wait what, how was I supposed to do the made up thing?
  • 0
    @booshi Azure documentation is not the only Microsoft documentation that are like that
Add Comment