Getting ready for a test run

On October 20, 2014, in news, by susan

Getting ready for a migration at the office from the 2008 R2 era HyperV to a 2012 R2 era hyperV

iphone 064

And as the server sounds like a jet engine taking off…

it always makes me laugh how small the drives are, and how big the unit it

iphone 065

Makes ya wanna buy more hard drives and fill that sucker up.

So one of the things I’m doing this time is rather than doing a router in front of the server to separate out from the production network, I’m trying a virtual router

Fastvue Sophos Reporter How to Deploy Sophos UTM on Hyper-V in 7 Simple Steps:

So far it’s not as simple as that leads one to think it is.  I obviously have networking/binding to the nics mucked up because it won’t find the web console address.

I’ll try again tomorrow and let you know how I get along with a virtual router.



5 Responses to Getting ready for a test run

  1. JamesH says:

    I deployed a Sophos UTM hardware device recently and I have been very impressed by the UTM interface and the granularity of what you can do. The SSL VPN was so easy to set up, as were the integration of Sophos wifi Access Points…

    Fingers cross you can get it up and running – you shouldn’t be disappointed when you do.

  2. JamesH says:

    Forgot to mention however, that currently active directory integration of the UTM does not work properly with Server 2012R2 – due to the change to SMB2/3. The UTM currently only supports SMB1 so you have to enable SMB1 on Server 2012R2 I believe.

  3. I know this sounds stupid, but you did make sure to assign a static IP address for the client? Sophos UTM doesn’t configure a DHCP server by default, so you need to do that.

    And glad to hear you’re using Sophos, it really is a very nice UTM/router platform.

  4. Arne says:

    I’ve been using Sophos UTM since it was Astaro, I don’t use it as a firewall, just as a SMTP virus/spam filter and it works very nicely on hyper-v

    LDAP user authentication works “out of the box” with Windows Domain controllers, including 2012r2

  5. Paul says:

    Ah Hyper-V 2012 R2… do yourself a favour…
    Build a 2012 R2, install Hyper-V, patch it (not necessary for the test). Back up the server using Windows server backup , restore the server from the backup, now try to back up the restored server again using Windows Server Backup….i’ll save you the hassle. it doesn’t work!

    Microsoft didn’t seem interested in this when I told them. we’ve stopped rolling our 2012 R2 hosts and instead we’re sticking with 2012 hosts.