Seriously, Given the potential (even if rare) downside to this, I would never consider it.
I'd also focus on the short sighted approach for which could lead to a business interruption and highlight that. In other words, so he wants to be lazy for like 5 minutes worth of work only to potentially impact business continuity? Now how does the idea sound? I know how I would respond to someone under my helm... jlc ________________________________ From: [email protected] <[email protected]> on behalf of Jonathan Raper <[email protected]> Sent: January 8, 2016 12:26 PM To: [email protected] Subject: [NTSysADM] In-place upgrade of a 2008 R2 DC to 2012 R2? Happy New Year to the collective! I know this has been supported since at least 2008....and sounds like it has improved with each iteration since. However, I am old school and have *never* been a fan of any kind of in-place upgrade. Further.... The very first sentence in Microsoft's TechNet article Upgrade Domain Controllers to Windows Server 2012 R2 and Windows Server 2012<https://technet.microsoft.com/en-us/library/hh994618.aspx#BKMK_UpgradeWorkflow> , updated less than a year ago: "The recommended way to upgrade a domain is to promote domain controllers that run newer versions of Windows Server and demote older domain controllers as needed. That method is preferable to upgrading the operating system of an existing domain controller." That being said, I've got an admin (junior to me) who seems to think it is a good idea (because he wants to cut a corner). I and another peer (also a senior engineer) disagree with him. Regardless, I'm curious if anyone here has tried this and if so what your experience was? Thanks, Jonathan
