tag:blogger.com,1999:blog-5976686513564131325.post8572937004952164008..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: SBS 2003 to 2008 Migration – DCPromo Fails – The wait operation timed outPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-5976686513564131325.post-64444571264132947122011-10-30T21:03:37.029-06:002011-10-30T21:03:37.029-06:00Wicked guys - thanks so much - you rock and you sa...Wicked guys - thanks so much - you rock and you saved us a huge headache!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-30970357515021268472011-10-13T06:57:17.310-06:002011-10-13T06:57:17.310-06:00Another vote for changing the DNS on the network a...Another vote for changing the DNS on the network adapter to point to the new DC before demotionAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-24729154410596671612011-04-20T15:03:33.324-06:002011-04-20T15:03:33.324-06:00Thank you so much for sharing this tip with everyb...Thank you so much for sharing this tip with everybody! I saved me from wasting hours of troubleshooting!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-54948869097117457682010-06-02T06:01:49.486-06:002010-06-02T06:01:49.486-06:00Amazing, life saverAmazing, life saverAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-67268510875094604282010-04-20T16:37:46.835-06:002010-04-20T16:37:46.835-06:00This is a catch 22 scenario. Point the DNS of this...This is a catch 22 scenario. Point the DNS of this server to another AD server before demoting this one. The server timed out because it couldn't locate another AD server to complete the demotion.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-32365070497262590352010-04-12T20:24:34.341-06:002010-04-12T20:24:34.341-06:00thanks heaps - also had a "oh cr@#" mome...thanks heaps - also had a "oh cr@#" moment... ! Thanks MSAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-26082440370856624232010-01-12T07:26:48.521-07:002010-01-12T07:26:48.521-07:00Great find!. Thanks helped me too.Great find!. Thanks helped me too.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-39628135836574907212009-12-30T22:18:28.914-07:002009-12-30T22:18:28.914-07:00Just had the same problem - and same fix. Thanks. ...Just had the same problem - and same fix. Thanks. <br /><br />It would be nice if Microsoft could tell us what could cause this .......Michael Greenhttp://www.solventgreen.comnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-23730206200420710772009-11-16T04:01:20.075-07:002009-11-16T04:01:20.075-07:00Thanks for the info, I also had a cold moment when...Thanks for the info, I also had a cold moment when the error first appeared. On the second run all seems to be runnig ok now.<br /><br />Nice One! :o)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-63811988064186035812009-11-07T20:29:02.108-07:002009-11-07T20:29:02.108-07:00Im sitting here after 2 days and I am tired. You h...Im sitting here after 2 days and I am tired. You helped me from having my first heart attack :)<br />God Bless and thank youAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-13024286450162508782009-07-01T13:37:40.629-06:002009-07-01T13:37:40.629-06:00We also had first round error and had to run dcpro...We also had first round error and had to run dcpromo a second time to have it complete the demotion successfully. Thanks for the tip! (again)Tim Barthelmanhttps://www.blogger.com/profile/09179396650316731483noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-13237833098905903822009-06-25T12:32:03.464-06:002009-06-25T12:32:03.464-06:00Amazing! I think this should make it into the mig...Amazing! I think this should make it into the migration document to prevent IT folks from disconnecting the Server before it has been fully removed from AD. Completely ridiculous! We saw this error as well and re-ran the process successfully. Thanks for the help.<br />-ScottMickelsonshttps://www.blogger.com/profile/13601686427626574934noreply@blogger.com