That's what I hear - I just have never done that. Kurt
On Tue, Jul 7, 2015 at 6:20 PM, Webster <[email protected]> wrote: > Why make it a member of the domain. Unnecessary step. > > Thanks > > > Webster > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Tuesday, July 07, 2015 7:19 PM > To: ntsysadm > Subject: Re: [NTSysADM] In place 2008 R2 DC to 2012 DC > > Even, or perhaps especially, in the case where there's only one DC, just spin > up a new machine, make it a member of the domain, then promo it, then let it > replicate, then demote the old one. > > If you have a hardware dependency, get a spare desktop/laptop/whatever and > use that, then do it again on the old hardware. > > Upgrades in place give me the cold shivers. > > Kurt > > On Tue, Jul 7, 2015 at 4:55 PM, J- P <[email protected]> wrote: >> +10000 >> >> Why introduce more variables , and since they spin up so quick, why >> would you go that route? >> Unless of course there is no other DC >> >> >> Jean-Paul Natola >> >> >> >> ________________________________ >> Date: Tue, 7 Jul 2015 09:57:37 -0800 >> Subject: Re: [NTSysADM] In place 2008 R2 DC to 2012 DC >> From: [email protected] >> To: [email protected] >> >> If you have another DC in the environment, what is preventing you from >> demoting the DC in question, rebuilding as new, and promoting? >> >> - Sean >> >> On Tue, Jul 7, 2015 at 8:58 AM, Kennedy, Jim >> <[email protected]> >> wrote: >> >> Certainly asked, but no, not answered. >> >> The original question was: "Anyone done it this way, how did it go?" >> >> To date no one has said they did it, let alone how it went for them. >> So far just the prevailing opinion that it is a bad thing to do. As my >> boss said as we debated this, we are not on NT 4 anymore, it is a >> supported documented procedure from MS. >> >> ________________________________ >> From: [email protected] [[email protected]] >> on behalf of Free Jr., Bob [[email protected]] >> Sent: Tuesday, July 07, 2015 12:26 PM >> To: [email protected] >> Subject: RE: [NTSysADM] In place 2008 R2 DC to 2012 DC >> >> Or as you tell a 2 year old..."asked and answered" >> >> >> >> Nie mój cyrk, nie moje małpy >> >> >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of Webster >> Sent: Tuesday, July 07, 2015 6:21 AM >> To: [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]] >> On Behalf Of Jonathan Link >> Sent: Tuesday, July 07, 2015 8:01 AM >> To: [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]> 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]] >> On Behalf Of Jonathan Link >> Sent: 07 July 2015 13:08 >> To: [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]> wrote: >> >> Two done in place so far, no issues. >> >> >> >> DIFGTBAG >> >> >> >> On Thursday, July 2, 2015, Kennedy, Jim <[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 >> ______________________________________________________________________ >> >> >> >> ________________________________ >> PG&E is committed to protecting our customers' privacy. >> To learn more, please visit >> http://www.pge.com/about/company/privacy/customer/ >> ________________________________ >> >> > >
