Perhaps, but it’s been > 1yr since I upgraded some of these and fortunately it’s not something I do with any frequency. I still prefer to stand up new and migrate over vs. upgrade in place.
I do know of an issue where 2012 R2 breaks something that works fine with 2012 R0: ADFS. As in, depending on how ADFS is leveraged, R2 handles it differently than R0 does. I know this because at %dayjob% we have a fairly sizable application that uses ADFS and the vendor that supports it explained that R2 breaks it….this after troubleshooting why a new 2012 R2 (not upgraded) server doesn’t work for hosting this app while all the other servers (at R0) work just fine. “I built a new server but we can’t get your app to run…yes it has 2012…yes 2012 R2…oh, that won’t work?”. Google-Fu “2012 R2 ADFS changes” and you’ll get a slew of hits, <long rant about the quality of application we use that leverages ADFS omitted for brevity>. Dave From: [email protected] [mailto:[email protected]] On Behalf Of Andrew S. Baker Sent: Tuesday, July 07, 2015 9:45 AM To: ntsysadm Subject: Re: [NTSysADM] In place 2008 R2 DC to 2012 DC >> All without issue ... Without *immediate* issue, anyway. Somehow, I suspect that this thought will be at the forefront of many minds, upon subsequent inquiries that you pose regarding 2012-R2. ASB http://XeeMe.com/AndrewBaker<http://xeeme.com/AndrewBaker> Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market… On Tue, Jul 7, 2015 at 11:49 AM, Michael Leone <[email protected]<mailto:[email protected]>> wrote: On Tue, Jul 7, 2015 at 11:21 AM, Dave Lum <[email protected]<mailto:[email protected]>> wrote: > On a slightly different but related front, I have upgraded Server 2012 to > 2012 R2 in-place a few times and that’s a total non-issue. I didn’t do that > to any DC’s though… I did that to 4 RDS servers. And my boss did it to 2 SQL servers. All without issue ... > > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Webster > Sent: Tuesday, July 07, 2015 6:21 AM > To: [email protected]<mailto:[email protected]> > Subject: RE: [NTSysADM] In place 2008 R2 DC to 2012 DC > > > > I am with you on that. > > > > Just asking for trouble. > > > > Thanks > > > > > > Webster > > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Jonathan Link > Sent: Tuesday, July 07, 2015 8:01 AM > To: [email protected]<mailto:[email protected]> > Subject: Re: [NTSysADM] In place 2008 R2 DC to 2012 DC > > > > /shakes head and walks away. > > On Tuesday, July 7, 2015, Gavin Wilby > <[email protected]<mailto:[email protected]>> wrote: > > To try and buy some time, I am also considering an inplace upgrade of one of > my DC’s from 2003 standard to 2008 standard (32bit). > > > > As below, anything to watch for? > > > > Gavin Wilby > > IT Support Engineer > > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Jonathan Link > Sent: 07 July 2015 13:08 > To: [email protected]<mailto:[email protected]> > Subject: Re: [NTSysADM] In place 2008 R2 DC to 2012 DC > > > > Less gangster, more thug. You are just brute forcing something that ought > not be brute forced. Good luck. And kids, don't try this at home. > > On Tuesday, July 7, 2015, Kennedy, Jim > <[email protected]<mailto:[email protected]>> wrote: > > Two done in place so far, no issues. > > > > DIFGTBAG > > > > On Thursday, July 2, 2015, Kennedy, Jim > <[email protected]<mailto:[email protected]>> > wrote: > > I know, don’t do it….migrate. > > But I am going for it, the boxes are pretty fresh with rock solid hardware. > I have no nagging event log issues or issues with the DC’s. I have a 2012 DC > on a VM in the same room if it goes bad. They only do DC stuff no other > crazy apps on them. My domain is very flat and simple…..it’s summer time > there are only 75 people tops working and they are all cool if it gets > annoying. > > Anyone done it this way, how did it go? > > No, not doing it today, don’t want to mess up the holiday weekend. > > SMP Partners Limited, SMP Trustees Limited and SMP Fund Services Limited are > licensed by the Isle of Man Financial Supervision Commission. SMP Accounting > & Tax Limited is a member of the ICAEW Practice Assurance Scheme. > > SMP Partners Limited registered in the Isle of Man, Company Registration No: > 000908V > Directors: M.W. Denton, M.J. Derbyshire, S.E McGowan, O. Peck, J.J. Scott, > S.J. Turner > > SMP Trustees Limited registered in the Isle of Man, Company Registration No: > 068396C > Directors: A.C. Baggesen, M.W. Denton, O. Peck, J.J. Scott, J. Watterson, J. > Cubbon > > SMP Fund Services Limited registered in the Isle of Man, Company > Registration No: 120288C > Directors: V. Campbell, M.W. Denton, D.A. Manser, S.E McGowan, J.J. Scott, > R.K. Corkill > > SMP Accounting & Tax Limited registered in the Isle of Man, Company > Registration No: 001316V > Directors: I.F. Begley, A.J. Dowling, P. Duchars, J.J. Scott, S.J. Turner > > SMP Capital Markets Limited registered in the Isle of Man, Company > Registration No: 002438V > Directors: M.W. Denton, M.J. Derbyshire, D.F Hudson, S.E McGowan, O. Peck, > J.J. Scott. > > SMP Partners Limited, SMP Trustees Limited, SMP Fund Services Limited, SMP > Accounting & Tax Limited and SMP Capital Markets Limited are members of the > SMP Partners Group of Companies. > > This email is confidential and is subject to disclaimers. Details can be > found at: http://www.smppartners.com/disclaimer.html > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > Attention: Information contained in this message and or attachments is > intended only for the recipient(s) named above and may contain confidential > and or privileged material that is protected under State or Federal law. If > you are not the intended recipient, any disclosure, copying, distribution or > action taken on it is prohibited. If you believe you have received this > email in error, please contact the sender, delete this email and destroy all > copies. Attention: Information contained in this message and or attachments is intended only for the recipient(s) named above and may contain confidential and or privileged material that is protected under State or Federal law. If you are not the intended recipient, any disclosure, copying, distribution or action taken on it is prohibited. If you believe you have received this email in error, please contact the sender, delete this email and destroy all copies.
