I can be done, as I have done it for three systems. But, you can just build a new 2012-R2 box and transfer the VMs from one to the other.
While in-place Windows upgrades have gotten easier and more straightforward over time, I find that there are always little gotchas that crop up afterwards -- sometimes minor something more annoying than that. I'd opt for the latter (migrate to new host) for any non-home-network scenario. *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…* * GPG: *1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A On Wed, Sep 9, 2015 at 8:43 PM, J- P <[email protected]> wrote: > Hi all, > > I have 2012 hyper v host that houses pretty much all our servers > (excluding exchange, still have a physical exchange) > > I was wondering if anyone has any feedback, "watch-outs, gotchas , beware > of" for upgrading it to 2012 r2. > > All docs indicate its pretty straight forward, "easy and seamless" but I > wanted REAL WORLD feedback. > > Any and all comments, feedback ,opinions, would be greatly appreciated. > > > TIA > >
