He's referring to his own DC's. He's the OP, and is referring to himself. -- ME2
On Wed, Sep 16, 2009 at 10:21 AM, Chyka, Robert <bch...@medaille.edu> wrote: > Not necessarily. You have to manually make a DC a GC. > > > > Bob C. > > > ------------------------------ > > *From:* Ziots, Edward [mailto:ezi...@lifespan.org] > *Sent:* Wednesday, September 16, 2009 9:06 AM > > *To:* NT System Admin Issues > *Subject:* RE: Question on Upgrade process > > > > DC’s are GC’s… > > > > So there are plenty of those. > > > > Z > > > > Edward Ziots > > Network Engineer > > Lifespan Organization > > MCSE,MCSA,MCP+I, ME, CCA, Security +, Network + > > ezi...@lifespan.org > > Phone:401-639-3505 > ------------------------------ > > *From:* Ken Schaefer [mailto:k...@adopenstatic.com] > *Sent:* Wednesday, September 16, 2009 5:25 AM > *To:* NT System Admin Issues > *Subject:* RE: Question on Upgrade process > > > > I think that’s a decent plan. If you run into issues, DCpromo the problem > DC out of the environment, fix SP issues, and re-promote. I assume you have > a couple of GCs per domain. > > > > Cheers > > Ken > > > > *From:* Ziots, Edward [mailto:ezi...@lifespan.org] > *Sent:* Tuesday, 15 September 2009 10:03 PM > *To:* NT System Admin Issues > *Subject:* RE: Question on Upgrade process > > > > Thanks Brian there isn’t 100’s of DCs in this upgrade only like 8 total, > and only 3-4 hold the FSMO roles, (1 in the root) and 2 in the child domain. > > > > Basically just use the GUI or NTDSUTIL to transfer the roles, do a netdom > query fsmo to check to make sure it moved, and do the SP as usual. > > > > Z > > > > > > Edward Ziots > > Network Engineer > > Lifespan Organization > > MCSE,MCSA,MCP+I, ME, CCA, Security +, Network + > > ezi...@lifespan.org > > Phone:401-639-3505 > ------------------------------ > > *From:* Brian Desmond [mailto:br...@briandesmond.com] > *Sent:* Tuesday, September 15, 2009 7:42 AM > *To:* NT System Admin Issues > *Subject:* RE: Question on Upgrade process > > > > *I don’t typically do all that stuff as I’m often doing hundreds of DCs. > What I will do is move FSMO roles to an alternate before bouncing the role > owners.* > > * * > > *Thanks,* > > *Brian Desmond* > > *br...@briandesmond.com* > > * * > > *c - 312.731.3132* > > * * > > *From:* Ziots, Edward [mailto:ezi...@lifespan.org] > *Sent:* Tuesday, September 15, 2009 6:31 AM > *To:* NT System Admin Issues > *Subject:* Question on Upgrade process > > > > Just like to quickly bounce this off the list. > > > > I have a task to upgrade a set of Domain Controllers from Windows 2003 SP1, > to Windows 2003 SP2 accordingly. > > > > Do most of you do the DC’s without the FSMO roles, first, and then do > dcdiag, netdiag, and repadmin then do the servers with the FSMO roles > accordingly? Do you usually move your FSMO Roles before you upgrade the > machines accordingly? > > > > I haven’t seen any issues in the 100+ upgrades that have been done already > but given these are the DC’s just a little leery about replication issues, > failure of a role-server etc etc afterwards. > > > > Has anyone seen or experienced anything negative in there travels through > the SP upgrade route? > > > > Z > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
