Does this include web servers? Our primary web server is still a 2012 box, and if we can just do an in-place upgrade that would be awesome.
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of David Lum > Sent: Thursday, September 10, 2015 6:12 AM > To: <[email protected]> > Subject: Re: [NTSysADM] 2012 to 2012r2 upgrade > > Crazy easy. 2012 to 2012 R2 is the first upgrade-in-place I'm comfortable > with. > I think I've done six or seven at this point. > > Dave Lum - [email protected] > > Sent from mobile device, please pardon the brevity. > > > On Sep 10, 2015, at 5:52 AM, Michael Leone <[email protected]> > wrote: > > > > I haven't done it to a Hyper-V server, but I did do it to 3 RDS > > (Remote Desktop Services) servers. Worked as advertised, no drama, > > quick and simple. Those 3 servers now have about 60 users spread > > across them, running a front end to a database application. > > > > You will end up with a "windows.old" directory, that has all the old > > (non-R2) system files in it. You can remove that with CleanMgr, I > > believe. > > > > > >> 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 > > > > >
