I need to read my own blog more often…

I need to read my own blog more often…

  • Comments 4

Over the last couple of weeks I have been playing around with some new (for me) server technology.  This has been a lot of fun – and I have been learning a lot.  However, a couple of days ago things started to go wrong.

Specifically I started seeing all sorts of strange problems with my Hyper-V server.  Virtual machines started going offline randomly.  The whole system would go unresponsive for a couple of minutes and then come back.  Once or twice the management operating system stopped responding, while virtual machines continued to respond over the network.

This was concerning to say the least.

However, as I have been busy this week I did not have time to investigate properly.  After three nights dealing with this behavior, I was starting to wonder if I had some failing hardware, and was thinking about what I would need to do over the weekend to track down the cause of the problem.

Then - as I was driving home yesterday – I suddenly realized what the problem was.  Last weekend I had setup a login script for my domain that would install antivirus automatically on any domain-joined computer that did not have antivirus on it already.  When I got home I checked – and there it was.  I setup exclusions for Hyper-V and my server has been rock solid ever since.

Now, why am I feeling quite foolish to recount this story?  Apart from the obvious fact that it took me days to figure out what the problem was – I have already blogged about this exact problemTwice.



Leave a Comment
  • Please add 2 and 8 and type the answer here:
  • Post
  • It's reassuring to know that even a master has the occasional lapse :-)

    For reasons such as this that I hate AV on the parent partition.  There are too many opportunities for AV updates/upgrades or operator error to mess things up.  

    Haven't looked At ForeFront yet - but I guess the exclusions are built-in and automated?

  • I've just installed AV on parent partition checking file operations only. May be just one file system mini-filter driver doesn't bother Hyper-V at all. As far as I have seen .vhd disks are used solely by Hyper-V when VM is operating and are not checked. May be not all AVs behaves the same, but steps Ben mentioned in his forgotten blog post ;) could do it for you.

  • At least you solved it.

    By the way, is there any chance to see that script?

    So we can all learn.


  • Aidan Finn -

    ForeFront does not have automatic exceptions at this point in time - but we are working on getting this in place.

    Percu -

    I will see if I can share the script at another time...



Page 1 of 1 (4 items)