I've actually had an experienced PFE tell me there is no reason to run that arg in production unless you have a "really good reason and know exactly what you are doing"
-----Original Message----- From: Webster [mailto:[email protected]] Sent: Thursday, December 13, 2012 2:11 PM To: NT System Admin Issues Subject: RE: DNS/Replication broken after MS updates? Why are you having to force replication between all domain controllers? Find and fix what is broken. Thanks Webster > -----Original Message----- > From: Phil Hershey [mailto:[email protected]] > Subject: RE: DNS/Replication broken after MS updates? > > Ah, but what tipped me off is definitely not normal. I have a batch > file that runs a series of REPADMIN /SYNCALL commands to force > replication between all the DCs. It hasn't thrown an error in > literally years, and normally takes about 5 seconds to complete. No > every single server coughs up the RPC Server is unavailable error. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin PG&E is committed to protecting our customers' privacy. To learn more, please visit http://www.pge.com/about/company/privacy/customer/ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
